Unsolved
This post is more than 5 years old
15 Posts
0
11335
December 30th, 2009 19:00
O2Micro SD Reader BSOD with Vostro 1520 Win7 x64
I am having a problem with my Vostro 1520. If I install a SDHC 8GB card in my laptop (formatted NTFS), the laptop bluescreens with a DRIVER_POWER_STATE_FAILURE.
I have already installed the latest O2Micro driver 2.0.09,A01. It made no difference.
Does anyone know how to use an SDHC card without bluescreening?
Here is the latest !analyze -v
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`03209000 PsLoadedModuleList = 0xfffff800`03446e50
Debug session time: Wed Dec 30 21:12:49.336 2009 (GMT-5)
System Uptime: 0 days 0:16:36.178
Loading Kernel Symbols
...............................................................
................................................................
..............................................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 9F, {3, fffffa800878a050, fffff80000b9c4d8, fffffa8005a1cc60}
*** ERROR: Module load completed but symbols could not be loaded for o2sdgx64.sys
Unable to open image file: C:\Program Files\Debugging Tools for Windows (x64)\sym\ntkrnlmp.exe\4A5BC6005dd000\ntkrnlmp.exe
The system cannot find the file specified.
Probably caused by : o2sdgx64.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: fffffa800878a050, Physical Device Object of the stack
Arg3: fffff80000b9c4d8, Functional Device Object of the stack
Arg4: fffffa8005a1cc60, The blocked IRP
Debugging Details:
------------------
Unable to open image file: C:\Program Files\Debugging Tools for Windows (x64)\sym\ntkrnlmp.exe\4A5BC6005dd000\ntkrnlmp.exe
The system cannot find the file specified.
DRVPOWERSTATE_SUBCODE: 3
IRP_ADDRESS: fffffa8005a1cc60
DEVICE_OBJECT: fffffa800878a050
DRIVER_OBJECT: fffffa80054f77b0
IMAGE_NAME: o2sdgx64.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4a0273f4
MODULE_NAME: o2sdgx64
FAULTING_MODULE: fffff88004528000 o2sdgx64
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x9F
PROCESS_NAME: System
CURRENT_IRQL: 2
LAST_CONTROL_TRANSFER: from fffff800032e9e23 to fffff8000327af00
STACK_TEXT:
fffff800`00b9c488 fffff800`032e9e23 : 00000000`0000009f 00000000`00000003 fffffa80`0878a050 fffff800`00b9c4d8 : nt!KeBugCheckEx
fffff800`00b9c490 fffff800`03286fa6 : fffff800`00b9c5c0 fffff800`00b9c5c0 00000000`00000001 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x29330
fffff800`00b9c530 fffff800`03286326 : fffffa80`07c31418 fffffa80`07c31418 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x66
fffff800`00b9c5a0 fffff800`03286e7e : 00000002`51c4c617 fffff800`00b9cc18 00000000`0000f971 fffff800`033f70a8 : nt!KiProcessExpiredTimerList+0xc6
fffff800`00b9cbf0 fffff800`03286697 : 00000000`8ade08c2 00000000`0000f971 00000000`8ade081b 00000000`00000071 : nt!KiTimerExpiration+0x1be
fffff800`00b9cc90 fffff800`032836fa : fffff800`033f3e80 fffff800`03401c40 00000000`00000002 fffff880`00000000 : nt!KiRetireDpcList+0x277
fffff800`00b9cd40 00000000`00000000 : fffff800`00b9d000 fffff800`00b97000 fffff800`00b9cd00 00000000`00000000 : nt!KiIdleLoop+0x5a
STACK_COMMAND: kb
FOLLOWUP_NAME: MachineOwner
FAILURE_BUCKET_ID: X64_0x9F_IMAGE_o2sdgx64.sys
BUCKET_ID: X64_0x9F_IMAGE_o2sdgx64.sys
Followup: MachineOwner
---------
0: kd> lmvm o2sdgx64
start end module name
fffff880`04528000 fffff880`04532480 o2sdgx64 (no symbols)
Loaded symbol image file: o2sdgx64.sys
Image path: \SystemRoot\system32\DRIVERS\o2sdgx64.sys
Image name: o2sdgx64.sys
Timestamp: Thu May 07 01:39:00 2009 (4A0273F4)
CheckSum: 00018D39
ImageSize: 0000A480
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
0: kd> lmvm o2sdgx64
start end module name
fffff880`04528000 fffff880`04532480 o2sdgx64 (no symbols)
Loaded symbol image file: o2sdgx64.sys
Image path: \SystemRoot\system32\DRIVERS\o2sdgx64.sys
Image name: o2sdgx64.sys
Timestamp: Thu May 07 01:39:00 2009 (4A0273F4)
CheckSum: 00018D39
ImageSize: 0000A480
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
0 events found


chesternerd
2 Posts
0
November 12th, 2011 05:00
I get the same thing - regularly. No doubt it is the 02 driver issue on win7 x64.