
Quote: Originally Posted by
dtslicker
Here's the information that the rules thread asks for:
-My Windows is a 64bit that came installed on my Dell Inspiron 15R N5010
I think I attached the ZIP file with the information in it. Any help would be great. It's been doing this sporadically. I play Sims 3 and I mostly notice it crashing out while I'm in-game. If anyone knows how to fix it I'd really appreciate the help.
Caused by 2 things.
1-your video driver re-install with newest using these.
When upgrading your graphic driver you MUST remove all traces of the current driver. In order to do that we recommend using
Guru3D - Driver Sweeper
Or
Phyxion.net - Driver Sweeper
When it is removed then download and install the fresh copy.
2- Your Symantec. Remove and replace with Microsoft Security Essentials
Download and run the Norton Removal Tool to uninstall your Norton product | Norton Support Virus, Spyware & Malware Protection | Microsoft Security Essentials Code:
Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\K\Desktop\Windows_NT6_BSOD_jcgriff2\060811-22932-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;srv*e:\symbols
*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.20941.amd64fre.win7_ldr.110408-1635
Machine Name:
Kernel base = 0xfffff800`02c04000 PsLoadedModuleList = 0xfffff800`02e38eb0
Debug session time: Wed Jun 8 13:03:40.115 2011 (GMT-4)
System Uptime: 0 days 10:36:42.847
Loading Kernel Symbols
...............................................................
................................................................
................................................
Loading User Symbols
Loading unloaded module list
.................................
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 116, {fffffa800a97a4e0, fffff88004b1b290, 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+1d290 )
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: fffffa800a97a4e0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff88004b1b290, 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+1d290
fffff880`04b1b290 4889542410 mov qword ptr [rsp+10h],rdx
DEFAULT_BUCKET_ID: GRAPHICS_DRIVER_TDR_FAULT
CUSTOMER_CRASH_COUNT: 1
BUGCHECK_STR: 0x116
PROCESS_NAME: System
CURRENT_IRQL: 0
STACK_TEXT:
fffff880`07aeea58 fffff880`04a5d000 : 00000000`00000116 fffffa80`0a97a4e0 fffff880`04b1b290 00000000`00000000 : nt!KeBugCheckEx
fffff880`07aeea60 fffff880`04a5cd87 : fffff880`04b1b290 fffffa80`0a97a4e0 fffffa80`0a0a3660 fffffa80`0885a080 : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`07aeeaa0 fffff880`0552cf07 : fffffa80`0a97a4e0 00000000`00000000 fffffa80`0a0a3660 fffffa80`0885a080 : dxgkrnl!TdrIsRecoveryRequired+0x21f
fffff880`07aeead0 fffff880`0555ad5a : fffffa80`ffffffff 00000000`00255d6e fffff880`07aeec30 00000000`00000002 : dxgmms1!VidSchiReportHwHang+0x40b
fffff880`07aeebb0 fffff880`0552829e : fffffa80`0885a080 ffffffff`feced300 fffffa80`0a0a3660 00000000`00000000 : dxgmms1!VidSchWaitForCompletionEvent+0x196
fffff880`07aeebf0 fffff880`05554e7a : 00000000`00000000 fffffa80`0a0a3660 00000000`00000080 fffffa80`0885a080 : dxgmms1!VidSchiScheduleCommandToRun+0x1b2
fffff880`07aeed00 fffff800`02f0e75a : 00000000`fffffc32 fffffa80`08bdfb60 fffffa80`03b4e890 fffffa80`08bdfb60 : dxgmms1!VidSchiWorkerThread+0xba
fffff880`07aeed40 fffff800`02c47106 : fffff880`031d3180 fffffa80`08bdfb60 fffff880`031ddfc0 fffff880`01638810 : nt!PspSystemThreadStartup+0x5a
fffff880`07aeed80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16
STACK_COMMAND: .bugcheck ; kb
FOLLOWUP_IP:
igdkmd64+1d290
fffff880`04b1b290 4889542410 mov qword ptr [rsp+10h],rdx
SYMBOL_NAME: igdkmd64+1d290
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: igdkmd64
IMAGE_NAME: igdkmd64.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4c75709e
FAILURE_BUCKET_ID: X64_0x116_IMAGE_igdkmd64.sys
BUCKET_ID: X64_0x116_IMAGE_igdkmd64.sys
Followup: MachineOwner
---------