Windows 10: BSOD UNEXPECTED_KERNAL_MODE_ TRAP Error: ks.sys

Hi,Lately I've been getting a lot of fast BSOD's constantly, and then my pc restarts. The screen is so fast I can barely see what it says, but I managed to take one photo of it. It says Stop code: UNEXPECTED_KERNEL_MODE_TRAP What failed: ks.sysIt's so annoying as it getting really constant, i get this problem several times a day.Here's a link to the last minidump files on my pc:https://www.dropbox.com/scl/fi/vuobr31lcilsopxtp1s4f/Minidump-files.zip?rlkey=81j5lk1pp6nutq14pkwql7a1l&st=yeoopmft&dl=0In case it's needed, my pc runs an AMD Ryzen 5900x, 32gb of 3200Mhz RAM, EVGA FTW3 207

:)

 

BSOD while using the internet. error (L1C63x64.sys)


Hi trainman81,

Welcome to the 10forums.

Daemon tools, Alcohol 120% and Power Archiver Pro uses SCSI Pass Through Direct (SPTD), which is a well known cause for BSOD's.
Please remove Daemon Tools and run the SPTD pass through remover.

1. Uninstall Daemon Tools
2. Download the SPTD standalone installer and follow these steps:
   • Double click the executable to open it
   • Click on the button shown below

If the button is grayed out, like in the image, there is no more SPTD installation on your system, and you can close the window


AVG is trying to request data from the internet, which is why the network driver is marked as the cause.
Code:

Code:

*** WARNING: Unable to verify timestamp for L1C63x64.sys *** ERROR: Module load completed but symbols could not be loaded for L1C63x64.sys 0: kd> lmvm L1C63x64 start             end                 module name fffff801`89700000 fffff801`89722000   L1C63x64 T (no symbols)                Loaded symbol image file: L1C63x64.sys     Image path: \SystemRoot\System32\drivers\L1C63x64.sys     Image name: L1C63x64.sys     Timestamp:        Mon Apr 01 05:15:17 2013 (5158FBC5)     CheckSum:         000245C4     ImageSize:        00022000     Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

AVG drivers that have been flagged
Code:

Code:

*** WARNING: Unable to verify timestamp for avgwfpa.sys *** ERROR: Module load completed but symbols could not be loaded for avgwfpa.sys *** WARNING: Unable to verify timestamp for avgfwd6a.sys *** ERROR: Module load completed but symbols could not be loaded for avgfwd6a.sys

Please uninstall AVG and see if it helps
Uninstall AVG | AVG
It is further recommended to check your Qualcomm network driver for updates, its driver is not supported for Windows 10.
Driver Reference Table - L1C63x64.sys

 

ks.sys BSOD dell built-in webcam

ok i think i kinda find how to fixed this

well at least the loop bsod everytime i plug the webcam usb or restart (while the usb plugged) stopped

i am not sure if this stable enough (random bsod)

after reading lots of bsod on net.. i found this post
http://www.sevenforums.com/bsod-help-support/156234-ks-sys-bsod-post1340079.html#post1340079

so culprit is between webcam creative driver and westerndigital mybook smartware

so i uninstall all webcam software (that packed with the dell driver installer) and then also uninstall wd smartware (also removing all things related to both that listen on uninstall program list)

reboot the system, then plug it... windows10 automatically install the driver, it showing up as correct device

just for be safe, i reboot once more...

and then re-install smartware (i know its **** and not needed)

so far no bsod

so for people having issue, and have both device

i suggest follow the step above

Just make sure let windows detect+install webcam first

before installing wd smartware

 

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