Windows 7 Forums
Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: Random reboot, bugcheck 124


16 May 2012   #1

Win7 Ult x64
 
 
Random reboot, bugcheck 124

I really have no clue why this is happening. Haven't really changed any hardware recently (except for a new mouse).
Does not happen often, happened about 3 times a couple of weeks ago and i thought it was gone. Just today it happened two times in a row.
Not load related since it happens while browsing or not really doing anything.
Attached sysdata and two minidumps (just in case) from these last two crashes.
And i obviously saw the "DO THIS BEFORE POSTING" after posting. Fixing files in a sec.
Done Fixed again, sorry about the mess. Bad day + 1 AM + computer crashes..not a good mix.


My System SpecsSystem Spec
.

16 May 2012   #2

Microsoft Community Contributor Award Recipient

Microsoft Windows 7 Home Premium 64-bits 7601 Multiprocessor Free Service Pack 1
 
 

My System SpecsSystem Spec
16 May 2012   #3

Microsoft Community Contributor Award Recipient

Microsoft Windows 7 Home Premium 64-bits 7601 Multiprocessor Free Service Pack 1
 
 

Quote   Quote: Originally Posted by keth View Post
I really have no clue why this is happening. Haven't really changed any hardware recently (except for a new mouse).
Does not happen often, happened about 3 times a couple of weeks ago and i thought it was gone. Just today it happened two times in a row.
Not load related since it happens while browsing or not really doing anything.
Attached sysdata and two minidumps (just in case) from these last two crashes.
And i obviously saw the "DO THIS BEFORE POSTING" after posting. Fixing files in a sec.
Done
please post bsod info http://www.sevenforums.com/crashes-d...tructions.html

Resplendence Software - WhoCrashed, automatic crash dump analyzer
My System SpecsSystem Spec
.


16 May 2012   #4

Win7 Ult x64
 
 

The original post has the proper files now. You posted that right as i was reuploading.
My System SpecsSystem Spec
16 May 2012   #5

Win 8 Release candidate 8400
 
 

Stop 0x124 is a hardware error

If you are overclocking try resetting your processor to standard settings and see if that helps.

If you continue to get BSOD here are some more things you may want to consider.

This is usually heat related, defective hardware, memory or even processor though it is"possible" that it is driver related (rare).



Quote:
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.
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.



Stop 0x124 - what it means and what to try
My System SpecsSystem Spec
17 May 2012   #6

Win7 Ult x64
 
 

Not overclocking, and i've read those steps before. Already did everything short of reinstalling windows. As for removing hardware..i don't really have anything no essential to remove, and considering that this doesn't happen often it would be hard to track. I just hoped that the dumps would give at least some sort of useful information.
My System SpecsSystem Spec
17 May 2012   #7

Win 8 Release candidate 8400
 
 

Quote   Quote: Originally Posted by keth View Post
Not overclocking, and i've read those steps before. Already did everything short of reinstalling windows. As for removing hardware..i don't really have anything no essential to remove, and considering that this doesn't happen often it would be hard to track. I just hoped that the dumps would give at least some sort of useful information.
There are ways to stress the hardware and software if you are interested.
My System SpecsSystem Spec
17 May 2012   #8

Win7 Ult x64
 
 

Quote   Quote: Originally Posted by zigzag3143 View Post
There are ways to stress the hardware and software if you are interested.
So i assume the files don't help with anything?
As for stress testing, i'm up for that as long as it wont make things worse.
My System SpecsSystem Spec
19 May 2012   #9

Windows 7 Home Premium 64 Bit
 
 

It is difficult to remotely debug a 0x124 crash since it is most often hardware related. Without having the system in front of us, it is impossible to determine which hardware is failing, so we have to give instructions to the owner of the system to determine the cause of the crashes.

Here is what I generally give for these types of crashes:
Quote   Quote: Originally Posted by writhziden View Post
You have a 0x124 hardware bugcheck. If the system is still under warranty, I would recommend sending it in to have diagnostic tests done and any bad hardware replaced.
warning   Warning
Before you proceed with the following, answer these two questions: Are you still under warranty? Does your warranty allow you to open up the machine to check hardware? If you are unsure of the answers to these questions, contact your system manufacturer. WARNING: The steps that follow can void your warranty!!!



For your hardware stop 0x124 crash, read through Stop 0x124 - what it means and what to try and use the following hardware checks to supplement that link.
  • If you are overclocking any hardware, please stop.

  • Monitor temperatures during the following tests.
    Use the following programs to monitor the temperatures.
  • Run the boot version of Memtest86+ paying close attention to Parts 2 and 3 of the tutorial. Also, in case Memtest86+ misses anything and comes up with no errors, run the extended version of the Windows Memory Diagnostics Tool for at least five passes. These you may want to run overnight since they take a long time to complete (run them an hour before bed each of the next two nights and check before going to sleep that they are still running).

    For Part 3: If You Have Errors: If you swap any memory components, follow these steps for ESD safety:
    1. Shut down and turn off your computer.
    2. Unplug all power supplies to the computer (AC Power then battery for laptops, AC power for desktops)
    3. Hold down the power button for 30 seconds to close the circuit and ensure all power drains from components.
    4. Make sure you are grounded by using proper grounding techniques, i.e. work on an anti-static workbench, anti-static desk, or an anti-static pad. Hold something metallic while touching it to the anti-static surface, or use an anti-static wristband to attach to the anti-static material while working. If you do not have an anti-static workbench, desk, or pad, you can use your computer tower/case by finding a metal hold in it, such as a drive bay.
    Once these steps have been followed, it is safe to remove and replace components within your computer.

Remember to read closely through Stop 0x124 - what it means and what to try for the crash.
My System SpecsSystem Spec
Reply

 Random reboot, bugcheck 124




Thread Tools



Similar help and support threads for2: Random reboot, bugcheck 124
Thread Forum
BSOD Random event, multiple times, Bugcheck reboot 0x000000e1 BSOD Help and Support
Random BSOD: The computer has rebooted from a bugcheck. BSOD Help and Support
Win7 x64 Random BSOD's, different bugcheck codes BSOD Help and Support
Random crashes, bugcheck 0x0000009F BSOD Help and Support
Reboot from bugcheck BSOD Help and Support
[REBOOT] Sudden Random Reboot and black screen at start up! BSOD Help and Support
Computer Freezing. Bugcheck reboot 0x00000124 BSOD Help and Support

Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd

All times are GMT -5. The time now is 08:43 PM.
Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App
  

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33