Windows 7 Forums
Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.

Windows 7: BSOD ten minutes after starting games, now crash after driver update

13 Jun 2015   #1

Windows Home Premium 64bit
BSOD ten minutes after starting games, now crash after driver update

Hello, everyone. I just got back to my PC after a my first year of college, and when I first started it up it bluescreened. I didn't manage to catch the error before it rebooted, then changed to a black screen said that there was no hard disk to boot with.
So I turned it off, turned it back on, and it booted just fine. I ran a full system scan with Avast to check for malware, updated some games on Steam, and basically did my best to get my computer up to speed since it had been off for so long (while I did use it during long breaks). While the Avast scan was running I played World of Warcraft for about an hour or two, and bam--another bluescreen. The error message said something along the lines of "Display drivers failed to restart," but again I couldn't catch the rest because it rebooted, coming up with the same black screen as before. So I turned it off.
When I booted it up for a third time Avast opened almost immediately and asked to restart my computer and run a scan of the startup files. So I obliged; it seemed like it scanned my whole system again, which lasted for an hour or two, and it seems like it moved Malwaregen and corrupted files to the chest. When it was done my computer booted normally. I installed some Windows updates and a new Nvidia driver, figuring that something was outdated, and once again started playing World of Warcraft. This time it didn't bluescreen; instead, the screen froze after ten minutes and turned a solid color. My PC rebooted almost immediately, again with the same black screen.
So I rebooted for a fourth time, just fine like before, and ran a disk check to find errors in my hard drive. None were found, so I don't think it's a hardware problem. Seems like a graphics driver issue, but I'm not sure of that and even if I were I wouldn't know how to fix it.

I changed some .dmp files settings and replicated the error with Team Fortress 2, so now I have a .dmp file and the typical package in the attachments. The first attachment is the DM Log Collector file, and the second is the .dmp file.

Thanks in advance, folks!
My System SpecsSystem Spec
14 Jun 2015   #2

Microsoft Community Contributor Award Recipient

Microsoft Windows 10 Pro Insider Preview 64-bit

Try any other driver version and see how it goes. Uninstall the installed display driver using Display Driver Uninstaller. Then install the NVIDIA DRIVERS GeForce Game Ready Driver WHQL

When done, stress test the Graphics Card using Furmark.
Video Card - Stress Test with Furmark
Take a screenshot of the furmark window before closing it. Upload the screenshot for us. Also let us know if you have experienced any crash/BSOD and/or artifacts during the test.

Also, Is the computer hot? Report us the heat of the computer after a couple of hours of your normal usage. Upload a screenshot of the summery tab of Speccy. Alternatively, you can publish a Speccy snapshot too: Speccy - Publish Snapshot of your System Specs .
BugCheck 116, {fffffa80081ba4e0, fffff88005055ad4, ffffffffc000009a, 4}

*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : nvlddmkm.sys ( nvlddmkm+82fad4 )

Followup: MachineOwner

3: kd> !analyze -v
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *

Attempt to reset the display driver and recover from timeout failed.
Arg1: fffffa80081ba4e0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff88005055ad4, The pointer into responsible device driver module (e.g. owner tag).
Arg3: ffffffffc000009a, Optional error code (NTSTATUS) of the last failed operation.
Arg4: 0000000000000004, Optional internal context dependent data.

Debugging Details:

fffff880`05055ad4 48ff25e5f1ebff  jmp     qword ptr [nvlddmkm+0x6eecc0 (fffff880`04f14cc0)]






ANALYSIS_VERSION: 6.3.9600.17336 (debuggers(dbg).150226-1500) amd64fre

fffff880`06f8fa48 fffff880`05346134 : 00000000`00000116 fffffa80`081ba4e0 fffff880`05055ad4 ffffffff`c000009a : nt!KeBugCheckEx
fffff880`06f8fa50 fffff880`05319867 : fffff880`05055ad4 fffffa80`096ce000 00000000`00000000 ffffffff`c000009a : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`06f8fa90 fffff880`05345f43 : fffffa80`ffffd846 ffffffff`fffe7960 fffffa80`081ba4e0 00000000`00000000 : dxgkrnl!DXGADAPTER::Reset+0x2a3
fffff880`06f8fb40 fffff880`0406f03d : fffffa80`0c03fb50 00000000`00000080 00000000`00000000 fffffa80`09105410 : dxgkrnl!TdrResetFromTimeout+0x23
fffff880`06f8fbc0 fffff800`03566456 : 00000000`0641db0e fffffa80`090ed760 fffffa80`06992b10 fffffa80`090ed760 : dxgmms1!VidSchiWorkerThread+0x101
fffff880`06f8fc00 fffff800`032be2c6 : fffff800`0344be80 fffffa80`090ed760 fffff800`03459cc0 00000000`00000001 : nt!PspSystemThreadStartup+0x5a
fffff880`06f8fc40 00000000`00000000 : fffff880`06f90000 fffff880`06f8a000 fffff880`1ecfed40 00000000`00000000 : nt!KxStartSystemThread+0x16

STACK_COMMAND:  .bugcheck ; kb

fffff880`05055ad4 48ff25e5f1ebff  jmp     qword ptr [nvlddmkm+0x6eecc0 (fffff880`04f14cc0)]

SYMBOL_NAME:  nvlddmkm+82fad4

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys


FAILURE_BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys

BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys


FAILURE_ID_HASH_STRING:  km:x64_0x116_image_nvlddmkm.sys

FAILURE_ID_HASH:  {1f9e0448-3238-5868-3678-c8e526bb1edc}

Followup: MachineOwner

3: kd> lmvm nvlddmkm
start             end                 module name
fffff880`04826000 fffff880`052e9000   nvlddmkm T (no symbols)           
    Loaded symbol image file: nvlddmkm.sys
    Image path: nvlddmkm.sys
    Image name: nvlddmkm.sys
    Timestamp:        Thu May 28 08:19:51 2015 (5566824F)
    CheckSum:         00A7E4BD
    ImageSize:        00AC3000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
My System SpecsSystem Spec

Thread Tools

Similar help and support threads
Thread Forum
BSOD After Driver Update CRASH nVidia GTX970, Safe mode works
I first had a random crash, i suspected because too many usb devices had been plugged in. Then another crash during driver update (Nvidia GTX 970). Getting BSOD of different titles a few seconds after login ever since, sometimes immediately after one or two startup programms crash since. ...
BSOD Help and Support
Driver problem? All my games crashes after 30 minutes!
Hello there, this happened for a while ago. I have two games, GTA IV and CrossFire. (One steam and one client.) In both those games, it crashes. Normally around 30 minutes. It closes, and I get redirected to the desktop, no errors, nothing. Do anyone know what to do? Please help me here. Im...
BSOD While starting games and updating video card driver
Hi, Just a few weeks ago i started getting random BSOD issues, what is strange is that it doesn't happen with all games, i can play World of Warcraft fine but games like Sims 3 and Counter Strike screw me over and also trying to update my graphics drivers makes me BSOD. My knowledge when it...
BSOD Help and Support
Bsod - 5 minutes after starting Skyrim driver-irql-not-less-or-equal
Hey guys, So I've been having this problem for quite some time now, it started a while back with a game called 'Prototype' and since then every BIG game I play gives me BSOD with the driver irql message. Now I would really like to get this solved but I am just a complete idiot when it comes to...

Our Sites

Site Links

About Us

Find 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 10:16.
Twitter Facebook