Solved BSOD 0x00000124 after installing updated NVidia driver

[Golden]

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

 

[HAVOC]

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

 

[writhziden]

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:

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. :warn:WARNING: The steps that follow can void your warranty!!!

For your hardware stop 0x124 crash, read through http://www.sevenforums.com/crash-lockup-debug-how/35349-stop-0x124-what-means-what-try.html 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.​
  • Real Temp is a good CPU temperature monitor.
  • Speccy - System Information - Free Download will monitor all hardware temperatures.
  • HWiNFO, HWiNFO32 & HWiNFO64 - Hardware Information and Analysis Tools can be inaccurate for CPU temperatures, but is a good program for GPU temperature monitoring.
  • Use FurMark: VGA Stress Test, Graphics Card and GPU Stability Test, Burn-in Test, OpenGL Benchmark and GPU Temperature | oZone3D.Net to test the graphics card GPU. Let it run until the GPU temperatures even out or until the GPU temperatures reach a dangerous level (you can find the max temperature for your card on either the nVidia or AMD sites; if you are not sure, ask us). The goal is to get a steady temperature, find out if the GPU is overheating, or to see if there are any artifacts present in the test itself: look for strange pixelated patterns on the screen or colors that do not look like they belong. Then use the |MG| Video Memory Stress Test 1.7.116 Download to test your graphics card memory. Let the memory test run for at least seven passes; the more the better.
    
    
  • Run http://www.sevenforums.com/tutorials/100352-hardware-stress-test-prime95.html to determine any hardware problems. Run all three tests for a few hours each. If you get errors, stop the test and post back here.
    
    
  • Follow the steps for doing CPU stress test using IntelBurnTest
  
  
• 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 http://www.sevenforums.com/crash-lockup-debug-how/35349-stop-0x124-what-means-what-try.html for the crash.

 

[Golden]

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

 

[writhziden]

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: http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html

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.

 

[Golden]

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

 

[writhziden]

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

 

[Golden]

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

I'll start checking hardware.

Regards,
Golden

 

[writhziden]

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

 

[Golden]

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

I'll do graphics card next.

Regards,
Golden

 

[writhziden]

You definitely have better cooling than I do on my system. Nice temperature.

FurMark is fairly easy to run and test with. There is actually a tutorial for it if you want to check it out: http://www.sevenforums.com/tutorials/100356-video-card-stress-test-furmark.html

The graphics memory test can take a while, so you may want to run that overnight.

Also, Vir Gnarus pointed out some more robust tests that can be run for graphics if you want to give them a go: Unigine: real-time 3D engine (game, simulation, visualization and VR).

 

[Golden]

Yep, I have the Corsair H60 water cooling kit, so CPU temps are well under control.

Just ran the Furmark 15min Burn-In test at 1920 x 1080 (my native resolution) - max temperature = 77. Didn't see any artifacts.

Going to check out the SSD and HDD's further. I did upgrade the firmware on the SSD from 1.25 to 1.35 about 3 days ago, but never received BSOD's during that time......I wonder if thats where the problem lies?

Regards,
Golden

 

[Golden]

Update : HDD activity light is on permanently with nothing untoward running in the background as far as I can tell. Just bad a black screen of detah - no blue screen this time.

I also managed to tease out some SMART data using the OCZ toolbox. Not sure if there is anything untoward here, apart from the 42 unexpected power losses.

SMART READ DATA

ModelNumber : OCZ-VERTEX2
Serial Number : OCZ-FR17KHHP129L3H40
WWN : 5-e8-3a-97 faafdc53f


Revision: 10
Attributes List
1: SSD Raw Read Error Rate Normalized Rate: 117 total ECC and RAISE errors
5: SSD Retired Block Count Reserve blocks remaining: 100%
9: SSD Power-On Hours Total hours power on: 5116
12: SSD Power Cycle Count Count of power on/off cycles: 609
171: SSD Program Fail Count Total number of Flash program operation failures: 0
172: SSD Erase Fail Count Total number of Flash erase operation failures: 0
174: SSD Unexpected power loss count Total number of unexpected power loss: 42
177: SSD Wear Range Delta Delta between most-worn and least-worn Flash blocks: 1
181: SSD Program Fail Count Total number of Flash program operation failures: 0
182: SSD Erase Fail Count Total number of Flash erase operation failures: 0
187: SSD Reported Uncorrectable Errors Uncorrectable RAISE errors reported to the host for all data access: 0
194: SSD Temperature Monitoring Current: 30 High: 30 Low: 30
195: SSD ECC On-the-fly Count Normalized Rate: 117
196: SSD Reallocation Event Count Total number of reallocated Flash blocks: 0
231: SSD Life Left Approximate SDD life Remaining: 95%
241: SSD Lifetime writes from host lifetime writes 1792 GB
242: SSD Lifetime reads from host lifetime reads 7360 GB

 

[writhziden]

Try doing a power cycle of the SSD. The following steps should be carried out and take ~1 hour to complete.

1. Power off the system.
2. Remove all power supplies (ac adapter then battery for laptop, ac adapter for desktop)
3. Hold down the power button for 30 seconds to close the circuit and drain all components of power.
4. Reconnect all power supplies (battery then ac adapter for laptop, ac adapter for desktop)
5. Turn on the system and enter the BIOS (see your manual for the steps to enter the BIOS)
6. Let the computer remain in the BIOS for 20 minutes.
7. Follow steps 1-3 and physically remove the SSD from the system by disconnecting the cables for a desktop or disconnecting the drive from the junction for a laptop.
8. Leave the drive disconnected for 30 seconds to let all power drain from it.
9. Do steps 1-3 and replace the drive connection(s) and then do steps 4-8 again.
10. Repeat steps 1-4.
11. Start your computer normally and run Windows.

The above steps were a result of: Why did my SSD "disappear" from my system? - Crucial Community

While that may not be your drive, a power cycle should be the same on all SSD drives. See how the system responds after the SSD power cycle.

 

[Golden]

OK. Just completed the power cycling, so we'll see what happens in about 3/4 hrs time.

When I entered the BIOS I realised why the HDD activity light was on permanently : the RAID1 is rebuilding itself, probably because of the BSOD. So, the HDD activity light is a red-herring regarding the original problem.

Regards,
Golden

 

[writhziden]

Thanks for the info about the HDD light. That makes sense. I still think the power cycle of the SSD may help with the firmware update and the unexpected power loss numbers. Hopefully it will also resolve the crashes.

 

[Golden]

I didn't want to talk too soon for fear of a jinx, but since my last post some 8hrs ago, this PC has been both idling, and been worked as normal, and so far.........cross-thumbs, toes and everything in between.........no....dare I say it.......BSOD or anything else untoward.

I can only put it down to the cycle thing, so definately keep that one handy
Lets now hope that soon as I press submit, the PC doesn't....you-know-what!

I'll leave it on overnight, and if its all good, I'll mark this as solved.

You've been a great help mate. Thanks.

Golden

 

[writhziden]

You're welcome. It was actually Brink who originally posted that link, and with all the problems occurring with SSDs on here, especially with people saying the SSD was often not showing up in the BIOS shortly after a crash, I added it to my repertoire.

Here is the original post by Brink:
http://www.sevenforums.com/hardware-devices/225487-ssd-not-showing-up-computer.html#post1889263

 

[Golden]

Well, after leaving in overnight both idling and doing a massive scheduled robocopy of all my user data, the PC seems absolutely rock solid, so I'll mark this as solved.

Thanks again writhziden.

 

[writhziden]

You're welcome. Glad to see it solved.