BSOD randomly - proper noob info included


  1. Posts : 1
    Windows 7 64bit
       #1

    BSOD randomly - proper noob info included


    Hey, I have an HPE-130f quadcore PC OEM Win 7 x64 tower that I had 2 get back to specs cause of a bad virus (1.5 yrs old, super clean still lookin new) - re-installed all my plugins & such, and with everything clean as sh*! & organized/defrag'd/all of it - she randomly shuts down & re-boots & gives me this:

    Problem signature:
    Problem Event Name: BlueScreen
    OS Version: 6.1.7600.2.0.0.768.3
    Locale ID: 4105

    Additional information about the problem:
    BCCode: 124
    BCP1: 0000000000000000
    BCP2: FFFFFA8008C457F8
    BCP3: 0000000000000000
    BCP4: 0000000000000000
    OS Version: 6_1_7600
    Service Pack: 0_0
    Product: 768_1

    Files that help describe the problem:
    C:\Windows\Minidump\051412-15568-01.dmp
    C:\Users\DZ\AppData\Local\Temp\WER-34835-0.sysdata.xml

    Read our privacy statement online:
    Windows 7 Privacy Statement - Microsoft Windows

    If the online privacy statement is not available, please read our privacy statement offline:
    C:\Windows\system32\en-US\erofflps.txt

    here is the BSOD required rar: Windows_NT6_BSOD_jcgriff2.rar

    this shit is driving me crazy any & all help is seriously appreciated!!
      My Computer


  2. Posts : 28,845
    Win 8 Release candidate 8400
       #2

    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).



    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 Computer


  3. JMH
    Posts : 7,952
    Win 7 Ultimate 64-bit. SP1.
       #3

    124 Error for desktops.

    {If you are at all uncomfortable don't do it.}


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


    Remove ALL power and reseat all cards, memory and cables (on both ends) - actually remove and replace - do not just snug.

    Make sure the system has adequate ventilation - add a small fan blowing into intakes.

    Carefully inspect the motherboard and other cards for damage.
    Pay attention to the fatal hardware error implication.You may need a real computer shop (not leeks and peeks at a BestBuy or other BigBox stores) or the System maker's Support.

    Check the processor seating, heat sink, and the compound between the processor and the heat sink which are common causes.

    There have been a few instances where Norton/Symantec and other antivirus/security programs have caused this error.

    BCCode: 124 0x00000124

    The WHEA_UNCORRECTABLE_ERROR bug check has a value of 0x00000124.
    This bug check indicates that a fatal hardware error has occurred.
    This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).

    0x00000124 <-- read this link
    The system encountered an uncorrectable hardware error.
      My Computer


 

  Related Discussions
Our Sites
Site Links
About 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 05:10.
Find Us