Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

BSOD


  • Please log in to reply
2 replies to this topic

#1 Zoo York

Zoo York

  • Members
  • 2 posts
  • OFFLINE
  •  
  • Local time:05:49 AM

Posted 07 July 2011 - 07:47 AM

Good Evening Bleepingcomputer!

I just had a BSOD on my laptop and have went through debugging the .dmp file and hoping you can help me troubleshoot for the problem.

I used these guides on here to go through the debugging.

How to receive help diagnosing Blue Screens and Windows crashes

How To Find Bsod Error Messages

The debugging and analyse text is this:

Microsoft ® Windows Debugger Version 6.12.0002.633 X86
Copyright © Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\LiveKernelReports\WATCHDOG\WD-20110707-1312-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17592.x86fre.win7sp1_gdr.110408-1631
Machine Name:
Kernel base = 0x82a08000 PsLoadedModuleList = 0x82b514d0
Debug session time: Thu Jul 7 13:12:28.627 2011 (UTC + 2:00)
System Uptime: 0 days 0:33:19.718
Loading Kernel Symbols
...............................................................
................................................................
..............................................
Loading User Symbols
Mini Kernel Dump does not contain unloaded driver list
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 117, {854de008, 9123af40, 0, 0}

Unable to load image nvlddmkm.sys, Win32 error 0n2
*** 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+df40 )

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

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

VIDEO_TDR_TIMEOUT_DETECTED (117)
The display driver failed to respond in timely fashion.
(This code can never be used for real bugcheck).
Arguments:
Arg1: 854de008, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: 9123af40, The pointer into responsible device driver module (e.g owner tag).
Arg3: 00000000, The secondary driver specific bucketing key.
Arg4: 00000000, Optional internal context dependent data.

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


FAULTING_IP:
nvlddmkm+df40
9123af40 ?? ???

DEFAULT_BUCKET_ID: GRAPHICS_DRIVER_TDR_TIMEOUT

TAG_NOT_DEFINED_202b: *** Unknown TAG in analysis list 202b


CUSTOMER_CRASH_COUNT: 1

BUGCHECK_STR: 0x117

PROCESS_NAME: System

CURRENT_IRQL: 0

STACK_TEXT:
8cee2b30 90f225b8 00000000 9123af40 8716f788 dxgkrnl!TdrUpdateDbgReport+0x68
8cee2b9c 90f2197e 00000000 00000001 854de008 dxgkrnl!TdrCollectDbgInfoStage1+0x715
8cee2bbc 91ba692c 00000000 00000102 8716f788 dxgkrnl!TdrIsRecoveryRequired+0xfe
8cee2c34 91bd0944 fffffcfb 0001f417 00000000 dxgmms1!VidSchiReportHwHang+0x3c0
8cee2c5c 91bd1065 00000000 00000000 00000000 dxgmms1!VidSchiCheckHwProgress+0x68
8cee2c98 91bad8f0 8cee2c90 87996858 871d11e8 dxgmms1!VidSchiWaitForSchedulerEvents+0x1b1
8cee2d28 91bd23c9 8716f788 82a3f50e 8716f788 dxgmms1!VidSchiScheduleCommandToRun+0xaa
8cee2d3c 91bd2485 8716f788 00000000 8718ca48 dxgmms1!VidSchiRun_PriorityTable+0xf
8cee2d50 82c10f64 8716f788 bcd7c403 00000000 dxgmms1!VidSchiWorkerThread+0x7f
8cee2d90 82ab9219 91bd2406 8716f788 00000000 nt!PspSystemThreadStartup+0x9e
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19


STACK_COMMAND: .bugcheck ; kb

FOLLOWUP_IP:
nvlddmkm+df40
9123af40 ?? ???

SYMBOL_NAME: nvlddmkm+df40

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME: nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4ac79286

FAILURE_BUCKET_ID: 0x117_IMAGE_nvlddmkm.sys

BUCKET_ID: 0x117_IMAGE_nvlddmkm.sys

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


I had trouble with my NVIDIA graphic card drivers has stop working, but thought it got fixed when I updatede the drivers.
That might be what caused the BSOD, but hoping you can tell if that is true or something else is wrong.

Thanks in advance

- Zoo York

BC AdBot (Login to Remove)

 


#2 MarkGS

MarkGS

  • Members
  • 245 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:12:49 AM

Posted 07 July 2011 - 10:23 PM

Good news.. It's just a driver.. Bad news.. it's the NVIDIA driver. When you updated the driver did you do it from windows update, the mfg website or NVIDIA?

#3 Zoo York

Zoo York
  • Topic Starter

  • Members
  • 2 posts
  • OFFLINE
  •  
  • Local time:05:49 AM

Posted 08 July 2011 - 07:36 PM

I updated through device Manager in control panel.
Will try through the website - does it say which driver I'm missing or that needs to be updated?

EDIT: NVIDIA's program found the drivers for me installing now. Hoping that will prevent any future BDOS.

Ty for reponse ;)

Edited by Zoo York, 08 July 2011 - 07:49 PM.





0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users