BSOD while trying to load some games

[Jaxtes]

Recently, trying to play games has caused BSOD. Did a factory reset worked for a bit then started crashing again. Always happens for same games during loading screen. System meets required specs. Nvidia and Intel drivers appear to be up to date.
Whocrashed Info:

System Information (local)
--------------------------------------------------------------------------------

Computer name: DESKTOP-T7MA1DR
Windows version: Windows 10 , 10.0, build: 14393
Windows dir: C:\WINDOWS
Hardware: N15_17RD, Notebook
CPU: GenuineIntel Intel(R) Core(TM) i7-6700HQ CPU @ 2.60GHz Intel586, level: 6
8 logical processors, active mask: 255
RAM: 17093951488 bytes total




--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\WINDOWS\Minidump

Crash dumps are enabled on your computer.

On Thu 12/8/2016 11:38:20 AM your computer crashed
crash dump file: C:\WINDOWS\Minidump\120816-21046-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14A510)
Bugcheck code: 0x9F (0x3, 0xFFFF91860BAD4060, 0xFFFFCB0039AFE8E0, 0xFFFF91861051C010)
Error: DRIVER_POWER_STATE_FAILURE
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that the driver is in an inconsistent or invalid power state.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Thu 12/8/2016 11:38:20 AM your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x9F (0x3, 0xFFFF91860BAD4060, 0xFFFFCB0039AFE8E0, 0xFFFF91861051C010)
Error: DRIVER_POWER_STATE_FAILURE
Bug check description: This bug check indicates that the driver is in an inconsistent or invalid power state.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

Let know if anything else needs to be uploaded.
Thanks.

 

[Ralston18]

I googled "Error: DRIVER_POWER_STATE_FAILURE"

Found a variety of website hits. Note: Be cautious of any websites offering an immediate repair or fix via some download....

Here is one current link that may be useful:

https://appuals.com/how-to-fix-the-driver_power_state_failure-bsod/

There are other similar links.

You might also look at your Event Viewer logs. Good chance that there will be additional details associated with any related log entries - especially entries with the red circle icon. Right click the entry for more details. May be able to identify a specific process or service that is involved with or causing the BSODs.

 

[Jaxtes]

Thanks for the quick reply Ralston18, I tried what was on the link you provided except for

"Insyde Airplane Mode HID Mini-Driver"
"Generic PnP Monitor"

were showing defect. Reinstalled them, still getting Blue Screen on trying to load these games.
Did the event log part got 4 criticals
Screenshot

Log Name: System
Source: Microsoft-Windows-Kernel-Power
Date: 12/8/2016 5:47:44 PM
Event ID: 41
Task Category: (63)
Level: Critical
Keywords: (70368744177664),(2)
User: SYSTEM
Computer: DESKTOP-T7MA1DR
Description:
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-Kernel-Power" Guid="{331C3B3A-2005-44C2-AC5E-77220C37D6B4}" />
<EventID>41</EventID>
<Version>4</Version>
<Level>1</Level>
<Task>63</Task>
<Opcode>0</Opcode>
<Keywords>0x8000400000000002</Keywords>
<TimeCreated SystemTime="2016-12-08T22:47:44.943423900Z" />
<EventRecordID>3159</EventRecordID>
<Correlation />
<Execution ProcessID="4" ThreadID="8" />
<Channel>System</Channel>
<Computer>DESKTOP-T7MA1DR</Computer>
<Security UserID="S-1-5-18" />
</System>
<EventData>
<Data Name="BugcheckCode">159</Data>
<Data Name="BugcheckParameter1">0x3</Data>
<Data Name="BugcheckParameter2">0xffff8303530de060</Data>
<Data Name="BugcheckParameter3">0xfffff80161079cb0</Data>
<Data Name="BugcheckParameter4">0xffff830357fb6010</Data>
<Data Name="SleepInProgress">0</Data>
<Data Name="PowerButtonTimestamp">0</Data>
<Data Name="BootAppStatus">0</Data>
<Data Name="Checkpoint">0</Data>
<Data Name="ConnectedStandbyInProgress">false</Data>
<Data Name="SystemSleepTransitionsToOn">0</Data>
<Data Name="CsEntryScenarioInstanceId">0</Data>
</EventData>
</Event>

 

[Ralston18]

Thanks. Unfortunately this is probably going to get tougher.

Google "Event 41 kernel-power windows 10" and then maybe try some word variations that customize the search to fit your computer setup. Add in "Task Category 63" for example.

You will find quite a few websites with related information. Probably best to just read and bookmark any website solutions that seem promising.

Avoid websites that claim to have fixes and/or want you to download some software. Those sites will most likely turn up no matter what problem you are trying to resolve.

Hopefully you will find some concensus with respect to your computer and setup. Then perhaps a few viable solutions to try.

Solutions may or may not work for you but you will have a better chance of noticing something or otherwise identifying some relevant factor.

And keep an eye on the Event Viewer logs. Another entry or two could show up and provide some additional information.

Post if you find something you wish to add. Hopefully someone following this thread may recognize an issue and offer an idea or two Or spot something I missed. No problem with that on my end.