Chronic NTSKRNL.exe BSOD's and GPU related BSOD's

brennon13 · 07 Sep 2012

I bought this PC used from a friend who said he never had any issues with the system and the price was right. From the start I had issues getting BSOD's while gaming (WoW, Diablo 3, Metro 2033 etc) though sometimes while simply watching a youtube video or a movie file. I should note that the games I play are installed on my secondary drive not the main SSD, but I have had BSOD's just running basic apps though much less frequent. After countless BSOD's I began to troubleshoot and eventually reinstalling windows. At first I figured it was audio related as it seemed the issue only happened when I used on board audio, but after using HDMI audio I found the issue still occurred. When this didnt work I began blaming hardware. First thing i replaced was the Wireless card as I did see some BSOD files that referred to the wireless card but this did not help. Next I replaced the GPU, previously an AMD Radeon HD 6870, and now an NVIDIA GeForce GTX 560ti (cpu and gpu are not overclocked) but the issue still occurs. I've tried almost everything I can think of shy of replacing the Mobo itself.

I have attached the 8 most recent BSOD files as .txt for anyone to review that can give me any suggestions or ideas what to do/try next.

I consider my self an intermediate PC user with a good understanding of hardware components and how they work but software ends of things go over my head a wee bit so head warning if i reply asking what your talking about.

Brennon
(PC Specs in profile)

koolkat77 · 07 Sep 2012

Welcome

BSOD Analyze

