BSOD - 7 x64 nvlddmkm.sys + dxgkrnl.sys + dxgmms1.sys

[mahiney]

A couple strange events lately, return to computer after having left it an hour or so and it seemed asleep, NO response what-so-ever, had to press reset button on the front. This has happened 3 times in a week. On reboot Windows tells me about recovering from unexpected shutdown, see at bottom.
Also, noticed when I turn on my printer then my keyboard has a mind of its own, won't type, instead the keys are making different windows open or new browser pages... and the mouse clicks weird too, will not deselect when selecting anything else (as tho I was holding the Control key), have to click on it again to deselect it. Restarting makes it all better. Doesn't seem right either that there should be so many start up thingies for the Epson 2200.
Every once in a while an open app will simply disappear, blip and its gone. Firefox especially does this, whole pages just vanish right before my eyes. (not printer related as far as I can tell)

The PerfMon report mentioned something about no anti-virus, but in fact I have MS SecEssentials.

I have dug around and hope that I don't have to do anything with the nVidia drivers, that is ALWAYS a major pain in the arse! Thinking I might need to do a system repair install? then update all the Windows Updates again... just did that a couple months ago tho. Is something having a little war in the Windows folder? Maybe someone can read all these files and have an answer, really admire that kind of techie!
Thanks so much for your time to look.

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.256.1
Locale ID: 1033

Additional information about the problem:
BCCode: 124
BCP1: 0000000000000000
BCP2: FFFFFA800BF535D8
BCP3: 0000000000000000
BCP4: 0000000000000000
OS Version: 6_1_7601
Service Pack: 1_0
Product: 256_1

Files that help describe the problem:
C:\Windows\Minidump\063012-14695-01.dmp
C:\Users\z\AppData\Local\Temp\WER-21886-0.sysdata.xml

 

[mahiney]

forgot the zip

here it is per rule about BSOD's
and my info:
Windows 7 x64
- installed OS on the system
- full retail version

- system built 3 years ago, new SSD
- OS new install 6/11

 

[writhziden]

Software Concerns:

Start Menu\Programs\Spybot - Search & Destroy	Public:Start Menu\Programs\Spybot - Search & Destroy	Public
Start Menu\Programs\SpywareBlaster	Public:Start Menu\Programs\SpywareBlaster	Public
Start Menu\Programs\TuneUp Utilities 2012	Public:Start Menu\Programs\TuneUp Utilities 2012	Public

• SpywareBlaster and Spybot Search and Destroy are not the best malware/spyware utilities. Take a look at http://www.sevenforums.com/system-s...-system-security-combination.html#post1732627 for better options.
  
  
• Many of us on the forums actually do not recommend automated optimization tools for Windows 7. Windows 7 does a much better job of handling its own optimization than its predecessors did. We especially do not recommend registry cleaning as an "optimization" step because automated registry cleaning causes more harm to the registry than it actually repairs.
  
  In the future, if you need help optimizing Windows 7, please post a thread in Performance & Maintenance - Windows 7 Forums or follow the tutorial enclosed in that forum to http://www.sevenforums.com/tutorial...ws-7-a.html?filter[2]=Performance Maintenance.

Analysis:

BugCheck 0x116

All of your crashes were DirectX/graphics card related. DirectX comes installed with Windows, so this may indicate Windows corruption. It may also be that you have corrupted drivers or a graphics card hardware problem.

• If you are overclocking any hardware, please stop.
  
  
• Check Windows for corruption. Run http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html up to three times to fix all errors with a restart in between each. Post back if it continues to show errors after a fourth run or if the first run comes back with no integrity violations. Use OPTION THREE of http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html to provide us with the sfcdetails.txt file if errors occur.

Follow the steps for Diagnosing basic problems with DirectX. To re-install your display card drivers as outlined in the DirectX link, use the following steps.

1. Download the drivers you want for your display card(s)
2. Click Start Menu
3. Click Control Panel
4. Click Uninstall a program
5. For NVIDIA:
   • Uninstall the NVIDIA Graphics Driver (this should uninstall all NVIDIA software and drivers)
   • Restart your computer
   • Make sure NVIDIA 3D Vision Driver, NVIDIA 3D Vision Video Player, NVIDIA HD Audio Driver, and NVIDIA PhysX System Software are not still listed under Uninstall a program through Control Panel
   • If any remain of the above, uninstall one at a time
   • If asked to restart after uninstalling any of the above, do so, and continue uninstalling any remaining NVIDIA items until all are removed
