Windows 10: BSOD kernel trap and wdf01000.sys

I tried to upgrade my ram to 32 with 2 new sticks and since then, even after removing the new sticks my pc won't stop getting BSOD, it stopped for a while when the ram was at 3333hz tried to get it back at 3600hz and the BSOD came back and this time even after I lowered it again it wont stop happeninggot these logsSourceWindowsSummaryHardware errorDate‎3/‎8/‎2023 3:04 AMStatusNot reportedDescriptionA problem with your hardware caused Windows to stop working correctly.Problem signatureProblem Event Name: LiveK

:)

 

wdf01000.sys and ntoskrnl.exe BSOD

I'm on Windows 10, 64bit

Basically, whenever I try to update my LPC controller through Device Manager, BSOD with WDF_VIOLATION occurs (culprit being wdf01000.sys)

So I try to use the driver verifier to see which driver is causing the BSOD, but then it causes BSOD (cultprit being ntoskrnl.exe)

Have no idea which driver is causing them

Please help!

Here are my list of drivers and system info: Microsoft OneDrive - Access files anywhere. Create docs with free Office Online.

 

unexpected kernel mode trap BSOD

Hi Adam,

Thank you for posting in Community.

We understand your concern and we will provide the information required to help you resolve the issue.

Before we proceed, I would like you to provide the information stated below:

Do you get the error message/BSOD only when you uninstall, reinstall, etc third party app?

The error UNEXPECTED_KERNEL_MODE_TRAP indicates that the Intel CPU generated a trap and the kernel failed to catch this trap. This trap could be a
bound trap (a trap the kernel is not permitted to catch) or a double fault (a fault that occurred while processing an earlier fault, which always results in a system failure).

To know the exact cause of the BSOD, I suggest that you provide the Dump files that were produced when the error occurred, or the Event ID from your Event Viewer which was recorded during the time of the crash.

Hope this helps

 

KMODE_EXCEPTION_NOT_HANDLED (wdf01000.sys)

Please run driver verifier again using the settings from the driver verifier tutorial in post KMODE_EXCEPTION_NOT_HANDLED (wdf01000.sys) - Windows 10 Forums