Erratic Boot Behavior

tjs4ever

Honorable
May 17, 2012
132
0
10,710
Erratic boot behavior

I'm having strange behavior at POST after a cold boot since I've upgraded my Q6700 to a Q9550. Occasionally (about 1 in 10 times) the machine will begin to POST, then suddenly turn off and then back on again. Every time this happens the clock in windows is incorrect and I am forced to change it (incorrect in BIOS as well, not a windows bug). Slightly less frequently (maybe 1 in 20) there is no POST at all: the machine just hangs and I get no video output. I also once got a BSOD at the Win7 welcome screen. I cannot reproduce these issues with a reboot, but only with a fresh boot of the machine. The overclock seems stable, I have already let it run 23 hrs 50 mins in prime (got impatient at the end), it passes many passes of intel burn test, and it passes many passes of memtest and linx. There has been no change to my machine save for a new processor and new overclock settings to match. My specs and settings are below:

MSi Neo 3 FR (P45) @400FSB, Q9550 @3400mhz (400x8.5) with 1.1675V, 6GB Corsair XMS2-6400 (2x1GB, 2x2GB) @ 960mhz (1:1.2) 5-5-5-12 with 1.908V, Zotac GTX570 @stock, Intel 330 series 120GB SSD, OCZ ModXstream Pro 600W. I don’t think I need to list my case, optical drives etc… My MCH, VTT, and ICH voltages have always remained at AUTO and my former overclock with my Q6700 was at 320FSB and identical RAM settings (just a higher RAM ratio before) and was previously perfectly stable and predictable.

I have no interest in building a new machine, and any suggestions to that effect will be ignored. This machine is dated, I realize, but I like it and I want to figure this thing out. I have a read-only OS, so I highly doubt something windows related. My temps were monitored during all my initial stress tests and CPU never peaked 61C on the hottest core, and I have checked all connections within the mobo. I’m really hoping one of my AUTO settings just needs adjustment. I look forward to any advice,

T.J.
 

tjs4ever

Honorable
May 17, 2012
132
0
10,710


My board is revision (pcb) 1.0 I should have specified, sorry. I am running the latest 1.A/1.10 BIOS for this board. BTW MSI Liveupdate was a terrible piece of software IMO, and I have read reports of failed flash attempts while using it...

As suggested I purchased and installed a new battery today (was only 80 cents), but will need a few days to test as the issue is so sporadic. Not surprisingly my CMOS settings were all lost afterwards, but I was happily surprised that the user-saved settings somehow remained intact.

T.J.
 

tjs4ever

Honorable
May 17, 2012
132
0
10,710
Well it did it again today... The on-off-on thing, with the clock being incorrect afterward. Tonight I will flash the lates BIOS anyway and manually enter all my settings. Is the flash chip dying or something? Any ideas would be appreciated.
 

tjs4ever

Honorable
May 17, 2012
132
0
10,710
I flashed the latest BIOS 1.A (it says 1.10 within BIOS menu) even though it was already in there, load safe default and rebooted. Then I manually entered all of my previous settings including overclock and it worked perfectly and predictably three cold boots in a row. On the 4th boot I only got a black screen, no post. On the 5th boot I was greeted with HALT at "cmos chksum bad" or failed chksum (I don't recall). So... is my board dying?
 
If thE chip is solider on then your going to have to replace the mb if the error keeps up. Messages is when the mb check the number of date bits in the CMOS the number came back wrong. Ie expected 4096 g0t 4095.
If the error still there try flashing the bios down to the last stable CMOS for you. In computer talk the letters a to f are used for the numbers 10 to 15.
 

tjs4ever

Honorable
May 17, 2012
132
0
10,710
Last stable BIOS version was 1.10 which is what I just flashed, which is what was already running. The battery is in correctly, it's voltage is read in hw monitor as 3.2v. There appears to be nothing physically wrong here as the CMOS power circuit is completing. Power supply is of decent calibre and is maybe 2 years old.