Jump to content

Welcome to Geeks to Go - Register now for FREE

Need help with your computer or device? Want to learn new tech skills? You're in the right place!
Geeks to Go is a friendly community of tech experts who can solve any problem you have. Just create a free account and post your question. Our volunteers will reply quickly and guide you through the steps. Don't let tech troubles stop you. Join Geeks to Go now and get the support you need!

How it Works Create Account
Photo

Vista MiniDump Analisys Help

Mini dump vista

  • Please log in to reply

#1
VistaDJ

VistaDJ

    New Member

  • Member
  • Pip
  • 1 posts

Hi

 

Can any one help with this and tell me what to fix and how.

 

Loading Dump File [C:\Windows\Minidump\Mini031415-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
 
Symbol search path is: SRV*c:\Windows\Symbols*http://msdl.microsof...ownload/symbols
Executable search path is: 
Windows Server 2008/Windows Vista Kernel Version 6002 (Service Pack 2) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 6002.19327.x86fre.vistasp2_gdr.150225-1506
Machine Name:
Kernel base = 0x83438000 PsLoadedModuleList = 0x8354fc70
Debug session time: Sat Mar 14 18:37:50.043 2015 (UTC + 7:00)
System Uptime: 0 days 0:03:27.729
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, {9ab102a8, 8fc13060, 0, 0}
 
*** 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+6060 )
 
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: 9ab102a8, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: 8fc13060, 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+6060
8fc13060 ??              ???
 
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:  
8e4ffb7c 8f9739e5 00000000 8fc13060 9b5798b8 dxgkrnl!TdrUpdateDbgReport+0x68
8e4ffbe8 8f973cba 00000000 00000001 9ab102a8 dxgkrnl!TdrCollectDbgInfoStage1+0x682
8e4ffc04 8f9104fd 00000000 00000102 9b5798b8 dxgkrnl!TdrIsRecoveryRequired+0xcf
8e4ffc6c 8f92cfaf 9b5798b8 000027df 00000000 dxgkrnl!VidSchiReportHwHang+0x2f5
8e4ffc98 8f92cd0f 9b5798b8 00000000 00000000 dxgkrnl!VidSchiCheckHwProgress+0x69
8e4ffcc4 8f8fe5c0 00000002 8347c92a 9b5798b8 dxgkrnl!VidSchiWaitForSchedulerEvents+0x13f
8e4ffd54 8f92d056 9b5798b8 8347c92a 9b5798b8 dxgkrnl!VidSchiScheduleCommandToRun+0xac
8e4ffd68 8f9626be 9b5798b8 00000000 957a9d78 dxgkrnl!VidSchiRun_PriorityTable+0xf
8e4ffd7c 8360e01c 9b5798b8 64865a4f 00000000 dxgkrnl!VidSchiWorkerThread+0x62
8e4ffdc0 83476f0e 8f96265c 9b5798b8 00000000 nt!PspSystemThreadStartup+0x9d
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16
 
 
STACK_COMMAND:  .bugcheck ; kb
 
FOLLOWUP_IP: 
nvlddmkm+6060
8fc13060 ??              ???
 
SYMBOL_NAME:  nvlddmkm+6060
 
FOLLOWUP_NAME:  MachineOwner
 
MODULE_NAME: nvlddmkm
 
IMAGE_NAME:  nvlddmkm.sys
 
DEBUG_FLR_IMAGE_TIMESTAMP:  47317db2
 
FAILURE_BUCKET_ID:  0x117_IMAGE_nvlddmkm.sys
 
BUCKET_ID:  0x117_IMAGE_nvlddmkm.sys
 
Followup: MachineOwner
---------
 

  • 0

Advertisements







Similar Topics

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users

As Featured On:

Microsoft Yahoo BBC MSN PC Magazine Washington Post HP