dails BSODs - all files attached! ntoskrnl.exe?

[wellysm]

Hi everyone,

I just seen the rules for the BSODs threads, so I had deleted my old improper thread.

Attached are all the files required,

Using BlueScreenView, it states that its caused by ntoskrnl.exe+80640 however reading several articles it seems that [COLOR=#0072bc !important][FONT=inherit !important][COLOR=#0072bc !important][FONT=inherit !important]windows [/FONT][/FONT][FONT=inherit !important][COLOR=#0072bc !important][FONT=inherit !important]7[/FONT][/COLOR][/FONT][/COLOR][/COLOR] basically gives wrong errors?

- 64 bit
- windows 7 home premium - upgraded from Vista via the microsoft/gateway free windows 7 program.
- age : 1.5 years
- over a year with windows 7, however I reformatted about a month and a half ago.

 

[wish]

Hi,
It seems your Memory Card Reader (by O2Micro) driver that causing the problems.
So you must update that driver or disable it for a while to see if the BSOD persist.
O2Micro - Welcome

Also update your Conexant Modem driver: → Conexant: Support

CAX_CNXT.sys Wed Oct 18 11:30:08 2006
CAX_DPV.sys  Wed Oct 18 11:33:30 2006 
CAXHWAZL.sys Wed Oct 18 11:31:09 2006

LOG

Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Machine Name:
Kernel base = 0xfffff800`02c51000 PsLoadedModuleList = 0xfffff800`02e96e90
Debug session time: Tue Mar  8 14:52:08.688 2011 (GMT-8)
System Uptime: 0 days 4:33:56.920
Loading Kernel Symbols
...............................................................
................................................................
.........................................
Loading User Symbols
Loading unloaded module list
.........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 9F, {3, fffffa8006dfb050, fffff80000b9c518, fffffa80043b2bd0}

Probably caused by : disk.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: fffffa8006dfb050, Physical Device Object of the stack
Arg3: fffff80000b9c518, Functional Device Object of the stack
Arg4: fffffa80043b2bd0, The blocked IRP

Debugging Details:
------------------


DRVPOWERSTATE_SUBCODE:  3

IRP_ADDRESS:  fffffa80043b2bd0

DEVICE_OBJECT: fffffa8006dfc790

DRIVER_OBJECT: fffffa80057ddc80

IMAGE_NAME:  disk.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc11d

MODULE_NAME: disk

FAULTING_MODULE: fffff88001ba7000 disk

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x9F

PROCESS_NAME:  System

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from fffff80002d3db52 to fffff80002cd1640

STACK_TEXT:  
fffff800`00b9c4c8 fffff800`02d3db52 : 00000000`0000009f 00000000`00000003 fffffa80`06dfb050 fffff800`00b9c518 : nt!KeBugCheckEx
fffff800`00b9c4d0 fffff800`02cdd062 : fffff800`00b9c600 fffff800`00b9c600 00000000`00000001 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x34a90
fffff800`00b9c570 fffff800`02cdcf06 : fffffa80`0748bc10 fffffa80`0748bc10 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x66
fffff800`00b9c5e0 fffff800`02cdcdee : 00000026`452b05e0 fffff800`00b9cc58 00000000`001013c9 fffff800`02e47ba8 : nt!KiProcessExpiredTimerList+0xc6
fffff800`00b9cc30 fffff800`02cdcbd7 : 00000008`987d6bc2 00000008`001013c9 00000008`987d6be1 00000000`000000c9 : nt!KiTimerExpiration+0x1be
fffff800`00b9ccd0 fffff800`02cc936a : fffff800`02e43e80 fffff800`02e51cc0 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_disk.sys

BUCKET_ID:  X64_0x9F_IMAGE_disk.sys

Followup: MachineOwner
---------

 

[wellysm]

This makes alot of sense, as last night I took out the SD card thats been in my laptop for a while to use in another laptop.

since then I havnt had the BSOD!

Thanks alot! i'll keep you updated if anything happens