The computer has rebooted from a bugcheck. The bugcheck was: 0x000000c2

sittingpilgrim · Oct 21, 2022

Couple of BSOD crashes this morning.

After the first, I ran the V2 Log Collector again - here are the results. At the end of this first run, system crashed again.

Immediately after rebooting, I ran the log collector again (no crash). Results from second run.

sittingpilgrim · Oct 21, 2022

Called

chkdsk /b /v C:

from admin prompt, rebooted, and let it run

Ran the V2 Log Collector again

sittingpilgrim · Oct 21, 2022

Crashed again, and then again while posting to this forum

V2 logs from after the initial crash

philc43 · Oct 21, 2022

Has this suddenly started to give more BSOD crashes or is it about the same as you had before you swapped the memory?

If it is crashing more I would start in safe mode and see if it is stable. Safe mode does not load 3rd party drivers and therefore if it continues to crash in safe mode we can deduce that it is a hardware problem.

Boot to Safe Mode in Windows 11

This tutorial will show you how to boot Windows 11 into normal mode, Safe Mode, Safe Mode with Networking, or Safe Mode with Command Prompt. Safe mode starts Windows in a basic state, using a limited set of files and drivers. If a problem doesn't happen in safe mode, this means that default...

www.elevenforum.com

I would also run another memtest86 to check you still have no errors.

sittingpilgrim · Oct 21, 2022

Seems to be more crashes, but can be stable for several hours. I haven't figured out what combination of active software increases the frequency.

I disabled the Intel Driver and Support Assistant Tray, which I had recently installed when trying to get all my drivers up-to-date. I will probably uninstall it, as I did not find it useful. I also disabled the startup utility BrCcBoot, which is a printer utility that I rarely use. And also HPNotifications, which isn't doing anything for me.

I'll try the Safe Mode with Networking soon.

sittingpilgrim · Oct 25, 2022

Ran the machine in Safe Mode (didn't get networking, even though I chose that option) for an hour or so this morning. No major problems, but none of the MS 365 programs (Word, Outlook, etc) would run. Ran almost everything else in an attempt to stress the system.

Upon restart, however, I got the BSOD, but with a new error -
Stop Code: DRIVER_UNLOADED_WITHOUT_CANCELING_PENDING_OPERATIONS
what failed: Netwtw06.sys

(previously it had always been stop code BAD_POOL_CALLER)

The bugcheck read: The computer has rebooted from a bugcheck. The bugcheck was: 0x000000ce (0xfffff80155bf64b0, 0x0000000000000010, 0xfffff80155bf64b0, 0x0000000000000002). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: 14904809-b887-402f-ae4a-c46165841fb4.

I've saved the new V2 Log Collector

philc43 · Oct 25, 2022

I'm away at the moment and can't access my debugging tools. Not sure if that latest crash is connected but it is the Intel network driver. You can check and update it if there is a newer one.

sittingpilgrim · Oct 25, 2022

~~I'll look into updating the driver.~~ Update was successful

In the meantime, I've turned off wifi on my machine as I am normally hard-wired to the router.

sittingpilgrim · Oct 25, 2022

Crashed again (BAD_POOL_CALLER), so that wasn't it.

sittingpilgrim · Oct 27, 2022

Any advice on doing a clean install of Windows 11?

Coolmistry · Oct 27, 2022

Try off 'Turn on fast Start-up' in Windows > Power Option! try reboot and check event viewer after reboot.

sittingpilgrim · Oct 28, 2022

Changing the power settings did not eliminate the BSOD

xaamooh · May 10, 2023

I know this is an old thread, but I would like to share my knowledge about this.

I followed this steps to get to the root cause of the problem:

Follow instructions (step 1-3) on:

Code:

https://learn.microsoft.com/en-us/windows-hardware/drivers/download-the-wdk

Open command-shell (cmd) with admin rights

Change directory to:

Code:

C:\Program Files (x86)\Windows Kits\10\Debuggers\x64\

Open event viewer > Windows Logs > System > Actions > Filter Current Log > Event sources: BugCheck
Copy dump path "A dump was saved in: <dump-path>"
Execute in console:
Code:
```
dumpchk.exe path-to-dump
```
In the last lines you will see the root cause:
1. PROCESS_NAME the program which caused the crash
2. IMAGE_NAME the module which caused the crash
3. Arg1 - Arg4: the reason why Windows decided to stop working

The computer has rebooted from a bugcheck. The bugcheck was: 0x000000c2

Member

My Computer

Member

My Computer

Member

My Computer

BSOD Analyst

My Computers

Member

My Computer

Member

My Computer

BSOD Analyst

My Computers

Member

My Computer

Member

My Computer

Member

My Computer

Well-known member

My Computer

Member

My Computer

New member

My Computer

Similar threads