BSOD 0x00000124 after installing updated NVidia driver

Page 1 of 2 12 LastLast

  1. Posts : 19,383
    Windows 10 Pro x64 ; Xubuntu x64
       #1

    BSOD 0x00000124 after installing updated NVidia driver


    G'day,

    I've been experiencing some BSOD's every few hours. I suspect its related to having updated my NVidia card driver to Version 301.42 today. The driver was downloaded directly from the NVidia site after being prompted by the NVidia update utilty that one was available. I use an EVGA NVidia GTX 560 1024MB card.

    As an interim measure, I've uninstalled this driver, and let Windows Update find one for me.

    Could someone have a look at my DMP file and confirm that this driver was the issue, or whether there is something else going on?

    Thanks,
    Golden
      My Computer


  2. Posts : 1,442
    Windows 7 Professional 64bit
       #2

    I would install driver 296.10
    Do a clean install and only choose the driver and physx software (click advanced before install).
    The newest driver isn't always the best one.

    I have two EVGA GTX580's, no issues whatsoever with 296.10
      My Computer


  3. Posts : 11,269
    Windows 7 Home Premium 64 Bit
       #3

    That bugcheck typically means hardware, and it is one of the harder ones to debug since it gives little useful information as a minidump. If it is a driver, it does not indicate it. What is interesting is there seems to be a problem with your PSHED.dll file. My debugger then gives a message that I am not using the correct symbols. I wonder if I need the latest debugger that works with Windows 8.

    I'll look into doing another analysis with the newer debugger; mine is one version behind.


    Here is what I typically suggest for a 0x124 crash:
    writhziden said:

    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
    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 Computer


  4. Posts : 19,383
    Windows 10 Pro x64 ; Xubuntu x64
    Thread Starter
       #4

    Thanks writhzeden. What is PSHED.dll, or specifically why is that critical to the system? I'll look out for your updated analysis.

    In the meantime I'll leave this PC on overnight and see if I wake to reboot, or not?

    Regards,
    Golden
      My Computer


  5. Posts : 11,269
    Windows 7 Home Premium 64 Bit
       #5

    It is the Platform Specific Hardware Error Driver built into Windows. The newer version of the debugging tools gives me the same error with the symbols, which I basically expected. If that driver is corrupted as it says, it will interfere with analysis of the 0x124 crash and may actually be why you received that crash instead of something else. In other words, this may be a false positive, at least in the 0x124 sense.

    See if sfc /scannow picks up the file as corrupted: SFC /SCANNOW Command - System File Checker

    If not, it could just be a one time thing or it may be the .dmp file was corrupted when it was generated and is throwing off the debugger.
      My Computer


  6. Posts : 19,383
    Windows 10 Pro x64 ; Xubuntu x64
    Thread Starter
       #6

    Microsoft Windows [Version 6.1.7601]
    Copyright (c) 2009 Microsoft Corporation. All rights reserved.

    C:\Windows\system32>sfc /scannow

    Beginning system scan. This process will take some time.

    Beginning verification phase of system scan.
    Verification 100% complete.

    Windows Resource Protection did not find any integrity violations.

    C:\Windows\system32>
    I'll leave PC on overnight and see what I wake up to tommorrow.

    Thanks,
    Golden
      My Computer


  7. Posts : 11,269
    Windows 7 Home Premium 64 Bit
       #7

    Good news. I much prefer a corrupted .dmp file than a corrupted Windows system. Best of luck!
      My Computer


  8. Posts : 19,383
    Windows 10 Pro x64 ; Xubuntu x64
    Thread Starter
       #8

    OK. Its still BSOD'ing every 3 or 4 hours, so its not the NVidia driver.

    I'll start checking hardware.

    Regards,
    Golden
      My Computer


  9. Posts : 11,269
    Windows 7 Home Premium 64 Bit
       #9

    Eek! Sorry to see that, my friend. Let us know how the hardware tests pan out.
      My Computer


  10. Posts : 19,383
    Windows 10 Pro x64 ; Xubuntu x64
    Thread Starter
       #10

    Just ran 5 Standard runs on IBT = no problems, all pass, max temperature reached = 51.

    I'll do graphics card next.

    Regards,
    Golden
      My Computer


 
Page 1 of 2 12 LastLast

  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 09:47.
Find Us