BSOD BugcheckCode 313

Question

Hi there!

I made a post here 3 months ago after my PC had crashed twice while gaming, one week apart. I updated all my drivers, did a memory test that came back without issues and then my PC have been working without issue since then. Until tonight that is.

Crashed while I was just browsing the internet, no gaming or anything. The error it gave me is BugcheckCode 313.

Here is the minidump file: https://drive.google.com/file/d/1IRVudF7eh1oPWVyKSYH5ZlHhewisGvxK/view?usp=sharing

After the crash I did a /sfc scannow and it found some corrupt files that it repaired. The files in question were:

BthA2dp.sys

bthmodem.sys

No idea if they could have been responsible for the crash.

I checked the minidump file and it says this:

SYMBOL_NAME:  nt!KiProcessExpiredTimerList+505

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

IMAGE_VERSION:  10.0.26100.8655

STACK_COMMAND: .process /r /p 0xfffff80484bcef00; .thread /r /p 0xffffe58b226ed040 ; kb

BUCKET_ID_FUNC_OFFSET:  505

FAILURE_BUCKET_ID:  0x139_3_CORRUPT_LIST_ENTRY_KTIMER_LIST_CORRUPTION_nt!KiProcessExpiredTimerList

OSPLATFORM_TYPE:  x64

Answer 1

Hi Axel,

BugcheckCode 313 usually means 0x139 KERNEL_SECURITY_CHECK_FAILURE.

Your dump shows:

CORRUPT_LIST_ENTRY_KTIMER_LIST_CORRUPTION

This usually does not mean ntkrnlmp.exe is the real cause. It more often points to a driver corrupting memory before the crash.

Since SFC already repaired files, please restart and monitor first. If it happens again, please provide your PC/laptop model or motherboard model, and I can help you find the correct chipset, GPU, network and storage drivers.

Also, temporarily disable any overclock/XMP or hardware monitoring/RGB tools for testing.

If another BSOD happens, please upload the new minidump file as well, so we can compare it with this one.

Answer 2

Bugcheck 0x139 (313 decimal) corresponds to KERNEL_SECURITY_CHECK_FAILURE, which indicates that a kernel component detected corruption of a critical data structure (for example, a corrupted list entry or stack-based buffer overrun). In practice this is usually caused by:

• Faulty or buggy third‑party drivers (very common)
• Less commonly, hardware issues (RAM, CPU, motherboard), but your previous memory test and long period of stability make drivers more likely

Because the crash occurred while only browsing and SFC reported corruption in Bluetooth stack drivers (BthA2dp.sys, bthmodem.sys) and repaired them, it is plausible that:

• The original crash was triggered by a driver or memory corruption, and
• The Bluetooth driver files on disk were also corrupted and have now been repaired by SFC.

However, SFC alone does not identify the exact driver that caused the bugcheck. The usual pattern in similar BSOD cases in the provided context is that stability is restored after addressing problematic vendor software/drivers or firmware:

• Removing or disabling OEM tuning/utility software that manipulates power/clock/driver behavior (for example, ASUS Armory Crate in one case) resolved repeated BSODs.
• Updating system firmware/BIOS resolved repeated ntkrnlmp.exe BSODs in another case.
• Disabling a problematic vendor service/driver (for example, AMD Crash Defender service) resolved KERNEL_SECURITY_CHECK_FAILURE crashes.

Actionable steps based on those patterns:

1. Ensure all OEM utilities that control performance, overclocking, or device behavior are either fully updated or temporarily uninstalled/disabled to test stability.
2. Update motherboard BIOS/UEFI and chipset drivers from the system or motherboard manufacturer.
3. Update Bluetooth, Wi‑Fi, GPU, and storage drivers directly from the hardware/OEM vendor.
4. If crashes continue, use Driver Verifier (with a restore point created first) to stress non‑Microsoft drivers and identify a faulty one, as was done in the similar KERNEL_SECURITY_CHECK_FAILURE case in the context.

If, after these steps, no further BSODs occur, the most likely cause was a transient or driver‑related corruption that has been corrected by SFC and driver/firmware updates.

---

References:

• Kernel_Security_Error BSOD. Driver Verifier causing bootloop. - Microsoft Q&A
• BSODs caused by ntkrnlmp.exe - Microsoft Q&A
• Please check my minidumps, BSOD and shutdowns - Microsoft Q&A