BSOD Help?

[f0rk_b0mb]

So, I've been getting this weird bsod now for the past few days. Does anybody else have this issue? How do I fix it?

 

[Xyphus]

You'll have to check the logs and see what caused the crashes...  I can try and help you with that tonight after work...

[LittleNeutrino Veteran]

The Stop 124 Error is Very Generic and inherently difficult to troubleshoot.

Windows passes on the hardware error report in the form of a "stop 0x124" because it can't do anything else once the hardware has signalled an uncorrectable fault condition. In technical terms, the vast majority of stop 0x124 crashes correspond to "Machine Check Exceptions" (MCEs) issued by the processor to alert the software to the existence of a hardware problem.

 

 

Troubleshooting steps. 

 

Check Drivers

Check for heat issues

Make sure you have the latest BIOS Version

If your computer has a hardware diagnostic tool as part of the main board run it.

run a chkdsk /r on the system

 

If you still have not found anything, try a clean install of windows (use a secondary hard drive if you can so you dont lose anything)

also you can try removing and reseating your hardware.

[Tews]

Your .dmp file is showing a general hardware 0x124 fault.  Stop 0x124 - what it means and what to try

Synopsis:

A "stop 0x124" is fundamentally different to many other types of bluescreens because it stems from a hardware complaint. Stop 0x124 minidumps contain very little practical information, and it is therefore necessary to approach the problem as a case of hardware in an unknown state of distress.


Generic "Stop 0x124" Troubleshooting Strategy:

1)

 Ensure that none of the hardware components are overclocked. Hardware that is driven beyond its design specifications - by overclocking - can malfunction in unpredictable ways.

2)

 Ensure that the machine is adequately cooled. If there is any doubt, open up the side of the PC case (be mindful of any relevant warranty conditions!) and point a mains fan squarely at the motherboard. That will rule out most (lack of) cooling issues.

3)

 Update all hardware-related drivers: video, sound, RAID (if any), NIC... anything that interacts with a piece of hardware. It is good practice to run the latest drivers anyway.

4)

 Update the motherboard BIOS according to the manufacturer's instructions. Their website should provide detailed instructions as to the brand and model-specific procedure.

5)

 Rarely, bugs in the OS may cause "false positive" 0x124 events where the hardware wasn't complaining but Windows thought otherwise (because of the bug). At the time of writing, Windows 7 is not known to suffer from any such defects, but it is nevertheless important to always keep Windows itself updated. 

6)

 Attempt to (stress) test those hardware components which can be put through their paces artificially. The most obvious examples are the RAM and HDD(s). For the RAM, use the in-built memory diagnostics (run MDSCHED) or the 3rd-party memtest86 utility to run many hours worth of testing. For hard drives, check whether CHKDSK /R finds any problems on the drive(s), notably "bad sectors". Unreliable RAM, in particular, is deadly as far as software is concerned, and anything other than a 100% clear memory test result is cause for concern. Unfortunately, even a 100% clear result from the diagnostics utilities does not guarantee that the RAM is free from defects - only that none were encountered during the test passes.

7)

 As the last of the non-invasive troubleshooting steps, perform a "vanilla" reinstallation of Windows: just the OS itself without any additional applications, games, utilities, updates, or new drivers - 

NOTHING AT ALL that is not sourced from the Windows 7 disc. 

Should that fail to mitigate the 0x124 problem, jump to the next steps. Otherwise, if you run the "vanilla" installation long enough to convince yourself that not a single 0x124 crash has occurred, start installing updates and applications slowly, always pausing between successive additions long enough to get a feel for whether the machine is still free from 0x124 crashes. Should the crashing resume, obviously the very last software addition(s) may be somehow linked to the root cause.

If stop 0x124 errors persist despite the steps above, and the harware is under warranty, consider returning it and requesting a replacement which does not suffer periodic MCE events. Be aware that attempting the subsequent harware troubleshooting steps may, in some cases, void your warranty:

8)

 Clean and carefully remove any dust from the inside of the machine. Reseat all connectors and memory modules. Use a can of compressed air to clean out the RAM DIMM sockets as much as possible.

