New build bluescreen

[DrunkenClam]

Hey everyone. First post here, I'm told your forum is one of the best, so I came to see if you can help me out.

I just recently built a new PC, one of many I've built (I'll detail the specs below). Every day, the first time I turn it on, it boots just fine and lasts about 5 minutes. Then it crashes with a win10 bluescreen "DRIVER_POWER_STATE_FAILURE" error. When it immediately reboots, its fine for the rest of the day. I've been using it a lot and gaming heavily on it and it has no other issues other than the first boot of the day.

I've gone through and verified that all the drivers are up to date and signed. My next plan is to go through the drivers individually and roll them back, trying to see if I can isolate the problem. If any of you have any suggestions, please help me out. Thanks!

PC Details:
http://pcpartpicker.com/p/qsKHVn

 

[Cycloid Torus]

Never had this - and I think you are right about drivers being the issue - is there anything you have (USB connected, etc) which gets a delayed start - maybe special driver for mouse or keyboard??

 

[DrunkenClam]

I've got a blackwidow keyboard and a rat7 mouse that both have programmable button suites. I made sure to update those as well, but the issue persists.

The most perplexing part is I can't seem to determine why it only happens for the first boot every day.

 

[Cycloid Torus]

Wild guess... capacitor... voltage comes on, system powers up, delayed driver kicks in...cap is not stable... error report ....reboot...cap is now sufficiently charged. Need to isolate the problem. Run with alternative mouse and keyboard - disable special m/k drivers.

 

[Cycloid Torus]

http://www.computerhope.com/issues/ch001141.htm

 

[DrunkenClam]

It may be helpful to note that the bluescreen happens even if I don't log in. I can turn it on and leave it on the login screen and it will still go down in about the same period of time. Then it will come back up and be fine all day.

 

[DrunkenClam]

I've been busy, but as an update: I went to my mobo support page and made sure all the chipset drivers/BIOS are up to date. I've verified every other driver is updated and that my mobo does not do APM. If the problem persists, I'll start unhooking hardware and see if it happens again.
Unfortunately, due to the nature of the problem, I won't know if this worked until tomorrow or this evening at the earliest :/

 

[DrunkenClam]

I ran windbg on the BSOD minidump and learned that its an ACPI.sys error, debug infor below:


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

DRIVER_POWER_STATE_FAILURE (9f)
A driver has failed to complete a power IRP within a specific time.
Arguments:
Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
Arg2: ffffe000e14db8e0, Physical Device Object of the stack
Arg3: fffff800f1e90890, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
Arg4: ffffe000e0efdb80, The blocked IRP

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


DUMP_CLASS: 1

DUMP_QUALIFIER: 400

BUILD_VERSION_STRING: 10586.212.amd64fre.th2_release_sec.160328-1908

SYSTEM_MANUFACTURER: EVGA INTERNATIONAL CO.,LTD

SYSTEM_PRODUCT_NAME: Default string

SYSTEM_SKU: Default string

SYSTEM_VERSION: Default string

BIOS_VENDOR: American Megatrends Inc.

BIOS_VERSION: 1.05

BIOS_DATE: 10/01/2015

BASEBOARD_MANUFACTURER: EVGA INTERNATIONAL CO.,LTD

BASEBOARD_PRODUCT: 140-SS-E177

BASEBOARD_VERSION: 1.0

DUMP_TYPE: 2

BUGCHECK_P1: 3

BUGCHECK_P2: ffffe000e14db8e0

BUGCHECK_P3: fffff800f1e90890

BUGCHECK_P4: ffffe000e0efdb80

DRVPOWERSTATE_SUBCODE: 3

IMAGE_NAME: ACPI.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 56cbf9c9

MODULE_NAME: ACPI

FAULTING_MODULE: fffff80016500000 ACPI

CPU_COUNT: 8

CPU_MHZ: fa8

CPU_VENDOR: GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 5e

CPU_STEPPING: 3

CPU_MICROCODE: 6,5e,3,0 (F,M,S,R) SIG: 33'00000000 (cache) 33'00000000 (init)

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

BUGCHECK_STR: 0x9F

PROCESS_NAME: System

CURRENT_IRQL: 2

ANALYSIS_SESSION_HOST: DESKTOP-RSEFKGE

ANALYSIS_SESSION_TIME: 04-15-2016 23:43:33.0447

ANALYSIS_VERSION: 10.0.10586.567 amd64fre

STACK_TEXT:
fffff800`f1e90858 fffff800`f0458e42 : 00000000`0000009f 00000000`00000003 ffffe000`e14db8e0 fffff800`f1e90890 : nt!KeBugCheckEx
fffff800`f1e90860 fffff800`f0458d62 : ffffe000`e57dc220 fffff800`f1e88070 00000000`00000000 fffff800`f03420a6 : nt!PopIrpWatchdogBugcheck+0xde
fffff800`f1e908c0 fffff800`f02e62c6 : ffffe000`e57dc258 fffff800`f1e90a10 00000000`00000001 00000000`00250231 : nt!PopIrpWatchdog+0x32
fffff800`f1e90910 fffff800`f03bd51a : 00000000`00000000 fffff800`f0595180 fffff800`f060b740 ffffe000`e4ad5800 : nt!KiRetireDpcList+0x5f6
fffff800`f1e90b60 00000000`00000000 : fffff800`f1e91000 fffff800`f1e8a000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x5a


