Hi,
I have a Dell 380 as a POS with a touch screen monitor.
I'm getting these Blue screens for no apparent reason.
I'm using the on-board output so there isn't any video cards involved.
The drivers are all up-to-date.
Here's a link to the dump file (220MB) : https://onedrive.live.com/redir?resid=819B12AEFF7B1804!138&authkey=!ADPdNBk7m3AJXRI&ithint=file%2c.DMP
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\DLiang\Desktop\MEMORY.DMP]
Kernel Summary Dump File: Only kernel address space is available
Symbol search path is: SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.18409.x86fre.win7sp1_gdr.140303-2144
Machine Name:
Kernel base = 0x82802000 PsLoadedModuleList = 0x8294b5b0
Debug session time: Thu Jun 19 11:44:59.317 2014 (UTC - 4:00)
System Uptime: 0 days 17:39:32.354
Loading Kernel Symbols
...............................................................
..................................................Page 7d0a9 not present in the dump file. Type ".hh dbgerr004" for details
..............
..................
Loading User Symbols
PEB is paged out (Peb.Ldr = 7ffdf00c). Type ".hh dbgerr001" for details
Loading unloaded module list
.................................................
kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: 86302008, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: 90c469b0, The pointer into responsible device driver module (e.g. owner tag).
Arg3: 00000000, Optional error code (NTSTATUS) of the last failed operation.
Arg4: 00000002, Optional internal context dependent data.
Debugging Details:
------------------
FAULTING_IP:
igdkmd32!DxgkDdiCollectDbgInfo+0
90c469b0 55 push ebp
DEFAULT_BUCKET_ID: GRAPHICS_DRIVER_TDR_FAULT
BUGCHECK_STR: 0x116
PROCESS_NAME: dwm.exe
CURRENT_IRQL: 0
STACK_TEXT:
9885b898 911bf0ff 00000116 86302008 90c469b0 nt!KeBugCheckEx+0x1e
9885b8bc 911b3ae6 90c469b0 00000000 00000002 dxgkrnl!TdrBugcheckOnTimeout+0x8d
9885b8e0 906e592c 00000000 00000000 9885b9a4 dxgkrnl!TdrIsRecoveryRequired+0xb8
9885b958 9070cd55 fffffcfb 003e2def 00000000 dxgmms1!VidSchiReportHwHang+0x3c0
9885b984 906f6471 85f5f008 9885b9a4 00000102 dxgmms1!VidSchWaitForCompletionEvent+0x16f
9885ba1c 906f7b0f b2899978 00000002 00000000 dxgmms1!VIDMM_GLOBAL::xWaitForAllEngines+0x181
9885ba34 906fa432 b5f387c0 85f5e718 9885bb94 dxgmms1!VIDMM_GLOBAL::WaitForAllPagingOperations+0x1b
9885ba9c 906faef8 9885bbe0 9885bb6c 9885bb9c dxgmms1!VIDMM_GLOBAL::ProcessDeferredCommand+0x338
9885bab4 907103b9 9885bb94 85f5e718 85f5e718 dxgmms1!VidMmiProcessSystemCommand+0x20
9885bad0 90711293 85f5fbb0 85f5f008 9885bb10 dxgmms1!VidSchiSubmitSystemCommand+0x33
9885bae0 906ec6dc 85f5e718 85f5e718 85f5f978 dxgmms1!VidSchiSubmitQueueCommand+0x7b
9885bb10 90711466 85f61000 9885bb34 85f5f978 dxgmms1!VidSchiSubmitQueueCommandDirect+0x1ae
9885bb38 9070c7f1 01f5e718 85f68000 b5f387c0 dxgmms1!VidSchiSubmitCommandPacketToQueue+0x180
9885bb50 906faf5f 85f5f008 906faed8 9885bb94 dxgmms1!VidSchSubmitSystemCommand+0xab
9885bb80 906fafc6 9885bb94 b29243f8 8632e9a0 dxgmms1!VIDMM_GLOBAL::QueueSystemCommandAndWait+0x41
9885bbb8 906fdee0 9885bbe0 b5fa75b0 9885bcac dxgmms1!VIDMM_GLOBAL::QueueDeferredCommandAndWait+0x3c
9885bc14 906e043b 019243f8 00000008 0000004d dxgmms1!VIDMM_GLOBAL::BeginCPUAccess+0xa18
9885bc34 91135329 85f68000 b29243f8 00000000 dxgmms1!VidMmBeginCPUAccess+0x1f
9885bc58 9115d1e3 8576fdc0 85f68000 b29243f8 dxgkrnl!VIDMM_EXPORT::VidMmBeginCPUAccess+0x23
9885bc90 9115d838 0000004d 09917c23 00eaead0 dxgkrnl!DXGDEVICE::Lock+0x24f
9885bd28 8283f8c6 00eaead0 00eaeaf8 774b70f4 dxgkrnl!DxgkLock+0x17b
9885bd28 774b70f4 00eaead0 00eaeaf8 774b70f4 nt!KiSystemServicePostCall
WARNING: Frame IP not in any known module. Following frames may be wrong.
00eaeaf8 00000000 00000000 00000000 00000000 0x774b70f4
STACK_COMMAND: .bugcheck ; kb
FOLLOWUP_IP:
igdkmd32!DxgkDdiCollectDbgInfo+0
90c469b0 55 push ebp
SYMBOL_NAME: igdkmd32!DxgkDdiCollectDbgInfo+0
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: igdkmd32
IMAGE_NAME: igdkmd32.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4a01d354
FAILURE_BUCKET_ID: 0x116_IMAGE_igdkmd32.sys
BUCKET_ID: 0x116_IMAGE_igdkmd32.sys
Followup: MachineOwner
---------
kd> lmvm igdkmd32
start end module name
90c35000 91132000 igdkmd32 (pdb symbols) c:\websymbols\igdkmd32.pdb\E0CDC49B931C4F6786A0C319D039E3BD1\igdkmd32.pdb
Loaded symbol image file: igdkmd32.sys
Image path: \SystemRoot\system32\DRIVERS\igdkmd32.sys
Image name: igdkmd32.sys
Timestamp: Wed May 06 14:13:40 2009 (4A01D354)
CheckSum: 0048DF97
ImageSize: 004FD000
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
Can anyone tell me what's going on?
Thanks,
Daniel