Windows 10: BSOD Unexpected_kernel_mode_trap

Hello everyone,

First time posting here and I am completely lost on what to do. I have tried everything I could think of to fix this issue and have not been able to find a solution. Hoping someone here can help. I have been getting random BSOD's for a few months now. I have installed Windows multiple times and it still happens. I will even get a BSOD in safe mode with networking so I am unsure what is causing the issue. I have attached the logs from the few most recent BSOD's. Any help is greatly appreciated.
Attachment 75993

:)

 

BSOD - KMODE_EXCEPTION_NOT_HANDLED

Also, the most recent BSOD displayed a new error message: UNEXPECTED_KERNEL_MODE_TRAP

 

BSOD: UNEXPECTED_KERNEL_MODE_TRAP

I keep getting this blue screen at random times(sometimes multiple times a day), and I sincerely have no idea what to do with it. I have run memcheck and dskchk and got no errors.

I have seen some posts saying it might be some driver, but I'd like some help.

Here is the dump file.

 

I forgot to mention I am running Windows 10 Pro on a Lenovo ThinkPad E450 with an Intel i5-5200u with 4 GB of RAM.

 

Please upload a new zip file, the attached zip file is empty

 

Everytime I run the dm log collector the zip file comes back empty. Is there something I am doing wrong or another way I can upload the files that you need?

 

Try running the .bat version of the DM Log Collector, right click the file and choose to run as administrator.
Attachment 76009

 

Thank you that solved the issue. As such here is the updated file.

 

There are quite some causes for this particular crash, but there doesn't look to be a clear cause for me.
Assuming your laptop has been properly configured by lenovo + you don't have any 3rd party protection software & no backup software we can skip a lot of possible causes.
Below is a list of the usual causes that would be left over, lets start with the drivers *Smile

• Memory corruption, this is a generic definition of things that can cause memory corruption: drivers passing bad stuff to the memory, the memory itself is bad, the hard drive is bad, there is a problem with the vram, etc.
• Hardware (memory in particular)
• Device drivers
• SCSI/network/BIOS updates needed

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.

Some windows drivers are blamed in a few crashes, but that usually means that a 3rd party driver is actually the cause.
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.

 

Every time I try to run the driver verifier, I get a BSOD before I can even get into Windows. After that I cannot get the computer to boot into windows and have to do a system restore to my last restore point. The error code says system_service_exception.

 

Do you have dumps in %systemroot%\minidump from when your system crashed when running driver verifier?
If you do, run the .bat file again and upload a new zip file.

 

I can't get either the .bat or the .exe to put files into the zip. I am running the .bat as administrator but it still leaves an empty file. If I run it without being an admin it puts info into the file but not the logs. Any advice?

 

I at least would like to have the dumps, select the dumps in %systemroot%\minidump > right click > send to > compressed (zipped) folder and upload the zip file.

 

I was finally able to get the collector to pull the files.

 

2 of the 6 crashes are caused by driver verifier flagging a driver from Webroot Security.
The recommended thing to do is to remove 3rd party AV, not AM, using the uninstaller that the company provides and use Windows Defender as alternative while troubleshooting.
After removing see how it goes and report back *Smile
Code: ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 3B, {80000003, fffff8013c14ec18, ffffd00020a0c260, 0} *** WARNING: Unable to verify timestamp for WRkrn.sys *** ERROR: Module load completed but symbols could not be loaded for WRkrn.sys Probably caused by : WRkrn.sys ( WRkrn+4043 )[/quote]