STACK_COMMAND: kb

THREAD_SHA1_HASH_MOD_FUNC: 81a7ba75a791115b4f55c8910c64a260d525502e

THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 936d5c51c0ad2157bf4c85af575dd55cea2c0947

THREAD_SHA1_HASH_MOD: f08ac56120cad14894587db086f77ce277bfae84

FOLLOWUP_NAME: MachineOwner

IMAGE_VERSION: 10.0.10586.122

FAILURE_BUCKET_ID: 0x9F_3_POWER_DOWN_i8042prt_IMAGE_ACPI.sys

BUCKET_ID: 0x9F_3_POWER_DOWN_i8042prt_IMAGE_ACPI.sys

PRIMARY_PROBLEM_CLASS: 0x9F_3_POWER_DOWN_i8042prt_IMAGE_ACPI.sys

TARGET_TIME: 2016-04-15T18:28:31.000Z

OSBUILD: 10586

OSSERVICEPACK: 0

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK: 272

PRODUCT_TYPE: 1

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

OSEDITION: Windows 10 WinNt TerminalServer SingleUserTS

OS_LOCALE:

USER_LCID: 0

OSBUILD_TIMESTAMP: 2016-03-28 23:19:02

BUILDDATESTAMP_STR: 160328-1908

BUILDLAB_STR: th2_release_sec

BUILDOSVER_STR: 10.0.10586.212.amd64fre.th2_release_sec.160328-1908

ANALYSIS_SESSION_ELAPSED_TIME: 6fa

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:0x9f_3_power_down_i8042prt_image_acpi.sys

FAILURE_ID_HASH: {22a3ff34-49ca-8d37-715b-ae023b6cc9fb}

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

0: kd> !irp ffffe000e0efdb80
Irp is active with 9 stacks 7 is current (= 0xffffe000e0efde00)
No Mdl: No System Buffer: Thread 00000000: Irp stack trace. Pending has been returned
cmd flg cl Device File Completion-Context
[N/A(0), N/A(0)]
0 0 00000000 00000000 00000000-00000000

Args: 00000000 00000000 00000000 00000000
[N/A(0), N/A(0)]
0 0 00000000 00000000 00000000-00000000

Args: 00000000 00000000 00000000 00000000
[N/A(0), N/A(0)]
0 0 00000000 00000000 00000000-00000000

Args: 00000000 00000000 00000000 00000000
[N/A(0), N/A(0)]
0 0 00000000 00000000 00000000-00000000

Args: 00000000 00000000 00000000 00000000
[N/A(0), N/A(0)]
0 0 00000000 00000000 00000000-00000000

Args: 00000000 00000000 00000000 00000000
[IRP_MJ_POWER(16), IRP_MN_WAIT_WAKE(0)]
0 0 ffffe000e14db8e0 00000000 fffff800194b1ec0-00000000
\Driver\ACPI i8042prt!I8xPowerUpToD0Complete
Args: 00000000 00000000 00000000 00000002
>[IRP_MJ_POWER(16), IRP_MN_SET_POWER(2)]
0 e1 ffffe000e1edf040 00000000 fffff800194e1060-00000000 Success Error Cancel pending
\Driver\i8042prt kbdclass!KeyboardClassPowerComplete
Args: 00051100 00000001 00000001 00000002
[IRP_MJ_POWER(16), IRP_MN_SET_POWER(2)]
0 e1 ffffe000e1edfa90 00000000 fffff800f03880b8-ffffe000e57dc220 Success Error Cancel pending
\Driver\kbdclass nt!PopRequestCompletion
Args: 00051100 00000001 00000001 00000002
[N/A(0), N/A(0)]
0 0 00000000 00000000 00000000-ffffe000e57dc220

Args: 00000000 00000000 00000000 00000000

 

[Tmagic650]

Lets see if there is any additional info in the minidumps by posting them this way:
Go to C:\windows\minidump and select all the .dmp files. Right-click sending these files to a compressed(zipped)folder. Upload this folder as a file to your post

 

[DrunkenClam]

"All" is probably overkill, because it crashes every day, and too big to attach. I grabbed a few from random days to get a representative sample. Thanks for taking a look.

 

[Tmagic650]

All the same... Driver Power State Failure bug check 0x000009f

 

[DrunkenClam]

I finally fixed the issue.
The problem was that the motherboard was trying to boot the legacy PS/2 keyboard/mouse ports but failing. I recognized i8042.sys as the issue in the dump files, so I went to regedit and flipped the "Start" variable. This didn't fix it, because upon reboot, the registry generated an override variable and overrode my new input.
I went into the motherboard BIOS and found (buried) an option to "support legacy USB controllers". I disabled this and proceeded to flip the override entry. From there, it hasn't tried to override me again and no more bluescreens!

 

[Tmagic650]

Nice work! Thanks for the update...