I seem to be getting BSOD after about 30 minutes of turning on my computer, it's getting more and more frequent. Here are my specs.
Operating System
Windows 10 Home 64-bit
CPU
Intel Core i7 6700HQ @ 2.60GHz 33 °C
Skylake 14nm Technology
RAM
12.0GB Dual-Channel Unknown @ 1063MHz (15-15-15-36)
Motherboard
ASUSTeK COMPUTER INC. GL502VT (U3E1) 36 °C
Graphics
Generic PnP Monitor (1920x1080@60Hz)
Intel HD Graphics 530 (ASUStek Computer Inc)
3072MB NVIDIA GeForce GTX 970M (ASUStek Computer Inc) 44 °C
ForceWare version: 359.54
SLI Disabled
Storage
931GB Seagate ST1000LM048-2E7172 (SATA) 36 °C
Optical Drives
No optical disk drives detected
Audio
Realtek High Definition Audio
as well as the WhoCrashed diagnosis
On Sun 9/17/2017 12:16:03 PM your computer crashed
crash dump file: C:\Windows\Minidump\091717-32656-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x142A00)
Bugcheck code: 0x9F (0x3, 0xFFFFE00134494060, 0xFFFFF803A1A86890, 0xFFFFE001343A5B40)
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 Sun 9/17/2017 12:16:03 PM 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, 0xFFFFE00134494060, 0xFFFFF803A1A86890, 0xFFFFE001343A5B40)
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.
Operating System
Windows 10 Home 64-bit
CPU
Intel Core i7 6700HQ @ 2.60GHz 33 °C
Skylake 14nm Technology
RAM
12.0GB Dual-Channel Unknown @ 1063MHz (15-15-15-36)
Motherboard
ASUSTeK COMPUTER INC. GL502VT (U3E1) 36 °C
Graphics
Generic PnP Monitor (1920x1080@60Hz)
Intel HD Graphics 530 (ASUStek Computer Inc)
3072MB NVIDIA GeForce GTX 970M (ASUStek Computer Inc) 44 °C
ForceWare version: 359.54
SLI Disabled
Storage
931GB Seagate ST1000LM048-2E7172 (SATA) 36 °C
Optical Drives
No optical disk drives detected
Audio
Realtek High Definition Audio
as well as the WhoCrashed diagnosis
On Sun 9/17/2017 12:16:03 PM your computer crashed
crash dump file: C:\Windows\Minidump\091717-32656-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x142A00)
Bugcheck code: 0x9F (0x3, 0xFFFFE00134494060, 0xFFFFF803A1A86890, 0xFFFFE001343A5B40)
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 Sun 9/17/2017 12:16:03 PM 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, 0xFFFFE00134494060, 0xFFFFF803A1A86890, 0xFFFFE001343A5B40)
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.