Windows 7: BSOD stop 124... please make it stop

Hi again, I appreciate all prior posts and will make this one fast. The BSOD for me occours primarily after i start up my computer. Itll run for a few minutes and then do its BSOD stop 124 thing and then run fine for days unless i reboot it and leave it off for any period of time. I could repost the dump files but no ones gotten anything out of them before except usama who told me to update a chipset which i did and it still dumps. Yes i did the ram thing too with no luck. Like i said above it runs fine unless its off for a while then it reboots. Ive also run the burnin test and put the components through torture tests to try and get a hardware device to fail no luck though. Please save my computer.

Have you looked at this? http://www.sevenforums.com/crash-loc...-what-try.html


Ken

... yes i have but contrary to popular belief taking apart your computer that you didnt build is not with in everyones skill level. I am simply curious as to wether the fact that my comp does this once shortly after start up identifies anything...


Trust me for those of us having this persistant problem we have probly read everything out there if this fact doesnt identify anything to you thats fine i was just hoping someone may of had this same problem and found the cause. The fact that a torture test on my ram has not caused a failure seems to indicate its working fine. My video cards were also tested like that and had nothing as with the cpu as well. Drivers are all up to date and no one can tell me if my motherboard has a built in overclock mode that may be causing this problem on start up.

A STOP 0x124 error is a hardware error - reported to Windows by your CPU.
As such it doesn't show any specifics about the error.

You either have broken hardware - or incompatible hardware/software/drivers
I say that corrupted drivers can cause this - but not all analysts agree with me on that.

The only clues were in your dump files - and that was the age of your chipset drivers (which weren't that old, but they were the only thing that I could find fault with).

So, unfortunately, you're at the point where someone's going to have to rip the computer apart. If you aren't up to it, then you're going to have to find someone who's capable of doing it.

My BSOD was caused by having a Seagate HDD and two WesternDigital HDD in the same computer...I removed the seagate , put it in a usb case and now all ok, bill also called around a week later and droped off some updates but i think the main problem was the two different drives....sata 0 WD, sata1 WD, sata3 Seagate.

BlaDe Hi and welcome

Just an FYI. This thread is about 6 months old and there isnt going to be much traffic to read your solution. I do thank you for letting us know about it however.


Again welcome

Ken