DRIVER_POWER_STATE_FAILURE BSOD on shutdown only

Hi all, I'm suffering from BSODs whenever I attempt to shutdown my computer. I never seem to have issues during normal operation. All I can tell is that ntoskrnl.exe seems to be related to the crashes. I haven't changed anything recently, to the best of my knowledge, and my computer had been functioning well in the past.

I would really appreciate any help you could give me. Thanks.

Welcome to Sevenforums. :)

That one is easy, your issues were caused by LEqdUsb.Sys, part of the Logitech Setpoint Software. (SetPoint Unifying KMDF USB Filter).
Update this software: Support + Downloads

If that doesn't stop the BSODs you should uninstall it from your system.

Code:

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

Use !analyze -v to get detailed debugging information.

BugCheck 9F, {3, fffffa80091f8a00, fffff80000b9c3d8, fffffa800cafbc10}

*** WARNING: Unable to verify timestamp for LEqdUsb.Sys
*** ERROR: Module load completed but symbols could not be loaded for LEqdUsb.Sys
Probably caused by : LEqdUsb.Sys

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: fffffa80091f8a00, Physical Device Object of the stack
Arg3: fffff80000b9c3d8, Functional Device Object of the stack
Arg4: fffffa800cafbc10, The blocked IRP

DRVPOWERSTATE_SUBCODE:  3

IRP_ADDRESS:  fffffa800cafbc10

DEVICE_OBJECT: fffffa80091f97c0

DRIVER_OBJECT: fffffa800919fa30

IMAGE_NAME:  LEqdUsb.Sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4e607640

MODULE_NAME: LEqdUsb

FAULTING_MODULE: fffff88006c4d000 LEqdUsb

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x9F

PROCESS_NAME:  System

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from fffff80003139092 to fffff800030cbc80

STACK_TEXT:  
fffff800`00b9c388 fffff800`03139092 : 00000000`0000009f 00000000`00000003 fffffa80`091f8a00 fffff800`00b9c3d8 : nt!KeBugCheckEx
fffff800`00b9c390 fffff800`030d695c : fffff800`00b9c4c0 fffff800`00b9c4c0 00000000`00000000 00000000`00000001 : nt! ?? ::FNODOBFM::`string'+0x34040
fffff800`00b9c430 fffff800`030d67f6 : fffff800`03275f00 00000000`03cd1526 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x6c
fffff800`00b9c4a0 fffff800`030d66de : 0000090c`50062305 fffff800`00b9cb18 00000000`03cd1526 fffff800`03243748 : nt!KiProcessExpiredTimerList+0xc6
fffff800`00b9caf0 fffff800`030d64c7 : 0000021d`22d342c1 0000021d`03cd1526 0000021d`22d342ae 00000000`00000026 : nt!KiTimerExpiration+0x1be
fffff800`00b9cb90 fffff800`030c398a : fffff800`03240e80 fffff800`0324ecc0 00000000`00000002 fffff880`00000000 : nt!KiRetireDpcList+0x277
fffff800`00b9cc40 00000000`00000000 : fffff800`00b9d000 fffff800`00b97000 fffff800`00b9cc00 00000000`00000000 : nt!KiIdleLoop+0x5a

STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

FAILURE_BUCKET_ID:  X64_0x9F_IMAGE_LEqdUsb.Sys

BUCKET_ID:  X64_0x9F_IMAGE_LEqdUsb.Sys

So, I've uninstalled logitech setpoint but my problem still seems to be ongoing. I continue to experience BSODs on shutdown.

Is there anything else I can do? I've attached another minidump which will hopefully reveal the true culprit.

Thanks so much for the help... This is really irksome.

Your last dumps blames Ak27x64.sys, Killer Wireless-N 1100 Series LAN device driver.
That needs to be updated/removed.
Killer Gaming :: Support :: Driver Downloads

Code:

BugCheck 9F, {3, fffffa80060d6060, fffff80000b9c3d8, fffffa800ab33c10}

*** WARNING: Unable to verify timestamp for Ak27x64.sys
*** ERROR: Module load completed but symbols could not be loaded for Ak27x64.sys
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : Ak27x64.sys