Machine Check Exception

86DRIFTER

Limp Gawd
Joined
Oct 3, 2006
Messages
355
I have been getting these blue screens lately that have been saying Machine Check Exception and then a big error code. I checked Microsoft's site and it says the problem is by design. Here it is btw.

I thought it was a CPU setting in the BIOS messing up so I cleared the CMOS. It didn't work, and I am all out of ideas. I am willing to do a full reinstall of Windows if I need to. I could use one anyway. But I am thinking that would not cure a hardware problem.
 
Basically what the M$ KB article said was that there is prolly something wrong with the motherboard, power supply, CPU or memory. Time to do some troubleshooting. I second you on the re-install.... I doubt it will fix anything either.
 
I did memtest for about an hour and it turned up nothing. But I can be suspicious of it because it was used by a friend for a couple years. He also has a spare CPU that, if it works, I could put in here for a small fee so he says. It is an Athlon 3400 anyway.

The strange thing is, it never does it while I'm around. I can be gaming for hours on end and it will never appear. So I think improper cooling is out of the equation. It only happens when I am not around and I leave it alone for 10 minutes or so. I heard that some programs can cause this sort of thing and I had a suspicious screen saver from a third party.

Does anyone have a guess on why it only happens when I am not around?
 
Huh. Don't you love the non-specific error messages?

I was getting this on a rig once, and I found a bad memory stick. It did it a couple more time after memory replacement, and a clean-up of all the dust clogging the cpu fan + heatsink made it go away for good.

I would'nt run memtest for only an hour. I never run it for less than 12 to be sure. Also, if you want to try and eliminate software, disable the screensaver, and run in safe mode. You can also disable everything in msconfig, and run the rig for a while.........re-enable one program and restart. Run for a while........re-enable next program and restart. ETC, ETC.
 
Back
Top