7276
Living Room / Re: [HELP!!] Win XP reboots sometimes *after* startup [Any Ideas?]
« Last post by 40hz on July 14, 2011, 06:06 PM »A machine check exception can be caused by a board, CPU, RAM, temperature, power voltage, or driver problem.
To get to the bottom of the error code you'd need to go to the CPU manufacturer's website and see if there was more info on that message under the specific processor. Since decoding machine check errors is a real nightmare, your best bet is to post a message on the manufacturer's troubleshooting forum with details and ask for help if you suspect the CPU.
FYI: Intel does publish a diagnostic utility for their CPUs. It will do a stress test so if there's a flakey in t he chip, it can help spot it. Unfortunately, it's Windows software so it's not going to help you out too much under Linux.
Addendum: did a little research. Under Linux, this error is most commonly caused by bad cache on the CPU according to one source. See here.
To get to the bottom of the error code you'd need to go to the CPU manufacturer's website and see if there was more info on that message under the specific processor. Since decoding machine check errors is a real nightmare, your best bet is to post a message on the manufacturer's troubleshooting forum with details and ask for help if you suspect the CPU.
FYI: Intel does publish a diagnostic utility for their CPUs. It will do a stress test so if there's a flakey in t he chip, it can help spot it. Unfortunately, it's Windows software so it's not going to help you out too much under Linux.

Addendum: did a little research. Under Linux, this error is most commonly caused by bad cache on the CPU according to one source. See here.

Recent Posts







) Its really big advantage (in the unlikely event of a catastrophic backbone crash) is it could be run (like POTS phones) without the Internet. You could even implement it to run using shortwave radio if you had to.
