Driver State Power Failure BSOD

Hello and Welcome !

Seems like lot of issues are going on. First thing i noticed is sptd.sys duplex driver which i well known for BSOD. I would recommend to uninstall it follow this article DuplexSecure - FAQ

Also it looks to me like it's an issue with AiCharger.sys - an Asus program named AiCharger (may also be a part of the Asus AISuite or ASUS Ai Charger). Then uninstall the current copy of the program and install the freshly downloaded copy.

Run a Hardware Diagnostic (Memory and Hard Drive) follow this link for instructions Hardware Diagnostic !! « Captain Debugger

Bugcheck:

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 9F, {3, fffffa80083a1060, fffff8000460e518, fffffa80060214c0}

Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+292b0 )

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: fffffa80083a1060, Physical Device Object of the stack
Arg3: fffff8000460e518, Functional Device Object of the stack
Arg4: fffffa80060214c0, The blocked IRP

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


DRVPOWERSTATE_SUBCODE:  3

IRP_ADDRESS:  fffffa80060214c0

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x9F

PROCESS_NAME:  System

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from fffff80002f34273 to fffff80002ec5740

STACK_TEXT:  
fffff800`0460e4c8 fffff800`02f34273 : 00000000`0000009f 00000000`00000003 fffffa80`083a1060 fffff800`0460e518 : nt!KeBugCheckEx
fffff800`0460e4d0 fffff800`02ed129e : fffff800`0460e600 fffff800`0460e600 00000000`00000001 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x292b0
fffff800`0460e570 fffff800`02ed0dd6 : fffff800`03075700 00000000`000360c1 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x66
fffff800`0460e5e0 fffff800`02ed14be : 00000008`0a74fb73 fffff800`0460ec58 00000000`000360c1 fffff800`03043aa8 : nt!KiProcessExpiredTimerList+0xc6
fffff800`0460ec30 fffff800`02ed0cb7 : 00000003`242506c1 00000003`000360c1 00000003`24250623 00000000`000000c1 : nt!KiTimerExpiration+0x1be
fffff800`0460ecd0 fffff800`02ecdeea : fffff800`0303fe80 fffff800`0304dc40 00000000`00000000 fffff800`02ed6a74 : nt!KiRetireDpcList+0x277
fffff800`0460ed80 00000000`00000000 : fffff800`0460f000 fffff800`04609000 fffff800`0460ed40 00000000`00000000 : nt!KiIdleLoop+0x5a


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt! ?? ::FNODOBFM::`string'+292b0
fffff800`02f34273 cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+292b0

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4c1c44a9

FAILURE_BUCKET_ID:  X64_0x9F_nt!_??_::FNODOBFM::_string_+292b0

BUCKET_ID:  X64_0x9F_nt!_??_::FNODOBFM::_string_+292b0

Followup: MachineOwner

Hope this helps,
Captain

The StarWind AE Service service failed to start due to the following error:
The system cannot find the file specified.

I'm noticing that in the IRP, even though this is a minidump with limited data, there's what appears to be a symantec driver there (well, specifically Norton Internet Security). Would you be able to remove NIS and re-test? The "driver" that can cause an inconsistent power state doesn't always have to be an actual hardware driver - it can be (and looks like it may be) a *filter* driver, specifically a *network* filter driver, SYMTDIV.sys (NIS's TDI interface).

Awesome - if you think it's resolved, don't forget to request the thread be marked as such.

Thanks for the Update. I'm glad that your up and running !

- Captain

Bobojeb said:

Alright guys, I think you can mark this thread as resolved, everything runs flawlessly.

Peace

Thanks for posting back. I'm glad everything is resolved :)

Good Luck,
Captain