My Computer has rebooted from a bugcheck

Question

The computer has rebooted from a bugcheck.

The bugcheck was: 0x000000c5 (0xffffe80092d39bb0, 0x0000000000000002, 0x0000000000000000, 0xfffff8021ecabb12). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 070624-21484-01.

the file i shared in https://1drv.ms/f/c/251d783eb317e50e/Epfb97Cb_udFgOJkCFRC0vMBaOkjPQMNuIcWZ9mDBd3B5w?e=EcWhFr

this is i got from bugchek anlysis

---

•                                                                         *
  

•                    Bugcheck Analysis                                    *
  

•                                                                         *
  

---

DRIVER_CORRUPTED_EXPOOL (c5)

An attempt was made to access a pageable (or completely invalid) address at an

interrupt request level (IRQL) that is too high. This is

caused by drivers that have corrupted the system pool. Run the driver

verifier against any new (or suspect) drivers, and if that doesn't turn up

the culprit, then use gflags to enable special pool.

Arguments:

Arg1: ffffe80092d39bb0, memory referenced

Arg2: 0000000000000002, IRQL

Arg3: 0000000000000000, value 0 = read operation, 1 = write operation

Arg4: fffff8021ecabb12, address which referenced memory

Debugging Details:

---

KEY_VALUES_STRING: 1

Key  : Analysis.CPU.mSec

Value: 1640

Key  : Analysis.Elapsed.mSec

Value: 2367

Key  : Analysis.IO.Other.Mb

Value: 0

Key  : Analysis.IO.Read.Mb

Value: 0

Key  : Analysis.IO.Write.Mb

Value: 0

Key  : Analysis.Init.CPU.mSec

Value: 671

Key  : Analysis.Init.Elapsed.mSec

Value: 52243

Key  : Analysis.Memory.CommitPeak.Mb

Value: 77

Key  : Bugcheck.Code.KiBugCheckData

Value: 0xc5

Key  : Bugcheck.Code.LegacyAPI

Value: 0xc5

Key  : Bugcheck.Code.TargetModel

Value: 0xc5

Key  : Failure.Bucket

Value: 0xC5_2_nt!ExDeferredFreePool

Key  : Failure.Hash

Value: {0e971f5b-bd0d-a80e-a2c0-cd331176cf49}

Key  : Hypervisor.Enlightenments.Value

Value: 17184

Key  : Hypervisor.Enlightenments.ValueHex

Value: 4320

Key  : Hypervisor.Flags.Value

Value: 17

Key  : Hypervisor.Flags.ValueHex

Value: 11

Key  : WER.OS.Branch

Value: winblue_ltsb_escrow

Key  : WER.OS.Version

Value: 8.1.9600.20666

BUGCHECK_CODE: c5

BUGCHECK_P1: ffffe80092d39bb0

BUGCHECK_P2: 2

BUGCHECK_P3: 0

BUGCHECK_P4: fffff8021ecabb12

FILE_IN_CAB: MEMORY.DMP

VIRTUAL_MACHINE: VMware

PROCESS_NAME: System

TRAP_FRAME: ffffd000aec3d7a0 -- (.trap 0xffffd000aec3d7a0)

NOTE: The trap frame does not contain all registers.

Some register values may be zeroed or incorrect.

rax=ffffe80092d39bb0 rbx=0000000000000000 rcx=ffffd000a6e00160

rdx=ffffe80092d39bb0 rsi=0000000000000000 rdi=0000000000000000

rip=fffff8021ecabb12 rsp=ffffd000aec3d930 rbp=0000000000000009

r8=ffffe00073cf66d0 r9=0000000000000000 r10=0000000000000001

r11=0000000000000000 r12=0000000000000000 r13=0000000000000000

r14=0000000000000000 r15=0000000000000000

iopl=0 nv up ei ng nz na pe nc

nt!ExDeferredFreePool+0x102:

fffff8021ecabb12 488b10 mov rdx,qword ptr [rax] ds:ffffe80092d39bb0=????????????????

Resetting default scope

STACK_TEXT:

ffffd000aec3d658 fffff8021eb6d3e9 : 000000000000000a ffffe80092d39bb0 0000000000000002 0000000000000000 : nt!KeBugCheckEx

