Windows 10: Seemingly random BSOD's on new laptop (ntoskrnl.exe)?

Hi everyone,

I'm having an issue with my new laptop running Windows 10. After increasingly short periods of time, I am experiencing a BSOD seemingly at random, with the error message "DRIVER_POWER_STATE_FAILURE". I have looked into my minidump file using BlueScreenViewer and it tells me that the ntoskrnl.exe driver causes the error, which isn't entirely useful. I have also looked at my device manager and there are no yellow exclamation marks suggesting an out of date driver. The BSOD happens more whenever I am gaming, but can crop up at times when I'm just listening to music or browsing on the internet, so I can't be sure of the cause.

That's pretty much the limit of my tech knowledge so I'm pretty stumped on what's causing the issue.

Any help you could give me would be greatly appreciated.

Thanks,
Tom


:)

 

Lots of BSOD's

PS: after my previous/last replie i had 3 more BSOD's:

seems like there are a lot of random once...

MEMORY_MANAGEMENT win32kbase.sys

MEMORY_MANAGEMENT ntoskrnl.exe

ntoskrnl.exe

 

Seemingly random BSODs

Running with verifier crashed immediately upon booting. Dump file is here: 100616 crash dump

Crash was caused by intcdaud.sys.

On Fri 10/7/2016 12:10:53 AM GMT your computer crashed

crash dump file: C:\WINDOWS\Minidump\100616-22468-01.dmp

This was probably caused by the following module: intcdaud.sys (IntcDAud+0x1F602)

Bugcheck code: 0xC4 (0x2000, 0xFFFFF802DFC1F602, 0x0, 0x20437A41)

Error: DRIVER_VERIFIER_DETECTED_VIOLATION

file path: C:\WINDOWS\system32\drivers\intcdaud.sys

product: Intel(R) Display Audio

company: Intel(R) Corporation

description: Intel(R) Display Audio Driver

Bug check description: This is the general bug check code for fatal errors found by Driver Verifier.

This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.

A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: intcdaud.sys (Intel(R) Display Audio Driver, Intel(R) Corporation).

Google query: Intel(R) Corporation DRIVER_VERIFIER_DETECTED_VIOLATION

On Fri 10/7/2016 12:10:53 AM GMT your computer crashed

crash dump file: C:\WINDOWS\memory.dmp

This was probably caused by the following module: intcdaud.sys (IntcDAud+0x1F602)

Bugcheck code: 0xC4 (0x2000, 0xFFFFF802DFC1F602, 0x0, 0x20437A41)

Error: DRIVER_VERIFIER_DETECTED_VIOLATION

file path: C:\WINDOWS\system32\drivers\intcdaud.sys

product: Intel(R) Display Audio

company: Intel(R) Corporation

description: Intel(R) Display Audio Driver

Bug check description: This is the general bug check code for fatal errors found by Driver Verifier.

This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.

A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: intcdaud.sys (Intel(R) Display Audio Driver, Intel(R) Corporation).

Google query: Intel(R) Corporation DRIVER_VERIFIER_DETECTED_VIOLATION

 

The yellow exclamation marks don't say a driver is outdated, but there are problems with the devices.

Daemon tools, Alcohol 120% and Power Archiver Pro uses SCSI Pass Through Direct (SPTD), which is a well known cause for BSOD's.
Please remove Daemon Tools and run the SPTD pass through remover.

• Uninstall Daemon Tools
• Download the SPTD standalone installer and follow these steps:
  • Double click the executable to open it
  • Click on the button shown below

If the button is grayed out, like in the image, there is no more SPTD installation on your system, and you can close the window



Warning Programs that claim to update your drivers install either the wrong or corrupted drivers.
If you have installed any driver with DriverEasy, please remove them as it may cause trouble.






Diagnostics Test

System File Check
Please try following:

• Open an admin command prompt
• Copy/paste "sfc/scannow" (without quotes) and press enter
• When it finished reboot your system
• Open again an admin command prompt
• Enter sfc/scannow again

If sfc/scannow does NOT say "Windows Resource Protection did not find any integrity violation" after the second SFC, please upload the cbs.log file located at {windows partition}\Windows\Logs\CBS\, if the file is too large try a 3rd party uploader like dropbox, onedrive, google drive, mediafire etc.
System File Check(SFC a.k.a. Windows Resource Protection) needs to have your system rebooted in order for sfc to try to fix the problems that it finds.

Best suggestion I currently can give is to check your manufacturer for drivers and (re)install them all.
The dumps aren't very useful, no driver has been flagged.