Har efter jeg har forsøgt at lave et netværk fået nogle BSOD crashes med fejlen "0x000000D1 DRIVER_IRQL_NOT_LESS_OR_EQUAL "
Efter at have kørt windows debugging tool har jeg ikke kunnet finde ud af præcis hvilken driver/fil der skaber problemet.
Håber der er en der kan se noget jeg ikke kan.
Her er bugcheck analysis:
Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\Mini052509-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
Executable search path is:
Windows Server 2008/Windows Vista Kernel Version 6001 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 6001.18226.amd64fre.vistasp1_gdr.090302-1506
Machine Name:
Kernel base = 0xfffff800`01a0f000 PsLoadedModuleList = 0xfffff800`01bd4db0
Debug session time: Mon May 25 10:35:48.934 2009 (GMT+2)
System Uptime: 0 days 0:04:58.111
Loading Kernel Symbols
...............................................................
................................................................
......................
Loading User Symbols
Loading unloaded module list
.......
*******************************************************************************
* *
* Bugcheck Analysis *
* *
******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck D1, {fffffa880dc6f828, 2, 0, fffffa6000fd060b}
Probably caused by : Unknown_Image ( PAGE_NOT_ZERO )
Followup: MachineOwner
---------
*** Memory manager detected 1 instance(s) of page corruption, target is likely to have memory corruption.
3: 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: fffffa880dc6f828, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffffa6000fd060b, address which referenced memory
Debugging Details:
------------------
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80001c38080
fffffa880dc6f828
CURRENT_IRQL: 2
FAULTING_IP:
ecache!EcBlockFind+b7
fffffa60`00fd060b 498b4108 mov rax,qword ptr [r9+8]
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xD1
PROCESS_NAME: svchost.exe
BAD_PAGES_DETECTED: 1
TRAP_FRAME: fffffa600bbcf930 -- (.trap 0xfffffa600bbcf930)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=00000000003596f8 rbx=0000000000000000 rcx=0000000000034ac6
rdx=0f506c47d09b4ac6 rsi=0000000000000000 rdi=0000000000000000
rip=fffffa6000fd060b rsp=fffffa600bbcfac8 rbp=0000000000000000
r8=0000000000ee91f8 r9=fffffa880dc6f820 r10=ffffffffffffffff
r11=0000000000ee91f8 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
ecache!EcBlockFind+0xb7:
fffffa60`00fd060b 498b4108 mov rax,qword ptr [r9+8] ds:21a0:fffffa88`0dc6f828=????????????????
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff80001a633ee to fffff80001a63650
STACK_TEXT:
fffffa60`0bbcf7e8 fffff800`01a633ee : 00000000`0000000a fffffa88`0dc6f828 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffffa60`0bbcf7f0 fffff800`01a622cb : 00000000`00000000 00000000`00000000 fffffa80`0a7cf000 fffffa80`0769c190 : nt!KiBugCheckDispatch+0x6e
fffffa60`0bbcf930 fffffa60`00fd060b : fffffa60`00fcde88 00000000`00ee91f8 00000000`00000000 fffffa60`00fe1fb0 : nt!KiPageFault+0x20b
fffffa60`0bbcfac8 fffffa60`00fcde88 : 00000000`00ee91f8 00000000`00000000 fffffa60`00fe1fb0 fffffa80`0820f8a0 : ecache!EcBlockFind+0xb7
fffffa60`0bbcfad0 fffffa60`00fca4ec : fffffa80`0820f800 fffffa60`0bbcfce0 fffffa60`0bbcfce8 fffffa80`0ea9fbc0 : ecache!EcCacheManagerStartDeviceIo+0x404
fffffa60`0bbcfba0 fffffa60`0138d40f : fffffa80`098e5800 fffffa60`0139070a fffffa80`0820f8a0 00000000`00000000 : ecache!EcDispatchReadWrite+0xb64
fffffa60`0bbcfcd0 fffffa60`01221616 : 00000000`00000002 fffffa80`048c7700 fffffa80`05bdde00 00000000`00000000 : volsnap!VolSnapRead+0x6f
fffffa60`0bbcfd30 fffff800`01a5d947 : 00000000`00000000 00000000`01d64218 00000000`77932f00 00000000`00000000 : Ntfs!NtfsStorageDriverCallout+0x16
fffffa60`0bbcfd60 fffff800`01a5d8fe : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxSwitchKernelStackCallout+0x27
fffffa60`0d564140 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSwitchKernelStackContinue
STACK_COMMAND: kb
SYMBOL_NAME: PAGE_NOT_ZERO
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: Unknown_Module
IMAGE_NAME: Unknown_Image
DEBUG_FLR_IMAGE_TIMESTAMP: 0
BUCKET_ID: PAGE_NOT_ZERO
Followup: MachineOwner
---------
*** Memory manager detected 1 instance(s) of page corruption, target is likely to have memory corruption.
