My PC crashes. Minidump tells A story I don't understand?

Question

My PC has started to crash more frequently.

I have already written something previously and at great length with a lot information. However, what I tried to post, got taken down before it even got posted.

So I am scared to write anything. I don't want to violate any terms of agreement.

Info on things I've done and not in that order:

Reinstalled a bunch of non-windows drivers. GPU included (RTX 2080)

SFC - some issues, got resolved

DISM - did its thing, didn't help.

MemTest86 - no errors

Checked for BIOS update - ok

And generated lots of mini dumps.

Latest Minidumps: https://1drv.ms/f/c/b5c719ec5f6f158a/IgDJAmbAX86mRYsQSU7nwOc4AZUW6XAHOJmiHZRI4MO_nUk?e=WueiS8

Latest Kernel Dumps: https://1drv.ms/f/c/b5c719ec5f6f158a/IgDG_qS568vOR6OJaLkizSflASRIFt7Nj25GCLUZAZqML7w?e=8hl8YF

Answer 1

If the BSOD occurs again, check if a new minidump file has been generated.

Answer 2

An alternative to download and install the drivers and update the BIOS when necessary is to go directly to the manufacturer's website and download there.

I'm glad the problem has been solved, if you wish you can mark a solved answer, this way it will help other users who have the same problem.

Answer 3

Hi Shawn,

The following is written by CP so it makes it better to understand, this is from your last dump listed, it is a little long but hopefully helps you. I also have a script which will tell you all your hardware so it easy to post here, let me know if you want to use it.

Thanks for sharing the minidump. I’ve reviewed the crash details, and here’s what it’s telling us in plain terms.

What the crash means

Your system hit a SYSTEM_SERVICE_EXCEPTION (0x3B) caused by an access violation (0xC0000005) inside the Windows kernel. The faulting instruction was inside:

nt!KeRemoveQueueEx

This is a core Windows routine used by worker threads inside svchost.exe. When a crash happens here, it does not mean Windows or svchost.exe is broken. Instead, it almost always means:

A third‑party driver corrupted memory earlier, and Windows only crashed later when it tried to use that corrupted data.

This is why the crash appears to come from the kernel — it’s a symptom, not the root cause.

What typically causes this type of crash

Crashes in KeRemoveQueueEx are strongly associated with:

• Outdated or unstable GPU drivers
• USB / Bluetooth / audio drivers (headset dongles, gaming audio software, etc.)
• Storage drivers (NVMe/SATA)
• Antivirus, anti‑cheat, or monitoring drivers
• Less commonly: faulty RAM

Any of these can write invalid data into kernel memory, and the corruption only becomes visible later inside a Windows worker thread.

Recommended next steps

Here are the steps most likely to identify or resolve the issue:

1. Update major drivers manually

Please update these from the manufacturer’s website (not Windows Update):

• GPU (NVIDIA / AMD / Intel)
• Motherboard chipset drivers
• NVMe/SATA storage drivers
• USB, Bluetooth, and audio drivers

This resolves the majority of 0x3B memory‑corruption crashes.

2. Check for patterns

If the crashes happen during gaming, USB device use, audio playback, sleep/wake, etc., that points directly at the driver involved.

3. Run basic hardware checks

Just to rule out hardware:

• Memory test: Run mdsched.exe
• Disk check: Run chkdsk /scan on the system drive

4. (Optional) Use Driver Verifier

If you’re comfortable with advanced tools, you can enable Driver Verifier only for non‑Microsoft drivers. This forces the faulty driver to crash immediately and name itself, making the root cause clear.

Summary

Your crash is caused by kernel memory corruption, almost certainly from a third‑party driver. Updating the major drivers listed above is the best first step, followed by hardware checks and (optionally) Driver Verifier if the issue continues.

Feel free to upload another dump if the problem repeats — we can look for patterns.

Answer 4

See if your computer is creating minidump files.

To find these files, this is the path "C:\Windows\Minidump".

First copy and paste all the minidump files you have to another folder and then zip it. Then upload the ZIP file to the cloud OneDrive.

Choose to share or right click and get the share link.

Please post the link to the ZIP file here so it can be reviewed.

Answer 5

If your PC is crashing frequently and you're seeing minidump files, these files can provide useful information about the crashes. A minidump contains data such as the crash code, the stack of the thread that was executing at the time of the crash, and a list of drivers loaded on the system. This information can help identify the cause of the crashes.

To analyze the minidump files, you can use tools like WinDbg or other debugging tools available from Microsoft. These tools can help you interpret the data in the minidump and potentially identify the problematic driver or application causing the crashes.

If you're unsure how to proceed, consider seeking help from forums or communities that specialize in crash analysis, as they can guide you through the process of interpreting the minidump files without violating any terms of agreement.

Additionally, if crashes started after a specific update or installation, it might be worth checking for driver updates or rolling back recent changes to see if that resolves the issue.

---

References:

• Crash Dump Analysis
• How to read the small memory dump file that is created by Windows if a crash occurs