laptop BSODs, several hours apart, unknown cause

DBlanc · 02 Mar 2013

The computer just bluescreened again, and it turns out its done it a few times since I thought it was fixed, just not with me, so I didn't know. I looks to have only happened a few times, and it seems like its usually when the computer is beening woken up from hibernation.

**Pauly** · 03 Mar 2013

Looks to be the same old problem, all recent dumps are same error code and all blame nvidia drivers, have a look at this snip, its a summary of all your crashes
Attachment 257819

Heres an output of the most recent one but they are all identical, i have highlighted the important parts

Code:

*** 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, fffff8800f8b8310, fffff8802235d308, fffff8802235cb60}
Probably caused by : nvlddmkm.sys ( nvlddmkm+45d310 )
Followup: MachineOwner
---------
0: 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: fffff8800f8b8310, The address that the exception occurred at
Arg3: fffff8802235d308, Exception Record Address
Arg4: fffff8802235cb60, 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+45d310
fffff880`0f8b8310 ff9068050000    call    qword ptr [rax+568h]
EXCEPTION_RECORD:  fffff8802235d308 -- (.exr 0xfffff8802235d308)
ExceptionAddress: fffff8800f8b8310 (nvlddmkm+0x000000000045d310)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: 0000000000000568
Attempt to read from address 0000000000000568
CONTEXT:  fffff8802235cb60 -- (.cxr 0xfffff8802235cb60)
rax=0000000000000000 rbx=fffffa8008933bb0 rcx=fffffa8009628000
rdx=0000000000000000 rsi=0000000000000002 rdi=0000000000000000
rip=fffff8800f8b8310 rsp=fffff8802235d540 rbp=fffff8802235d590
 r8=0000000000000000  r9=0000000000000000 r10=fffffa8009628000
r11=0000000000022500 r12=0000000000000000 r13=fffffa800967d001
r14=0000000000000002 r15=fffffa8009628000
iopl=0         nv up ei ng nz na pe nc
cs=0010  ss=0000  ds=002b  es=002b  fs=0053  gs=002b             efl=00010282
nvlddmkm+0x45d310:
fffff880`0f8b8310 ff9068050000    call    qword ptr [rax+568h] ds:002b:00000000`00000568=????????????????
Resetting default scope
CUSTOMER_CRASH_COUNT:  1
DEFAULT_BUCKET_ID:  WIN7_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:  0000000000000000
EXCEPTION_PARAMETER2:  0000000000000568
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800032fa100
GetUlongFromAddress: unable to read from fffff800032fa1c0
 0000000000000568 Nonpaged pool
FOLLOWUP_IP: 
nvlddmkm+45d310
fffff880`0f8b8310 ff9068050000    call    qword ptr [rax+568h]
BUGCHECK_STR:  0x7E
LAST_CONTROL_TRANSFER:  from fffffa8008933bb0 to fffff8800f8b8310
STACK_TEXT:  
fffff880`2235d540 fffffa80`08933bb0 : 00000000`00000002 00000000`00000000 fffff880`2235d590 00000000`00000005 : nvlddmkm+0x45d310
fffff880`2235d548 00000000`00000002 : 00000000`00000000 fffff880`2235d590 00000000`00000005 00000000`0017e8c0 : 0xfffffa80`08933bb0
fffff880`2235d550 00000000`00000000 : fffff880`2235d590 00000000`00000005 00000000`0017e8c0 00000000`3f800ff3 : 0x2
 
SYMBOL_STACK_INDEX:  0
SYMBOL_NAME:  nvlddmkm+45d310
FOLLOWUP_NAME:  MachineOwner
MODULE_NAME: nvlddmkm
IMAGE_NAME:  nvlddmkm.sys
DEBUG_FLR_IMAGE_TIMESTAMP:  506b3099
STACK_COMMAND:  .cxr 0xfffff8802235cb60 ; kb
FAILURE_BUCKET_ID:  X64_0x7E_nvlddmkm+45d310
BUCKET_ID:  X64_0x7E_nvlddmkm+45d310
Followup: MachineOwner
---------
0: kd> lmvm nvlddmkm
start             end                 module name
fffff880`0f45b000 fffff880`1014f000   nvlddmkm T (no symbols)           
    Loaded symbol image file: nvlddmkm.sys
   Image path: \SystemRoot\system32\DRIVERS\nvlddmkm.sys
   Image name: nvlddmkm.sys
   Timestamp:        Tue Oct 02 19:21:13 2012 (506B3099)
    CheckSum:         00CD4613
    ImageSize:        00CF4000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

First you can see the actual driver reports to not be loaded properly, this can sometimes indicate a problem with the driver not being installed properly or is not compatible on some level

The last part you can see tells us the driver is dated from oct 2012 so is not the latest, the problematic one was dated around dec 12/jan 13 but i believe that has now been superceded so it may be worth trying one last update as before

Update your graphics drivers to the latest ones, its best to uninstall old drivers then run Drivers - Clean Left over Files after Uninstalling then install new drivers from here Drivers - Download NVIDIA Drivers option 2 is easiest as will auto detect what you need.

Failing that some manufacturers make custom modded drivers for there machines (dell for eg) so may be worth checking into this also

Lastly you need to keep an eye on your temps for your gfx card as this could still be a hardware fault
If you want to check your card out you could try Video Card - Stress Test with Furmark while checking temps