Windows 10: BSOD playing Overwatch; Now stuck in boot loop with WDF01000.sys fail

Hello TenForums,

I was hoping someone could address an issue I was having today.

The issues cropped up a month ago or so with a few BSOD detailing a Security_Kernel_Error. Then it went silent for awhile.

However, just last night while playing Overwatch I got a BSOD, or orange screen of death rather, that said "WHEA_UNCONTROLLABLE_ERROR"

Ever since, my computer was stuck in a never ending restart loop each ending in a BSOD saying "BAD_POOL_CALLER" "What failed: Wdf01000.sys" until I entered safe mode and now it is usable, but only during safe mode.

Hopefully the attached logs can help you find whats wrong with my computer as it is very stressful! Thank you very much for further feedback.

Attachment 110481

EDIT: I looked through the logs and saw Ilok driver as one of the last drivers loaded so I uninstalled it and took it out of my usb slot for now and am still getting crashes but now it says "SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION", "Driver_Verifier_Detected_Violation", and "BAD_POOL_CALLER" on the BSOD. I will attach my new logs here.

Attachment 110485

:)

 

Windows 10 Error

Windows 10 fails frequently with different errors, could anyone help me with this.

System restarts after the fail.

Stop code:

-Kernal Security Check Failure,

-Driver IRQL not Less or Equal, What failed: Wdf01000.sys,

-System Thread Exception not Handled, what failed: UsbHub3.sys

 

Stopcode Loop NTFS FILE SYSTEM to FAT FILE SYSTEM

Hi

Also stuck In this loop,

NTFS.and FAT FILE SYS

Starts auto repair but it keeps failing,so can't get to start up...

Any ideas?

Jeferis

 

The 11/18 3:44, 3:55 and 3:56 dumps are empty, 0 length.

Why are you running with Driver Verifier enabled? That's only for use for short periods of time to look for problems with device drivers. Please follow the directions here to turn it off, rthen run and see if still problems or not:
===================================================
Driver Verifier is a diagnostic tool built into Windows 10, it is designed to verify both native Microsoft drivers and third party drivers. Driver Verifier's verification process involves putting heavy stress on drivers with the intention of making bad, outdated, incompatible or misbehaving drivers fail. The required result is a BSOD (Blue Screen of Death) which will generate a crash dump for debugging purposes.
Machines exposed to Driver Verifier will run very sluggishly due to the stress being applied to the drivers.

Driver Verifier - Enable and Disable in Windows 10

Warning:
It is not advised to run Driver Verifier for more than 48 hours at a time. Disable Driver Verifier after 48 hours or after receiving a BSOD, whichever happens soonest.

Always create a Restore Point prior to enabling Driver Verifier.

What we're looking for is a BSOD with a mini dump that will tell us what driver caused it.