Associate
- Joined
- 10 Dec 2007
- Posts
- 445
First of all, apologies for the crosspost - this has metamorphosed from an OCing to a motherboard problem ;-(
I've just put together a setup comprising a Gigabyte GA-P35-DS3P, Q6600 and 4GB OCZ DDR2 800MHz RAM. I was having stability issues when I overclocked and was advised to run memtest on the RAM, which I did. After getting a ton of errors, I tested it with different RAM which I'm sure was good, and got a ton of errors again, the same ones. A bit of research suggested that these errors were false-positives that some versions of the DS3 BIOS throw up in conjunction with memtest86+. In order to get shot of the false-positives and get a definitive answer on whether or not the original RAM was bad, I decided to update the BIOS to the newest version.
Off I go to Gigabyte's website to download the newest version of the BIOS (F10), and I see a banner at the side of the page advertising their new @BIOS update utility (comical pdf here), which flashes the BIOS from Windows. Cool, I thought, that'll be much less hassle. So I download and install @BIOS, back up my current BIOS version (F8), point it at the p35ds3p.f10 file, and set it going. After a few seconds, I get some error popups that loop indefinitely in the order "Alloc kernel memory failure!!" > "Translate memory failure!!" > "Free kernel memory failure!!". I have to kill @BIOS's process to get them to stop. I start @BIOS again, and try to restore the old BIOS version from the backup that I just made, but the same error loop happens again. Trying to flash the BIOS with any of the three BIOS versions (F8, F9, F10) as well as the backup I made of my original F8 BIOS all fail with the same error messages.
Back to google I go, and I find that a few people have had similar issues with @BIOS, and that if I turn my computer off now, it is basically gg for the motherboard. Apparently there is ordinarily some chance of recovery, but if you have a RAID 0 array (like what I do) then the jig is pretty much up. I'm posting here in the hope that people may have some suggestions as to things I can try to avoid the motherboard permanently dying the next time I restart.
I've just put together a setup comprising a Gigabyte GA-P35-DS3P, Q6600 and 4GB OCZ DDR2 800MHz RAM. I was having stability issues when I overclocked and was advised to run memtest on the RAM, which I did. After getting a ton of errors, I tested it with different RAM which I'm sure was good, and got a ton of errors again, the same ones. A bit of research suggested that these errors were false-positives that some versions of the DS3 BIOS throw up in conjunction with memtest86+. In order to get shot of the false-positives and get a definitive answer on whether or not the original RAM was bad, I decided to update the BIOS to the newest version.
Off I go to Gigabyte's website to download the newest version of the BIOS (F10), and I see a banner at the side of the page advertising their new @BIOS update utility (comical pdf here), which flashes the BIOS from Windows. Cool, I thought, that'll be much less hassle. So I download and install @BIOS, back up my current BIOS version (F8), point it at the p35ds3p.f10 file, and set it going. After a few seconds, I get some error popups that loop indefinitely in the order "Alloc kernel memory failure!!" > "Translate memory failure!!" > "Free kernel memory failure!!". I have to kill @BIOS's process to get them to stop. I start @BIOS again, and try to restore the old BIOS version from the backup that I just made, but the same error loop happens again. Trying to flash the BIOS with any of the three BIOS versions (F8, F9, F10) as well as the backup I made of my original F8 BIOS all fail with the same error messages.
Back to google I go, and I find that a few people have had similar issues with @BIOS, and that if I turn my computer off now, it is basically gg for the motherboard. Apparently there is ordinarily some chance of recovery, but if you have a RAID 0 array (like what I do) then the jig is pretty much up. I'm posting here in the hope that people may have some suggestions as to things I can try to avoid the motherboard permanently dying the next time I restart.
Last edited: