Windows 10: KMODE_EXCEPTION_NOT_HANDLED (wdf01000.sys)

Got a blue screen while using discord, here's the attachment

:)

 

Windows 10 Clean Install - Microsoft-Windows-Kernel-Power Event ID: 41 BugcheckCode 30

Memtest passed without error.

I tried nirsoft BlueScreenView and it showed some interesting things:

- Most recent crash caused by driver: intelppm.sys (as well as one earlier crash)

- DRIVER_VERIFIER_DETECTED_VIOLATION: atikmdag.sys

- Two other KMODE_EXCEPTION_NOT_HANDLED: Wdf01000.sys

What would you recommend as a next step?

 

Nokia E71 driver problem

1. Uninstalled PC Suite, reinstalled PC Suite 7.1.18.0. Still has "Nokie E71 USB Phone Parent" error.



2. On PC Suite 7.1.18.0.Removed wdf01000.sys. Rebooted. Plugged in E71. No rebuilding of wdf01000.sys. Still has "Nokie E71 USB Phone Parent" error in device manager. After few minutes, went into windows/system32/drivers, no wdf01000.sys!



I give up!

 

Hi Shirubidu,

Reinstall the IRST drivers.



Please uninstall everything of Nvidia using Display Driver Uninstaller and install new drivers from Nvidia. Be sure the clean install box is checked and only install the Graphics driver and the PhysX driver, you can use this tutorial for the installation part *Arrow NVIDIA Drivers - Avoid Problems - Windows 7 Help Forums

 

I reinstalled the IRST drivers and unistalled everything from Nvidia using DDU, and performed a clean install following the tutorial.
10 mins ago got another BSOD, now while watching a video, here's the attachment

 

Are you cleaning up your disk to reserve space?

 

I only defrag my disks just to keep them optimized, these are my current drives atm:

Left: SSD and the right: HDD

 

I was wondering it, because the dump file that is in the previous logs is not in the newest logs. Not a problem though *Smile






Diagnostic Test

DRIVER VERIFIER


Warning Please make a backup of your important files and get your rescue media or create one.
Please create a restore point.
Please follow this tutorial to run driver verifier.

Driver verifier stresses your drivers and will crash your pc if any driver fails due to a violation.

Driver verifier should be performed for a max of 48 hours, or when you have a bluescreen, whatever comes first.

If driver verifier has found a violation and you can't get back into windows normally, try to boot into safe mode and reset in safe mode driver verifier, or in the troubleshooting options open command prompt and type verifier /reset.



Note Your system will act very sluggishly while driver verifier is enabled, this is normal as your drivers will be being subjected to heavy testing in order to make them crash.

 

24h with verifier enabled, either idling or watching videos/playing games, still no BSOD at all

But i found something intruiging:
STRIX-GTX980-DC2OC-4GD5 Driver & Tools | Graphics Cards | ASUS USA


This is my GPU, and i noticed that has a recent update (21/1/2018) as i always downloaded my GPU driver directly from the Nvidia website. I also never used that BIOS & Firmware update for it as well.

Can this be the solution for my problem ?

 

I don't think so, because when I suggested to reinstall the drivers using new drivers the 390.85 version was already available since the beginning of this month. You should already have it installed if you followed the suggestion I posted earlier, or at least updated the NVIDIA display driver.

 

I had the 390.65 version before the first BSOD and i followed your instructions on unistalling and re-installing, i also did a memtest last week using the version provided in this forum and i had 8 passes 0 errors..
But still, 48h with driver verifier on and not a single BSOD

 

Please check the following in driver verifier and run driver verifier for 48h.

• Special Pool
• Force IRQL checking
• Pool Tracking
• Deadlock Detection
• Security Checks
• Miscellaneous Checks
• Power framework delay fuzzing
• DDI compliance checking

 

quick question, is there a way to keep driver verifier enabled even if I shut down my computer so it keeps checking from the last point?

 

Yes and no, yes driver verifier stays enabled so long as you don't reset the settings, but I don't think driver verifier keeps progress since there isn't really 'progress'.
Drivers are designed to do things over and over again, possibly in multiple ways. When you shut down the computer, the driver doesn't save its progress, it finishes what it started and then stops. When the system starts up, the driver executes its task as soon as it's called, not knowing where it stopped since there's no need to know.

 

I was just thinking about that because it's too much power consuming, since my computer is a desktop, and I'm dealing with this problem for almost a year now.
my motherboard is 2 years old, and the latest drivers of Intel (Rapid Storage, Management and Chipset) are from late 2016/early 2017, never understood the difference between manufacturer drivers and retailers drivers, like msi or gigabite but I always sticked to the retailer ones, maybe that's bad and causes some weird corruptions as it becomes outdated compared to the OS