Is Windows 7 Professional x64 its the original OS on the system it is less than one month old hardware (never reinstalled OS and it is less than one month old as well.) So I was running crysis fine after I tried playing around with CUDA I can't play crysis anymore I get a BSOD with information bellow. I tried resintalling drivers (as instructed on other posts) to no avail, I have all the latest drivers. Attached is the Windows_NT6_BSOD_jcgriff2 folder, the PERFMON HTML, and the DUMP file (in case it helps.) On cyrsis I never see the BSOD per se my display goes black and my computer freezes, on Furmark i'm able to max out GPU temperature (85 C) without problems (my GPU is not OC'ed.) Thanks in advance!
Code:
Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7600.2.0.0.256.48
Locale ID: 1033
Additional information about the problem:
BCCode: 116
BCP1: FFFFFA8011C8C4E0
BCP2: FFFFF880080216F0
BCP3: FFFFFFFFC000009A
BCP4: 0000000000000004
OS Version: 6_1_7600
Service Pack: 0_0
Product: 256_1
These are all virtually identical. They are a classic video card reset. The system found a video problem and attempted to reset the video card but it took too long to respond so the crash.
I know you have installed the video drivers but give it another try this way.
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\032711-16208-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 (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Machine Name:
Kernel base = 0xfffff800`0320d000 PsLoadedModuleList = 0xfffff800`0344ae50
Debug session time: Sun Mar 27 10:34:58.129 2011 (GMT-4)
System Uptime: 0 days 0:50:29.004
Loading Kernel Symbols
...............................................................
................................................................
..........................................................
Loading User Symbols
Loading unloaded module list
..............
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 116, {fffffa8011c8c4e0, fffff880080216f0, 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+7dd6f0 )
Followup: MachineOwner
---------
7: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: fffffa8011c8c4e0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff880080216f0, 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+7dd6f0
fffff880`080216f0 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`0d4c6b48 fffff880`10ae6000 : 00000000`00000116 fffffa80`11c8c4e0 fffff880`080216f0 ffffffff`c000009a : nt!KeBugCheckEx
fffff880`0d4c6b50 fffff880`10ab9867 : fffff880`080216f0 fffffa80`111ec000 00000000`00000000 ffffffff`c000009a : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`0d4c6b90 fffff880`10ae5e0f : fffffa80`ffffd84d 00000000`00000000 fffffa80`11c8c4e0 00000000`00000000 : dxgkrnl!DXGADAPTER::Reset+0x2a3
fffff880`0d4c6c40 fffff880`10bb4ec1 : fffffa80`10b1e370 00000000`00000080 00000000`00000000 fffffa80`10e520f0 : dxgkrnl!TdrResetFromTimeout+0x23
fffff880`0d4c6cc0 fffff800`035207c6 : fffff880`0b8fb650 fffffa80`10806310 fffffa80`0cd635f0 fffff800`032755c7 : dxgmms1!VidSchiWorkerThread+0x101
fffff880`0d4c6d00 fffff800`0325bc26 : fffff880`009b2180 fffffa80`10806310 fffff880`009bd0c0 fffff880`01263a90 : nt!PspSystemThreadStartup+0x5a
fffff880`0d4c6d40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16
STACK_COMMAND: .bugcheck ; kb
FOLLOWUP_IP:
nvlddmkm+7dd6f0
fffff880`080216f0 4883ec28 sub rsp,28h
SYMBOL_NAME: nvlddmkm+7dd6f0
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nvlddmkm
IMAGE_NAME: nvlddmkm.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4d61a03d
FAILURE_BUCKET_ID: X64_0x116_IMAGE_nvlddmkm.sys
BUCKET_ID: X64_0x116_IMAGE_nvlddmkm.sys
Followup: MachineOwner
---------
7: kd> lmvm nvlddmkm
start end module name
fffff880`07844000 fffff880`084df300 nvlddmkm T (no symbols)
Loaded symbol image file: nvlddmkm.sys
Image path: \SystemRoot\system32\DRIVERS\nvlddmkm.sys
Image name: nvlddmkm.sys
Timestamp: Sun Feb 20 18:14:05 2011 (4D61A03D)
CheckSum: 00C9F6C0
ImageSize: 00C9B300
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
Also these drivers are way too old and need updating.
Code:
lvpopf64.sys 5/11/2007 07:56:21 PM fffff880`06e96000 fffff880`06fe0d00 0x0014ad00 0x464502a5
lvuvc64.sys 5/11/2007 07:59:12 PM fffff880`02861000 fffff880`02bd1500 0x00370500 0x46450350
LVUSBS64.sys 5/11/2007 08:01:20 PM fffff880`07760000 fffff880`0776a900 0x0000a900 0x464503d0
ctac32k.sys 7/2/2008 04:38:22 AM fffff880`05800000 fffff880`058ae000 0x000ae000 0x486b3e7e
nvcwfpco.sys 12/4/2008 12:08:32 PM fffff880`0a74c000 fffff880`0a762000 0x00016000 0x49380080
ntnvca.sys 12/4/2008 12:08:39 PM fffff880`052b5000 fffff880`052c3000 0x0000e000 0x49380087
How To Find Drivers:
- search Google for the name of the driver
- compare the Google results with what's installed on your system to figure out which device/program it belongs to
- visit the web site of the manufacturer of the hardware/program to get the latest drivers (DON'T use Windows Update or the Update driver function of Device Manager).
- if there are difficulties in locating them, post back with questions and someone will try and help you locate the appropriate program.
- - The most common drivers are listed on this page: Driver Reference Driver Reference
- - Driver manufacturer links are on this page: Drivers and Downloads
Quote