BSOD 4A - prime stable, memtest stable in safe mode.

[Stvwndr219]

Hey guys,

You've been a great resource for my past BSOD issues but I have a new one now and hope you can help. I recently started getting random freezes with no BSODs so I've been fiddling with the BIOS settings and such until I got a BSOD. Here is the BSOD I got, hopefully this will help me get toward the freeze problem.

System:
Core i7 920 (@4.2 Ghz - prime stable in safe mode, system freezes in regular windows)
Rampage III Formula
3 x 2GB Kingston HyperX (7-8-7-20-1T)
OS Drive 80GB Intel G2 SSD
2 x GTX 470 SLi

Retail Version of x64 Windows 7 - System hardware is less than a year and a half old; OS installation is approximately a year and a couple months old.

Attached is the zip file with the recommended files.

Thanks!

 

[zigzag3143]

Hey guys,

You've been a great resource for my past BSOD issues but I have a new one now and hope you can help. I recently started getting random freezes with no BSODs so I've been fiddling with the BIOS settings and such until I got a BSOD. Here is the BSOD I got, hopefully this will help me get toward the freeze problem.

System:
Core i7 920 (@4.2 Ghz - prime stable in safe mode, system freezes in regular windows)
Rampage III Formula
3 x 2GB Kingston HyperX (7-8-7-20-1T)
OS Drive 80GB Intel G2 SSD
2 x GTX 470 SLi

Retail Version of x64 Windows 7 - System hardware is less than a year and a half old; OS installation is approximately a year and a couple months old.

Attached is the zip file with the recommended files.

Thanks!

The more recent ones are classic BC116 (video reset timeout). Means your system tried to reset the video card but it took to long

Causes include video driver, card, power, heat, vram.

I would re-install the video driver with the newest version using this
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.

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\050411-51792-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 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Machine Name:
Kernel base = 0xfffff800`0481b000 PsLoadedModuleList = 0xfffff800`04a60e90
Debug session time: Wed May  4 18:26:18.789 2011 (GMT-4)
System Uptime: 0 days 22:17:36.584
Loading Kernel Symbols
...............................................................
................................................................
................................................................
..................
Loading User Symbols
Loading unloaded module list
.........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 116, {fffffa8008ea11f0, fffff8800f9f0970, 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
---------

7: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: fffffa8008ea11f0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff8800f9f0970, 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`0f9f0970 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`042dab88 fffff880`0ff10000 : 00000000`00000116 fffffa80`08ea11f0 fffff880`0f9f0970 ffffffff`c000009a : nt!KeBugCheckEx
fffff880`042dab90 fffff880`0fee3867 : fffff880`0f9f0970 fffffa80`07c33000 00000000`00000000 ffffffff`c000009a : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`042dabd0 fffff880`0ff0fe0f : 00000000`ffffd84d ffffffff`fffe7960 fffffa80`08ea11f0 00000000`0000000f : dxgkrnl!DXGADAPTER::Reset+0x2a3
fffff880`042dac80 fffff880`0ffdeec1 : fffffa80`07cd8660 00000000`00000080 00000000`00000000 fffffa80`07adc410 : dxgkrnl!TdrResetFromTimeout+0x23
fffff880`042dad00 fffff800`04b38cce : 00000000`09d9f9f0 fffffa80`07727b60 fffffa80`0548eb30 fffffa80`07727b60 : dxgmms1!VidSchiWorkerThread+0x101
fffff880`042dad40 fffff800`0488cfe6 : fffff800`04a0de80 fffffa80`07727b60 fffff800`04a1bcc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`042dad80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_IP: 
nvlddmkm+7e4970
fffff880`0f9f0970 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
---------

7: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: fffffa8008ea11f0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff8800f9f0970, 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`0f9f0970 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`042dab88 fffff880`0ff10000 : 00000000`00000116 fffffa80`08ea11f0 fffff880`0f9f0970 ffffffff`c000009a : nt!KeBugCheckEx
fffff880`042dab90 fffff880`0fee3867 : fffff880`0f9f0970 fffffa80`07c33000 00000000`00000000 ffffffff`c000009a : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`042dabd0 fffff880`0ff0fe0f : 00000000`ffffd84d ffffffff`fffe7960 fffffa80`08ea11f0 00000000`0000000f : dxgkrnl!DXGADAPTER::Reset+0x2a3
fffff880`042dac80 fffff880`0ffdeec1 : fffffa80`07cd8660 00000000`00000080 00000000`00000000 fffffa80`07adc410 : dxgkrnl!TdrResetFromTimeout+0x23
fffff880`042dad00 fffff800`04b38cce : 00000000`09d9f9f0 fffffa80`07727b60 fffffa80`0548eb30 fffffa80`07727b60 : dxgmms1!VidSchiWorkerThread+0x101
fffff880`042dad40 fffff800`0488cfe6 : fffff800`04a0de80 fffffa80`07727b60 fffff800`04a1bcc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`042dad80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_IP: 
nvlddmkm+7e4970
fffff880`0f9f0970 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
---------

 

[Stvwndr219]

Hi,

Thanks for your reply. I've managed to resolve the nvklddm.sys problem by doing a clean install of my drivers. I also adjusted the TDR values in the registry which seemed to help with all the freezes I was getting in games.

It's the 4A BSOD that concerns me as the minidump pointed to svchost.exe. Also, not sure what to make of the errors on perfmon.

Any insight? The BSOD occurred right after I started prime95 after a few hours with the computer on. When it happened, I let it collect the dump and rebooted the computer. Went into Safemode and prime95 worked fine for 45 mins. Rebooted into normal mode and it worked fine for the 5 minutes I had the computer on before I decided it would be more prudent to wait for your insight. I guess I could always reinstall the OS and check that way...

Thanks!

 

[zigzag3143]

Hi,

Thanks for your reply. I've managed to resolve the nvklddm.sys problem by doing a clean install of my drivers. I also adjusted the TDR values in the registry which seemed to help with all the freezes I was getting in games.

It's the 4A BSOD that concerns me as the minidump pointed to svchost.exe. Also, not sure what to make of the errors on perfmon.

Any insight? The BSOD occurred right after I started prime95 after a few hours with the computer on. When it happened, I let it collect the dump and rebooted the computer. Went into Safemode and prime95 worked fine for 45 mins. Rebooted into normal mode and it worked fine for the 5 minutes I had the computer on before I decided it would be more prudent to wait for your insight. I guess I could always reinstall the OS and check that way...

Thanks!

While extreme the re-install is the fastest, easiest way to get rid of pesky problems. I do it every 3 months needed or not.

The difference between prime in safe mode and in normal still feels like a driver conflict so I would.