You currently have javascript disabled. Several functions may not work. Please re-enable javascript to access full functionality.

Register a free account to unlock additional features at BleepingComputer.com

Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.

W10 INSTANTLY CRASHES ON STARTUP

This is a new computer I built myself, i've contacted MSI (MB manufacturer) and Microsoft both haven't helped, unfortunately. MSI said it's MS' fault.. Microsoft remote connected and deleted files, rebooted and worked once. Must've been a fluke. Problem still persists. Now I am here for you guys! If a solution is found I'd love to send 50 USD through PayPal for your help. I know it's not much, but I highly appreciate the help. Please accept, thank you.

The Problem

Every day when I start up my computer, before it even displays the Windows logo the computer will abruptly shut off. I'll proceed to manually turn it back on, then it'll show Windows repair. However, Windows can never solve the issue. So it asks for me to troubleshoot or restart. After I choose restart, it'll reboot and go straight to Windows login. This is strange, because the computer operates perfectly smooth otherwise; no anomalies, ect. I use Video intensive programs, rendering, CPU intensive simulations, and no BSOD during these normal operations. Only during power-ons.

I'd like to also note this has happened after Anniversary Update (yes, I've been doing this for this long). I can also verify that, because I did system restores at the time. At least until W10 forced the update onto my computer.

Occasional BSOD error messages after rebooting:

Phase0_exception

IRQL less than or equal

Unexpected kernal mode trap

System thread exception not handled

Pool corruption in file area

​Most Recent WhoCrashed Report:

On Tue 4/25/2017 1:54:18 AM your computer crashed
crash dump file: C:\WINDOWS\Minidump\042517-45718-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x16BF70)
Bugcheck code: 0xD1 (0x0, 0xFF, 0x1, 0x0)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUALfile path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating Systemcompany: Microsoft Corporationdescription: NT Kernel & System
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
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 4/20/2017 10:38:19 PM your computer crashed
crash dump file: C:\WINDOWS\Minidump\042117-23015-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x16BF70)
Bugcheck code: 0xD1 (0x0, 0xFF, 0x0, 0x0)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
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 Tue 4/18/2017 5:10:00 AM your computer crashed
crash dump file: C:\WINDOWS\Minidump\041817-30953-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x16BF70)
Bugcheck code: 0xD1 (0xFFFFF80226657C10, 0xFF, 0x0, 0xFFFFF80226657C10)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
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 Tue 4/18/2017 5:10:00 AM your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: ahcache.sys (ahcache+0x28C73)
Bugcheck code: 0xD1 (0xFFFFF80226657C10, 0xFF, 0x0, 0xFFFFF80226657C10)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\WINDOWS\system32\drivers\ahcache.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Application Compatibility Cache
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
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 a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.

Also Should I be concerned about this from Perfmon?

Motherboard Device Configured Fail Count
31
2
Motherboard devices.

Things I've Tried

I've uninstalled and reinstalled and updated every driver I could.

I made sure I had all the drivers from my motherboard's web page

​I ran memtest86 with 4 passes - all succeeded

Safe Mode; it works.

Disabled all startup programs

Update to latest BIOS

I am unclear whether it's hardware or software at this point. I attached one of the dump files in WinDbg, but I don't understand it. Also a Bluescreenview report. I can post dump files from as far as December if needed.

Please re-run MemTest86 for EIGHT passes, instead of four. Eight passes is necessary to completely ensure that your RAM is fine. Also, please run Seagate SeaTools for Windows. Be sure to test all your drives with the S.M.A.R.T. and Long Generic tests. (If you have time, run these hardware diagnostics too... skip the HDD and RAM tests since you ran them already).

• Press and hold the Windows Key + R on your keyboard at the same time.• In the Run box, type in %WinDir% and hit Enter on your keyboard.• Find the file MEMORY.DMP and copy/paste it on to your Desktop.• Zip up MEMORY.DMP (use .ZIP please!!!) and upload it to a trustworthy file-sharing service.

Hello, thanks for checking my question! I used Intel's own stress and diagnostics tool, also MSI's GPU stress tester. However, Furmark stress tested for 20 minutes @ 77C -- OK! No crashes.. I haven't tried Prime95, though. It says to run for 6-24 hours?

Seagate tool showed my 3rd drivefailed the SMART test. I'll atempt a fix and see what that does. Afterall, it is an old drive. Would a faulty drive cause a Windows boot to fail? Besides that, the others passed the Long Generic test.

I'll have to get back to you tomorrow on the Memtest86 one, because the 4 passes took around 5 hours. Yikes!

Yes, I disabled the Nvidia audio devices, because I have an audio interface plugged in. I thought I'd temporarly disable it as a way to diagnose the BSOD crashes.

Seagate tool showed my 3rd drivefailed the SMART test. I'll atempt a fix and see what that does. Afterall, it is an old drive. Would a faulty drive cause a Windows boot to fail? Besides that, the others passed the Long Generic test.

It could in theory, but I'm not sure myself. Is this your system drive? Best to backup all the data on the drive for now and disconnect it.

Yes, please run Prime95 for 6-24 hours, until you get errors... which ever comes first.

The memory dump unfortunately had very little information. We'll probably have to run Driver Verifier in the end.

On Thu 5/4/2017 11:54:50 PM your computer crashed
crash dump file: C:\WINDOWS\Minidump\050517-26359-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x16BFD0)
Bugcheck code: 0x139 (0x3, 0xFFFFF802084975A0, 0xFFFFF802084974F8, 0x0)
Error: KERNEL_SECURITY_CHECK_FAILURE
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: The kernel has detected the corruption of a critical data structure.
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 5/4/2017 11:54:50 PM your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: usbxhci.sys (USBXHCI+0xB120)
Bugcheck code: 0x139 (0x3, 0xFFFFF802084975A0, 0xFFFFF802084974F8, 0x0)
Error: KERNEL_SECURITY_CHECK_FAILURE
file path: C:\WINDOWS\system32\drivers\usbxhci.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: USB XHCI Driver
Bug check description: The kernel has detected the corruption of a critical data structure.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.

I don't see any warnings in Device Manager, hmm..

I can try the Prime95 one and report back in, thanks again!

EDIT: forgot to mention the 8 passes didn't find anything in memtest. So far so good on memory.

"Pool corruption in file area" tells me a driver that is trying to start up is causing it. it might be a wifi driver, a video card driver, etc... do you have any weird goofy hardware connected? unplug all externals and reboot. do you have a disc in the DVD player or a USB key plugged it when booting?

My computer is still running this morning. I don't think Driver verifier will work here, because my system ONLY crashes when I first turn it on for the day. No crashes after that during operation. That means reboots wont crash. Also if I turn off the computer for 2-5 minutes no crash. However, if I leave the computer off for say 24 hours, then turn it on it will do the crash. Seeing how I did a reboot to enable Driver Verifier, I'm not so optimistic on this one

It seems whatever causes the crash Windows disables after the automatic power off? I am completely stumped.

I took out the disc reader, all internal drives except for main, no USB devices are connected..