BSOD reports please help

hi i have read your bsod thread and heres my reports, also only happens when opening or playing world of warcraft.

My PC is custom built from all new parts i have not got part models etc only retailer names. i would have to find out the rest if you need to know all i can tell you right now is:

OS: windows 7 home premium 64 bit
installed from retail.

the PC is still brand new was built around 6 months ago

feel free to ask for any other info thank you very much.

fezbombmatt said:

hi i have read your bsod thread and heres my reports, also only happens when opening or playing world of warcraft.

My PC is custom built from all new parts i have not got part models etc only retailer names. i would have to find out the rest if you need to know all i can tell you right now is:

OS: windows 7 home premium 64 bit
installed from retail.

the PC is still brand new was built around 6 months ago

feel free to ask for any other info thank you very much.

There are several sources but my hunch is that it is your symantec causing them. I would (just to test) remove and replace with Microsoft security essentials.

Download and run the Norton Removal Tool to uninstall your Norton product | Norton Support

http://www.microsoft.com/security_essentials/




I would also re-install the video driver using this method.

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 if the above doesnt work for you. Phyxion.net - Driver Sweeper

When it is removed then download and install the fresh copy.

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\052411-13681-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.16792.amd64fre.win7_gdr.110408-1633
Machine Name:
Kernel base = 0xfffff800`02e0e000 PsLoadedModuleList = 0xfffff800`0304be50
Debug session time: Tue May 24 16:31:33.998 2011 (GMT-4)
System Uptime: 0 days 1:43:39.089
Loading Kernel Symbols
...............................................................
................................................................
......................
Loading User Symbols
Loading unloaded module list
.......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 116, {fffffa8006d494e0, fffff8801260b970, ffffffffc000009a, 4}

Unable to load image \SystemRoot\system32\DRIVERS\nvlddmkm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : nvlddmkm.sys ( nvlddmkm+7e4970 )

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: fffffa8006d494e0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff8801260b970, The pointer into responsible device driver module (e.g. owner tag).
Arg3: ffffffffc000009a, Optional error code (NTSTATUS) of the last failed operation.
Arg4: 0000000000000004, Optional internal context dependent data.

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


FAULTING_IP: 
nvlddmkm+7e4970
fffff880`1260b970 4883ec28        sub     rsp,28h

DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT

CUSTOMER_CRASH_COUNT:  1

BUGCHECK_STR:  0x116

PROCESS_NAME:  System

CURRENT_IRQL:  0

STACK_TEXT:  
fffff880`03cb3b88 fffff880`12b2b000 : 00000000`00000116 fffffa80`06d494e0 fffff880`1260b970 ffffffff`c000009a : nt!KeBugCheckEx
fffff880`03cb3b90 fffff880`12afe867 : fffff880`1260b970 fffffa80`0748d000 00000000`00000000 ffffffff`c000009a : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`03cb3bd0 fffff880`12b2ae0f : fffffa80`ffffd84d ffffffff`fffe7960 fffffa80`06d494e0 fffff880`03ecddc0 : dxgkrnl!DXGADAPTER::Reset+0x2a3
fffff880`03cb3c80 fffff880`03ecdec1 : fffffa80`054ef950 00000000`00000080 00000000`00000000 fffffa80`07482410 : dxgkrnl!TdrResetFromTimeout+0x23
fffff880`03cb3d00 fffff800`03121bc6 : 00000000`01cad7b2 fffffa80`074a7210 fffffa80`05193b30 fffffa80`074a7210 : dxgmms1!VidSchiWorkerThread+0x101
fffff880`03cb3d40 fffff800`02e5cbc6 : fffff880`02f64180 fffffa80`074a7210 fffff880`02f6efc0 fffff880`01223810 : nt!PspSystemThreadStartup+0x5a
fffff880`03cb3d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16


STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_IP: 
nvlddmkm+7e4970
fffff880`1260b970 4883ec28        sub     rsp,28h

SYMBOL_NAME:  nvlddmkm+7e4970

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4d9e7f64

FAILURE_BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys

BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys

Followup: MachineOwner
---------

thanks for the info. what i have done is gone to symantec and told them about the problem and they remote fixed a few things they mentioned scanning the game while playing can cause it.
they added the whole game folder to the scan exclusion list. do you know from the results i posted would that cure the issue fully?
thanks

fezbombmatt said:

thanks for the info. what i have done is gone to symantec and told them about the problem and they remote fixed a few things they mentioned scanning the game while playing can cause it.
they added the whole game folder to the scan exclusion list. do you know from the results i posted would that cure the issue fully?
thanks

No I am unsure if that would fix it. You will know if the system doesnt crash. Symantec has a poor track record (IMO) and is difficult to remove.