BIOS damage

I Have a G 62-340us
Serial number  CNF044CGBP
Product number  XH066UA
Warranty status  Warranty has expired
Warranty end date  2011-12-17 (YYYY-MM-DD)
the computer dont start windows 7 load,  because i think the BIOS sotfware is damage,
only found http://h10025.www1.hp.com/ewfrf/wc/previousVersions?softwareitem=ob-93590-1&cc=us&dlc=en&lc=en&os=40...= this only in 7 normal use.
I want updated bios from usb pendrive or cd boot.
could you give me a link to get this BIN image or creator boot disk to update bios?

Hello AlejandroMP
I am sorry to hear that you are having the blinking lights. I am providing you with a link to an HP Support document here titled Blank Screen LED Error Codes that I think you should follow. The issue you have indicated is a BIOS corruption failure and there are steps that may rectify the error.
I hope this helps you to resolve your issue. Thank you for posting on the HP Forums. Have a great day!
Please click the "Thumbs Up" on the bottom right of this post to say thank you if you appreciate the support I provide!
Also be sure to mark my post as “Accept as Solution" if you feel my post solved your issue, it will help others who face the same challenge find the same solution.
Dunidar
I work on behalf of HP
Find out a bit more about me by checking out my profile!
"Customers don’t expect you to be perfect. They do expect you to fix things when they go wrong." ~ Donald Porter