ffffd000aec3d660 fffff8021eb6a5a2 : ffffcc0d8787c6e2 0000000000000001 0000000000000200 fffff8021eaf5dbe : nt!KiBugCheckDispatch+0x69

ffffd000aec3d7a0 fffff8021ecabb12 : ffffe80193282010 fffff800e8afed11 000000000000122c 0000000000000000 : nt!KiPageFault+0x422

ffffd000aec3d930 fffff8021ecaa874 : ffffe0006fb993b0 ffffe00074979090 0000000074654e56 ffffd000a6e00000 : nt!ExDeferredFreePool+0x102

ffffd000aec3d9b0 fffff800ea34bad0 : fffff8021ecbb4c0 0000000000000000 ffff1eb100000000 ffffe00000000006 : nt!ExFreePoolWithTag+0x874

ffffd000aec3da50 fffff800ea34bb64 : 0000000000000a00 fffff800ea34f320 ffffe000749790a0 0000000000000a04 : vnetWFP+0x2ad0

ffffd000aec3da80 fffff800ea34b291 : 0000000000000a04 fffff800ea34f030 fffff80000000000 0000000000000006 : vnetWFP+0x2b64

ffffd000aec3dab0 fffff8021ea5ca90 : ffffe00074405160 0000000000000000 fffff800ea34b14c ffffe00000000004 : vnetWFP+0x2291

ffffd000aec3dae0 fffff8021ea5c63f : fffff8021ee7d978 fffff8021ea5ca10 ffffe0006d7c0880 0000000000000000 : nt!IopProcessWorkItem+0x80

ffffd000aec3db50 fffff8021eaed9f6 : 0000000000000000 fffff8021ecfe180 0000000000000080 ffffe0006c4a9040 : nt!ExpWorkerThread+0x69f

ffffd000aec3dc00 fffff8021eb645e6 : fffff8021ecfe180 ffffe0006d7c0880 fffff8021ed65a40 0000000000000000 : nt!PspSystemThreadStartup+0x18a

ffffd000aec3dc60 0000000000000000 : ffffd000aec3e000 ffffd000aec38000 0000000000000000 0000000000000000 : nt!KiStartSystemThread+0x16

SYMBOL_NAME: nt!ExDeferredFreePool+102

IMAGE_NAME: Pool_Corruption

MODULE_NAME: Pool_Corruption

STACK_COMMAND: .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET: 102

FAILURE_BUCKET_ID: 0xC5_2_nt!ExDeferredFreePool

OS_VERSION: 8.1.9600.20666

BUILDLAB_STR: winblue_ltsb_escrow

OSPLATFORM_TYPE: x64

OSNAME: Windows 8.1

FAILURE_ID_HASH: {0e971f5b-bd0d-a80e-a2c0-cd331176cf49}

Followup: Pool_corruption

Answer 1

Hello

The bugcheck code 0x000000c5 indicates an issue typically related to driver errors or hardware malfunctions. Here are some steps you can take to troubleshoot this problem:

Update your drivers: Ensure that all your device drivers, especially those related to storage and memory, are up to date.

Run a memory check: Use Windows Memory Diagnostic tool to check for any issues with your RAM.

Check for hardware issues: If you have recently added new hardware, ensure it is compatible and properly installed.

System Restore: If the issue started occurring recently, you can try performing a system restore to a point where the issue was not present.

Check for malware: Run a full system scan to ensure that your system is not infected with malware which could be causing the issue.

Windows Update: Make sure your system is up to date with the latest Windows patches and updates.

Analyze the dump file: The MEMORY.DMP file can be analyzed to get more details about the crash which can help in pinpointing the exact issue.

Get Started with Windows Debugging - Windows drivers | Microsoft Learn

 

Additionally, since the issue is occurring on a VMware virtual machine, checking VMware tools and settings might also be beneficial.

Answer 2

I have been dealing with non-stop issues for the past month and I am convinced this is on Microsoft's end. I've been trying to find a remedy for problem after problem when trying to play CS2. I have Microsoft Windows 11 Pro w/ Beta and after the latest update, nothing seems to want to work as I can't go playing 15 minutes without seeing some BSOD screen with different code errors. Seriously Microsoft, get your crap together as a billion dollar company, it is sad to see how awful you take care of customers.