Main Area and Open Discussion > Living Room
[HELP!!] Win XP reboots sometimes *after* startup [Any Ideas?]
tomos:
Looks like the CPU might be the problem.
I booted with a Parted Magic CD - it got as far as this with the CPU message at the end
"kernel panic - not syncing: cpu context corrupt"
Ath:
Hmm, the Bank 0: / Bank 5: messages would suggest me memory errors, not CPU, but both are alarming :'(
Stoic Joker:
Bank 5? With a 2GB memory kit (generally 2x1GB). I don't think the bank references are memory, on chip cache maybe... *Shrug* ...Not sure. But Memtest86+ already passed the memory.
Still could be the PSU; brownout on boot load spike.
Or just for fun disable all the onboard USB stuff and see what happens...it is the last thing it was loading before it go poof.
tomos:
^ yeah, memtest did three full passes without errors...
Or just for fun disable all the onboard USB stuff and see what happens...it is the last thing it was loading before it go poof.
-Stoic Joker (July 14, 2011, 03:54 PM)
--- End quote ---
:D
how do I disable USB? Physically - unplug cables?
There's usb on the front of the machine & I can see where the cable goes into the motherboard, the usb connection in the back is encased in metal - arrows going to the box containing the usb sockets, and to the right/above the circular thingy I see USB139 written
I also see "LAN USB 1" centre-right
40hz:
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.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version