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 After bootup. No new hardware - Driver issue?

14 Aug 2014   #1
jon0507

windows home premuim 64bit
 
 
BSOD After bootup. No new hardware - Driver issue?

Happened about 20 seconds after logging in, no idea why, maybe it was something i downloaded? Ive run malwarebytes, MSSE, all clear

can someone help identify the problem?

Thanks in advance, you guys are lifesavers!


My System SpecsSystem Spec
.
14 Aug 2014   #2
Arc

Microsoft Community Contributor Award Recipient

Microsoft Windows 10 Pro Insider Preview 64-bit
 
 

What about the network adapter issue? You did not responded there. I think you should have marked that one as solved before starting a new discussion.
Seemingly random BSOD - PFN list corrupt

This time it is a display issue. And the display driver is the latest, 340.52 WHQL.

Stress test the Graphics Card using Furmark.
Video Card - Stress Test with Furmark
Take the 15 minutes benchmark test.

Check if the Power Supply Unit (PSU) supplying adequate power to the computer or not.
eXtreme Power Supply Calculator
Also let us know the wattage of the PSU.

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 .

Let us know the results.
_______________________________________
Code:
BugCheck 116, {fffffa800b6b3010, fffff8800f5c193c, 0, 2}

*** 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+15393c )

Followup: MachineOwner
---------

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

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

Debugging Details:
------------------


FAULTING_IP: 
nvlddmkm+15393c
fffff880`0f5c193c 48ff256d6d7200  jmp     qword ptr [nvlddmkm+0x87a6b0 (fffff880`0fce86b0)]

DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT

CUSTOMER_CRASH_COUNT:  1

BUGCHECK_STR:  0x116

PROCESS_NAME:  System

CURRENT_IRQL:  0

ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre

STACK_TEXT:  
fffff880`029c71c8 fffff880`10159134 : 00000000`00000116 fffffa80`0b6b3010 fffff880`0f5c193c 00000000`00000000 : nt!KeBugCheckEx
fffff880`029c71d0 fffff880`10158e3e : fffff880`0f5c193c fffffa80`0b6b3010 fffffa80`0b60fa60 fffffa80`0a4c8410 : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`029c7210 fffff880`0f40ff13 : fffffa80`0b6b3010 00000000`00000000 fffffa80`0b60fa60 fffffa80`0a4c8410 : dxgkrnl!TdrIsRecoveryRequired+0x1a2
fffff880`029c7240 fffff880`0f43ded6 : fffffa80`ffffffff 00000000`0000523b fffff880`029c7390 00000000`00000005 : dxgmms1!VidSchiReportHwHang+0x40b
fffff880`029c7320 fffff880`0f423ce9 : fffffa80`0a4ea000 ffffffff`feced300 00000000`00000005 fffff880`0f55852a : dxgmms1!VidSchWaitForCompletionEvent+0x196
fffff880`029c7360 fffff880`0f426be7 : 00000000`00000001 00000000`00000000 fffffa80`0b606010 fffff8a0`09e05250 : dxgmms1!VIDMM_GLOBAL::xWaitForAllEngines+0x1e9
fffff880`029c7460 fffff880`0f4252d8 : fffff8a0`09e05250 00000000`00000000 fffffa80`0a4ea000 00000004`00000005 : dxgmms1!VIDMM_GLOBAL::SetupForBuildPagingBuffer+0xd7
fffff880`029c74a0 fffff880`0f42522e : 00000000`00000000 00000000`00000001 fffffa80`0a4ea000 fffff880`0f423b56 : dxgmms1!VIDMM_GLOBAL::UnmapVideoApertureSegmentInternal+0x34
fffff880`029c7630 fffff880`0f42e77e : fffffa80`0a2cb930 00000000`00000001 00000000`00000001 00000000`00000000 : dxgmms1!VIDMM_GLOBAL::UnmapVideoApertureSegment+0x13e
fffff880`029c76a0 fffff880`0f42e527 : fffff8a0`09e05250 00000000`00001000 fffffa80`0a2cb930 fffff8a0`09e05250 : dxgmms1!VIDMM_APERTURE_SEGMENT::UnmapApertureRange+0x7a
fffff880`029c76f0 fffff880`0f42decb : fffff8a0`09e05250 fffffa80`0a4eac80 00000000`00000000 fffffa80`0a4eac80 : dxgmms1!VIDMM_APERTURE_SEGMENT::UnmapTemporaryResource+0x9b
fffff880`029c7750 fffff880`0f4218a4 : fffffa80`0a4ea000 fffffa80`0a4ea000 fffffa80`0a4eac80 fffffa80`0a4ea000 : dxgmms1!VIDMM_APERTURE_SEGMENT::ReleaseTemporaryResource+0xcf
fffff880`029c7790 fffff880`0f41e257 : 00000000`c0000001 00000000`00000000 00000000`0000000d fffffa80`0a4ea000 : dxgmms1!VIDMM_GLOBAL::EvictTemporaryAllocations+0xbc
fffff880`029c77d0 fffff880`0f4387d9 : 00000000`00000000 fffff8a0`09be2480 fffffa80`00000000 fffffa80`0b563dc0 : dxgmms1!VIDMM_GLOBAL::PrepareDmaBuffer+0x69f
fffff880`029c79a0 fffff880`0f438514 : fffff880`03369f40 fffff880`0f437f00 fffffa80`00000000 fffffa80`00000000 : dxgmms1!VidSchiSubmitRenderCommand+0x241
fffff880`029c7b90 fffff880`0f438012 : 00000000`00000000 fffffa80`0b60fa60 00000000`00000080 fffffa80`0a4c8410 : dxgmms1!VidSchiSubmitQueueCommand+0x50
fffff880`029c7bc0 fffff800`0336273a : 00000000`00a625ab fffffa80`0a2cab50 fffffa80`066769e0 fffffa80`0a2cab50 : dxgmms1!VidSchiWorkerThread+0xd6
fffff880`029c7c00 fffff800`030b78e6 : fffff880`03365180 fffffa80`0a2cab50 fffff880`0336ffc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`029c7c40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_IP: 
nvlddmkm+15393c
fffff880`0f5c193c 48ff256d6d7200  jmp     qword ptr [nvlddmkm+0x87a6b0 (fffff880`0fce86b0)]

