New
#1
Cold Boot BSOD
BSOD on startup after 8 hours or so of being off overnight. Occurs everyday.
Ran memtest+86 & passed 7 loops..
I remove a ram stick & replace it for the BSODs to go away and windows to startup, continues to run fine all day.
Ran through windbg but I don't really know what I'm looking at.
I have also attached my minidump file and my system.nfo for reference if needed.
In hopes that I was reading the results correctly I updated my nvidia drivers from nvidia's website and thought it would help, but no luck.
Thanks in advance, any ideas or suggestions are appreciated.
Code:Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [c:\windows\minidump\031310-15406-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;symsrv*symsrv.dll*c:\symbols*http://msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel Version 7600 MP (3 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7600.16385.amd64fre.win7_rtm.090713-1255 Machine Name: Kernel base = 0xfffff800`02a15000 PsLoadedModuleList = 0xfffff800`02c52e50 Debug session time: Sat Mar 13 07:43:47.609 2010 (UTC - 6:00) System Uptime: 0 days 0:00:15.015 Loading Kernel Symbols ............................................................... ................................................................ .... Loading User Symbols Loading unloaded module list .... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck A, {10, 2, 1, fffff80002aac35f} 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+1fd27 ) Processing initial command '!analyze -v' Followup: MachineOwner --------- 2: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* IRQL_NOT_LESS_OR_EQUAL (a) An attempt was made to access a pageable (or completely invalid) address at an interrupt request level (IRQL) that is too high. This is usually caused by drivers using improper addresses. If a kernel debugger is available get the stack backtrace. Arguments: Arg1: 0000000000000010, memory referenced Arg2: 0000000000000002, IRQL Arg3: 0000000000000001, bitfield : bit 0 : value 0 = read operation, 1 = write operation bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status) Arg4: fffff80002aac35f, address which referenced memory Debugging Details: ------------------ WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002cbd0e0 0000000000000010 CURRENT_IRQL: 2 FAULTING_IP: nt!MiReplenishPageSlist+100 fffff800`02aac35f f00fba6b1000 lock bts dword ptr [rbx+10h],0 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0xA PROCESS_NAME: csrss.exe TRAP_FRAME: fffff88005de5ac0 -- (.trap 0xfffff88005de5ac0) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=ffffffffffffffff rbx=0000000000000000 rcx=fdffffffffffffff rdx=0000000000000047 rsi=0000000000000000 rdi=0000000000000000 rip=fffff80002aac35f rsp=fffff88005de5c50 rbp=fffffa8006600de8 r8=fffff80002cbf400 r9=fffffa8006600000 r10=000000000021ffff r11=0000000000000000 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei pl nz na pe nc nt!MiReplenishPageSlist+0x100: fffff800`02aac35f f00fba6b1000 lock bts dword ptr [rbx+10h],0 ds:00000000`00000010=???????? Resetting default scope LAST_CONTROL_TRANSFER: from fffff80002a86469 to fffff80002a86f00 STACK_TEXT: fffff880`05de5978 fffff800`02a86469 : 00000000`0000000a 00000000`00000010 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx fffff880`05de5980 fffff800`02a850e0 : 00000000`00000021 00000000`00000000 fffffa80`079c6c40 00000000`00000000 : nt!KiBugCheckDispatch+0x69 fffff880`05de5ac0 fffff800`02aac35f : fffffa80`0890ac50 fffff880`04948887 fffffa80`078e7010 00000000`00000801 : nt!KiPageFault+0x260 fffff880`05de5c50 fffff800`02ba76ec : fffff800`02cbf400 00000000`0000174e 00000000`00000059 fffffa80`028390b0 : nt!MiReplenishPageSlist+0x100 fffff880`05de5cb0 fffff800`02ba7f06 : 00000000`00000080 00000000`00004000 00000000`00000000 00000000`0021ffff : nt!MiAllocateMdlPagesByLists+0x60c fffff880`05de5de0 fffff800`02ba8769 : 00000000`00000001 fffff880`05de6801 fffffa80`07cb3000 fffff880`038d5000 : nt!MiAllocatePagesForMdl+0x456 fffff880`05de5ee0 fffff880`04824d27 : 00000000`00000000 fffffa80`07b77ba0 00000000`00000000 fffff880`05de6980 : nt!MmAllocatePagesForMdlEx+0x89 fffff880`05de5f20 00000000`00000000 : fffffa80`07b77ba0 00000000`00000000 fffff880`05de6980 fffffa80`00000001 : nvlddmkm+0x1fd27 STACK_COMMAND: kb FOLLOWUP_IP: nvlddmkm+1fd27 fffff880`04824d27 ?? ??? SYMBOL_STACK_INDEX: 7 SYMBOL_NAME: nvlddmkm+1fd27 FOLLOWUP_NAME: MachineOwner MODULE_NAME: nvlddmkm IMAGE_NAME: nvlddmkm.sys DEBUG_FLR_IMAGE_TIMESTAMP: 4a5ce19c FAILURE_BUCKET_ID: X64_0xA_nvlddmkm+1fd27 BUCKET_ID: X64_0xA_nvlddmkm+1fd27 Followup: MachineOwner ---------