Similar Messages

  • Portege M100 Bios damaged

    Hi,
    yesterday i turned off my M100 by holding the power switch while it starts. Since the the power LED blinks orange when I turn it on and nothing else happens.
    I read that this means, that the BIOS is damaged.
    Is there a way to fix that or is this really the end of my little M100?
    Thanks.

    Hi!
    You should try this at first: Remove the battery and AC/DC adaptor, wait up to one hour and then connect the battery and the AC/DC adaptor. Now you can try it again.
    In worst case the mainboard must be replaced. For this you can go to an authorized service provider.
    Bye

  • Bios damage due to heat

    How can i replace bios on my note book pavilion g4 series
    .i turn off laptop normally and when i restart it . It dosnt start ,then i go to hp web site for this solution ,i compare it, when i start note book it shows two time caps LED blink and wifi led permanant on .so i try to updat it by pressing button power key andB and windows key but not successful. So please give me any idea to solve this problem.thanks

    Hi @bilalzaidi1 
    Welcome to the HP Support Forums!
    I am happy to help you with your BIOS problem, but I need to know the exact version of your notebook. Pavilion G4 is part of a series with many variations.  Please read the following documents if you need help in finding those.
    How Do I Find My Model Number or Product Number?
    Is the Windows Version on My Computer 32-bit or 64-bit?
    The following has instructions on restoring the BIOS, I realize that you have already tried WIndows+B, but there are instructions on how to restore from an external device as well.
    Restoring the BIOS
    Computer Does Not Start and the LEDs Blink or the Computer Beeps
    If you cannot make any headway with this then you may have to call technical phone support at 800-474-6836. If you live outside the US/Canada Region, please click the link below to get the support number for your region.
    http://www8.hp.com/us/en/contact-hp/ww-phone-assist.html
    Malygris1
    I work on behalf of HP
    Please click Accept as Solution if you feel my post solved your issue, it will help others find the solution.
    Click Kudos Thumbs Up on the right to say “Thanks” for helping!

  • Z77A-GD65 ram and DR. mos problem after 2 years without any HW change or OC!

    Hi guys, i have three Z77A-GD65 from 2 years with the same hardware config, no overclock or others OC settings ....simply default bios settings;  in this last 2 months, not at the same time, all of my 3 mainboards  have the same identical problem.
    One day, from nowhere, without any reason, i start my pc and mobo don't start, hangs with code 55 ( memory error) and Dr mos alarm led goes on, i try to reset bios .. nothing.
    I Switch multibios to "B" bios and works perfectly .. i've tested all of RAM modules and result works perfectly !! .... all of three mainboards have the same identical problem!!
    Now i use all my 3 PCs with "B" bios and works perfectly, because "A" bios hangs always with code 55 and with Dr. mos alarm led on, i try to update and downgrade "A" bios ... nothing to do ... "A" bios don't work anymore.
    Any idea?

    Quote from: Nichrome on 19-July-14, 02:32:51
    Don't have to be rude 
    If same problem is on 3 motherboards then is something wrong with RAM or BIOS not the motherboard
    >>Posting Guide<< Reminding again if you want to receive any help.
    Nichrome, you misunderstood! ... I just responded to your affirmation .. that's all, it was not my intention to was "rude" as you wrote! OK? 
    Ram  modules have been tested on other Asus mainboard  .. .. no read/write errors and no hangs problems ... so all Ram modules are fine
    About bios ..... maybe primary bios is physically damaged.... i try to reflash bios also with old version .. no way .. maybe primary bios damage in all 3 mainboards  !! very strange!!! ... you know if there's a know manufacturing defect on this MB bios maybe on a particular MB serial part number? because i bought all 3 mainboards at same time about 2 years ago.
    Quote from: Sea Dog on 19-July-14, 02:40:52
    Obviously, there is 'something' that has caused BIOS corruption in all 3 mainboards A chips. Whatever that 'something' is, it may happen to the backup B chips as well. Recommend to concentrate on finding this 'something', what the common denominator is, and restoring BIOS chips A before the mainboards may become expensive paperweights. A shop with an SPI flash programmer device can fix the broken BIOS chips if not comfortable with doing the recovery procedure yourself.
    Hi, yes i agree,  In fact, my fear is to have, in a while, these mainboard totally unusable!  ..... i think that primary bios is physically damaged or i hope, software damaged, I would try to recover it,  if it's only a software problem (i hope so) ... do you know a procedure to completely erase cleanly that reflash the primary bios? i try to use dos MSI flash utility with "/p /b /n" options .. no success to restore A bios ... same story ... error 55 and DR-mos alarm led on.

  • Equium M50-164: Question about Fan usage & battery timer

    Hi !!
    Just got hold of my equium m50-164 laptop today and I wanted to clarify a few issues
    firstly,
    I flashed my bios with the latest version and upon the reboot the fan kicked in at full power and didn't turn off until i put the laptop into standby mode, this seemed to of rectified the problem but the fan seems to be kicking in a lot more than compared to before, luckily the fan isn't kicking into 100% speed but more like 15% - 20% every 30 secs or a minute then goes into silent mode, the fan hasn't hit 100% unless i do a reboot :),
    I know the fan will speed faster based on the cpu usage etc (thermal) but is this normal? I spoke to support and they wanted me to have an instant replacement but I said I would wait a few days to see if it would calm down :)
    and finally looking at the power meter and other software tools there seems to be no battery calibration, with previous laptops i noticed that numerical calculations are made based on battery usage and time left [i.e a timer] but with this laptop i kind find a timer - i would of thought tha every laptop has this facility nowadays !
    any advice would be helpful
    cheers
    Ephid0r UK

    Hi
    Please dont be mad on me but I really dont understood why your first step is BIOS update. The unit is delivered with actual BIOS and it is really not necessary to make it before you notice some problems. I just hope that you have enough experience with it because I have read a few postings on this forum about BIOS damage while BIOS update and to make it good again costs a lot of money.
    Your BIOS is updated and there are new values that should be used by Power saver utility (responsible for cooling fan monitoring). I recommend you to remove preinstalled power saver, restart the unit and install it again. I hope that the result will be better.
    Battery calibration I dont know what you want exactly but the battery usage can be control by power saver tool. On the task bar there is symbol for power saver and if you move the mouse pointer on it the battery capacity and left time will be shown.

  • MSI Z68A-GD80 (B3) problem with m4 128 GB

    One week ago, I bought m4 SSD 128 GB, installed win7 system, the firmware upgrade done from 002 to 009, and then upgrade the motherboard BIOS MSI Z68A-GD80 (B3). Received a message that "Missing operating system" and since then the BIOS does not detect SSD m4. I tried all the SATA connectors on the motherboard, without effect. Can update the BIOS damaged SSD? Any ideas? Help: (( Thanks George

    so I took out the batteries and waited half an hour. Upgraded the BIOS files on the USB. When first installed win7 is SSD, plugged in, there were two HDDs (1TB Hitachi + Seagate 200GB) On the first drive (Hitachi 1TB), was the system partition with win7. Then I tried to install the system, a message ...." Appeared Setup was unable to create a new system partition or locate an existing system partition. See the Setup log files for more information. "After changing the BIOS boot drive is That Appears the message "Bootmgr Is Missing"

  • I get a message - BIOS block 1 is damaged, please call your service

    Hi !
    I have this message "BIOS block 1 is damaged, please call your serviceman" when i start my PC...
    What does it mean ?
    TX

    Hi,
    Check the Toshiba Website and search a new Bios Update for your Model. Maybe is this the Problem.
    By

  • BIOS (Block 1) damaged - Satellite Pro 6000 - WinXP

    Hi there,
    I've tried to update my BIOS from Version 1.3 to 1.6. During that process my child pressed the power button. The result is: I'm not able to start the machine. It asks me for a maintenance disk, because BIOS (Block 1) is damaged. I do not have any maintenance disks, only some recovery CD's. They do not work and there are no *.rom files on them.
    So, what can I do? Thanks in advance for your answers!
    Mac

    Dear Marcus,
    I believe you are right now living the nightmare of every BIOS/PHONE/CD-DRIVE/YOU-NAME-IT flashing person. As you are already aware about, it's never good to get either a wrong BIOS or a Power loss during this procedure.
    Every newer BIOS has a protection mechanism which means that even in case of an incomplete flashing procedure, the responsible area in the BIOS-flash for the upgrade is NEVER DELETED. This means, that you can still upload a firmware on your BIOS although the procedure went wrong the previous time.
    Usually this "emergency flash program" will run automatically out of the BIOS when you turn on your Laptop, and will search for a *.ROM file on your floppy drive. The floppy disk does not need to be a bootable one, just it should include this one required file.
    I assume, that the necessary .rom file is the same .bin file, that comes with your regular BIOS upgrade... just renamed into the extension .rom but since I can not take the risk of providing you with wrong information, I would suggest you to have your Notebook repaired by an authorized Toshiba service provider.
    There are just TOO MANY things that can get wrong, especially if this is the last "easy" way (without hardware exchange) to get your laptop running again after a failed BIOS update.
    Regards,
    electrochain

  • Linux Install (Opensuse 12.2) damage Bios in Lenovo G480

    Hello,
    Actually I bought the Lenovo G480. Once Opensuse 12.2 was Installed, for some reason i cant enter to the Bios with F2... if I try with F12 show a lot of times "opensuse" and at last the Ethernet, HD and CD for boot.
    I cant find the bios for this model,
    Can you help me please? Sorry for my english Im Chilean
    Thanks

    Hi
    Welcome To Lenovo Community
    We are really sorry to hear about the issue you are facing,  
    You'll want to run these commands in the command prompt provided on the install disc: 
    bootrec.exe /fixmbr 
    bootrec.exe /rebuildbcd 
    After that check
    Do give this a try and let us know  
    Hope This Helps
    Cheers!!!
    WW Social Media
    Important Note: If you need help, post your question in the forum, and include your system type, model number and OS. Do not post your serial number.
    Did someone help you today? Press the star on the left to thank them with a Kudo!
    If you find a post helpful and it answers your question, please mark it as an "Accepted Solution"!
    Follow @LenovoForums on Twitter!
    How to send a private message? --> Check out this article.
                            English Community   Deutsche Community   Comunidad en Español

  • Damaged BIOS on Tecra M5

    inadvertently I updated my BIOS to an older version 1.60, I downloaded the wrong version and now the laptop wont boot up at all, it will power up, screen blank, and the fan is constantly on, that's it.
    I Rang Toshiba, they said BIOS updates are not covered by the warranty. I will have to take it to a Toshiba service provider and it could be a simple (1) cheap bios replacement or (2) expensive system board replacement.
    Does anyone has any experience with this issue before and could offer any advice?
    Thanks

    Doesn't look to promising, but don't give up yet. I will give you an option, that "might" work to get your system back running without need from the service center. I can not guarantee that it will work for your model, as this procedure is different for each BIOS brand and also I don't know in what condition the current installed firmware is.
    Tools you will need:
    = External Floppy drive (USB Floppy drive unless your notebook has an installed 3.5 drive)
    = A formated 3.5 Floppy disk (not a bootable one, just a plain formated disk)
    = The !!correct!! firmware for your model (uncompressed without the flasher software)
    = A working computer to prepare the BIOS emergency upgrade disk
    = Some nerves and Luck ;)
    Ok, now that you have gathered all the required tools from above, we will create a "BIOS image Disk for DOS" with the normal "BIOS update utility" downloaded from Toshiba's BIOS download section for your notebook. It is listed there as the Traditional Bios Update for Tecra M5 (PTM50) or Traditional Bios Update for Tecra M5 (PTM51). Make sure to download the correct model (PTM50??? PTM51??? check this on your notebook}
    Let's move to the next step: You should let that tool create the "bootable BIOS update Disk" so we can afterwards extract the required file from that disk to use on OUR EMERGENCY Bios upgrade disk.
    Once you have this disk ready, you will have to list the directory and search for a file with a .bin extension. This is the firmware file we will need for our project. Do not accidentally use a different file type like an .exe or .txt file.... those are wrong and might mess up the BIOS if used instead of the correct .bin file. (in some cases the correct file is something else than a .bin, it could also be i.e. a file named flash.hex)
    Ok, let's assume you found that file and it's name is something like (example only) "Bios320flashfile.bin". Copy this file on an empty, formated floppy disk and rename it into BIOS.ROM .
    Once you have this NEW disk ready, you can start to "pray" it will work as an Emergency BIOS repair disk. Just insert that disk into the external floppy drive of your "non working" notebook and let the Floppy boot (keep the U key pressed during startup). If you are lucky, the upgrade process will start and repair your notebook.
    This guide is meant to describe the procedure of an emergency repair after a failed BIOS upgrade. I can not assure you it will work for your case, but there are some good chances it will, so consider taking the risk on YOUR OWN, and give it a try.
    Please come back to describe your experience with this guide in order to allow us provide accurate and confirmed information to notebook owners like you for future cases.
    Regards,
    electrochain

  • Z87 Mpower SP : BIOS A is dead or can be saved??

    Hi guys,
    I accidentally did a failed flashing and caused my board doesn't wanna boot to post but all LEDs, fans on CPU and card are working only blackscreen on monitor and there is no LED show up on Debug LED. I use MSI Z87 Mpower SP with BIOS A (damaged) and BIOS B (working normal).
    I already did a recovery way that xmad have said before while I used MSI Z77A-GD80 (dual BIOS) and it was working at that time but now with Z87 Mpower SP (dual BIOS) it won't work, I use MSI HQ Forum USB flasher btw when I did failed flashing I was using M-flash after finished mainboard was turn off it self, then I did CLEAR CMOS ... after that I powered up PC and it turned out to begin flashing ME .
    The process with MSI HQ Forum USB flashing Tool is normal but when it is done I do a clear-CMOS and power up PC still debug LED is not showing anything although mainboard is power up (all fans, card, LEDs are on)
    So is the BIOS A dead?? Or can be saved?
    Btw I use i5 4430, Gskill ARES 2x4G GBA 2133MHz CL9 1.64v, WD Black 500G SATA3, Corsair HX750 & MSI GTX780 Lightning with windows 7 x64 SP1.
    Note : Now I use BIOS V1.6 on BIOS B, before this BIOS A is V1.7 and I wanna tried to downgrade BIOS to V1.5.
    One last thing I did flash with 4G USB FD with FAT formatted, is it OK? Next I will try to use FAT32 on my TOSHIBA 16G USB3.0.

    You needed special archives to allow fpt flashing, else forum tool won't work.
    >>Use the MSI HQ Forum USB flasher<<
         A.) Download the attached archive and place it on your desktop. Do not decompress.
         B.) Download and install the Forum flash tool.
         C.) Insert your FAT32 formatted usb stick.
         D.) Make sure that all win 8 options are disabled. (Fast Boot etc) Also make sure the legacy USB is enabled.
         E.) Start the forum flash tool and select option 1. Then point the tool at the compressed archive we downloaded earlier. Then to your USB Flash Drive.
         F.) Boot to the USB from working bios B.
         G.) Once it booted successfully switch to bios A without powering down or rebooting
         H.) Now follow the directions and let the tool flash bios A with desired version

  • Bios Flashing and Recovery

    BIOS FLASHING
    We do not recommend using the MSI LiveUpdate tool to update your BIOS! It may be okay for updating your drivers, but please do not use it to flash the BIOS in Windows!
    Windows-based flashing - If you REALLY insist on flashing the BIOS under Windows, if you encounter any error during flashing, whatever you do, DON'T restart your PC! Try again until the flash is successful, otherwise your board will not start! Disable any anti-virus program (along with any other programs) prior to flashing.
    Boards with built-in M-Flash function - While M-Flash work's properly most of the time, it has still proved to be less reliable than the forum tool / manual flash.
    Before flashing your BIOS, you must ensure your system is fully stable! Any instabilities can cause a bad flash and create an expensive paper weight. Included with the forum flash tool is MEMTEST, we recommend running this for 2 or more passes prior to a flash.
    If you do not understand what your BIOS is, or what it does, please read: >> BIOS. What it is, and all you need to know <<
    Our first choice we recommend you use is our own USB flashing tool, developed by Svet.
    It is important to note, that the only way to flash the ME extension of the BIOS of modern Intel boards is through the use special processes. The bios versions posted by moderators here: >>BIOSes<< include the additional files to accomplish this. These bios are all official and are directly from MSI.
    >>>MSI Forum HQ USB Flashing Tool<<<
    If you are unable to use the MSI HQ USB BIOS Flashing Tool
    >>How to create a dos bootable USB stick>>
    It is important to note that if any BIOS, EC FIRMWARE or any other type of FIRMWARE downloaded from MSI for a manual flash contains an BAT file it must be used. Not doing so will cause the flash to fail and require RMA.
    For Intel Users, flash via FPT
         Socket LGA 1150           : >>ME 9 FPT files & Instruction>>
    Many of the bios versions posted here: >>BIOSes<< Contain a .bat file. All you need to do is extract all of the contents of the archive into the root directory of a DOS bootable USB stick and run the bat file from pure DOS.
         Socket LGA 1155 & 2011: >>ME 7&8 FPT Files and instruction<<
    Linux users
    See this topic: >>Flash your BIOS, the Linux way! [beware the dangers!!]<<
    Modified and BETA BIOSes
    Use only at your own risk! All BETA BIOS versions posted by the moderators of this forum are directly from MSI and will not effect your warranty.The use of user modified BIOS versions may damage the board and may void your warranty. Exercise extreme caution in regards to user posted BIOS versions. Please also be aware that MSI and this forum can not be held responsible if you trash your mobo by using a modded, beta or otherwise incorrect BIOS.
    WHEN IT ALL GOES WRONG...
    BIOS RECOVERY
    In many cases, provided the 'bootblock' of your BIOS is not corrupted during a bad flash, the BIOS can often be recovered by following the recovery procedures detailed below. NOTE: this recovery method should not be followed for normal practice of updating your BIOS!
    For Modern MSI Systems, refer to:
    <<Multi-Bios Equipped Mainboards>>
    <<Single-Bios Equipped Mainboards>>
    Legacy Systems:
     For Award BIOS
    Make a bootable floppy disk*
    Copy the Award flash utility & BIOS file to the said floppy disk
    Create an autoexec.bat with "Award_Flash_Utility BiosFilename" in the content (e.g. awdfl823K w6378vms.130)
    Sample on how to create an autoexec:
    a. On Windows, open the notepad
    b. On the notepad, write "awdfl823K w6378vms.130" (without the " ")**
    c. Save the file as autoexec.bat
    Boot up system with the said floppy (it will take less than 2 minutes before screen comes out)
    Re-flash the BIOS & reboot.
    *Need a bootable floppy disk? Look here: http://www.bootdisk.com
    **Make sure you enter the correct filenames for your flasher program and BIOS ROM file!
     For AMI BIOS
    Rename the desired AMI BIOS file to AMIBOOT.ROM and save it on a floppy disk. e.g. Rename A569MS23.ROM to AMIBOOT.ROM
    Insert this floppy disk in the floppy drive. Turn On the system and press and hold Ctrl-Home to force update. It will read the AMIBOOT.ROM file and recover the BIOS from the A drive.
    When 4 beeps are heard you may remove the floppy disk and restart the computer.
     For new boards with AMI BIOS core 8 (4MB)
    Discovered by Jack The Newbie:
    Of course, the steps are similar to the standard AMI BIOS Recovery Procedure for internal floppy drives (rename corresponding BIOS File to AMIBOOT.ROM, hit CTRL + HOME after starting the system).
    What has to be done (tested on P45 Platinum):
    1. An optical SATA Drive needs to be connected to one of the Intel ICH10R SATA ports. {After a lot of testing, I found that it does not work with the same optical drive connected to the SATA Ports hosted by the secondary JMicron Controller.  Also, using an optical drive on the JMicron IDE/PATA port does not help either.}
    2. A proper BIOS File has to be renamed to AMIBOOT.ROM and burned on an empty CD.
    3. CMOS-Clear with main A/C power cable removed from PSU has to be performed. {If this step is not done, the system will reboot after pressing CTRL + Home and will not proceed with recovery procedure.}
    4. Press CTRL + Home to trigger BIOS Recovery.  -> The system should enter BIOS Recovery Routine. {Will basically work with both USB & PS/2 keyboard.  However, a PS/2 Keyboard is recommended as the system will respond earlier to PS/2 Keyboard than to USB Devices.}
    What should happen now:
    1. After pressing CTRL + HOME the LED Status should change to "Intializing Hard Disk Controller" and there should be access to the optical drive connected to the Intel ICH10R SATA ports.
    2. It can take up to 30+ seconds until the BIOS File that was renamed to AMIBOOT.ROM is found. {Drive Bay can be opened to try a different CD without turning off or restarting the system.}
    3. When the system finds the BIOS File, LED Status will change to "Testing RTC" and there should be a message on the screen indicating that the Flash Recovery Procedure has started.
    4.  Since the BIOS File is 4MB in size, it will take a while until the BIOS is actually reflashed.
    Its also possible that BIOS recovery on boards with AMIBIOS8 can be done using a FAT-formatted USB stick, containing the renamed BIOS file. Be warned, in some circumstances it may take several moments before recovery procedure actually begins. See Bas' reply below for further information.
    BIOS recovery on Wind netbooks
    See this post here:
    https://forum-en.msi.com/index.php?topic=130509.msg982711#msg982711
    BIOS recovery on non-UEFI notebooks
    In order to recovery this type of system you will need an FAT32 formatted USB stick.
    Download the applicable bios from MSI's website and rename this bios.
    It must be re-named to either AMIBOOT.ROM or xxxxIMS.ROM / xxxxAMS.ROM  You may need to try each way to determine which one is necessary.
    Then place the renamed bios onto the root directory of the FAT32 formatted USB stick.
    Now you are ready to cover the Notebook.
    To do this, remove the AC power cord and battery. Once that has been completed, install the USB stick you prepared earlier.
    Now, apply AC power (leaving the battery disconnected) and turn on the notebook. Recovery should begin after 5 minutes.
    IF ALL ELSE FAILS...
    Locate the BIOS chip on your mainboard. If it is soldered directly to the PCB like...
    ...then you have no choice but to return the board to your supplier, or to MSI, for replacement.
    To request an RMA from MSI, open a support ticket at https://register.msi.com/ocss/
    If your BIOS chip is in a socket, like...
    ...then you may be able to source a replacement BIOS chip, either from MSI, or from a website such as www.badflash.com
    Updated 11/21/2013, original post by Stu

         A.) Download >>this<< bios archive and place it on your desktop. Do not decompress.
         B.) Download and install the >>MSI HQ Forum USB flasher<< .
         C.) Insert your FAT32 formatted usb stick.
         D.) Make sure that all win 8 options are disabled. (Fast Boot etc) Also make sure the legacy USB is enabled.
         E.) Start the forum flash tool and select option 1. Then point the tool at the compressed archive we downloaded earlier. Then to your USB Flash Drive.
         F.) Boot to the USB from working bios B.
         G.) Once it booted successfully switch to bios A without powering down or rebooting
         H.) Now follow the directions and let the tool flash bios A with desired version

  • K9N Platinum - Wrong CPU Temperature in BIOS

    Hi, I have a K9N Platinum (7250-020) with the latest 1.3 BIOS and an AMD X2 3800+. The CPU Temperature in the BIOS has a negative sign in front of it, and it seems to always report -48*C. I tried the latest nVidia nTune and it was reporting the CPU temperature to be 208*C, which is absolutely impossible...
    Does anyone have the same problem? I searched around and it seems I'm not the only one, but I still cannot understand if it affects only some K9N Platinums or all...
    Thanks.

    Quote from: CBR600RR on 09-November-06, 06:51:56
    I assume you are talking about checking voltages as reported by the BIOS in the HW Monitor page, not physically checking them with a multimeter, correct?
    I'll take a look at the numbers in the BIOS, but last time I checked they were ok.
    As for raising the issue with MSI, eventually I will, even if they ask you soooooo many questions (for good reasons, I know...) that it would take me half an hour to fill that form... 
    I've checked with both and software is a little out from what a multimeter state's. Only check with a multimeter if your happy to do so. http://forums.extremeoverclocking.com/showthread.php?t=137886 offer good advise if using a multimeter .....
    The only issue I see is the AUX connector for 3.3v with ATX2.0 spec (Modular cables etc)
    Quote
    TheCleaner:
    CAUTION: This test involves using probes with the computer ON. Please only do this if you feel competent enough to be dealing with electricity. If you short rails, you could risk damaging the PSU and possibly your components. I cannot be held responsible if something goes wrong, this is merely a guide. If you feel any concern, please post BEFORE doing this, and I will be glad to help.
    Contacting MSI would be good to let them know of the problems your having

  • K9N Platinum Bios flash

    Hello, I got a K9N Platinum and I did flash is succesfull to 1.8, but did screw my windows vista drivers  :( .
    so np, C:/ is only windows for me, my files are on other drives and I installed windows again.
    but after a few restart system files get damaged again. now I want flash it back to a version with full support with the amd x2 6000+. (flasht my bios with a x2 3800+ but someone said to me 1.0 bios version dont support 6000+ so flasht it before I did put in my new processor)
    anyone can tell me the most stable version or I should flash it back to 1.0? (btw that backup I made with live update 3 is 1.8 too  ??? )
    can someone give me some advice me what are the best options for me? many thanks.

    Quote from: Arcur on 16-September-07, 06:01:22
    everything works fine now, but when I shut down my pc and after 5 minutes I turn him on, the computer starts but he lost the videocard driver  ???
    When I install the driver again it works fine and restarting the computer too, but a compleet shut down let him lose the driver or something.
    Is this because I dont have activated my windows copy yet or just because when I first time restarted my pc, after installing chipset drivers, he deleted some files with checkdisk again (checkdisk dont start anymore now when starting up windows only just once, but windows did start succesfull after checkdisk without errors in windows).
    I really dont know if this something has to do with my bios, but windows did never start checkdisk before starting up my OS and del. some files or something. If you dont know what this is I gonna try XP I think, because I almost want to trow my pc out of the window 
    EDIT:
    Did delete the driver and let Windows install it byhimself instead of the exe file from Nvidia and now he dont lose the driver info anymore when I shut down my pc  :D really I dont know, but strange things are computers or windows just suck
    "but strange things are computers or windows just suck "
    Its Vista... make sure that vista is up to date... especially of those patches:
    Microsoft Issues Windows Vista Hotfix for Gaming: https://forum-en.msi.com/index.php?topic=110767.0
    Update for Windows Vista (KB938979) - Performance Update: https://forum-en.msi.com/index.php?topic=110273.0
    "everything works fine now, but when I shut down my pc and after 5 minutes I turn him on, the computer starts but he lost the videocard driver  ???"
    update vista via windows update and re-install the drivers...
    Have you tested under XP? i don't expect such problems there..

  • Satellite 1410-604 - BIOS update Incorrect BIOS update in the web?

    Hi there again!
    Now with a new and weird matter.
    We all know that old say... "If it is not break, don't fix it". And if you put it into more informatic terms, "specially if it is a BIOS".
    Yes, we all know that the BIOS is something quite dellitate to handle. For some reason we normally feel like if we were handling something like nitro-glycerine, or some radioactive product. And this is because we all know what is being put in risk in that moment: our (or sometimes others) computer, the full system could end as dead as some pieces of metal, plastic, and wires.
    Well. I passed through all of that more than ten times in my life, and only once it went wrong. But since that old motherboard was already dead, It was not important. But I allways was EXTREMELY care. I allways cross checked everything before doing anything, allways got a backup and a way to restore that backup... and allways did this in COMPAQ systems, that were prepared that way. Updating a BIOS was just about preparing a disk, turn on the PC with the disk in the diskette drive, and wait. And if you didn't like the results, you simply click "return to previus BIOS" and that was it... very nice. And easy.
    Few days ago, a friend brought me a Toshiba Satellite 1410-604 to solve some issues that were driving him crazy. After removing an expired Norton Internet Security, install avast and scan, I found more than one hundred files infected with a wide variety of virus, malware, trojans, and whatever you could imagine. Avast removed them all, but the remains of the operating system was so unstable that we decide to format and install from scratch.
    I asked for the restoration disks, that obviously he don't have because they were lost in one of his movings. After we got the confirmation from Toshiba reps that there are no recovery disk available for this model, because it is too old, we decided to install from scratch like any other normal PC, and resigned to loose some of the utilities that come with that CDs and that are not available for download in the website.
    I downloaded all of the software available for this model, including two BIOS updates. (Actually only one update, but in two versions: Windows and Traditional), and prepared a CD with all the drivers and programs just like if it were a brand new system install. And everything went very well, no problems at all. Until we got to the Wireless LAN card, but that is another issue that is already solved (the mini PCI card for the WLAN does not support WEP or WAP encription, and it is not possible to connect to any wireless LAN encripted).
    At this point, and when I started configuring and enabling PCMCIA devices, and USB devices (this computer only supports USB 1.1 not 2.0) I discovered this text in the Toshiba Website:
    "This Bios Update adds increased functionality to your system.
    (BIOS is an acronym for Basic Input and Output System. This program is stored in a Read-Only Memory chip on the motherboard.
    When the computer powers up, the BIOS is launched to perform various start-up functions.)
    For detailed update information please refer to Toshiba BIOS-Update Information"
    (you can find this here:
    [http://eu.computers.toshiba-europe.com/innovation/download_drivers_bios.jsp?service=EU] you have to look for:
    Archive
    Satellite
    Satellite 14xx
    Satellite 1410-604
    PS141E
    Quite specific. Isn't it?)
    According to the information in that same website, the BIOS available fits the following models:
    "Satellite 2410-414, Satellite 1410, Satellite 1410-654S, Satellite 1410-814, Satellite 2410-303, Satellite 2410-304S, Satellite 1410-354, Satellite 2410-601, Satellite 1410-401, {color:#ff0000}*Satellite 1410-604*{color}, Satellite 2410-404, Satellite 1410-301, Satellite 1410-304, Satellite 2410-S403, Satellite Pro 2100, Satellite 1410-S203, Satellite 2410-304, Satellite 1410-554, Satellite 1410-S102, Satellite 1410-354E, Satellite 2410-703, Satellite 1410-303, Satellite 2410-S203, Satellite 1410-801, Satellite 2410-603, Satellite 1410-902, Satellite 1410-313, Satellite 1410-802, Satellite 1410-714, Satellite 2410-354, Satellite 2410-514, Satellite 1410-614, Satellite 1410-704, Satellite 2410-515, Satellite 2410-504, Satellite 2410-702, Satellite 1410-S103"
    Yes... it's there!
    Now, when you go to the "Toshiba BIOS-Update Information", you get:
    "FAQ Ref.: TRO0000000b07
    A BIOS update is a {color:#ff0000}*relatively simple operation and can be carried out by most competent computer users*{color}. All BIOS upgrades can be obtained from "BIOS Update" Download Section click here..
    Note: The BIOS files are machine specific so the correct BIOS for your machine must be used."
    Please note that Toshiba does not disencourage the handling of BIOS, on the contrary: they even encourage people to do so. This is not necessary bad, but at the same time they encourage people to 'play around' with such a delicate matter, at the end of that same page, in little letters they say:
    "Toshiba provides this information "as is" {color:#ff0000}*without warranty of any kind*{color}, either expressed or implied, including, but not limited to, the implied warranties of merchantability or fitness for a particular purpose. Toshiba shall not be responsible for the topicality, correctness, completeness or quality of the information provided. {color:#ff0000}*Toshiba is not liable for any damage caused by the use of any information provided, including information that is incomplete or incorrect*{color}."
    This should trigger yellow alarms in our minds.
    +"Human error is inherent to humans, and it is not possible to erradicate. It will allways appear, sooner or later" (Prof. James Reason).+
    And finally I made the mistake. Even though I read that warning, I remembered all those successfull BIOS update with COMPAQ, and relied in Toshiba. That update was available there, and Toshiba was telling me that it was for this computer. Great!
    So finally I unplugged all devices (USB), removed the PCMCIA (WLAN),plugged the battery charger to avoid any possible battery problem, restarted windows, and then from within windows I started the updater (windows version, as recommended by Toshiba). Everithing looked fine, nothing different of what I used to see on those old COMPAQs.
    As warned by the updating program, the system was going to reboot. And actually it did so.
    Windows closed quite normally (a bit quicker than normal, but without errors, and since there were no other programs than the essentials -even the antivirus was not running-), the computer switched of, all lights off (normal), and then it switched on again...
    {color:#0000ff}*BEEEEEEEEEEEEP... BEEEP... BEEEEP...*{color}
    OMG! I never espected something THAT bad. 3-1-1!
    And now... What a 3-1-1 stands for here? Award BIOS would mean no video card or deffective video card, but it is not true, since it was working up to 20 seconds ago. It must be the BIOS.
    It never came again to life. It is still beeping 3-1-1.
    But now comes the investigation of the human-factors involved in this accident.
    I found I commited the following failures:
    *(1)* To rely in the manufacturer, even though they WROTE their information could be wrong or incomplete. (BAD if I were a QA&QC inspector).
    *(2)* I didn't cross checked deeply enough (until it was already too late).
    *(3)* I didn't looked previously for the way to make a backup of the BIOS, in order to restore should anything go wrong.
    *(4)* Let Toshiba lead me to a path I didn't want to walk, just because of their offer of "increased functionality".
    *(5)* Beleave in Toshiba when they said "relatively simple operation and can be carried out by most competent computer users"... they never said it is failproof.
    Then I started the most interesting part of the investigation.
    {color:#0000ff}*"What went wrong?"*{color}
    Obviously, the BIOS update failed somehow, somewhere. And I wanted to know what and where.
    First thing I discovered was that there are another search engine in Toshiba called "askiris" ([http://askiris.toshiba.com]) and I looked there in order to see if for any chance I could get the old 1.20 BIOS version that was installed originally in that machine.
    And I found something... VERY interesting:
    bq. {color:#800080}*From: * \\ {color}{color:#800080}* ACPI Flash BIOS version 1.10 for Satellite 1410/1415/2410* \\ {color}{color:#800080}* bios for these models. TAIS. Downloads. DL. 105481 289838 289838 ACPI Flash BIOS version 1.10 for Satellite 1410/1415/2410. 2002-10-04. 105589...* \\ {color}{color:#800080}* Published 10/4/02* \\ {color}{color:#800080}* From: * \\ {color}{color:#800080}* ACPI Flash BIOS version 1.40 for Satellite 1410/1415/2410/2415* \\ {color}{color:#800080}* FDD Version 1.30 TAIS. Downloads. DL. 105481 357972 357972 ACPI Flash BIOS version 1.40 for Satellite 1410/1415/2410/2415. 2003-01-31. 105589 PUB...* \\ {color}{color:#800080}* Published 1/31/03 | Rating:* \\ {color}{color:#800080}* From: * \\ {color}{color:#800080}* ACPI Flash BIOS version 1.20 for Satellite 1410/2410* \\ {color}{color:#800080}* error message during BIOS TAIS. Downloads. DL. 105481 305240 305240 ACPI Flash BIOS version 1.20 for Satellite 1410/2410. 2002-11-01. 105589 PUB...* \\ {color}{color:#800080}* Published 11/1/02 | Rating:* \\ {color}{color:#800080}* From: * \\ {color}{color:#800080}* ACPI Flash BIOS version 1.30 for Satellite 1410/1415/2410* \\ {color}{color:#800080}* 1) Changed the content TAIS. Downloads. DL. 105481 330963 330963 ACPI Flash BIOS version 1.30 for Satellite 1410/1415/2410. 2003-01-03. 105589...* \\ {color}{color:#800080}* Published 1/3/03 | Rating:* {color}
    Those are: V110, V140, V120 and V130 for series 1410/15 and 2410.
    GOOD! Or not?
    Let's take a look:
    First thing I did was download everything all four files.
    Then I took the same version that made the crash: 1.40
    Than I uncompressed the file, and I found:
    06/05/2009 00:17 &lt;DIR&gt; .
    06/05/2009 00:17 &lt;DIR&gt; ..
    31/01/2003 08:38 1,605,632 11410v14.iso
    31/01/2003 08:38 511,764 1370D14.EXE
    {color:#ff0000}*08/01/2003 17:03 724,480 2410a9v140.exe*{color}
    09/01/2003 09:32 250,663 biofca9t.com
    08/10/2002 05:26 30,697 chgbiosa.exe
    31/01/2003 08:36 1,087 instinfo.bat
    13/05/2002 15:25 378,175 launcher.exe
    31/01/2003 08:36 433 launcher.ini
    06/05/2009 00:17 0 list.txt
    31/01/2003 08:36 14,768 readme.com
    *{color:#ff0000}31/01/2003 08:36 12,513 readme.txt{color}*
    11 archivos 3,530,212 bytes
    3 dirs 9,404,600,320 bytes libres
    And I got my first surprise here: There is a {color:#ff0000}*README.TXT*{color} that was not present in the file I downloaded previously from the drivers repository.
    So I went to the readme.txt and I found this:
    "README.TXT 01-31-2003 CDC
    Flash BIOS version 1.40 for Satellite 1410
    This BIOS is applicable to the following models:
    Satellite 1410-S105
    Satellite 1410-S106
    Satellite 1410-S173
    Satellite 1410-S174
    Satellite 1410-S175
    Satellite 1410-S176
    Satellite 1415-S105
    Satellite 1415-S106
    Satellite 1415-S115
    Satellite 1415-S173
    Satellite 1415-S174
    Satellite 1415-S175
    Satellite 1415-S176
    Satellite 2410-S203
    Satellite 2410-S204"
    Please note that the model 1410-604 is *NOT* listed.
    I thought "well, it must be another archive..."
    But then I realized of a name that sounds familiar, it was there, in the directory where I uncompressed this 1.40 file, and the name is:
    {color:#0000ff}*2410A9V140.EXE*{color}
    So I took the other file, the BIOS_Win update, and I discovered that the file name is:
    *{color:#0000ff}2410A9V140.EXE{color}* (Ups!)
    So I uncompressed it again, to find:
    El volumen de la unidad D no tiene etiqueta.
    El n&pound;mero de serie del volumen es: 8838-E175
    Directorio de D:\Shared\diskette\2410A9v140
    06/05/2009 00:43 &lt;DIR&gt; .
    06/05/2009 00:43 &lt;DIR&gt; ..
    *{color:#0000ff}09/01/2003 09:32 _250,663_ BIOFCA9T.COM{color}*
    17/07/2002 03:38 35 biosupd2.ini
    13/07/2001 13:22 6,277 chgbios2.vxd
    *{color:#0000ff}08/10/2002 04:26 _30,697 _CHGBIOSA.EXE{color}*
    09/11/2001 09:14 134 clean2.reg
    17/07/2002 03:35 342,064 install2.exe
    16/07/2002 06:55 241,664 nchgbios2.exe
    18/08/2001 11:41 3,435 nchgbios2.sys
    23/10/2001 18:55 11,476 nchgbios2NT.sys
    26/08/2001 09:00 49,152 nchgbios2svc.exe
    13/07/2001 17:05 49,152 tbdecode.dll
    14/03/2002 06:42 49,152 TCHGBIOSInfo.dll
    21/06/2002 11:25 1,796 tosclean2.bat
    09/11/2001 12:01 967 tosclean2.pif
    21/06/2002 11:34 1,841 toscleanAUTO2.bat
    21/06/2002 11:44 1,796 toscleanSMS2.bat
    21/06/2002 08:51 2,038 tosntclean2.bat
    21/06/2002 08:51 2,084 tosntcleanAUTO2.bat
    21/06/2002 08:52 2,038 tosntcleanSMS2.bat
    20 archivos 1,046,461 bytes
    2 dirs 9,402,793,984 bytes libres
    No readme file...
    Then another question arised in my mind: What about the other 1.40 file? What does the other 2410A9V140.EXE have inside?
    This:
    El volumen de la unidad D no tiene etiqueta.
    El n&pound;mero de serie del volumen es: 8838-E175
    Directorio de D:\Shared\diskette\comparacion_toshiba\askiris\241 0a9v140
    06/05/2009 00:46 &lt;DIR&gt; .
    06/05/2009 00:46 &lt;DIR&gt; ..
    *{color:#0000ff}09/01/2003 09:32 _250,663 _BIOFCA9T.COM{color}*
    17/07/2002 03:38 35 biosupd2.ini
    13/07/2001 13:22 6,277 chgbios2.vxd
    *{color:#0000ff}08/10/2002 04:26 _30,697 _CHGBIOSA.EXE{color}*
    09/11/2001 09:14 134 clean2.reg
    17/07/2002 03:35 342,064 install2.exe
    16/07/2002 06:55 241,664 nchgbios2.exe
    18/08/2001 11:41 3,435 nchgbios2.sys
    23/10/2001 18:55 11,476 nchgbios2NT.sys
    26/08/2001 09:00 49,152 nchgbios2svc.exe
    13/07/2001 17:05 49,152 tbdecode.dll
    14/03/2002 06:42 49,152 TCHGBIOSInfo.dll
    21/06/2002 11:25 1,796 tosclean2.bat
    09/11/2001 12:01 967 tosclean2.pif
    21/06/2002 11:34 1,841 toscleanAUTO2.bat
    21/06/2002 11:44 1,796 toscleanSMS2.bat
    21/06/2002 08:51 2,038 tosntclean2.bat
    21/06/2002 08:51 2,084 tosntcleanAUTO2.bat
    21/06/2002 08:52 2,038 tosntcleanSMS2.bat
    20 archivos 1,046,461 bytes
    2 dirs 9,402,781,696 bytes libres
    *{color:#ff0000}They both have 20 files, and 1,046,461 bytes. I asumed they are both the SAME file{color}*.
    And the readme file does not list the model 1410-604 in its readme file, therefore I cannot explain this except as a mistake from Toshiba. *{color:#ff0000}They put an incorrect BIOS in their website, and suggested the update, and somehow leaded to this kind of errors.{color}*
    (Except in the case that one of those models is a different name of the 1410-604 model, and if it is the case... now I don't know why this BIOS do not work with this computer).
    The worst part is that neither of those other files (V1.10, 1.20 and 1.30) lists the 1410-604, therefore there seems no possible workaround for this problem. I need an original v1.20 for this CMOS, and Toshiba seems not to have it. They offered me to solve the problem, by leaving the notebook at an ASP, and paying only 95&euro; for the work and about 280&euro; for a motherboard replacement, I will get it solved. But they offer no warranty of their possibilities because is a model 'too old' and 'discontinued' and with 'no support'...
    In other words, they said "don't bother with this, just go out there and buy a new one" (something absolutely out of my scope in this crisis-time) :P
    Thank you for reading soooo far.
    Now what I need is to get any ideas of a workaround for this, my ideas are:
    (1) This CMOS has a boot-part that still works (it allows a roll-back if you have the appropriate file). So I need a good BIOS to burn into the CMOS, from the VERY SAME model (a BIOS backup) but the backup must be adequate for the burning program (CHGBIOSA.COM).
    (2) It is still possible that the BIOS could be OK but the data on the CMOS got somehow corrupted. If so, clearing the CMOS could solve de problem. But I was not able to find a clear cmos button from outside, and after disasembling I took of the battery, with no good results. I have to try leaving the MOBO without battery for longer period (I left it about 20 seconds) just in case 20 seconds don't allow all the capacitors to fully go to zero values. I have not much hope in this point.
    (3) Try to get a REAL good update from Toshiba. I contacted several times technical support, and I was able to verify they are only phone-operators, with a script in front of them, and when the problem goes-out-of-scope they fall always in the same answer: "you have to go to an ASP". I still have a low hope to find someone who really knows a bit, and could enlighten with a good BIOS to put in this disks.
    (4) As far as I could find, this BIOS is not from any known BIOS-maker. It seems it has been developed by Toshiba (own brand), therefore the Crisis Recovery Disk from Phoenix will not be of any help here. As well as any other BIOS recovery tool not designed for Toshiba's BIOS. But I'm open to any ideas, that could be tested more or less safely. (Remember that the 'BIOS-BOOT-PART' feature is still working, I don't want to loose this only possibility of redemption).
    Wwwaaaaoooowww... what a long-post falks! Sorry for that!
    Forgive me, but I wanted to be really clear.
    Should anyone give some hints or advice, will be greatly appreciated.
    Please don't say what I shouldn't do... I already know that. I already researched and already found my mistakes, in order not to repeat them. Now I need to move on, to advance, and to try to solve this, or at least learn how to solve similar things. As much as possible.
    Thank you again, in advance, and sorry again.
    FenixDigital
    Message was edited by: Fenix_D
    Changed subject to beter reflect what is the matter about (apparently erroneous BIOS file in Toshiba download center).

    Well.<br />
    <br />
    It's not dead, certainly.<br />
    <br />
    The steps that I put in my procedure were:<br />
    <br />
    --&gt; There are two memory sims, that I am going to identify as M1 and M2<br />
    --&gt; There are two memory banks, that I am going to identify as A and B<br />
    <br />
    Next step in order to identify if there are some module or bank that is not working properly are:<br />
    <br />
    The modules were installed as:<br />
    <br />
    M1 --&gt; A<br />
    M2 --&gt; B<br />
    <br />
    <strong>1--&gt; Boot without any memory chip.</strong><br />
    <br />
    <blockquote>
    A--&gt; X<br />
    B--&gt; X<br />
    </blockquote>
    <br />
    <strong>2--&gt; Boot with ONE module</strong><br />
    <br />
    <blockquote>
    A--&gt;M1<br />
    B--&gt;X<br />
    </blockquote>
    <br />
    <strong>3--&gt; Boot with the OTHER module</strong><br />
    <br />
    <blockquote>
    A--&gt; X<br />
    B--&gt; M2<br />
    </blockquote>
    <br />
    <strong>4--&gt; Boot with BOTH modules swapped:</strong><br />
    <br />
    <blockquote>
    A--&gt; M2<br />
    B--&gt; M1<br />
    </blockquote>
    <br />
    <strong>5--&gt; Boot with ONE module swapped:</strong><br />
    <br />
    <blockquote>
    A--&gt; M2<br />
    B--&gt; X<br />
    </blockquote>
    <br />
    <strong>6--&gt; Boot with the OTHER module swapped:</strong><br />
    <br />
    <blockquote>
    A--&gt; X<br />
    B--&gt; M1<br />
    </blockquote>
    <br />
    At this point I got a great difference. It booted, finally. But in order to make a diagnostic, I have to complete the full test, and the results were:<br />
    <br />
    1--&gt; Boot without any memory chip.<br />
    <br />
    A--&gt; X<br />
    B--&gt; X<br />
    <br />
    <strong>NOT BOOTING</strong> Actually the computer not even tries to read the disk. Only the power led turns on, but even prior to press the 'on/off' button. I think this indicates 'no memory installed'. I would have expected a post failure beeps, but there were no beeps at all.<br />
    <br />
    2--&gt; Boot with ONE module<br />
    <br />
    A--&gt;M1<br />
    B--&gt;X<br />
    <br />
    <strong>BOOTED NORMALLY</strong> Well. This obviously means that the 3-1-1 beep code means memory error, or one bank failing of two installed. Now I didn't know if the problem was the module, or the bank B.<br />
    <br />
    3--&gt; Boot with the OTHER module<br />
    <br />
    A--&gt; X<br />
    B--&gt; M2<br />
    <br />
    <strong>NOT BOOTING</strong> Just like the condition in 1. Like no memory installed, therefore there are two possibilities: The bank B is not working, or the memory module M2 is not working.<br />
    <br />
    4--&gt; Boot with BOTH modules swapped:<br />
    <br />
    A--&gt; M2<br />
    B--&gt; M1<br />
    <br />
    <strong>NOT BOOTING</strong> Just like previous to test condition. Beep code 3-1-1, no boot at all.<br />
    <br />
    5--&gt; Boot with ONE module swapped:<br />
    <br />
    A--&gt; M2<br />
    B--&gt; X<br />
    <br />
    <strong>NOT BOOTING</strong> This was the important test, because it finally let me determine that the problem is at the module 2 (M2) not at the bank B. But still there could be a failure IN THE BANK B and IN THE MEMORY MODULE 2. Have to do the other test.<br />
    <br />
    6--&gt; Boot with the OTHER module swapped:<br />
    <br />
    A--&gt; X<br />
    B--&gt; M1<br />
    <br />
    <strong>BOOTING NORMALLY</strong> This really confirmed there is nothing wrong with ANY bank, but one of the modules is not working, actually is not being even detected. This is quite weird, because this computer was working perfectly with those two modules, and in the moment of the BIOS upgrade it seems to fail... How come?<br />
    <br />
    Something weird happened here. I don't know what, but something ruined one memory module (fortunately only one), what I would like to know now is what happened. But at least I have the machine running, with very low memory, but running.<br />
    <br />
    What I am thinking now is what about this BIOS upgrade makes the motherboard not to recognize one of the modules for some reason?<br />
    <br />
    <img class="jive-emoticon" src="images/emoticons/happy.gif" border="0" alt=":)" /><br />
    <br />
    I will continue my research, but certainly the memory made the difference.<br />
    <br />
    I am not sure why I didn't discover this before, I think I didn't perform this test before, for two reasons:<br />
    <br />
    (1) I tried to boot with no memory, and this was impossible, so I assumed that the problem was not at the memory.<br />
    <br />
    (2) When I heard the beep code (3-1-1), somewhere I read it was a video problem, and I asume most probably it was a video problem (since no video at all was being displayed) but I should have take into consideration that Phoenix BIOS also means with the same 3-1-1 a DMA problem (memory problem).<br />
    <br />
    Okis... It's a pitty having to wait so much between a post and it's approval. I posted my answer two days ago, and since it didn't appear, I believe It didn't upload, so I replied again, and also didn't appeared... until now. It is obvious that a moderator approval is required. That's why I have to wait 24 hours or more to read my post. This slows this forum effectiveness.<br />
    <br />
    Thank you very much for your help. I'll keep you informed. Until we get to a final diagnosis and solution.

Maybe you are looking for

  • Printer Officejet Pro 8500 wireless

    My printer was working OK until I switched to Windows 8.1.  Now it will not print although printing gets sent to printing queue and rapidly disapprears.  Have gone through all forums, troubleshooting, etc and no solution.  And I get the error Windows

  • Virtual PC 7 any good?

    Hi there, I am in the process of purchasing new workstations and server for our office (replacing our whole network). There are 2 schools of thought, that we should go all Mac or all PC. The all Mac side is just me! Right now we have a horrible mixed

  • No Quiz Results in E-mail

    Hello, I created a quiz, and set the results to be e-mailed. When I tested it with F4, the quiz results showed up in the e-mail. But, when I publish it and upload the files, the send e-mail button initiates an e-mail to the correct address, but there

  • Rfc to xi tto file

    Hi, Iam struck up with scenario in rfc to file where , rfc is taken as sender communication channel. what is the way to configure sender communication channel.

  • DNG won't convert CR2 files from Canon 30D

    I have installed Camera Raw 2.4 and also DNG converter.  But when I try to convert Canon 30D CR2 raw files the DNG converter simply says: The source folder does not contain any supported camera raw files. Have also tried dragging an individual image