SYMBOL_NAME:  nvlddmkm+15393c

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  53b4446a

FAILURE_BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys

BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:x64_0x116_image_nvlddmkm.sys

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

Followup: MachineOwner
---------

2: kd> lmvm nvlddmkm
start             end                 module name
fffff880`0f46e000 fffff880`100fc000   nvlddmkm T (no symbols)           
    Loaded symbol image file: nvlddmkm.sys
    Image path: \SystemRoot\system32\DRIVERS\nvlddmkm.sys
    Image name: nvlddmkm.sys
    Timestamp:        Wed Jul 02 23:12:02 2014 (53B4446A)
    CheckSum:         00C4C7C9
    ImageSize:        00C8E000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
My System SpecsSystem Spec
14 Aug 2014   #3
jon0507

windows home premuim 64bit
 
 

Ran furmark, it was fine, it did say the gpu was using up to 119% power? Also the gpu was happy to let it reach 80c with the fan speed only at 50% (i know thats still within safe bounds, but a little hot for my liking) so i increased the fan speed via afterburner and ran it again, the fan speed at 70%, temp maxed at 69c,

PSU is a corsair cx 600, nothing is overclocked, temps all seem fine, ive never noticed the pc getting hot before, there are 4 case fans.

On the power calculator i added everything i could find, psu power didnt make it to 400w

I regularly switch displays between my monitor and an on-screen graphics tablet, dont know if that would affect anything?

EDIT: As for the network drivers, i have been using an Ethernet cable since and have had no issues, my apologies for not replying
My System SpecsSystem Spec
.

14 Aug 2014   #4
Arc

Microsoft Community Contributor Award Recipient

Microsoft Windows 10 Pro Insider Preview 64-bit
 
 

Go to Seemingly random BSOD - PFN list corrupt and mark it as solved.

Attachment 329232

Everything seems to be fine. The system is not overheating. Furmark ran fine (stress test consumes more power). Power supply is enough for your GPU.

Plus it is a first instance of such a BSOD in your system.

In that case we may consider this one as a glitch. But if you get one more stop 0x116 BSOD, then further troubleshooting will be needed.
My System SpecsSystem Spec
14 Aug 2014   #5
jon0507

windows home premuim 64bit
 
 

Ok, i hope so! I will keep an eye out. Thanks again, i will mark this thread as solved too for the time being
My System SpecsSystem Spec
15 Aug 2014   #6
Arc

Microsoft Community Contributor Award Recipient

Microsoft Windows 10 Pro Insider Preview 64-bit
 
 

Dont forget that we may consider a stray BSOD as a glitch, but not more than one.
Inform us as and when you have another one.
My System SpecsSystem Spec
02 Sep 2014   #7
jon0507

windows home premuim 64bit
 
 

Well, looks like it may not be a glitch! Happened 10 or so minutes after boot up, just surfing, so i wasn't stressing the card.
My System SpecsSystem Spec
03 Sep 2014   #8
Arc

