MACHINE_CHECK_EXCEPTION BSOD

[fixxxer0]

I haven't had this problem since I built my computer. I recently had a minor problem where my MP3's would not show icons. So after trying everything I knew to fix that, I tried to reload windows on top of that without formatting. That was a disaster.... its also when my BSOD started. So I said screw it, formatted and clean instal.


Now every now and then when I boot i get a MACHINE_CHECK_EXCEPTION blue screen crash. (Usually after a warm reboot which is fine because for some reason my computer doesnt like warm reboots - it hangs in bios on scanning the IDE Bus) But now I woke up to my computer having that on with no programs running over night except AIM.


WTF can this be? I highly highly doubt its temperatures. It has been fine this whole time (9 months).

 

[BadThad]

One thing at a time, first thing to address is the warm boot issue. What mobo? What drives are connected and how are they configured? Do you have the latest BIOS?

 

[fixxxer0]

when i upgraded bios it woudlnt boot at all

its on a ga-k8nxp-sli mobo F9 ... im running F6 now


i was running memtest just now, the memorys giving me errors

 

[plamalice]

The Machine Check is a feature from the processor that detects integrity failures.

This could be a number of things but is usually due to defective or improperly configured memory or defective cache on the CPU.

Since you said memtest reported a lot of errors, you should try "relaxing" your memory timings. (i have a nForce4 mobo as well and memory has given me trouble in the past - Corsair Pro XMS (2-2-2-5) that i had to run 2.5-2-2-5 to solve the problem).

The quickest way to identify if your memory is the cause would be to underclock it to 180Mhz (DDR 360). If your issue goes away (or becomes a lot less frequent), then start working on those timings.

If that doesnt help at all, try disabling the CPU Cache (note that this will dramatically affect performance and cannot be considered a viable solution). If that fixes your problem, you probably have a defective CPU cache (dont jump to conclusions though, as the cache malfunctioning could be the result of some other problem).

This being said, I'd be willing to bet good money the problem is your memory.

Good luck..