mein zweiter Bluescreen
_____________________________________________
WARNING: Inaccessible path: 'c:\windows\System32; c:\windows\system\System32;
http://www.alexander.com/SymServe'
Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\Animator\Desktop\Stefan\Bluescreens\043010-20779-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
WARNING: Inaccessible path: 'c:\windows\System32; c:\windows\system\System32;
http://www.alexander.com/SymServe'
Symbol search path is: srv*C:\symbol_cache*
http://msdl.microsoft.com/download/symbols
Executable search path is: c:\windows\System32; c:\windows\system\System32;
http://www.alexander.com/SymServe
Windows 7 Kernel Version 7600 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`02e06000 PsLoadedModuleList = 0xfffff800`03043e50
Debug session time: Fri Apr 30 07:45:31.201 2010 (GMT+2)
System Uptime: 0 days 0:20:20.216
Loading Kernel Symbols
...............................................................
................................................................
.................................
Loading User Symbols
Loading unloaded module list
.......
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck D1, {28, 2, 0, fffff88003c4bbb4}
Unable to load image \SystemRoot\system32\DRIVERS\fwl*Z*b.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for fwl*Z*b.sys
*** ERROR: Module load completed but symbols could not be loaded for fwl*Z*b.sys
Probably caused by : fwl*Z*b.sys ( fwl*Z*b+2bbb4 )
Followup: MachineOwner
---------
4: kd>
4: 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: 0000000000000028, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff88003c4bbb4, address which referenced memory
Debugging Details:
------------------
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800030ae0e0
0000000000000028
CURRENT_IRQL: 2
FAULTING_IP:
fwl*Z*b+2bbb4
fffff880`03c4bbb4 488b4928 mov rcx,qword ptr [rcx+28h]
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VERIFIER_ENABLED_VISTA_MINIDUMP
BUGCHECK_STR: 0xD1
PROCESS_NAME: System
TRAP_FRAME: fffff8800334d600 -- (.trap 0xfffff8800334d600)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000f88003c88ac4 rbx=0000000000000000 rcx=0000000000000000
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88003c4bbb4 rsp=fffff8800334d790 rbp=0000000000000000
r8=0000000000000009 r9=0000000000000000 r10=fffff80003005888
r11=fffff8800334d9c8 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na po nc
fwl*Z*b+0x2bbb4:
fffff880`03c4bbb4 488b4928 mov rcx,qword ptr [rcx+28h] ds:0103:00000000`00000028=????????????????
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff80002e75b69 to fffff80002e76600
STACK_TEXT:
fffff880`0334d4b8 fffff800`02e75b69 : 00000000`0000000a 00000000`00000028 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`0334d4c0 fffff800`02e747e0 : fffffa80`054c82d8 00000000`00000000 00000000`000007ff 00000000`00000040 : nt!KiBugCheckDispatch+0x69
fffff880`0334d600 fffff880`03c4bbb4 : fffff980`1ca08530 fffff880`03c211ff 00000000`00000110 00000000`00000000 : nt!KiPageFault+0x260
fffff880`0334d790 fffff980`1ca08530 : fffff880`03c211ff 00000000`00000110 00000000`00000000 fffff980`1ca08a50 : fwl*Z*b+0x2bbb4
fffff880`0334d798 fffff880`03c211ff : 00000000`00000110 00000000`00000000 fffff980`1ca08a50 fffff980`1d6bee78 : 0xfffff980`1ca08530
fffff880`0334d7a0 00000000`00000110 : 00000000`00000000 fffff980`1ca08a50 fffff980`1d6bee78 fffff980`1ca74500 : fwl*Z*b+0x11ff
fffff880`0334d7a8 00000000`00000000 : fffff980`1ca08a50 fffff980`1d6bee78 fffff980`1ca74500 fffff880`03c2a9a9 : 0x110
STACK_COMMAND: kb
FOLLOWUP_IP:
fwl*Z*b+2bbb4
fffff880`03c4bbb4 488b4928 mov rcx,qword ptr [rcx+28h]
SYMBOL_STACK_INDEX: 3
SYMBOL_NAME: fwl*Z*b+2bbb4
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: fwl*Z*b
IMAGE_NAME: fwl*Z*b.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 45818437
FAILURE_BUCKET_ID: X64_0xD1_VRF_fwl*Z*b+2bbb4
BUCKET_ID: X64_0xD1_VRF_fwl*Z*b+2bbb4
Followup: MachineOwner
---------