Microsoft Community Contributor Award Recipient

Microsoft Windows 10 Pro Insider Preview 64-bit
 
 

Uninstall the installed display driver 340.25 WHQL using Display Driver Uninstaller. Then install 335.23 WHQL.
Drivers | GeForce
Follow NVIDIA Drivers - Avoid Problems to install it.

Run furmark again. Take the 15 minutes benchmark test.

Let us know the results.
____________________________________________
Code:
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 116, {fffffa8006d19010, fffff8800f5bf93c, 0, 2}

*** 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+15393c )

Followup: MachineOwner
---------

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

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

Debugging Details:
------------------


FAULTING_IP: 
nvlddmkm+15393c
fffff880`0f5bf93c 48ff256d6d7200  jmp     qword ptr [nvlddmkm+0x87a6b0 (fffff880`0fce66b0)]

DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT

CUSTOMER_CRASH_COUNT:  1

BUGCHECK_STR:  0x116

PROCESS_NAME:  System

CURRENT_IRQL:  0

ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre

STACK_TEXT:  
fffff880`029c71c8 fffff880`10157134 : 00000000`00000116 fffffa80`06d19010 fffff880`0f5bf93c 00000000`00000000 : nt!KeBugCheckEx
fffff880`029c71d0 fffff880`10156e3e : fffff880`0f5bf93c fffffa80`06d19010 fffffa80`06c47560 fffffa80`0a3c2410 : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`029c7210 fffff880`0f40ff13 : fffffa80`06d19010 00000000`00000000 fffffa80`06c47560 fffffa80`0a3c2410 : dxgkrnl!TdrIsRecoveryRequired+0x1a2
fffff880`029c7240 fffff880`0f43ded6 : fffffa80`ffffffff 00000000`0001d17b fffff880`029c7390 00000000`00000005 : dxgmms1!VidSchiReportHwHang+0x40b
fffff880`029c7320 fffff880`0f423ce9 : fffffa80`0a49f000 ffffffff`feced300 00000000`00000005 fffff880`0f55652a : dxgmms1!VidSchWaitForCompletionEvent+0x196
fffff880`029c7360 fffff880`0f426be7 : 00000000`00000001 00000000`00000000 fffffa80`06c3d9e0 fffff8a0`033f0650 : dxgmms1!VIDMM_GLOBAL::xWaitForAllEngines+0x1e9
fffff880`029c7460 fffff880`0f4252d8 : fffff8a0`033f0650 00000000`00000000 fffffa80`0a49f000 00000004`00000005 : dxgmms1!VIDMM_GLOBAL::SetupForBuildPagingBuffer+0xd7
fffff880`029c74a0 fffff880`0f42522e : 00000000`00000000 00000000`00000001 fffffa80`0a49f000 fffff880`0f423b56 : dxgmms1!VIDMM_GLOBAL::UnmapVideoApertureSegmentInternal+0x34
fffff880`029c7630 fffff880`0f42e77e : fffffa80`0a206930 00000000`00000001 00000000`00000001 fffff880`0f4c721a : dxgmms1!VIDMM_GLOBAL::UnmapVideoApertureSegment+0x13e
fffff880`029c76a0 fffff880`0f42e527 : fffff8a0`033f0650 00000000`00001000 fffffa80`0a206930 fffff8a0`033f0650 : dxgmms1!VIDMM_APERTURE_SEGMENT::UnmapApertureRange+0x7a
fffff880`029c76f0 fffff880`0f42decb : fffff8a0`033f0650 fffffa80`0a49fc80 00000000`00000000 fffffa80`0a49fc80 : dxgmms1!VIDMM_APERTURE_SEGMENT::UnmapTemporaryResource+0x9b
fffff880`029c7750 fffff880`0f4218a4 : fffffa80`0a49f000 fffffa80`0a49f000 fffffa80`0a49fc80 fffffa80`0a49f000 : dxgmms1!VIDMM_APERTURE_SEGMENT::ReleaseTemporaryResource+0xcf
fffff880`029c7790 fffff880`0f41e257 : 00000000`c0000001 00000000`00000000 00000000`0000000d fffffa80`0a49f000 : dxgmms1!VIDMM_GLOBAL::EvictTemporaryAllocations+0xbc
fffff880`029c77d0 fffff880`0f4387d9 : 00000000`00000000 fffff8a0`10359d70 fffffa80`00000000 fffffa80`06bcd010 : dxgmms1!VIDMM_GLOBAL::PrepareDmaBuffer+0x69f
fffff880`029c79a0 fffff880`0f438514 : fffff800`00b96080 fffff880`0f437f00 fffffa80`00000000 fffffa80`00000000 : dxgmms1!VidSchiSubmitRenderCommand+0x241
fffff880`029c7b90 fffff880`0f438012 : 00000000`00000000 fffffa80`06c47560 00000000`00000080 fffffa80`0a3c2410 : dxgmms1!VidSchiSubmitQueueCommand+0x50
fffff880`029c7bc0 fffff800`0335b73a : 00000000`00b42c20 fffffa80`0a205b50 fffffa80`066769e0 fffffa80`0a205b50 : dxgmms1!VidSchiWorkerThread+0xd6
fffff880`029c7c00 fffff800`030b08e6 : fffff800`0323ae80 fffffa80`0a205b50 fffff800`03248cc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`029c7c40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_IP: 
nvlddmkm+15393c
fffff880`0f5bf93c 48ff256d6d7200  jmp     qword ptr [nvlddmkm+0x87a6b0 (fffff880`0fce66b0)]