Code:

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
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000007E, {ffffffffc0000005, fffff88013cfeb60, fffff880033b4128, fffff880033b3980}
Probably caused by : hardware ( nvlddmkm+ccab60 )
Followup: MachineOwner
---------
5: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003.  This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG.  This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG.  This will let us see why this breakpoint is
happening.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff88013cfeb60, The address that the exception occurred at
Arg3: fffff880033b4128, Exception Record Address
Arg4: fffff880033b3980, Context Record Address
Debugging Details:
------------------
 
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
FAULTING_IP: 
nvlddmkm+ccab60
fffff880`13cfeb60 0000            add     byte ptr [rax],al
EXCEPTION_RECORD:  fffff880033b4128 -- (.exr 0xfffff880033b4128)
ExceptionAddress: fffff88013cfeb60 (nvlddmkm+0x0000000000ccab60)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000001
   Parameter[1]: 0000000000000000
Attempt to write to address 0000000000000000
CONTEXT:  fffff880033b3980 -- (.cxr 0xfffff880033b3980)
rax=0000000000000000 rbx=0000000000000002 rcx=fffff880033b40c0
rdx=fffff880033b4530 rsi=0000000000000000 rdi=fffffa800b1d0000
rip=fffff88013cfeb60 rsp=fffff880033b4360 rbp=0000000000000002
 r8=fffff880033b40c0  r9=0000000000080000 r10=0000000000000000
r11=00000000001e0000 r12=0000000000000000 r13=0001f5d000000000
r14=0000000000000000 r15=fffff88009ab0a30
iopl=0         nv up ei ng nz na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00210286
nvlddmkm+0xccab60:
fffff880`13cfeb60 0000            add     byte ptr [rax],al ds:002b:00000000`00000000=??
Resetting default scope
CUSTOMER_CRASH_COUNT:  1
DEFAULT_BUCKET_ID:  NULL_DEREFERENCE
PROCESS_NAME:  System
CURRENT_IRQL:  0
ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
EXCEPTION_PARAMETER1:  0000000000000001
EXCEPTION_PARAMETER2:  0000000000000000
WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff800030b1100
 0000000000000000 
FOLLOWUP_IP: 
nvlddmkm+ccab60
fffff880`13cfeb60 0000            add     byte ptr [rax],al
BUGCHECK_STR:  0x7E
MISALIGNED_IP: 
nvlddmkm+ccab60
fffff880`13cfeb60 0000            add     byte ptr [rax],al
LAST_CONTROL_TRANSFER:  from fffff880033b4530 to fffff88013cfeb60
STACK_TEXT:  
fffff880`033b4360 fffff880`033b4530 : fffff880`1313ba40 fffffa80`0b43f010 fffff880`033b4530 00000000`00000002 : nvlddmkm+0xccab60
fffff880`033b4368 fffff880`1313ba40 : fffffa80`0b43f010 fffff880`033b4530 00000000`00000002 00000000`d0160000 : 0xfffff880`033b4530
fffff880`033b4370 fffffa80`0b43f010 : fffff880`033b4530 00000000`00000002 00000000`d0160000 fffff880`13928218 : nvlddmkm+0x107a40
fffff880`033b4378 fffff880`033b4530 : 00000000`00000002 00000000`d0160000 fffff880`13928218 fffffa80`0a6f9000 : 0xfffffa80`0b43f010
fffff880`033b4380 00000000`00000002 : 00000000`d0160000 fffff880`13928218 fffffa80`0a6f9000 fffff880`1392fe80 : 0xfffff880`033b4530
fffff880`033b4388 00000000`d0160000 : fffff880`13928218 fffffa80`0a6f9000 fffff880`1392fe80 00000000`00000000 : 0x2
fffff880`033b4390 fffff880`13928218 : fffffa80`0a6f9000 fffff880`1392fe80 00000000`00000000 fffff880`033b4530 : 0xd0160000
fffff880`033b4398 fffffa80`0a6f9000 : fffff880`1392fe80 00000000`00000000 fffff880`033b4530 fffff880`13d6011e : nvlddmkm+0x8f4218
fffff880`033b43a0 fffff880`1392fe80 : 00000000`00000000 fffff880`033b4530 fffff880`13d6011e fffffa80`0a6f9000 : 0xfffffa80`0a6f9000
fffff880`033b43a8 00000000`00000000 : fffff880`033b4530 fffff880`13d6011e fffffa80`0a6f9000 fffff880`13cfeb60 : nvlddmkm+0x8fbe80
 
SYMBOL_STACK_INDEX:  0
SYMBOL_NAME:  nvlddmkm+ccab60
FOLLOWUP_NAME:  MachineOwner
MODULE_NAME: hardware
IMAGE_NAME:  hardware
DEBUG_FLR_IMAGE_TIMESTAMP:  0
STACK_COMMAND:  .cxr 0xfffff880033b3980 ; kb
FAILURE_BUCKET_ID: X64_IP_MISALIGNED_nvlddmkm.sys
BUCKET_ID:  X64_IP_MISALIGNED_nvlddmkm.sys
Followup: MachineOwner
---------

Suggestions:

Download and install Driver_Sweeper
Reboot the computer to Advanced Boot Options, Safe Mode.
Click on the start and search for Driver Fusion
Uninstall the drivers of your nVidia display driver

Boot normally and Drivers - Download NVIDIA Drivers | Using option 2 from this link http://www.nvidia.in/Download/index.aspx?lang=en-in | nvlddmkm.sys

Then test the video card following the tutorial below:

Video Card - Stress Test with Furmark

brennon13 · 07 Sep 2012

Considering I've had the same issue with 2 different graphics cards I fail to see how the drivers are an issue. I will attempt what your suggesting but I'm highly skeptical about it. Also, I have run several stress tests and they all run fine without lag, artifacting or any significant heat issues...

brennon13 · 07 Sep 2012

As i figured, After doing what was suggested still getting BSOD... this time showing tcpip.sys which is new but not the first network related Ive seen... (dump attached)

would really appreciate some proper guidance here...

Arc · 07 Sep 2012

tcpip.sys is network related. So you should update your network driver.
First, download the network card driver from manufactuer's website.
Then reinstall the driver:

Click the Start Button, type "devmgmt.msc" (without quotation marks) in the Start Menu Search box and press Enter.
Double click to expand "Network adaptors".
Right click your network card and click Uninstall.
Check "Delete driver software for this device" check box, click OK.
Restart the computer
If windows does not auto configure the appropriate drivers at startup, install the downloaded one manually.

Next time please post following the Blue Screen of Death (BSOD) Posting Instructions

centaur78 · 08 Sep 2012

Brennon

Let start by taking the most obvious causes of BSOD out of the loop

Based on the dmps and the logs and your system settings here is my analyses.

1. Most of the BSOD has access violation error usually a sign of problem with accessing the memory... so please do a memtest for at least 6-8 passes for each RAM at each slot .. this is going to take long and better do it overnight.... You might have done this before... but i would prefer you do this for each stick at each slot for 6 - 8 passes...

2. You bios has updates....Your current version is F4 and the once available is F5A. Please update this.

3. In your logs , precursor to your bsod..... you have these entries... these are caused by you Logitech Gaming Keyboard G510 drivers.... . which has know issues with Windows 7 and causes of BSOD.... Please uninstall ....i repeat please uninstall all the software and drivers related to Logitech.... If possible after you do this ... use a normal keyboard... till we finish troubleshooting

The driver \Driver\WUDFRd failed to load for the device Root\SIDESHOW\0000.

The UMDF reflector was unable to complete startup because the WUDFPf service was not found. This service may be started later during boot, at which point Windows will attempt to start the device again.

The driver \Driver\WUDFRd failed to load for the device Root\SIDESHOW\0001.

4. I am not sure you removed the ATI drivers....prior to the installation of the Nvidia cards and drives...as there are remnants of the ATI Fuel service and drivers.......I would suggest you use revo uninstaller or iobit uninstaller to completely remove it....

Do these and let me know

brennon13 · 08 Sep 2012

I will do this tomorrow and post back, I have done a basic mem test a long time ago but it's a good idea.. I'm pretty sure I just did a bios update as well but will also try that, will post back ASAP.

brennon13 · 09 Sep 2012

So, memtest ran fine, I let it do 8 passes with no errors. I was having the BSOD issue before I got the Logitech G510 keyboard, but I did remove it any way. I updated my BIOS to the most current version and did everything I could think of to get rid of any lingering AMD stuff... long story short, still getting BSOD's. Re-ran SF Diagnostics and re attaching.

Arc · 09 Sep 2012

Have you done this?

Then test the video card following the tutorial below:

Video Card - Stress Test with Furmark

Somehow your display driver causing problems to your Graphics card.

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {ffffffffc0000005, fffff88013cfeb60, fffff880033b4128, fffff880033b3980}

Probably caused by : hardware ( nvlddmkm+ccab60 )

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

brennon13 · 09 Sep 2012

I've ran several stress tests and they all run fine. Including the above mentioned one... It's odd because sometimes it will bsod 3 times in an hour and sometimes I'll go 6 hours straight on diablo 3 without one I cannot find a specific trigger