none
BSOD Daily RRS feed

  • Question

  • Hi, I have a win 7 x64 machine that is getting daily BSOD's and I can't figure it out.  Also can't read dump files.  Wondering if someone might be able to shed some light on it for me.  Here is my dump file:

    http://speedy.sh/WgZh6/072213-55193-01.dmp

    Thanks in advance for any help!

    Monday, July 22, 2013 4:38 PM

Answers

  • Hi Ronowicker,

    The BSOD can be caused by 3rd part program or driver conflict, or  corrupted system components or files.

    In order to narrow down the issue, please help to clarify following questions and do some test:

    1. Did you install some updates both for windows and other software on your computer?
    2. Did you upgrade or install any hardware before this issue occurred?

    Regarding current situation, I suggest that we do following test to see if the issue persists:

    To test in Clean boot mode:

    How to perform a clean boot to troubleshoot a problem in Windows 8, Windows 7, or Windows Vista

    http://support.microsoft.com/kb/929135

    Note After clean boot troubleshooting, please follow steps under “How to reset the computer to start as usual after clean boot troubleshooting” in above article.

    To test in Safe Mode:

    Start your computer in safe mode:

    http://windows.microsoft.com/en-us/windows/start-computer-safe-mode#start-computer-safe-mode=windows-7

    Please let me know your testing results and we can move toward a solution.

    Keep post.


    Best Regards, StarSprite


    Tuesday, July 23, 2013 8:19 AM

All replies

  • Ronowicker

    90% of the time this is a hardware issue but since it is so much easier I would remove Symantec and update the below drivers before investigating the hardware

    Symantec  is a frequent cause of BSOD's.  

    I would remove and replace it with Microsoft Security Essentials AT LEAST TO TEST
    http://us.norton.com/support/kb/web_view.jsp?wv_type=public_web&docurl=20080710133834EN

    Drivers

    lmimirr.sys    4/10/2007 6:32:45 PM                     
    adfs.SYS    6/26/2008 4:52:37 PM                          
    LMIRfsDriver.sys    7/14/2008 12:26:56 PM   
    atikmdag.sys    4/24/2009 6:51:57 AM  
    PxHlpa64.sys    6/23/2009 7:16:35 PM   
    lmimirr.sys    4/10/2007 6:32:45 PM                        
    adfs.SYS    6/26/2008 4:52:37 PM                          
    LMIRfsDriver.sys    7/14/2008 12:26:56 PM  
    atikmdag.sys    4/24/2009 6:51:57 AM  
    PxHlpa64.sys    6/23/2009 7:16:35 PM   

    How To Find Drivers:


    Search
     Google for the name of the driver
    Compare the Google results with what's installed on your system to figure out which device/program it belongs to
    Visit the web site of the manufacturer of the hardware/program to get the latest drivers (DON'T use Windows Update or the Update driver function of Device Manager).
    If there are difficulties in locating them, post back with questions and someone will try and help you locate the appropriate program

    The most common drivers are listed on these pages: 
    http://www.carrona.org/dvrref.php
    http://sysnative.com/drivers/

    Driver manufacturer links are on this page: http://www.carrona.org

    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 BSODs 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 3rd-party memtest86 utility to run many hours worth of testing. (6-8 passes to stress the ram out)
    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 hardware is under warranty, consider returning it and requesting a replacement which does not suffer periodic MCE events.
    Be aware that attempting the subsequent hardware 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.


    BugCheck 124, {0, fffffa8004fad028, f605c000, 145}
    Probably caused by : AuthenticAMD


    Wanikiya & Dyami--Team Zigzag

    Monday, July 22, 2013 5:00 PM
    Moderator
  • Hi Ronowicker,

    The BSOD can be caused by 3rd part program or driver conflict, or  corrupted system components or files.

    In order to narrow down the issue, please help to clarify following questions and do some test:

    1. Did you install some updates both for windows and other software on your computer?
    2. Did you upgrade or install any hardware before this issue occurred?

    Regarding current situation, I suggest that we do following test to see if the issue persists:

    To test in Clean boot mode:

    How to perform a clean boot to troubleshoot a problem in Windows 8, Windows 7, or Windows Vista

    http://support.microsoft.com/kb/929135

    Note After clean boot troubleshooting, please follow steps under “How to reset the computer to start as usual after clean boot troubleshooting” in above article.

    To test in Safe Mode:

    Start your computer in safe mode:

    http://windows.microsoft.com/en-us/windows/start-computer-safe-mode#start-computer-safe-mode=windows-7

    Please let me know your testing results and we can move toward a solution.

    Keep post.


    Best Regards, StarSprite


    Tuesday, July 23, 2013 8:19 AM