SYMBOL_NAME:  nvlddmkm+15393c

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  53b4446a

FAILURE_BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys

BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:x64_0x116_image_nvlddmkm.sys

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

Followup: MachineOwner
---------

2: kd> lmvm nvlddmkm
start             end                 module name
fffff880`0f46c000 fffff880`100fa000   nvlddmkm T (no symbols)           
    Loaded symbol image file: nvlddmkm.sys
    Image path: \SystemRoot\system32\DRIVERS\nvlddmkm.sys
    Image name: nvlddmkm.sys
    Timestamp:        Wed Jul 02 23:12:02 2014 (53B4446A)
    CheckSum:         00C4C7C9
    ImageSize:        00C8E000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
My System SpecsSystem Spec
03 Sep 2014   #9
jon0507

windows home premuim 64bit
 
 

Will do that as soon as i got the time and post back, do you guys have any sort of donation system or anything, as you guys are always so helpful i feel like i owe you!
My System SpecsSystem Spec
03 Sep 2014   #10
Arc

Microsoft Community Contributor Award Recipient

Microsoft Windows 10 Pro Insider Preview 64-bit
 
 

There was a donation system, long ago, even earlier than I joined here. And it was revoked long ago.

If you want to contribute, you may. Help the other members where and when you can.
My System SpecsSystem Spec
Reply

 BSOD After bootup. No new hardware - Driver issue?




Thread Tools Search this Thread
Search this Thread:

Advanced Search




Similar help and support threads
Thread Forum
Hardware acceleration alt. driver issue
My wife bought an ACER AX3400 64-bit (4GB memory, GeForce 315 video card) with "empty" HDD and no drivers CD from her friend. Installed WIN7 ULTIMATE and installed all the ACER X3400 drivers available on Acer download site. When she tries to play a quite simple card game, she gets the message...
Graphic Cards
BSOD with different reasons: hardware of driver issue ?
Hi Experts, I have been investigating for a while now and I'm still stuck with no explanation. I just bought a new desktop choosing every component and I have BSOD coming randomly, most frequently during video games / video editing. Sometimes i don't even get a blue screen but a freeze and i...
BSOD Help and Support
BSOD issues - driver or hardware issue?
Hi all, sorry for the vague title. Getting bluescreens again. As far as I know the only changes I have made is adding a fan to my case, and installing a later graphics driver (Catalyst 13.11 beta 7). I have also got a new GPU but I've had this about a week now and only started seeing bluescreens...
BSOD Help and Support
Multiple BSOD in custom build can't tell if driver or hardware issue
I am getting various BSODs after installing Windows and still haven't figured out the cause of the problem and what I need to do to fix it. Here is a log of what I did/problems I experienced (don't know if helpful): -installed windows 8, drivers for motherboard, gpu, and wireless adapter...
BSOD Help and Support
Random BSOD, error 0x07E and 0x01E, hardware or driver issue?
Hello, I have had this computer about a month and had two BSOD. It is a custom build. ASRock Extreme4 Z77, I7 3770k, ocz 60gb SSD, 8gb Gskill 2100. The first BSOD was a memory corruption caused by dropbox desktop app. Uninstalling dropbox seemed to fix that issue. The second BSOD was a system...
BSOD Help and Support
Driver issue, or is my hardware bad.
Yesterday I decided to take apart my case and clean everything, and I cleaned EVERYTHING. The mobo, HDD's, gfx cards, sound cards and everything. I have been using an ATI RADEON X850XT PE for about a year now, and it doesn't support pixel shader 3.0 so then I decided to put in a ATI RADEON X1600...
Drivers


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 07:39.

Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App