Recurring BSOD over past few days - logs attached

penguinracer · 27 Mar 2012

Hi Guys,
Unfortunately I didn't write down the error code I got the last couple of times and cannot figure out how to bring it back up again. The BSOD seems to happen randomly and does not happen with any pattern that I have noticed so far (over the course of four crashes).

Attached are the log files and Perfmon html files. If there is an analyzer I can use to read these files and track down the cause, please let me know.

Thanks!!!
-Patrick

ePeen · 27 Mar 2012

Hello Patrick, my name's Patrick as well!

All of the attached dumps are the 7e* bugcheck, all point to the same culprit as well - nvlddmkm.sys, which is the nVidia video driver.

I recommend fully uninstalling your video card drivers and reinstalling the latest version. If you are on the latest version now and the BSODs just started happening, rollback a version or two that worked fine prior to the newest version.

Drivers that need to be updated:

tap0901.sys - Wed Oct 08 01:15:10 2008 (OpenVPN driver or COMODO). Update here or here (requires forum registration).

Dump for reference:

Code:

Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\Icarus\Downloads\032712-19390-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: 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 Personal
Built by: 7601.17727.amd64fre.win7sp1_gdr.111118-2330
Machine Name:
Kernel base = 0xfffff800`03667000 PsLoadedModuleList = 0xfffff800`038ab650
Debug session time: Tue Mar 27 11:42:57.332 2012 (UTC - 4:00)
System Uptime: 0 days 20:49:53.206
Loading Kernel Symbols
...............................................................
................................................................
...................................................
Loading User Symbols
Loading unloaded module list
..........
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, fffff8800f8248a3, fffff8800356fb38, fffff8800356f390}

Probably caused by : nvlddmkm.sys ( nvlddmkm+5748a3 )

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

6: 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: fffff8800f8248a3, The address that the exception occurred at
Arg3: fffff8800356fb38, Exception Record Address
Arg4: fffff8800356f390, 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+5748a3
fffff880`0f8248a3 44890401        mov     dword ptr [rcx+rax],r8d

EXCEPTION_RECORD:  fffff8800356fb38 -- (.exr 0xfffff8800356fb38)
ExceptionAddress: fffff8800f8248a3 (nvlddmkm+0x00000000005748a3)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000001
   Parameter[1]: 0000000000008250
Attempt to write to address 0000000000008250

CONTEXT:  fffff8800356f390 -- (.cxr 0xfffff8800356f390)
rax=0000000000008000 rbx=fffffa800c0da550 rcx=0000000000000250
rdx=0000000000000000 rsi=fffffa800b99f000 rdi=0000000000000002
rip=fffff8800f8248a3 rsp=fffff8800356fd70 rbp=fffffa800b9bb880
 r8=0000000000000004  r9=0000000000000010 r10=fffff8800356fa00
r11=fffffa8009d30000 r12=fffffa800b9b25b0 r13=fffffa800c0da480
r14=0000000000000000 r15=0000000000000002
iopl=0         nv up ei pl nz na pe nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010202
nvlddmkm+0x5748a3:
fffff880`0f8248a3 44890401        mov     dword ptr [rcx+rax],r8d ds:002b:00000000`00008250=????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

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:  0000000000008250

WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80003915100
 0000000000008250 

FOLLOWUP_IP: 
nvlddmkm+5748a3
fffff880`0f8248a3 44890401        mov     dword ptr [rcx+rax],r8d

BUGCHECK_STR:  0x7E

LAST_CONTROL_TRANSFER:  from fffffa800c0da550 to fffff8800f8248a3

STACK_TEXT:  
fffff880`0356fd70 fffffa80`0c0da550 : fffffa80`0b99f000 fffffa80`00000000 fffffa80`0b99f000 fffff880`0356fdd4 : nvlddmkm+0x5748a3
fffff880`0356fd78 fffffa80`0b99f000 : fffffa80`00000000 fffffa80`0b99f000 fffff880`0356fdd4 fffff880`0356fea8 : 0xfffffa80`0c0da550
fffff880`0356fd80 fffffa80`00000000 : fffffa80`0b99f000 fffff880`0356fdd4 fffff880`0356fea8 fffff880`0356fdb8 : 0xfffffa80`0b99f000
fffff880`0356fd88 fffffa80`0b99f000 : fffff880`0356fdd4 fffff880`0356fea8 fffff880`0356fdb8 fffff880`0356fea0 : 0xfffffa80`00000000
fffff880`0356fd90 fffff880`0356fdd4 : fffff880`0356fea8 fffff880`0356fdb8 fffff880`0356fea0 00000000`00008000 : 0xfffffa80`0b99f000
fffff880`0356fd98 fffff880`0356fea8 : fffff880`0356fdb8 fffff880`0356fea0 00000000`00008000 fffffa80`00000254 : 0xfffff880`0356fdd4
fffff880`0356fda0 fffff880`0356fdb8 : fffff880`0356fea0 00000000`00008000 fffffa80`00000254 00000000`00000000 : 0xfffff880`0356fea8
fffff880`0356fda8 fffff880`0356fea0 : 00000000`00008000 fffffa80`00000254 00000000`00000000 fffffa80`0bffc650 : 0xfffff880`0356fdb8
fffff880`0356fdb0 00000000`00008000 : fffffa80`00000254 00000000`00000000 fffffa80`0bffc650 00000001`00000000 : 0xfffff880`0356fea0
fffff880`0356fdb8 fffffa80`00000254 : 00000000`00000000 fffffa80`0bffc650 00000001`00000000 fffff880`0356fe10 : 0x8000
fffff880`0356fdc0 00000000`00000000 : fffffa80`0bffc650 00000001`00000000 fffff880`0356fe10 00000000`00000002 : 0xfffffa80`00000254


SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  nvlddmkm+5748a3

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4dbf4e5f

STACK_COMMAND:  .cxr 0xfffff8800356f390 ; kb

FAILURE_BUCKET_ID:  X64_0x7E_nvlddmkm+5748a3

BUCKET_ID:  X64_0x7E_nvlddmkm+5748a3

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

penguinracer · 27 Mar 2012

Awesome! Thanks for your help ePeen!!! I installed the latest driver so hopefully the new driver fixed whatever was buggy.