Upgraded BIOS now system completely unstable

[dwell]

I've been using a E6400 @ 3.2Ghz for two years now. This CPU ran at that speed on a P5B Deluxe for a year and on my P5E-VM HDMI for another. I've run Prime95 for over 24 hours, ran 24/7, 12+ hour gaming sessions. The rig was 100% stable.

Here's where stupidity comes into play. I bought a Q6600 and to prepare to install I flashed the BIOS to the latest version (dumb move). It borked my settings but I had what I thought was the important ones written down and re-entered them. However, my system became unstable right off (on the old E6400). I didn't have time to really mess with it at the time so I came back the next day with graysky's (excellent) guide to try and fix it. Nothing I tried worked, and the funny part is the only things I restored from the configuration were multipler, FSB, memory timings, vcore, memory voltage, and nbcore -- I don't remember every having to tweak anything else, but nothing i tried worked.

Prime95 would fail straight off on the second core either in the first 15 seconds or the system would reboot. Temps were low so I ruled heat out. Finally I decided it was something the BIOS upgrade did so I rolled back to the previous version but that did nothing either, all the problems remain.

At this point I am at wit's end. I am completely hosed. My trusty E6400 won't OC for squat anymore and the Q6600 is not overclocking well at all (must be related).

Any help, advice, anything would be appreciated. This has me totally bummed.

Rig in sig. Pertinent BIOS settings:

CPU Ratio: 8.0
FSB Strap: Auto
FSB Freq: 400
PCIE Freq: 100
DRAM Freq: DDR2-800 5-5-5-12-5-42-14-3-5

CPU Spread Spectrum: Disabled
PCIE Spread Spectrum: Disabled

CPU Voltage: 1.40v
CPU Voltage: Auto
CPU Voltage Damper: Auto
PLL Voltage: Auto
DRAM Voltage: 1.9v
FSB Termination Voltage: Auto
North Bridge Voltage: 1.35v (tried bumping it to no avail)
North Bridge Voltage Reference: Auto
South Bridge Voltage: Auto

 

[Phynaz]

Go back to the BIOS version you were on before?

Also, there should be an option to reset cmos to default - use it.

 

[dwell]

Tried going all the way back to the first BIOS for the mobo with the DOS utility. Wiped the nvram, everything.

Memtest86 runs fine but Prime95 bombs in under 15 seconds. It's driving me crazy but I think I may have to resort to running my q6600 stock if I can't figure it out

 

[NXIL]

Hi Chris,

sort of controversial here, but may I recommend an overnight CMOS clear? OK, in theory, CMOS should clear pretty rapidly, but, personal experience: sometimes it takes longer.

Edit: remove motherboard battery, and use clear CMOS jumper too....leave it that way overnight. This pleases the BIOS gods, and they may reward your time sacrifice.

Then, load BIOS that worked, the one you were using before this incident occured.

Then, back to the basics you are familiar with:

make sure heatsink and thermal compound are ok (stock intel heat sink? As you know, they suck, and can look like they are OK until disaster strikes.)

Slowly start step by step overclock, not all at once.

By the way, new q6600? Or, bought used?

HTH

NXIL

 

[dwell]

NXIL: Draining the battery is great advice, I didn't think of that. Unfortunately it looks like the motherboard started degrading on me. The onboard LAN starting acting weird, so I assumed the board was going or something with the BIOS flash killed it. Reinstalled Windows and still problems, so I sent it in for RMA.

The Q6600 is new. Hopefully when I get the board back I can hit 3.2Ghz with the E6400 again and then work on overclocking the Q6600. Hopefully it's not a dud, but I've not heard of any Q6600s that can't hit at least 3.0ghz with less than 1.4v, especially G0s.

 

[NXIL]

Sorry to hear about the untimely demise of your Mobo.

And, congrats on your AT anniversary.

GL w/ new mobo,

NXIL