New
#1
Unexpected BSOD results in crash Dump
hi,everyone
i need help for analysing the minidump that causes unexpected bsod
Thanks in Advance
hi,everyone
i need help for analysing the minidump that causes unexpected bsod
Thanks in Advance
Try updating the intel graphics driver: Driver Reference Table - igdkmd32.sys
Code:******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 116, {8559e510, 9201f9b0, 0, c} *** WARNING: Unable to verify timestamp for igdkmd32.sys *** ERROR: Module load completed but symbols could not be loaded for igdkmd32.sys Probably caused by : igdkmd32.sys ( igdkmd32+119b0 ) Followup: MachineOwner --------- 0: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* VIDEO_TDR_FAILURE (116) Attempt to reset the display driver and recover from timeout failed. Arguments: Arg1: 8559e510, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT). Arg2: 9201f9b0, The pointer into responsible device driver module (e.g. owner tag). Arg3: 00000000, Optional error code (NTSTATUS) of the last failed operation. Arg4: 0000000c, Optional internal context dependent data. Debugging Details: ------------------ FAULTING_IP: igdkmd32+119b0 9201f9b0 55 push ebp DEFAULT_BUCKET_ID: GRAPHICS_DRIVER_TDR_FAULT CUSTOMER_CRASH_COUNT: 1 BUGCHECK_STR: 0x116 PROCESS_NAME: chrome.exe CURRENT_IRQL: 0 STACK_TEXT: 8e3c865c 9259807b 00000116 8559e510 9201f9b0 nt!KeBugCheckEx+0x1e 8e3c8680 9258c937 9201f9b0 00000000 0000000c dxgkrnl!TdrBugcheckOnTimeout+0x8d 8e3c86a4 925c892c 0059e510 00000000 8e3c8768 dxgkrnl!TdrIsRecoveryRequired+0xb8 8e3c871c 925efc1d fffffcfb 0002fa7c 00000000 dxgmms1!VidSchiReportHwHang+0x3c0 8e3c8748 925d944b 864e0008 8e3c8768 00000102 dxgmms1!VidSchWaitForCompletionEvent+0x16f 8e3c87e0 925daaaf 85121728 00000002 00000000 dxgmms1!VIDMM_GLOBAL::xWaitForAllEngines+0x181 8e3c87f8 925ea751 85120da8 8653b538 8e3c8894 dxgmms1!VIDMM_GLOBAL::WaitForAllPagingEngines+0x1b 8e3c8810 82dce4b6 8e3c8834 8e3c8894 8e3c89ec dxgmms1!VIDMM_MEMORY_SEGMENT::RotateCopyCallback+0x87 8e3c893c 925e3ce1 02eed000 8e3c8984 00000000 nt!MmRotatePhysicalView+0x597 8e3c898c 925eace0 8ff0c4d0 00000002 00000000 dxgmms1!VIDMM_PROCESS_HEAP::Rotate+0xe1 8e3c8a78 925d4ac7 85120da8 00000001 86874838 dxgmms1!VIDMM_MEMORY_SEGMENT::EvictResource+0x4b2 8e3c8a9c 925dadac 86874840 00000000 86874824 dxgmms1!VIDMM_GLOBAL::EvictAllAllocationInList+0x2f 8e3c8ac0 925dc87b 00000000 00000000 00000000 dxgmms1!VIDMM_GLOBAL::EvictAllReclaimedAllocation+0x2a 8e3c8bb8 925f3850 b9259108 00000000 8607c7e0 dxgmms1!VIDMM_GLOBAL::PrepareDmaBuffer+0x925 8e3c8d18 925f4141 84db0008 84f0c178 8e3c8d3c dxgmms1!VidSchiSubmitRenderCommand+0x1c0 8e3c8d28 925f43de 84db0008 82c39fc5 864e0008 dxgmms1!VidSchiSubmitQueueCommand+0x61 8e3c8d3c 925f4485 864e0008 00000000 8653b538 dxgmms1!VidSchiRun_PriorityTable+0x24 8e3c8d50 82df350a 864e0008 aaa4e748 00000000 dxgmms1!VidSchiWorkerThread+0x7f 8e3c8d90 82c94879 925f4406 864e0008 00000000 nt!PspSystemThreadStartup+0x9e 00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19 STACK_COMMAND: .bugcheck ; kb FOLLOWUP_IP: igdkmd32+119b0 9201f9b0 55 push ebp SYMBOL_NAME: igdkmd32+119b0 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 --------- 0: kd> lmvm igdkmd32 start end module name 9200e000 9250b000 igdkmd32 T (no symbols) Loaded symbol image file: igdkmd32.sys Image path: \SystemRoot\system32\DRIVERS\igdkmd32.sys Image name: igdkmd32.sys Timestamp: Thu May 07 00:13:40 2009 (4A01D354) CheckSum: 0048DF97 ImageSize: 004FD000 Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4