Windows 7: New BSOD on Boot, once every two days

Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\JMH\Desktop\Windows_NT6_BSOD_jcgriff2-604\060811-19765-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 (6 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16792.amd64fre.win7_gdr.110408-1633
Machine Name:
Kernel base = 0xfffff800`0305a000 PsLoadedModuleList = 0xfffff800`03297e50
Debug session time: Wed Jun  8 11:26:02.432 2011 (GMT-4)
System Uptime: 0 days 0:00:14.430
Loading Kernel Symbols
...............................................................
................................................................
......
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1E, {ffffffffc0000005, fffff88014283b9c, 0, 1890}

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+408b9c )

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

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

KMODE_EXCEPTION_NOT_HANDLED (1e)
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.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff88014283b9c, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: 0000000000001890, Parameter 1 of the exception

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+408b9c
fffff880`14283b9c ff9090180000    call    qword ptr [rax+1890h]

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  0000000000001890

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800033020e0
 0000000000001890 

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x1E

PROCESS_NAME:  csrss.exe

CURRENT_IRQL:  0

EXCEPTION_RECORD:  fffff88005f9f5a8 -- (.exr 0xfffff88005f9f5a8)
ExceptionAddress: fffff88014283b9c (nvlddmkm+0x0000000000408b9c)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: 0000000000001890
Attempt to read from address 0000000000001890

TRAP_FRAME:  fffff88005f9f650 -- (.trap 0xfffff88005f9f650)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000000
rdx=0000000000000046 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88014283b9c rsp=fffff88005f9f7e0 rbp=0000000000000000
 r8=0000000000000000  r9=0000000000000000 r10=fffff80003259888
r11=fffff88005f9f820 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na po nc
nvlddmkm+0x408b9c:
fffff880`14283b9c ff9090180000    call    qword ptr [rax+1890h] ds:f820:00000000`00001890=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80003104ab9 to fffff800030ca700

STACK_TEXT:  
fffff880`05f9edd8 fffff800`03104ab9 : 00000000`0000001e ffffffff`c0000005 fffff880`14283b9c 00000000`00000000 : nt!KeBugCheckEx
fffff880`05f9ede0 fffff800`030c9d42 : fffff880`05f9f5a8 00000000`00000000 fffff880`05f9f650 fffffa80`0f17abb0 : nt!KiDispatchException+0x1b9
fffff880`05f9f470 fffff800`030c88ba : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000801 : nt!KiExceptionDispatch+0xc2
fffff880`05f9f650 fffff880`14283b9c : fffffa80`0e26b000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x23a
fffff880`05f9f7e0 fffffa80`0e26b000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nvlddmkm+0x408b9c
fffff880`05f9f7e8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 fffffa80`0ecb0000 : 0xfffffa80`0e26b000


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nvlddmkm+408b9c
fffff880`14283b9c ff9090180000    call    qword ptr [rax+1890h]

SYMBOL_STACK_INDEX:  4

SYMBOL_NAME:  nvlddmkm+408b9c

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4dd73a68

FAILURE_BUCKET_ID:  X64_0x1E_nvlddmkm+408b9c

BUCKET_ID:  X64_0x1E_nvlddmkm+408b9c

Followup: MachineOwner

---------