New
#1
BSOD when entering Sleep mode
Hello,
I recently got a BSOD when I entered Sleep mode.
I thought a program which I recently installed caused the problem,
but I got another BSOD when I restarted my computer,
uninstalled the program and tried entering Sleep mode a second time.
My second thought was that the power cut today could have caused this problem, but I don't really know.
I ran WinDbg and got this:
Microsoft (R) Windows Debugger Version 6.2.8229.0 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\032412-20092-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17727.amd64fre.win7sp1_gdr.111118-2330
Machine Name:
Kernel base = 0xfffff800`03268000 PsLoadedModuleList = 0xfffff800`034ac650
Debug session time: Sat Mar 24 20:27:44.980 2012 (UTC + 13:00)
System Uptime: 0 days 0:08:14.073
Loading Kernel Symbols
...............................................................
................................................................
..........................................
Loading User Symbols
Loading unloaded module list
.....
TRIAGER: Could not open triage file : C:\Debuggers\Debuggers\x64\triage\oca.ini, error 2
TRIAGER: Could not open triage file : C:\Debuggers\Debuggers\x64\winxp\triage.ini, error 2
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck D1, {fffff880016e56a0, 2, 8, fffff880016e56a0}
*** WARNING: Unable to verify timestamp for wsimdx.sys
*** ERROR: Module load completed but symbols could not be loaded for wsimdx.sys
TRIAGER: Could not open triage file : C:\Debuggers\Debuggers\x64\triage\modclass.ini, error 2
Probably caused by : wsimdx.sys ( wsimdx+7959 )
Followup: MachineOwner
---------
1: 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: fffff880016e56a0, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000008, value 0 = read operation, 1 = write operation
Arg4: fffff880016e56a0, address which referenced memory
Debugging Details:
------------------
TRIAGER: Could not open triage file : C:\Debuggers\Debuggers\x64\triage\modclass.ini, error 2
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80003516100
GetUlongFromAddress: unable to read from fffff800035161c0
fffff880016e56a0 Nonpaged pool
CURRENT_IRQL: 2
FAULTING_IP:
ndis!NdisIMNotifyPnPEvent+0
fffff880`016e56a0 48895c2408 mov qword ptr [rsp+8],rbx
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
BUGCHECK_STR: 0xD1
PROCESS_NAME: System
TRAP_FRAME: fffff8800a8ce600 -- (.trap 0xfffff8800a8ce600)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=fffffa80061f21a0
rdx=fffff8800a8ce928 rsi=0000000000000000 rdi=0000000000000000
rip=fffff880016e56a0 rsp=fffff8800a8ce798 rbp=fffff8800a8ce928
r8=0000000000000000 r9=0000000000000000 r10=fffff880016c5ec0
r11=0000000000000002 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na po nc
ndis!NdisIMNotifyPnPEvent:
fffff880`016e56a0 48895c2408 mov qword ptr [rsp+8],rbx ss:fffff880`0a8ce7a0=fffff8800a8cebd4
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff800032e42e9 to fffff800032e4d40
FAILED_INSTRUCTION_ADDRESS:
ndis!NdisIMNotifyPnPEvent+0
fffff880`016e56a0 48895c2408 mov qword ptr [rsp+8],rbx
STACK_TEXT:
fffff880`0a8ce4b8 fffff800`032e42e9 : 00000000`0000000a fffff880`016e56a0 00000000`00000002 00000000`00000008 : nt!KeBugCheckEx
fffff880`0a8ce4c0 fffff800`032e2f60 : fffffa80`058d8850 20707249`00000000 fffff800`0341ec50 fffffa80`0b53bb80 : nt!KiBugCheckDispatch+0x69
fffff880`0a8ce600 fffff880`016e56a0 : fffff880`047eb959 fffff880`0a8cebd4 00000000`00000001 00000000`00000001 : nt!KiPageFault+0x260
fffff880`0a8ce798 fffff880`047eb959 : fffff880`0a8cebd4 00000000`00000001 00000000`00000001 fffffa80`0b53bb80 : ndis!NdisIMNotifyPnPEvent
fffff880`0a8ce7a0 fffff880`0a8cebd4 : 00000000`00000001 00000000`00000001 fffffa80`0b53bb80 00000000`00000000 : wsimdx+0x7959
fffff880`0a8ce7a8 00000000`00000001 : 00000000`00000001 fffffa80`0b53bb80 00000000`00000000 fffffa80`041d5f28 : 0xfffff880`0a8cebd4
fffff880`0a8ce7b0 00000000`00000001 : fffffa80`0b53bb80 00000000`00000000 fffffa80`041d5f28 fffffa80`061f73c0 : 0x1
fffff880`0a8ce7b8 fffffa80`0b53bb80 : 00000000`00000000 fffffa80`041d5f28 fffffa80`061f73c0 00000000`00000000 : 0x1
fffff880`0a8ce7c0 00000000`00000000 : fffffa80`041d5f28 fffffa80`061f73c0 00000000`00000000 fffff880`0a8ce928 : 0xfffffa80`0b53bb80
STACK_COMMAND: kb
FOLLOWUP_IP:
wsimdx+7959
fffff880`047eb959 ?? ???
SYMBOL_STACK_INDEX: 4
SYMBOL_NAME: wsimdx+7959
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: wsimdx
IMAGE_NAME: wsimdx.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 49bf410b
FAILURE_BUCKET_ID: X64_0xD1_CODE_AV_BAD_IP_wsimdx+7959
BUCKET_ID: X64_0xD1_CODE_AV_BAD_IP_wsimdx+7959
Followup: MachineOwner
---------
1: 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: fffff880016e56a0, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000008, value 0 = read operation, 1 = write operation
Arg4: fffff880016e56a0, address which referenced memory
Debugging Details:
------------------
TRIAGER: Could not open triage file : C:\Debuggers\Debuggers\x64\triage\modclass.ini, error 2
READ_ADDRESS: fffff880016e56a0 Nonpaged pool
CURRENT_IRQL: 2
FAULTING_IP:
ndis!NdisIMNotifyPnPEvent+0
fffff880`016e56a0 48895c2408 mov qword ptr [rsp+8],rbx
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
BUGCHECK_STR: 0xD1
PROCESS_NAME: System
TRAP_FRAME: fffff8800a8ce600 -- (.trap 0xfffff8800a8ce600)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=fffffa80061f21a0
rdx=fffff8800a8ce928 rsi=0000000000000000 rdi=0000000000000000
rip=fffff880016e56a0 rsp=fffff8800a8ce798 rbp=fffff8800a8ce928
r8=0000000000000000 r9=0000000000000000 r10=fffff880016c5ec0
r11=0000000000000002 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na po nc
ndis!NdisIMNotifyPnPEvent:
fffff880`016e56a0 48895c2408 mov qword ptr [rsp+8],rbx ss:fffff880`0a8ce7a0=fffff8800a8cebd4
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff800032e42e9 to fffff800032e4d40
FAILED_INSTRUCTION_ADDRESS:
ndis!NdisIMNotifyPnPEvent+0
fffff880`016e56a0 48895c2408 mov qword ptr [rsp+8],rbx
STACK_TEXT:
fffff880`0a8ce4b8 fffff800`032e42e9 : 00000000`0000000a fffff880`016e56a0 00000000`00000002 00000000`00000008 : nt!KeBugCheckEx
fffff880`0a8ce4c0 fffff800`032e2f60 : fffffa80`058d8850 20707249`00000000 fffff800`0341ec50 fffffa80`0b53bb80 : nt!KiBugCheckDispatch+0x69
fffff880`0a8ce600 fffff880`016e56a0 : fffff880`047eb959 fffff880`0a8cebd4 00000000`00000001 00000000`00000001 : nt!KiPageFault+0x260
fffff880`0a8ce798 fffff880`047eb959 : fffff880`0a8cebd4 00000000`00000001 00000000`00000001 fffffa80`0b53bb80 : ndis!NdisIMNotifyPnPEvent
fffff880`0a8ce7a0 fffff880`0a8cebd4 : 00000000`00000001 00000000`00000001 fffffa80`0b53bb80 00000000`00000000 : wsimdx+0x7959
fffff880`0a8ce7a8 00000000`00000001 : 00000000`00000001 fffffa80`0b53bb80 00000000`00000000 fffffa80`041d5f28 : 0xfffff880`0a8cebd4
fffff880`0a8ce7b0 00000000`00000001 : fffffa80`0b53bb80 00000000`00000000 fffffa80`041d5f28 fffffa80`061f73c0 : 0x1
fffff880`0a8ce7b8 fffffa80`0b53bb80 : 00000000`00000000 fffffa80`041d5f28 fffffa80`061f73c0 00000000`00000000 : 0x1
fffff880`0a8ce7c0 00000000`00000000 : fffffa80`041d5f28 fffffa80`061f73c0 00000000`00000000 fffff880`0a8ce928 : 0xfffffa80`0b53bb80
STACK_COMMAND: kb
FOLLOWUP_IP:
wsimdx+7959
fffff880`047eb959 ?? ???
SYMBOL_STACK_INDEX: 4
SYMBOL_NAME: wsimdx+7959
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: wsimdx
IMAGE_NAME: wsimdx.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 49bf410b
FAILURE_BUCKET_ID: X64_0xD1_CODE_AV_BAD_IP_wsimdx+7959
BUCKET_ID: X64_0xD1_CODE_AV_BAD_IP_wsimdx+7959
Followup: MachineOwner
---------
Please help me.
Thanks in advance.
Regards,
Christian
PS: Would a System Restore do the trick?
Last edited by christianb9632; 24 Mar 2012 at 04:11.