machine_check_exception then disk error

aardvark · 22 Apr 2006 at 13:32

probably not the right forum but....
i had my pc on last night but when i woke up there was a blue screen of death and a machine_check_exception error.

after a reset it was fine.... for a few hours, when the bsod suddenly appeared and on reseting i got a disk read error.
i opened the case and jiggled the connections (sata) around and now its turned on fine.

do you think this is something to worry about??
i've never had one of those errors before.

cheers

SiriusB · 22 Apr 2006 at 15:20

MACHINE_CHECK_EXCEPTIONs happen when your CPU and/or Windows determines that a piece of important hardware aint doing its job properly.

This could be iffy memory, dodgy mobo, power fluctuations because of a faulty PSU... all sorts. I have seen no specific mention of HDDs causing this error, but the disk error you got would suggest it was the cause.

It could be as simple as a cable coming loose so your jiggling may have solved it. If it happens again you may want to check the cables, maybe even buy some replacements to be sure.

If that doesnt work it could be your HDD, or as said, another important piece of hardware.

SiriusB

aardvark · 22 Apr 2006 at 15:39

thanks, i'll have to watch it.

maybe it was the loose connection -i was panicing for a while.

maybe i'll get some better sata conectors - i'm still using the ones that came with the motherboard.

SiriusB · 22 Apr 2006 at 21:38

I would think it was a loose cable. However, a good check to see if the cable is faulty is to turn your PC on, boot into Windows then move the SATA cables around and see if anything unfortunate happens

If not, odds are cables are fine.

SiriusB

acharris · 23 Apr 2006 at 00:40

Hi, I would say watch as it could be a intermittent HD failure. I had this on a maxtor drive and sometimes it would go weeks, sometime days or a few hours. Mostly mine happened at idle and not when in use, only when the HD became really faulty did it show once installing a game, but otherwise no sign of failure on the HD.

Jonesiani · 23 Apr 2006 at 11:34

I had this exact problem, and after spending hour and hours testing all my components, the whole problem bioled down to a dodgy seagate harddrive sent to me by another websire that i never buy from anymore

After getting a replacement all my problems vanished.

aardvark · 23 Apr 2006 at 12:04

i think it was a loose cable - nothing bad has happened so far since i 'jiggled' the cables (thats a technical term) and its not a new pc or anything.

the drive health program i have says everythings fine (don't know how reliable that is though)
i'll certainly be making backups often!

kutmasta · 24 Apr 2006 at 21:03

i whacked my pc once by accident when i was moving it, and when i turned it on i got this error

but it didnt happen again

smsmasters · 12 May 2007 at 10:31

I got this problem about twice at totally random times. Once when playing CS:S and once when just at idle.

When I rebooted the computer my hard drive was not detected. I had to unplug and replug the sata connector and power connector a few times till it was detected. I'm not really sure why this happens... :mad: