Problems? See this thread at archive.org.
Does anyone know what this is all about?
Upon restart got message no attempts have been made to start the service since the last boot
The BSOD read Driver power state error
Event viewer details below. Has happened 4 times. I have made some hardware changes ie new drive but this started before any changes. The biggest change was using W7!
- System
- Provider
[ Name] Microsoft-Windows-Kernel-Power
[ Guid] {331C3B3A-2005-44C2-AC5E-77220C37D6B4}
EventID 41
Version 2
Level 1
Task 63
Opcode 0
Keywords 0x8000000000000002
- TimeCreated
[ SystemTime] 2009-12-31T23:35:06.004446600Z
EventRecordID 16449
Correlation
- Execution
[ ProcessID] 4
[ ThreadID] 8
Channel System
Computer BHTX-PC
- Security
[ UserID] S-1-5-18
- EventData
BugcheckCode 127
BugcheckParameter1 0x8
BugcheckParameter2 0x80050031
BugcheckParameter3 0x6f8
BugcheckParameter4 0xfffff80004883798
SleepInProgress false
PowerButtonTimestamp 0
+ System
- Provider
[ Name] Microsoft-Windows-Kernel-Power
[ Guid] {331C3B3A-2005-44C2-AC5E-77220C37D6B4}
EventID 41
Version 2
Level 1
Task 63
Opcode 0
Keywords 0x8000000000000002
- TimeCreated
[ SystemTime] 2010-01-29T12:28:25.626849400Z
EventRecordID 31399
Correlation
- Execution
[ ProcessID] 4
[ ThreadID] 8
Channel System
Computer BHTX-PC
- Security
[ UserID] S-1-5-18
- EventData
BugcheckCode 159
BugcheckParameter1 0x3
BugcheckParameter2 0xfffffa800461a060
BugcheckParameter3 0xfffff80000b9c518
BugcheckParameter4 0xfffffa8013c02410
SleepInProgress true
PowerButtonTimestamp 0
+ System
- Provider
[ Name] Microsoft-Windows-Kernel-Power
[ Guid] {331C3B3A-2005-44C2-AC5E-77220C37D6B4}
EventID 41
Version 2
Level 1
Task 63
Opcode 0
Keywords 0x8000000000000002
- TimeCreated
[ SystemTime] 2010-01-01T00:16:31.173615300Z
EventRecordID 16566
Correlation
- Execution
[ ProcessID] 4
[ ThreadID] 8
Channel System
Computer BHTX-PC
- Security
[ UserID] S-1-5-18
- EventData
BugcheckCode 127
BugcheckParameter1 0x8
BugcheckParameter2 0x80050031
BugcheckParameter3 0x6f8
BugcheckParameter4 0xfffff8000489d798
SleepInProgress false
PowerButtonTimestamp 0
+ System
- Provider
[ Name] Microsoft-Windows-Kernel-Power
[ Guid] {331C3B3A-2005-44C2-AC5E-77220C37D6B4}
EventID 41
Version 2
Level 1
Task 63
Opcode 0
Keywords 0x8000000000000002
- TimeCreated
[ SystemTime] 2009-12-31T23:35:06.004446600Z
EventRecordID 16449
Correlation
- Execution
[ ProcessID] 4
[ ThreadID] 8
Channel System
Computer BHTX-PC
- Security
[ UserID] S-1-5-18
- EventData
BugcheckCode 127
BugcheckParameter1 0x8
BugcheckParameter2 0x80050031
BugcheckParameter3 0x6f8
BugcheckParameter4 0xfffff80004883798
SleepInProgress false
PowerButtonTimestamp 0
-
-
Got any external usb or firewire devices that draw their power from the laptop? (no external power, like a harddrive). When you installed Win7, did you also install the lenovo power management software?
-
As they say you da man! On to something hopefully.
I thought about the hardware and it might be due to a cheap USB hub (with no external power) being used. Chronologically, yes had changes but this is the only device that has been through all 4 BSOD events (at least as far as ownership) so its a clue. In one instance, I cant recall if it was plugged in. I thought something strange happened as system shut off when I placed my mobile phone near the computer. Back to the USB hub, in device manager it reads generic hub. But says self powered. But its powered by the PC.
This latest crash happened when I fell asleep. Computer should hibernate/sleep (dont know the difference) but when I woke up it was off with lights still on. Press power and it seemed like cold boot then showed BSOD message. That message about power failure is consistant among all four times this happened.
I have the latest Lenovo updates and software, all of them. Constantly up to date.
What do do next?
Also on restart for the last crash, I saw that device manager showed a problem with PnP device. I unplugged the hub, the replugged it in. Then device manager showed no error.
Can this problem be attributed to the hub, or is it something else? I mean in layman's speak, the PC crashed so the USB hub didnt shut down fast enough but that doesnt mean something is wrong with the hub? Perplexed. -
Same situation. USB hub still connected. Computer went to sleep/hibernate but this time no BSOD. Is something else causing this?
How do I get the minidump files for review? Know location but doesnt seem readable in txt format. -
You need to download the windows debugging tools
http://www.microsoft.com/whdc/devtools/debugging/installx86.Mspx
It's not as easy to setup or read as you think....
Did you DISCONNECT the usb hub? Does the problem recur?
p.s.--attach your minidump to a post and I will take a look -
OK, here goes. Took me a long time to fig out how to get the reports. Seems to be unrelated problems but the common thing is W7. Weird thing is I see something about VISTA drivers. I also checked and all my drivers are digitally signed.
INSTANCE #1
Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\010110-22370-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: symsrv*symsrv.dll*c:\Windows\symbols* http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`04863000 PsLoadedModuleList = 0xfffff800`04aa0e50
Debug session time: Fri Jan 1 08:11:29.578 2010 (GMT+8)
System Uptime: 0 days 0:36:52.420
Loading Kernel Symbols
...............................................................
................................................................
................................................
Loading User Symbols
Loading unloaded module list
.......
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 7F, {8, 80050031, 6f8, fffff8000489d798}
Probably caused by : ntkrnlmp.exe ( nt!KiDoubleFaultAbort+b2 )
Followup: MachineOwner
Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\010110-22370-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: symsrv*symsrv.dll*c:\Windows\symbols* http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`04863000 PsLoadedModuleList = 0xfffff800`04aa0e50
Debug session time: Fri Jan 1 08:11:29.578 2010 (GMT+8)
System Uptime: 0 days 0:36:52.420
Loading Kernel Symbols
...............................................................
................................................................
................................................
Loading User Symbols
Loading unloaded module list
.......
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 7F, {8, 80050031, 6f8, fffff8000489d798}
Probably caused by : ntkrnlmp.exe ( nt!KiDoubleFaultAbort+b2 )
Followup: MachineOwner
---------
1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
UNEXPECTED_KERNEL_MODE_TRAP (7f)
This means a trap occurred in kernel mode, and it's a trap of a kind
that the kernel isn't allowed to have/catch (bound trap) or that
is always instant death (double fault). The first number in the
bugcheck params is the number of the trap (8 = double fault, etc)
Consult an Intel x86 family manual to learn more about what these
traps are. Here is a *portion* of those codes:
If kv shows a taskGate
use .tss on the part before the colon, then kv.
Else if kv shows a trapframe
use .trap on that value
Else
.trap on the appropriate frame will show where the trap was taken
(on x86, this will be the ebp that goes with the procedure KiTrap)
Endif
kb will then show the corrected stack.
Arguments:
Arg1: 0000000000000008, EXCEPTION_DOUBLE_FAULT
Arg2: 0000000080050031
Arg3: 00000000000006f8
Arg4: fffff8000489d798
Debugging Details:
------------------
BUGCHECK_STR: 0x7f_8
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: System
CURRENT_IRQL: 2
LAST_CONTROL_TRANSFER: from fffff800048d4469 to fffff800048d4f00
STACK_TEXT:
fffff880`009f4c68 fffff800`048d4469 : 00000000`0000007f 00000000`00000008 00000000`80050031 00000000`000006f8 : nt!KeBugCheckEx
fffff880`009f4c70 fffff800`048d2932 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff880`009f4db0 fffff800`0489d798 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDoubleFaultAbort+0xb2
fffff880`03115da0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!SeAccessCheckFromState+0x58
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!KiDoubleFaultAbort+b2
fffff800`048d2932 90 nop
SYMBOL_STACK_INDEX: 2
SYMBOL_NAME: nt!KiDoubleFaultAbort+b2
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc600
FAILURE_BUCKET_ID: X64_0x7f_8_nt!KiDoubleFaultAbort+b2
BUCKET_ID: X64_0x7f_8_nt!KiDoubleFaultAbort+b2
Followup: MachineOwner
---------
INSTANCE #2
Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\010110-36863-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: symsrv*symsrv.dll*c:\Windows\symbols* http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`04849000 PsLoadedModuleList = 0xfffff800`04a86e50
Debug session time: Fri Jan 1 07:32:53.364 2010 (GMT+8)
System Uptime: 0 days 1:16:17.346
Loading Kernel Symbols
...............................................................
................................................................
................................................
Loading User Symbols
Loading unloaded module list
.......
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 7F, {8, 80050031, 6f8, fffff80004883798}
Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\010110-36863-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: symsrv*symsrv.dll*c:\Windows\symbols* http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`04849000 PsLoadedModuleList = 0xfffff800`04a86e50
Debug session time: Fri Jan 1 07:32:53.364 2010 (GMT+8)
System Uptime: 0 days 1:16:17.346
Loading Kernel Symbols
...............................................................
................................................................
................................................
Loading User Symbols
Loading unloaded module list
.......
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 7F, {8, 80050031, 6f8, fffff80004883798}
Probably caused by : ntkrnlmp.exe ( nt!KiDoubleFaultAbort+b2 )
Followup: MachineOwner
---------
1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
UNEXPECTED_KERNEL_MODE_TRAP (7f)
This means a trap occurred in kernel mode, and it's a trap of a kind
that the kernel isn't allowed to have/catch (bound trap) or that
is always instant death (double fault). The first number in the
bugcheck params is the number of the trap (8 = double fault, etc)
Consult an Intel x86 family manual to learn more about what these
traps are. Here is a *portion* of those codes:
If kv shows a taskGate
use .tss on the part before the colon, then kv.
Else if kv shows a trapframe
use .trap on that value
Else
.trap on the appropriate frame will show where the trap was taken
(on x86, this will be the ebp that goes with the procedure KiTrap)
Endif
kb will then show the corrected stack.
Arguments:
Arg1: 0000000000000008, EXCEPTION_DOUBLE_FAULT
Arg2: 0000000080050031
Arg3: 00000000000006f8
Arg4: fffff80004883798
Debugging Details:
------------------
BUGCHECK_STR: 0x7f_8
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: System
CURRENT_IRQL: 2
LAST_CONTROL_TRANSFER: from fffff800048ba469 to fffff800048baf00
STACK_TEXT:
fffff880`009f4c68 fffff800`048ba469 : 00000000`0000007f 00000000`00000008 00000000`80050031 00000000`000006f8 : nt!KeBugCheckEx
fffff880`009f4c70 fffff800`048b8932 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff880`009f4db0 fffff800`04883798 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDoubleFaultAbort+0xb2
fffff880`03115da0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!SeAccessCheckFromState+0x58
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!KiDoubleFaultAbort+b2
fffff800`048b8932 90 nop
SYMBOL_STACK_INDEX: 2
SYMBOL_NAME: nt!KiDoubleFaultAbort+b2
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc600
FAILURE_BUCKET_ID: X64_0x7f_8_nt!KiDoubleFaultAbort+b2
BUCKET_ID: X64_0x7f_8_nt!KiDoubleFaultAbort+b2
Followup: MachineOwner
---------
INSTANCE #3
Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\012910-48407-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?fffff800`00b9c500?
Symbol search path is: symsrv*symsrv.dll*c:\Windows\symbols* http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`04857000 PsLoadedModuleList = 0xfffff800`04a94e50
Debug session time: Fri Jan 29 20:24:59.468 2010 (GMT+8)
System Uptime: 1 days 6:18:24.528
Loading Kernel Symbols
...............................................................
................................................................
..........................................................
Loading User Symbols
Loading unloaded module list
................
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 9F, {3, fffffa800461a060, fffff80000b9c518, fffffa8013c02410}
*** WARNING: Unable to verify timestamp for netw5v64.sys
*** ERROR: Module load completed but symbols could not be loaded for netw5v64.sys
Probably caused by : netw5v64.sys
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
DRIVER_POWER_STATE_FAILURE (9f)
A driver is causing an inconsistent power state.
Arguments:
Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
Arg2: fffffa800461a060, Physical Device Object of the stack
Arg3: fffff80000b9c518, Functional Device Object of the stack
Arg4: fffffa8013c02410, The blocked IRP
Debugging Details:
------------------
DRVPOWERSTATE_SUBCODE: 3
IRP_ADDRESS: fffffa8013c02410
DEVICE_OBJECT: fffffa8007034050
DRIVER_OBJECT: fffffa8007037ba0
IMAGE_NAME: netw5v64.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 49cbab84
MODULE_NAME: netw5v64
FAULTING_MODULE: fffff880058be000 netw5v64
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x9F
PROCESS_NAME: System
CURRENT_IRQL: 2
LAST_CONTROL_TRANSFER: from fffff80004937e23 to fffff800048c8f00
STACK_TEXT:
fffff800`00b9c4c8 fffff800`04937e23 : 00000000`0000009f 00000000`00000003 fffffa80`0461a060 fffff800`00b9c518 : nt!KeBugCheckEx
fffff800`00b9c4d0 fffff800`048d4fa6 : fffff800`00b9c600 fffff800`00b9c600 00000000`00000004 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x29330
fffff800`00b9c570 fffff800`048d4326 : fffffa80`06b99768 fffffa80`06b99768 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x66
fffff800`00b9c5e0 fffff800`048d4e7e : 000000fe`075de4ca fffff800`00b9cc58 00000000`006ab7ab fffff800`04a457e8 : nt!KiProcessExpiredTimerList+0xc6
fffff800`00b9cc30 fffff800`048d4697 : 00000036`c4a761cc 00000036`006ab7ab 00000036`c4a7616b 00000000`000000ab : nt!KiTimerExpiration+0x1be
fffff800`00b9ccd0 fffff800`048d16fa : fffff800`04a41e80 fffff800`04a4fc40 00000000`00000002 fffff880`00000000 : nt!KiRetireDpcList+0x277
fffff800`00b9cd80 00000000`00000000 : fffff800`00b9d000 fffff800`00b97000 fffff800`00b9cd40 00000000`00000000 : nt!KiIdleLoop+0x5a
STACK_COMMAND: kb
FOLLOWUP_NAME: MachineOwner
FAILURE_BUCKET_ID: X64_0x9F_IMAGE_netw5v64.sys
BUCKET_ID: X64_0x9F_IMAGE_netw5v64.sys
Followup: MachineOwner
---------
Instance #4
Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\021710-40653-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: symsrv*symsrv.dll*c:\Windows\symbols* http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`0480f000 PsLoadedModuleList = 0xfffff800`04a4ce50
Debug session time: Wed Feb 17 22:20:56.542 2010 (GMT+8)
System Uptime: 0 days 3:33:47.602
Loading Kernel Symbols
...............................................................
................................................................
..................................................
Loading User Symbols
Loading unloaded module list
........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck A0, {b, bceb5000, 3, 12c18000}
Probably caused by : ntkrnlmp.exe ( nt!PopWriteHiberPages+a3 )
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
INTERNAL_POWER_ERROR (a0)
The power policy manager experienced a fatal error.
Arguments:
Arg1: 000000000000000b, The hibernation file is too small.
Arg2: 00000000bceb5000, Size of the hibernation file.
Arg3: 0000000000000003, HIBERFILE_PROGRESS_MEMORY_RANGES
Arg4: 0000000012c18000, Size of the remaining memory ranges.
Debugging Details:
------------------
BUGCHECK_STR: 0xA0
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: System
CURRENT_IRQL: 2
LAST_CONTROL_TRANSFER: from fffff80004abf513 to fffff80004880f00
STACK_TEXT:
fffff880`0baf31b8 fffff800`04abf513 : 00000000`000000a0 00000000`0000000b 00000000`bceb5000 00000000`00000003 : nt!KeBugCheckEx
fffff880`0baf31c0 fffff800`04abfbbb : fffffa80`09840670 00000000`0000e000 fffffa80`09840670 00000000`00005b98 : nt!PopWriteHiberPages+0xa3
fffff880`0baf33c0 fffff800`04abfd25 : 00001104`4d56c3e1 fffff880`0baf36c8 fffff880`0000e000 00000000`00000010 : nt!PopAddPagesToCompressedPageSet+0x1eb
fffff880`0baf3450 fffff800`04ac1132 : fffff880`0ff86000 fffff880`0baf36c8 00000000`00000020 00000000`000000f7 : nt!PopBufferCompressedPageSet+0xd5
fffff880`0baf34c0 fffff800`04ac1919 : fffffa80`0000ddde fffff880`08bcf000 00000000`000bceb5 00000000`00005b98 : nt!PopWriteHiberImage+0x3d2
fffff880`0baf36b0 fffff800`04df209e : 00000000`0000c2b4 00000000`00000000 fffff800`04ac1730 00000000`00000000 : nt!PopSaveHiberContext+0x1ea
fffff880`0baf3860 fffff800`04ac6be9 : 00000000`00001466 00000000`00000000 00000000`00000000 fffff800`0488f1ed : hal!HaliAcpiSleep+0x18f
fffff880`0baf38d0 fffff800`04ac6c8f : 00000000`00000000 fffffa80`09840670 fffff800`04a2f420 00000000`04ac2ee0 : nt!PopHandleNextState+0x12a
fffff880`0baf3920 fffff800`04acc140 : 00000000`00000005 00000000`0020b3d9 00000000`00000000 fffff880`0baf3aa0 : nt!PopIssueNextState+0x1f
fffff880`0baf3950 fffff800`04acc5a4 : 00000000`00000000 00000000`001349fd 00000000`00000000 00000000`00000001 : nt!PopInvokeSystemStateHandler+0x3c0
fffff880`0baf3b10 fffff800`04ac8464 : ffffffff`ffffffff ffffffff`ffffffff 00000000`001349fd 00000000`00000000 : nt!PopEndMirroring+0x84
fffff880`0baf3be0 fffff800`04acc925 : fffff880`0baf3d00 fffff880`00000007 00000000`00000000 fffffa80`00000007 : nt!MmDuplicateMemory+0xb64
fffff880`0baf3cd0 fffff800`04b24166 : fffffa80`04509040 fffffa80`00000000 00000000`00000000 fffff800`04878d87 : nt!PopTransitionToSleep+0xd5
fffff880`0baf3d40 fffff800`0485f486 : fffff800`049f9e80 fffffa80`04509040 fffffa80`047044c0 fffff880`01410534 : nt!PspSystemThreadStartup+0x5a
fffff880`0baf3d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!PopWriteHiberPages+a3
fffff800`04abf513 cc int 3
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: nt!PopWriteHiberPages+a3
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc600
FAILURE_BUCKET_ID: X64_0xA0_nt!PopWriteHiberPages+a3
BUCKET_ID: X64_0xA0_nt!PopWriteHiberPages+a3
Followup: MachineOwner
---------
INSTANCE #5
Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\021710-41199-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: symsrv*symsrv.dll*c:\Windows\symbols* http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`0484f000 PsLoadedModuleList = 0xfffff800`04a8ce50
Debug session time: Wed Feb 17 18:44:37.515 2010 (GMT+8)
System Uptime: 1 days 9:09:53.575
Loading Kernel Symbols
...............................................................
................................................................
...................................................
Loading User Symbols
Loading unloaded module list
............................
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000009F, {4, 258, fffffa8003c46680, fffff80000b9e510}
Probably caused by : ntkrnlmp.exe ( nt!KiSwapContext+7a )
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
DRIVER_POWER_STATE_FAILURE (9f)
A driver is causing an inconsistent power state.
Arguments:
Arg1: 0000000000000004, The power transition timed out waiting to synchronize with the Pnp
subsystem.
Arg2: 0000000000000258, Timeout in seconds.
Arg3: fffffa8003c46680, The thread currently holding on to the Pnp lock.
Arg4: fffff80000b9e510
Debugging Details:
------------------
DRVPOWERSTATE_SUBCODE: 4
FAULTING_THREAD: fffffa8003c46680
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x9F
PROCESS_NAME: System
CURRENT_IRQL: 2
LAST_CONTROL_TRANSFER: from fffff800048c8052 to fffff800048c6dda
STACK_TEXT:
fffff880`031f6760 fffff800`048c8052 : fffffa80`03c46680 fffffa80`03c46680 00000000`00000000 fffffa80`00000001 : nt!KiSwapContext+0x7a
fffff880`031f68a0 fffff800`048ca1af : fffffa80`0b4e9010 fffffa80`0b4e9010 fffffa80`00000079 fffff800`04a39e80 : nt!KiCommitThreadWait+0x1d2
fffff880`031f6930 fffff800`04889b1e : 00000000`00000000 fffff800`0000001b 00000000`00000000 fffff800`04a39e00 : nt!KeWaitForSingleObject+0x19f
fffff880`031f69d0 fffff800`048c91bc : ffffffff`fd9da600 fffffa80`0464c700 fffff800`04ac3400 fffff880`04c2c3e8 : nt!ExpWaitForResource+0xae
fffff880`031f6a40 fffff800`04b1b3cf : fffff880`031f6cb8 00000000`00000000 00000000`00000001 00000000`00000000 : nt!ExAcquireResourceExclusiveLite+0x14f
fffff880`031f6ab0 fffff800`04d39917 : 00000000`00000000 fffffa80`0b078820 fffff8a0`1027be60 fffff880`031f6cb8 : nt! ?? ::NNGAKEGL::`string'+0x1351c
fffff880`031f6ae0 fffff800`04d3ab2c : fffff880`031f6cb8 fffffa80`09b72b00 fffffa80`03c46680 fffffa80`09b72ba0 : nt!PnpProcessQueryRemoveAndEject+0x77
fffff880`031f6c20 fffff800`04c25c48 : 00000000`00000000 fffffa80`09b72ba0 fffff8a0`1027be60 00000000`00000000 : nt!PnpProcessTargetDeviceEvent+0x4c
fffff880`031f6c50 fffff800`048ce161 : fffff800`04b2bfc0 fffff8a0`1027be60 fffff800`04a645f8 00000000`00000000 : nt! ?? ::NNGAKEGL::`string'+0x5abab
fffff880`031f6cb0 fffff800`04b64166 : e8654d0f`28f5188a fffffa80`03c46680 00000000`00000080 fffffa80`03c35040 : nt!ExpWorkerThread+0x111
fffff880`031f6d40 fffff800`0489f486 : fffff880`009ee180 fffffa80`03c46680 fffff880`009f8f40 07601031`13b6a212 : nt!PspSystemThreadStartup+0x5a
fffff880`031f6d80 00000000`00000000 : fffff880`031f7000 fffff880`031f1000 fffff880`031f69f0 00000000`00000000 : nt!KxStartSystemThread+0x16
STACK_COMMAND: .thread 0xfffffa8003c46680 ; kb
FOLLOWUP_IP:
nt!KiSwapContext+7a
fffff800`048c6dda 488d8c2400010000 lea rcx,[rsp+100h]
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: nt!KiSwapContext+7a
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc600
FAILURE_BUCKET_ID: X64_0x9F_nt!KiSwapContext+7a
BUCKET_ID: X64_0x9F_nt!KiSwapContext+7a
Followup: MachineOwner
--------- -
Just as a follow on, things done before these errors by instance of BSOD:
#1) Do not recall
#2) Set up and turned on WIFI on a MAC book for friend while my Thinkpad was also connected to WIFI. I thought it was coincidental but when walked into other room saw BSOD.
#3) Blacked Blackberry near palmrest (which is also near HDD). Though it was coincidental????
#4) Mucking around trying to get a 10 year old firewire drive working. Changed drivers then revert back. Didnt work so revert back but froze so I just used task manger to get out. Continued to use notebok aks "NB", then went to sleep /nap (me). When woke up, saw a BSOD had happened. During this period, it was also long enought for the NB to hibernate/sleep.
#5) Related to #4.
For instnaces 4 and 5, USB hub was connected.
For 1 to 5, common factors are W7 and WIFI being used.
What to do next?
As an aside I also downloaded and installed the whole symbol library and isntalled it. This was from MDN (Microsoft). But did not know how to link the debuger to it. So found this way. Why when this downloads my firewall doesnt ask for pemission!!!! this is alarming so say the least!
Symbol search path is: symsrv*symsrv.dll*c:\Windows\symbols* http://msdl.microsoft.com/download/symbols -
netw5v64.sys--find and right click...what version?
-
Hi, again thanks for helping. Much appreciated. I did a search, including enabling viewing of hidden files but nothing showed up. But went to device manager and the driver is netw5v64.sys for Intel 4965AGN. Version 12.4.1.4 Provided by Intel and digitally signed by Bill Gates himself on 3/26/2009.
http://www.sevenforums.com/crashes-debugging/21228-need-help-windows-7-bsod-lenovo-t500-2.html
Here is a similar prob?
Anyway my total BSODs since W7 has been 5. Not sure all of them are related. What do you think? -
From the bugcheck it appears to be an issue with the network card drivers. Try updating your WLAN and LAN NICs to the latest versionstrying one at a time to determine where the culprit lies. This includes trying the latest drivers from Lenovos and Intels web site.
-
Hi thanks so much. Very appreciative. You know I have never used LAN. Always on WIFI connection to a router. Is that considered a network?
Also I get some error message about Torenodo IPV6 but dont know what it is but read might be related to Zone Alarm so I just ignored it.
I have all the Lenovo updates installed. Will check Intel. Is it wise to assume Lenovo is slower in providing Intel's drivers?
BSOD W7 imperfect? Please Help Me!
Discussion in 'Windows OS and Software' started by BaldwinHillsTrojan, Feb 17, 2010.
