Lately, I've been experiencing numerous Windows 11 BSOD crashes reporting KERNEL_SECURITY_CHECK_FAILURE while playing games with my Xbox Elite Series 2 controller. Analyzing the memory dump in WhoCrashed reports this:
Google searches referred me to ReWASD as the potential perpetrator. Independently running the minidump through ChatGPT has also implicated ReWASD with the following response:
This suggests a buffer-management bug or compatibility issue involving reWASD and the Xbox controller stack. The minidump cannot prove whether it was a double release, a timing issue, or earlier corruption, but it gives a clear troubleshooting target.
This has been occurring across multiple versions of ReWASD. I have previously attempted to delete/reboot/reinstall the software. Please see attached outputs for details.
| Crash dump file: | C:\Windows\MEMORY.DMP (Kernel memory dump) |
| Uptime: | 01:46:35 (hh:mm:ss) |
| Bugcheck code: | 0x139(0x3, 0xFFFFC48D3D7CDFD0, 0xFFFFC48D3D7CDF28, 0x0) |
| Bugcheck name: | KERNEL_SECURITY_CHECK_FAILURE |
| Driver or module in which error occurred: | wjl19drv.sys (wjl19drv+0x15430) |
| File path: | C:\WINDOWS\System32\drivers\wjl19drv.sys |
| Description: | System Driver |
| Bug check description: | The kernel has detected the corruption of a critical data structure. |
| Analysis: | This particular bugcheck may be caused by malware or a security product that does not follow programming guidelines. This can also be caused by memory corruption. This is possibly a software problem. There is a possibility that this is caused by memory corruption. Memory corruption can be caused by a faulty driver, faulty RAM, overheating and more. Read this article on memory corruption. Read this article on thermal issues A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: wjl19drv.sys (System Driver, ). |
| Google query: | wjl19drv KERNEL_SECURITY_CHECK_FAILURE |
Google searches referred me to ReWASD as the potential perpetrator. Independently running the minidump through ChatGPT has also implicated ReWASD with the following response:
Yes—the minidump strongly implicates reWASD’s driver while handling Xbox controller traffic.
With Microsoft’s debugging symbols loaded, I found:
With Microsoft’s debugging symbols loaded, I found:
- The active process was jlserv.exe, identified locally as reWASD Mapping Service.
- wjl19drv.sys called NdisFreeNetBufferList to free a buffer.
- Windows detected corrupted linked-list bookkeeping during that operation.
- Microsoft’s Xbox Game Input Protocol driver (xboxgip.sys) appears directly in the same call chain.
This suggests a buffer-management bug or compatibility issue involving reWASD and the Xbox controller stack. The minidump cannot prove whether it was a double release, a timing issue, or earlier corruption, but it gives a clear troubleshooting target.
This has been occurring across multiple versions of ReWASD. I have previously attempted to delete/reboot/reinstall the software. Please see attached outputs for details.