9)

 If all else fails, start removing items of hardware one-by-one in the hope that the culprit is something non-essential which can be removed. Obviously, this type of testing is a lot easier if you've got access to equivalent components in order to perform swaps.

 

Should you find yourself in the situation of having performed all of the steps above without a resolution of the symptom, unfortunately the most likely reason is because the error message is literally correct - something is fundamentally wrong with the machine's hardware. 





 

[f0rk_b0mb]

The Stop 124 Error is Very Generic and inherently difficult to troubleshoot.

Windows passes on the hardware error report in the form of a "stop 0x124" because it can't do anything else once the hardware has signalled an uncorrectable fault condition. In technical terms, the vast majority of stop 0x124 crashes correspond to "Machine Check Exceptions" (MCEs) issued by the processor to alert the software to the existence of a hardware problem.

 

 

Troubleshooting steps. 

 

Check Drivers

Check for heat issues

Make sure you have the latest BIOS Version

If your computer has a hardware diagnostic tool as part of the main board run it.

run a chkdsk /r on the system

 

If you still have not found anything, try a clean install of windows (use a secondary hard drive if you can so you dont lose anything)

also you can try removing and reseating your hardware.

 

Yeah it's funny you mention the processor. I found this in the event viewer:

 

Event filter with query "SELECT * FROM __InstanceModificationEvent WITHIN 60 WHERE TargetInstance ISA "Win32_Processor" AND TargetInstance.LoadPercentage > 99" could not be reactivated in namespace "//./root/CIMV2" because of error 0x80041003. Events cannot be delivered through this filter until the problem is corrected.

 

I just recently upgraded my AMD x4 B50 to a x6 1045T. Does Windows not like me swapping those out? How can I correct this issue? I am running the latest BIOS and my board does support this processor. I looked in the manual and made sure.

[LittleNeutrino Veteran]

Yeah it's funny you mention the processor. I found this in the event viewer:

 

Event filter with query "SELECT * FROM __InstanceModificationEvent WITHIN 60 WHERE TargetInstance ISA "Win32_Processor" AND TargetInstance.LoadPercentage > 99" could not be reactivated in namespace "//./root/CIMV2" because of error 0x80041003. Events cannot be delivered through this filter until the problem is corrected.

 

I just recently upgraded my AMD x4 B50 to a x6 1045T. Does Windows not like me swapping those out? How can I correct this issue? I am running the latest BIOS and my board does support this processor. I looked in the manual and made sure.

The swap can actually be the problem, i went from an x2 to an x6 and i had to upgrade the bios on my motherboard to work with it.

[f0rk_b0mb]

The swap can actually be the problem, i went from an x2 to an x6 and i had to upgrade the bios on my motherboard to work with it.

 

I have this mobo: http://www.asus.com/Motherboards/M4N98TD_EVO/

 

I have the most recent 1301 BIOS.

[sc302 Veteran]

Can you monitor your temps when you blue screen?

 

If you are contemplating a reformat, instead of a reformat, you could try to do a sysprep /generalize to see if it fixes your issue.  This will reset the hardware configuration in windows 7 to default and force a redetect of the hardware at next boot.  You can only do this 3 times, then the generalize fails.  Do this instead of formating and reinstalling windows, this will save you from reinstalling your software.

[f0rk_b0mb]

Can you monitor your temps when you blue screen?

 

If you are contemplating a reformat, instead of a reformat, you could try to do a sysprep /generalize to see if it fixes your issue.  This will reset the hardware configuration in windows 7 to default and force a redetect of the hardware at next boot.  You can only do this 3 times, then the generalize fails.  Do this instead of formating and reinstalling windows, this will save you from reinstalling your software.

 

Thanks I will keep that in mind if worse comes to worse. I'll probably let my friend Xyphus take a look at everything first. 

[f0rk_b0mb]

Well, my ram passed a memtest. I also cleaned up my case a bit and made sure everything was making good contact. I'm still bsoding tho. :(