New
#1
BSOD Minidump
Hello everyone, me again. I was using my laptop a few ago and it BSOD'd after my display driver crashing around 5 times.
Here is the dump file; Attachment 15357
Last edited by Dark Nova Gamer; 14 Jul 2009 at 12:35.
Hello everyone, me again. I was using my laptop a few ago and it BSOD'd after my display driver crashing around 5 times.
Here is the dump file; Attachment 15357
Last edited by Dark Nova Gamer; 14 Jul 2009 at 12:35.
Please describe what you were doing when the BSOD's occurred. Have you done anything to the system recently that may have caused this? Is there anything unusual that sticks out in your mind about the system?
The bug check points at your Intel video drivers as the issue. But without further descriptions of the problem, this is only a guess.
1 - Download the latest version of the driver from Intel
2 - Uninstall the current video drivers from Control Panel...Programs...Uninstall a program
3 - Install the freshly downloaded drivers
4 - Test to see if it worked.
Here's the memory dump:
Code:Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Users\FUBAR-RC1-Desktop\TempDUMP\DATA\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 7100 MP (2 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7100.0.amd64fre.winmain_win7rc.090421-1700 Machine Name: Kernel base = 0xfffff800`02a19000 PsLoadedModuleList = 0xfffff800`02c52e90 Debug session time: Tue Jun 23 15:50:35.130 2009 (GMT-4) System Uptime: 0 days 2:05:05.956 Loading Kernel Symbols ............................................................... ................................................................ ...................................... Loading User Symbols Loading unloaded module list ...... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 116, {fffffa8004456010, fffff88004b09640, 0, d} *** WARNING: Unable to verify timestamp for igdkmd64.sys *** ERROR: Module load completed but symbols could not be loaded for igdkmd64.sys Probably caused by : igdkmd64.sys ( igdkmd64+16640 ) Followup: MachineOwner --------- 0: kd> !thread;!analyze -v;r;kv;lmtn;lmtsmn;.bugcheck;.logclose;q GetPointerFromAddress: unable to read from fffff80002cbd000 THREAD fffffa80064d3770 Cid 0004.01d0 Teb: 0000000000000000 Win32Thread: 0000000000000000 RUNNING on processor 0 Not impersonating GetUlongFromAddress: unable to read from fffff80002bfbb74 Owning Process fffffa8003cec040 Image: System Attached Process N/A Image: N/A fffff78000000000: Unable to get shared data Wait Start TickCount 481147 Context Switch Count 1348694 ReadMemory error: Cannot get nt!KeMaximumIncrement value. UserTime 00:00:00.000 KernelTime 00:00:00.000 Win32 Start Address dxgmms1!VidSchiWorkerThread (0xfffff88004a37dc0) Stack Init fffff88002a2cd70 Current fffff880080bab20 Base fffff88002a2d000 Limit fffff88002a27000 Call 0 Priority 21 BasePriority 15 UnusualBoost 0 ForegroundBoost 0 IoPriority 2 PagePriority 5 Child-SP RetAddr : Args to Child : Call Site fffff880`02a2c988 fffff880`05552cbc : 00000000`00000116 fffffa80`04456010 fffff880`04b09640 00000000`00000000 : nt!KeBugCheckEx fffff880`02a2c990 fffff880`05552a43 : fffff880`04b09640 fffffa80`04456010 00000000`00000000 fffffa80`064cd010 : dxgkrnl!TdrBugcheckOnTimeout+0xec fffff880`02a2c9d0 fffff880`04a0ff07 : fffffa80`04456010 00000000`00000000 00000000`00000000 fffffa80`064cd010 : dxgkrnl!TdrIsRecoveryRequired+0x21f fffff880`02a2ca00 fffff880`04a39bd4 : fffffa80`00000000 00000000`000756b1 00000000`00000000 00000000`00000002 : dxgmms1!VidSchiReportHwHang+0x40b fffff880`02a2cae0 fffff880`04a382bb : 00000000`00000102 00000000`00000000 00000000`000756b1 00000000`00000000 : dxgmms1!VidSchiCheckHwProgress+0xd0 fffff880`02a2cb10 fffff880`04a0b2c6 : ffffffff`ff676980 fffffa80`064cd010 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiWaitForSchedulerEvents+0x1fb fffff880`02a2cbb0 fffff880`04a37e7a : 00000000`00000000 fffffa80`0447dd50 00000000`00000080 fffffa80`064cd010 : dxgmms1!VidSchiScheduleCommandToRun+0x1da fffff880`02a2ccc0 fffff800`02d1de66 : 00000000`fffffc32 fffffa80`064d3770 fffffa80`03cec040 fffffa80`064d3770 : dxgmms1!VidSchiWorkerThread+0xba fffff880`02a2cd00 fffff800`02a4aa86 : fffff800`02bffe80 fffffa80`064d3770 fffff800`02c0dc40 fffff880`014489a0 : nt!PspSystemThreadStartup+0x5a fffff880`02a2cd40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16 ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* VIDEO_TDR_FAILURE (116) Attempt to reset the display driver and recover from timeout failed. Arguments: Arg1: fffffa8004456010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT). Arg2: fffff88004b09640, The pointer into responsible device driver module (e.g. owner tag). Arg3: 0000000000000000, Optional error code (NTSTATUS) of the last failed operation. Arg4: 000000000000000d, Optional internal context dependent data. Debugging Details: ------------------ FAULTING_IP: igdkmd64+16640 fffff880`04b09640 4889542410 mov qword ptr [rsp+10h],rdx DEFAULT_BUCKET_ID: GRAPHICS_DRIVER_TDR_FAULT BUGCHECK_STR: 0x116 PROCESS_NAME: System CURRENT_IRQL: 0 STACK_TEXT: fffff880`02a2c988 fffff880`05552cbc : 00000000`00000116 fffffa80`04456010 fffff880`04b09640 00000000`00000000 : nt!KeBugCheckEx fffff880`02a2c990 fffff880`05552a43 : fffff880`04b09640 fffffa80`04456010 00000000`00000000 fffffa80`064cd010 : dxgkrnl!TdrBugcheckOnTimeout+0xec fffff880`02a2c9d0 fffff880`04a0ff07 : fffffa80`04456010 00000000`00000000 00000000`00000000 fffffa80`064cd010 : dxgkrnl!TdrIsRecoveryRequired+0x21f fffff880`02a2ca00 fffff880`04a39bd4 : fffffa80`00000000 00000000`000756b1 00000000`00000000 00000000`00000002 : dxgmms1!VidSchiReportHwHang+0x40b fffff880`02a2cae0 fffff880`04a382bb : 00000000`00000102 00000000`00000000 00000000`000756b1 00000000`00000000 : dxgmms1!VidSchiCheckHwProgress+0xd0 fffff880`02a2cb10 fffff880`04a0b2c6 : ffffffff`ff676980 fffffa80`064cd010 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiWaitForSchedulerEvents+0x1fb fffff880`02a2cbb0 fffff880`04a37e7a : 00000000`00000000 fffffa80`0447dd50 00000000`00000080 fffffa80`064cd010 : dxgmms1!VidSchiScheduleCommandToRun+0x1da fffff880`02a2ccc0 fffff800`02d1de66 : 00000000`fffffc32 fffffa80`064d3770 fffffa80`03cec040 fffffa80`064d3770 : dxgmms1!VidSchiWorkerThread+0xba fffff880`02a2cd00 fffff800`02a4aa86 : fffff800`02bffe80 fffffa80`064d3770 fffff800`02c0dc40 fffff880`014489a0 : nt!PspSystemThreadStartup+0x5a fffff880`02a2cd40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16 STACK_COMMAND: .bugcheck ; kb FOLLOWUP_IP: igdkmd64+16640 fffff880`04b09640 4889542410 mov qword ptr [rsp+10h],rdx SYMBOL_NAME: igdkmd64+16640 FOLLOWUP_NAME: MachineOwner MODULE_NAME: igdkmd64 IMAGE_NAME: igdkmd64.sys DEBUG_FLR_IMAGE_TIMESTAMP: 49ca5fb7 FAILURE_BUCKET_ID: X64_0x116_IMAGE_igdkmd64.sys BUCKET_ID: X64_0x116_IMAGE_igdkmd64.sys Followup: MachineOwner --------- rax=fffffa80043b6010 rbx=fffffa8004456010 rcx=0000000000000116 rdx=fffffa8004456010 rsi=000000000000000d rdi=fffffa80045d9000 rip=fffff80002a97f80 rsp=fffff88002a2c988 rbp=0000000000000000 r8=fffff88004b09640 r9=0000000000000000 r10=fffff80002a19000 r11=00000000000001b5 r12=0000000000000000 r13=0000000000000001 r14=fffffa80064cd928 r15=0000000000000000 iopl=0 nv up ei ng nz na pe nc cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00000282 nt!KeBugCheckEx: fffff800`02a97f80 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:fffff880`02a2c990=0000000000000116 Child-SP RetAddr : Args to Child : Call Site fffff880`02a2c988 fffff880`05552cbc : 00000000`00000116 fffffa80`04456010 fffff880`04b09640 00000000`00000000 : nt!KeBugCheckEx fffff880`02a2c990 fffff880`05552a43 : fffff880`04b09640 fffffa80`04456010 00000000`00000000 fffffa80`064cd010 : dxgkrnl!TdrBugcheckOnTimeout+0xec fffff880`02a2c9d0 fffff880`04a0ff07 : fffffa80`04456010 00000000`00000000 00000000`00000000 fffffa80`064cd010 : dxgkrnl!TdrIsRecoveryRequired+0x21f fffff880`02a2ca00 fffff880`04a39bd4 : fffffa80`00000000 00000000`000756b1 00000000`00000000 00000000`00000002 : dxgmms1!VidSchiReportHwHang+0x40b fffff880`02a2cae0 fffff880`04a382bb : 00000000`00000102 00000000`00000000 00000000`000756b1 00000000`00000000 : dxgmms1!VidSchiCheckHwProgress+0xd0 fffff880`02a2cb10 fffff880`04a0b2c6 : ffffffff`ff676980 fffffa80`064cd010 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiWaitForSchedulerEvents+0x1fb fffff880`02a2cbb0 fffff880`04a37e7a : 00000000`00000000 fffffa80`0447dd50 00000000`00000080 fffffa80`064cd010 : dxgmms1!VidSchiScheduleCommandToRun+0x1da fffff880`02a2ccc0 fffff800`02d1de66 : 00000000`fffffc32 fffffa80`064d3770 fffffa80`03cec040 fffffa80`064d3770 : dxgmms1!VidSchiWorkerThread+0xba fffff880`02a2cd00 fffff800`02a4aa86 : fffff800`02bffe80 fffffa80`064d3770 fffff800`02c0dc40 fffff880`014489a0 : nt!PspSystemThreadStartup+0x5a fffff880`02a2cd40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16
Will do. Also I was using Windows Media Player, was on IE x86 and Trillian Astra (Instant Messenger)
Hi,
It appears there are two different crashes being discussed under this one thread, but I have an almost identical crash Stop 116 with igkdmd64.sys, and I was wondering if anyone has any ideas what to do with it. From the Event Viewer, System Log:
The computer has rebooted from a bugcheck. The bugcheck was: 0x00000116 (0xfffffa8002a55010, 0xfffff88004c257f0, 0x0000000000000000, 0x000000000000000d). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 032410-27752-02.
This is a Dell Vostro 1510 and below is the system information from Performance Test. It should be noted that I was once running RMClock with the 64-bit updated (Vista) driver - never overclocked, but have turned it off in hopes of resolving this issue. Thanks in advance!
**************
System Summary
**************
Windows 7 (64-bit)
Intel Core2 Duo T5870 @ 2.00GHz
3062 MB RAM
Mobile Intel(R) 965 Express Chipset Family
233GB HDD
CD-RW/DVDRW
System Information
System Name: VOSTRO
Operating System: Windows 7 (64-bit)
Motherboard Manufacturer: Dell Inc.
Motherboard Model: 0R780K
Motherboard Version:
BIOS Manufacturer: Dell Inc.
BIOS Version: A15
BIOS Release Date: 03/18/2009
CPU Information
Manufacturer: GenuineIntel
Type: Intel Core2 Duo T5870 @ 2.00GHz
Number of CPU's: 1
Cores per CPU: 2
Hyperthreading: Not capable
Measured Speed: 2198.1 MHz
Multiplier: 11X
Bus Speed: 200Mhz
Front Side Bus Speed: 200Mhz
L1 Instruction Cache: 2 x 32 KB
L1 Data Cache: 2 x 32 KB
L2 Cache Size: 1 x 2 MB
L3 Cache: (N/A)
Memory Information
Total Physical Memory: 3062 MB RAM
Available Physical Memory: 1576 MB RAM
Slot 1: DDR2, 2048MB, 800MHz
Slot 2: DDR2, 1024MB, 800MHz
Virtual Memory: C:\pagefile.sys (4593 MB)
Disk Information
Drive Letter (Number): C (Physical drive 0)
Model Number: ST9250827AS
Disk Size (Free space): 223.0 GBytes (169.3 GBytes)
Disk Cluster Size: 4 KBytes
File System: NTFS
Video Adapters
Description: Mobile Intel(R) 965 Express Chipset Family
Chip Type: Mobile Intel(R) 965 Express Chipset Family
DAC Type: Internal
Memory: 384MB
Video BIOS: Intel Video BIOS
Driver Provider: Intel Corporation
Driver Version: 8.15.10.1930
Driver Date: 9-23-2009
Monitor 1: 1280x800x32 60Hz (Primary monitor)