6. For AMD:
   • Uninstall AMD Catalyst Install Manager if it is listed (this should remove all AMD graphics software and drivers)
   • If AMD Catalyst Install Manager is not listed, use the following method to uninstall the graphics drivers (this applies to onboard graphics, as well):
     1. Click Start Menu
     2. Right Click My Computer/Computer
     3. Click Manage
     4. Click Device Manager from the list on the left
     5. Expand Display adapters
     6. Do the following for each adapter (in case you have multiple display cards)
        • Right click the adapter
        • Click Uninstall (do not click OK in the dialog box that pops up after hitting Uninstall)
        • Put a tick in Delete driver software for this device (if this option is available, otherwise just hit OK) and hit OK
     Alternatively:
     1. Login as an adminstrative user
     2. Click Start Menu
     3. Click Control Panel
     4. Click Hardware and Sound
     5. Click Device Manager (the last link under Devices and Printers)
     6. Expand Display adapters
     7. Do the following for each adapter (in case you have multiple display cards)
        • Right click the adapter
        • Click Uninstall (do not click OK in the dialog box that pops up after hitting Uninstall)
        • Put a tick in Delete driver software for this device (if this option is available, otherwise just hit OK) and hit OK
7. Restart your computer after uninstalling drivers for all display cards
8. Install the driver you selected for the display cards once Windows starts

Remember to try multiple versions of the graphics drivers, download them fresh, and install the freshly downloaded drivers.

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

Your crashes were all 0x116 Video TDR Error crashes:

• 
  

  These are all stop 0x116 VIDEO_TDR_FAILURE conditions.
  
  It's not a true crash, in the sense that the bluescreen was initiated only because the combination of video driver and video hardware was being unresponsive, and not because of any synchronous processing exception.
  
  Since Vista, the "Timeout Detection and Recovery" (TDR) components of the OS video subsystem have been capable of doing some truly impressive things to try to recover from issues which would have caused earlier OSs like XP to crash. As a last resort, the TDR subsystem sends the video driver a "please restart yourself now!" command and waits a few seconds. If there's no response, the OS concludes that the video driver/hardware combo has truly collapsed in a heap, and it fires off that stop 0x116 BSOD.
  
  If playing with video driver versions hasn't helped, make sure the box is not overheating. Try removing a side panel and aiming a big mains fan straight at the motherboard and GPU. Run it like that for a few hours or days - long enough to ascertain whether cooler temperatures make a difference. If so, it might be as simple as dust buildup and subsequently inadequate cooling.

  
  The above quote was taken from http://www.sevenforums.com/crashes-debugging/25912-bsod.html#post280172, which is linked to in usasma's thread about this error. Closely follow the first three posts of usasma's thread outlining http://www.sevenforums.com/crash-lo...op-0x116-video_tdr_error-troubleshooting.html and proceed through each step. Let us know if you need further help.

BugCheck 0x124

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.
  
  
• If you have an SSD, make sure the following are up to date:
  • SSD firmware
  • BIOS Version
  • Chipset Drivers
  • Hard disk controller drivers/SATA drivers
  • If you have a Marvell IDE ATA/ATAPI device, make sure the drivers are up to date from the Intel site or Marvell site and not from your motherboard/vendor support site.
  
  
• Run all but the advanced tests with SeaTools for HDDs.
  SeaTools for Windows
  
  SeaTools for DOS​
  
  
• 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.​

 

[mahiney]

Ok, thank you for all this info!
So no, not overclocking. Warantee, ha ha. And yes, my nVidia drivers probably could use an update, but like I said, what a huge pain that is, the worst driver updating there is, even with the special instructions. When Iever I was successful updating nVidia the new drivers seemed to really mess up the whole view (monitors - does it matter if they're like 7 years old?). I will have a go at it again tho, and let you know. Will get rid of those spyware stupids then.

I haven't been able to get my esata port to work for like a year, that wonderful Marvell driver, no matter what I've tried. Used the latest, used the internet fave version drivers, but it just continues to NOT hot-swap.

BIOS is the latest minus any updates only for newer mobo's. Always hard to tell if Intel Chipset is completely correct, seems to be a driver set that only likes to F6 at a new install. I've checked CPU temps with Real Temp, ok at 42-45C ? GPU is at 57C with Speccy. This machine is great in the winter, but makes ME too hot in the summer. The tower ventilation is pretty good, all the heat is under my desk!

I've run SFC recently with no info, but will run again. Will also read and run the other suggestions and certainly get back about it. Naturally I'm always suspicious of the SSD, being kind of new technology with some if-y rep in www, will check its firmware again. I really appreciate your time and insight, for sure! Soon...

 

[writhziden]

For the SSD, I have seen 0x124 crashes due to them when they are disappearing from the system due to a bad power state or corruption.

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