New
#11
Hi and welcome
this one was caused by nvstor.sys. the the other two were not. My gut says you should
update you graphics driver, and directx.
I would also run a system file check. to do that type cmd in search>right click and run as admin> sfc /scannow
Let us know if you need help.
Ken J+
Code:010510-14149-01.dmp 1/5/2010 4:04:56 PM DRIVER_IRQL_NOT_LESS_OR_EQUAL 0x000000d1 00000000`00043378 00000000`00000005 00000000`00000000 fffff880`01101470 pci.sys pci.sys+170470 010510-15990-01.dmp 1/5/2010 6:57:50 AM DRIVER_IRQL_NOT_LESS_OR_EQUAL 0x000000d1 00000000`0000000f 00000000`00000002 00000000`00000001 fffff880`00fce95a 010510-14757-01.dmp 1/5/2010 4:47:54 PM IRQL_NOT_LESS_OR_EQUAL 0x0000000a 00000000`00000048 00000000`00000002 00000000`00000000 fffff800`02ae391a ntoskrnl.exe ntoskrnl.exe+7ef80Code:Microsoft (R) Windows Debugger Version 6.11.0001.404 X86 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Users\K\Desktop\New folder (2)\010510-15990-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*d:\symbols*http://msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel Version 7100 MP (2 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7100.0.amd64fre.winmain_win7rc.090421-1700 Machine Name: Kernel base = 0xfffff800`02a1e000 PsLoadedModuleList = 0xfffff800`02c57e90 Debug session time: Tue Jan 5 07:55:13.647 2010 (GMT-5) System Uptime: 0 days 0:11:01.707 Loading Kernel Symbols ...............................................Unable to load image Unknown_Module_00000000`00000000, Win32 error 0n2 *** WARNING: Unable to verify timestamp for Unknown_Module_00000000`00000000 Unable to add module at 00000000`00000000 Loading User Symbols Missing image name, possible paged-out or corrupt data. Loading unloaded module list .Missing image name, possible paged-out or corrupt data. .Missing image name, possible paged-out or corrupt data. .Missing image name, possible paged-out or corrupt data. .Missing image name, possible paged-out or corrupt data. .Missing image name, possible paged-out or corrupt data. .Missing image name, possible paged-out or corrupt data. .Missing image name, possible paged-out or corrupt data. .Missing image name, possible paged-out or corrupt data. .Missing image name, possible paged-out or corrupt data. .Missing image name, possible paged-out or corrupt data. .Missing image name, possible paged-out or corrupt data. .Missing image name, possible paged-out or corrupt data. .Missing image name, possible paged-out or corrupt data. .Missing image name, possible paged-out or corrupt data. .Missing image name, possible paged-out or corrupt data. .Missing image name, possible paged-out or corrupt data. . ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck D1, {f, 2, 1, fffff88000fce95a} Unable to load image \SystemRoot\system32\DRIVERS\nvstor.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for nvstor.sys *** ERROR: Module load completed but symbols could not be loaded for nvstor.sys Probably caused by : nvstor.sys ( nvstor+1895a ) Followup: MachineOwner --------- 0: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1) 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 kernel debugger is available get stack backtrace. Arguments: Arg1: 000000000000000f, memory referenced Arg2: 0000000000000002, IRQL Arg3: 0000000000000001, value 0 = read operation, 1 = write operation Arg4: fffff88000fce95a, address which referenced memory Debugging Details: ------------------ WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002cc20e0 000000000000000f CURRENT_IRQL: 0 FAULTING_IP: nvstor+1895a fffff880`00fce95a 894710 mov dword ptr [rdi+10h],eax CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0xD1 PROCESS_NAME: System LAST_CONTROL_TRANSFER: from fffff80002aa735a to fffff88003fa61e2 STACK_TEXT: fffff800`00b9cc98 fffff800`02aa735a : fffff800`02c04e80 fffffa80`053a40a8 00000001`8a687ba4 00000000`0000a5b0 : 0xfffff880`03fa61e2 fffff800`00b9cca0 fffff800`02a943ec : fffff800`02c04e80 00000000`00000000 fffff800`00000000 fffffa80`03d27b60 : nt!PoIdle+0x53a fffff800`00b9cd80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x2c STACK_COMMAND: .bugcheck ; kb FOLLOWUP_IP: nvstor+1895a fffff880`00fce95a 894710 mov dword ptr [rdi+10h],eax SYMBOL_NAME: nvstor+1895a FOLLOWUP_NAME: MachineOwner MODULE_NAME: nvstor IMAGE_NAME: nvstor.sys DEBUG_FLR_IMAGE_TIMESTAMP: 49e529c4 FAILURE_BUCKET_ID: X64_0xD1_nvstor+1895a BUCKET_ID: X64_0xD1_nvstor+1895a Followup: MachineOwner ---------