Crash dump skapas efter installation av drivrutiner till grafikkort. Hjälp o tolka den önskas.

Skriv svar

2016-10-01 01:55

Permalänk

daspunner

Medlem

Plats: Swe
Registrerad: Jun 2008

●

Crash dump skapas efter installation av drivrutiner till grafikkort. Hjälp o tolka den önskas.

Får en krashdump varje gång jag installerar grafikkortets drivrutiner på en Dell Latitude E6410. Fått igång WinDbg med rätt symboltabell eller va det heter men det är ju rena grekiskan det jag får ut av det. Har ju fått detta o funka med drivrutinerna en gång i tiden (ca 1 år sen). Testat allt o blev så sur med o behöva o köra med kass upplösning så jag ställde den åt sidan tills vidare men nu är jag på det igen. Om nån vill vara så vänlig o titta på dump-filen så hade jag varit superglad! Texten ur den följer nedan:

Loading Dump File [C:\Users\Linda\Desktop\dump gpu\093016-17362-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

************* Symbol Path validation summary **************
Response Time (ms) Location
Deferred SRV*C:\Temp*http://msdl.microsoft.com/download/symbols
Symbol search path is: SRV*C:\Temp*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.23539.amd64fre.win7sp1_ldr.160902-0600
Machine Name:
Kernel base = 0xfffff800`02c09000 PsLoadedModuleList = 0xfffff800`02e4b730
Debug session time: Fri Sep 30 21:13:15.809 2016 (UTC + 2:00)
System Uptime: 0 days 0:00:32.902
Loading Kernel Symbols
.

Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading symbols.

..............................................................
............................................................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 116, {fffffa800663f4e0, fffff8800f3da9dc, 0, 2}

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

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: fffffa800663f4e0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff8800f3da9dc, 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+1559dc
fffff880`0f3da9dc 803d265d740000 cmp byte ptr [nvlddmkm+0x89b709 (fffff880`0fb20709)],0

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.17336 (debuggers(dbg).150226-1500) amd64fre

STACK_TEXT:
fffff880`033bb9c8 fffff880`0ff381f0 : 00000000`00000116 fffffa80`0663f4e0 fffff880`0f3da9dc 00000000`00000000 : nt!KeBugCheckEx
fffff880`033bb9d0 fffff880`0ff37efa : fffff880`0f3da9dc fffffa80`0663f4e0 fffffa80`061fdd50 fffffa80`061de410 : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`033bba10 fffff880`0f20ffbf : fffffa80`0663f4e0 00000000`00000000 fffffa80`061fdd50 fffffa80`061de410 : dxgkrnl!TdrIsRecoveryRequired+0x1a2
fffff880`033bba40 fffff880`0f239d09 : 00000000`ffffffff 00000000`00000710 00000000`00000000 00000000`00000002 : dxgmms1!VidSchiReportHwHang+0x40b
fffff880`033bbb20 fffff880`0f23844f : 00000000`00000102 00000000`00000000 00000000`00000710 00000000`00000000 : dxgmms1!VidSchiCheckHwProgress+0x71
fffff880`033bbb50 fffff880`0f20b2e6 : ffffffff`ff676980 fffffa80`061de410 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiWaitForSchedulerEvents+0x1fb
fffff880`033bbbf0 fffff880`0f23800e : 00000000`00000000 00000000`0000000f 00000000`00000080 fffffa80`05840168 : dxgmms1!VidSchiScheduleCommandToRun+0x1da
fffff880`033bbd00 fffff800`02f12ee6 : 00000000`037ac0a7 fffffa80`061e4060 fffffa80`0390b040 fffffa80`061e4060 : dxgmms1!VidSchiWorkerThread+0xba
fffff880`033bbd40 fffff800`02c6a706 : fffff880`031e7180 fffffa80`061e4060 fffff880`031f1fc0 00000006`09910000 : nt!PspSystemThreadStartup+0x5a
fffff880`033bbd80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16

STACK_COMMAND: .bugcheck ; kb

FOLLOWUP_IP:
nvlddmkm+1559dc
fffff880`0f3da9dc 803d265d740000 cmp byte ptr [nvlddmkm+0x89b709 (fffff880`0fb20709)],0

SYMBOL_NAME: nvlddmkm+1559dc

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME: nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 538f8008

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

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

FAULTING_IP:
nvlddmkm+1559dc
fffff880`0f3da9dc 803d265d740000 cmp byte ptr [nvlddmkm+0x89b709 (fffff880`0fb20709)],0

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.17336 (debuggers(dbg).150226-1500) amd64fre

STACK_COMMAND: .bugcheck ; kb

FOLLOWUP_IP:
nvlddmkm+1559dc
fffff880`0f3da9dc 803d265d740000 cmp byte ptr [nvlddmkm+0x89b709 (fffff880`0fb20709)],0

SYMBOL_NAME: nvlddmkm+1559dc

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME: nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 538f8008

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

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

FAULTING_IP:
nvlddmkm+1559dc
fffff880`0f3da9dc 803d265d740000 cmp byte ptr [nvlddmkm+0x89b709 (fffff880`0fb20709)],0

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.17336 (debuggers(dbg).150226-1500) amd64fre

STACK_COMMAND: .bugcheck ; kb

FOLLOWUP_IP:
nvlddmkm+1559dc
fffff880`0f3da9dc 803d265d740000 cmp byte ptr [nvlddmkm+0x89b709 (fffff880`0fb20709)],0

SYMBOL_NAME: nvlddmkm+1559dc

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME: nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 538f8008

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

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

FAULTING_IP:
nvlddmkm+1559dc
fffff880`0f3da9dc 803d265d740000 cmp byte ptr [nvlddmkm+0x89b709 (fffff880`0fb20709)],0

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.17336 (debuggers(dbg).150226-1500) amd64fre

STACK_COMMAND: .bugcheck ; kb

FOLLOWUP_IP:
nvlddmkm+1559dc
fffff880`0f3da9dc 803d265d740000 cmp byte ptr [nvlddmkm+0x89b709 (fffff880`0fb20709)],0

SYMBOL_NAME: nvlddmkm+1559dc

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME: nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 538f8008

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

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

FAULTING_IP:
nvlddmkm+1559dc
fffff880`0f3da9dc 803d265d740000 cmp byte ptr [nvlddmkm+0x89b709 (fffff880`0fb20709)],0

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.17336 (debuggers(dbg).150226-1500) amd64fre

STACK_COMMAND: .bugcheck ; kb

FOLLOWUP_IP:
nvlddmkm+1559dc
fffff880`0f3da9dc 803d265d740000 cmp byte ptr [nvlddmkm+0x89b709 (fffff880`0fb20709)],0

SYMBOL_NAME: nvlddmkm+1559dc

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME: nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 538f8008

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

Rapportera Redigera

Citera flera Citera

Skriv svar

Crash dump skapas efter installation av drivrutiner till grafikkort. Hjälp o tolka den önskas.

Crash dump skapas efter installation av drivrutiner till grafikkort. Hjälp o tolka den önskas.

Externa nyheter

Spelnyheter från FZ