[SOLVED] [RECURRING WHEN IDLE] Unknown bugcheck code 0x5000000c

[MercyPrevails]

Hello! I'm just here seeking help, after finally exhausting the extent of my ability to research my own bugcheck code. I've done /sfc scannow, I've done DISM, I've done MemTest with no errors and good ram stats. Attached is the minidump of the unknown error, aside from today I also got this BSOD 3 days ago on the 15th.

If anyone can offer their knowledge, I'd greatly appreciate it!

011822-7890-01.dmp

Microsoft (R) Windows Debugger Version 10.0.22473.1005 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\011822-7890-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available


* Path validation summary **
Response Time (ms) Location
Deferred srv*
Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 19041 MP (12 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Machine Name:
Kernel base = 0xfffff8044c400000 PsLoadedModuleList = 0xfffff8044d02a2b0
Debug session time: Tue Jan 18 02:25:55.364 2022 (UTC - 5:00)
System Uptime: 1 days 23:36:10.938
Loading Kernel Symbols
...............................................................
................................................................
................................................................
......................................
Loading User Symbols
Loading unloaded module list
..................................................
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff8044c7f72e0 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffffde8c8278ce20=000000005000000c
0: kd> !analyze -v
***

• *
• Bugcheck Analysis *
• *

***

Unknown bugcheck code (5000000c)
Unknown bugcheck description
Arguments:
Arg1: 000000023bab66e0
Arg2: 0000000000000001
Arg3: fffff8044caadd63
Arg4: ffffde8c8278cf70

Debugging Details:
------------------


KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 1530

Key : Analysis.DebugAnalysisManager
Value: Create

Key : Analysis.Elapsed.mSec
Value: 1938

Key : Analysis.Init.CPU.mSec
Value: 218

Key : Analysis.Init.Elapsed.mSec
Value: 16115

Key : Analysis.Memory.CommitPeak.Mb
Value: 75


FILE_IN_CAB: 011822-7890-01.dmp

DUMP_FILE_ATTRIBUTES: 0x8
Kernel Generated Triage Dump

BUGCHECK_CODE: 5000000c

BUGCHECK_P1: 23bab66e0

BUGCHECK_P2: 1

BUGCHECK_P3: fffff8044caadd63

BUGCHECK_P4: ffffde8c8278cf70

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: MSIAfterburner

STACK_TEXT:
ffffde8c8278ce18 ffff9d80daa11ee7 : 000000005000000c 000000023bab66e0 0000000000000001 fffff8044caadd63 : nt!KeBugCheckEx
ffffde8c8278ce20 000000005000000c : 000000023bab66e0 0000000000000001 fffff8044caadd63 ffffde8c8278cf70 : 0xffff9d80daa11ee7 ffffde8c8278ce28 000000023bab66e0 : 0000000000000001 fffff8044caadd63 ffffde8c8278cf70 0000000000000002 : 0x5000000c ffffde8c8278ce30 0000000000000001 : fffff8044caadd63 ffffde8c8278cf70 0000000000000002 ffffde8c8278cec0 : 0x000000023bab66e0
ffffde8c8278ce38 fffff8044caadd63 : ffffde8c8278cf70 0000000000000002 ffffde8c8278cec0 ffff9d80daa14984 : 0x1
ffffde8c8278ce40 ffffde8c8278cf70 : 0000000000000002 ffffde8c8278cec0 ffff9d80daa14984 000000000010000f : nt!RtlpReadExtendedContext+0x3
ffffde8c8278ce48 0000000000000002 : ffffde8c8278cec0 ffff9d80daa14984 000000000010000f fffff38b163a7c10 : 0xffffde8c8278cf70 ffffde8c8278ce50 ffffde8c8278cec0 : ffff9d80daa14984 000000000010000f fffff38b163a7c10 fffff780000003d8 : 0x2 ffffde8c8278ce58 ffff9d80daa14984 : 000000000010000f fffff38b163a7c10 fffff780000003d8 0000000000000001 : 0xffffde8c8278cec0
ffffde8c8278ce60 000000000010000f : fffff38b163a7c10 fffff780000003d8 0000000000000001 0000000000000000 : 0xffff9d80daa14984 ffffde8c8278ce68 fffff38b163a7c10 : fffff780000003d8 0000000000000001 0000000000000000 0000000000000000 : 0x10000f ffffde8c8278ce70 fffff780000003d8 : 0000000000000001 0000000000000000 0000000000000000 fffff38b163a7710 : 0xfffff38b163a7c10
ffffde8c8278ce78 0000000000000001 : 0000000000000000 0000000000000000 fffff38b163a7710 ffff9d80daa135f3 : 0xfffff780000003d8 ffffde8c8278ce80 0000000000000000 : 0000000000000000 fffff38b163a7710 ffff9d80daa135f3 00000000`0010000f : 0x1


SYMBOL_NAME: nt!RtlpReadExtendedContext+3

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

IMAGE_VERSION: 10.0.19041.1466

STACK_COMMAND: .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET: 3

FAILURE_BUCKET_ID: 0x5000000C_nt!RtlpReadExtendedContext

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {655d267d-ed97-b686-7a29-33d72ed83766}

Followup: MachineOwner
---------

**note, this bugcheck says MSIafterburner, the other bugcheck doesn't and cites a totally different process

 

[Colif]

process named is victim anyway. IF it were MSI afterburner each time I would suggest updating GPU drivers.

1. Open Windows File Explore
   
2. Navigate to C:\Windows\Minidump
   
3. Copy the mini-dump files out onto your Desktop
   
4. Do not use Winzip, use the built in facility in Windows
   
5. Select those files on your Desktop, right click them and choose 'Send to' - Compressed (zipped) folder
   
6. Upload the zip file to the Cloud (OneDrive, DropBox . . . etc.)
   
7. Then post a link here to the zip file, so we can take a look for you . . .
   

what are specs of the PC?

 

[MercyPrevails]

process named is victim anyway. IF it were MSI afterburner each time I would suggest updating GPU drivers.

1. Open Windows File Explore
2. Navigate to C:\Windows\Minidump
3. Copy the mini-dump files out onto your Desktop
4. Do not use Winzip, use the built in facility in Windows
5. Select those files on your Desktop, right click them and choose 'Send to' - Compressed (zipped) folder
6. Upload the zip file to the Cloud (OneDrive, DropBox . . . etc.)
7. Then post a link here to the zip file, so we can take a look for you . . .

what are specs of the PC?

-----------------------------------
Here's the dropbox

Specs:

Processor: Intel® Core™ i7-8086K (6 x 4.00 GHz/12MB L3 Cache) - (Stable OC at 4.9GHz)
Motherboard: MSI Z370 GAMING PLUS LGA1151 -- Gb LAN, USB 3.1
Memory: 16 GB [8 GB x2] XPG Z1 ADATA DRAM DDR4-3000 Memory
Video Card: NVIDIA GeForce GTX 1060 - 3GB (OC with afterburner)
Power Supply: Thermaltake Smart 600W 80+ Gold Certified
Processor Cooling: DEEPCOOL Gammaxx GT RGB CPU Cooler - RGB
Primary Hard Drive: WDC WD10EZEX-08WN4A0 -- 32MB Cache, 7200RPM, 6.0Gb/s - Single 1TB Drive (Blue 1TB 2012)
M.2/PCI-E SSD Card: SAMSUNG (MZ-V7E500BW) 970 EVO SSD 500GB - Internal Solid State Drive with V-NAND
Secondary Hard Drive: 2 External USB HDDs (Unplugged)
Network Card: Onboard LAN Network (Gb or 10/100)
Operating System: Windows 10 Home - (64-bit)
WiFi Adapter: ASUS USB-AC51 AC600 Dual Band Wireless USB Adapter
SLI Bridge: None
Intel Optane Memory Accelerator?: No
----------------------
Power Watt Measurement: https://outervision.com/b/gzuDOm
Load Wattage: 344 W
Recommended UPS rating: 750 VA
Reccomended PSU Wattage: 394 W

 

[MercyPrevails]

process named is victim anyway. IF it were MSI afterburner each time I would suggest updating GPU drivers.

1. Open Windows File Explore
2. Navigate to C:\Windows\Minidump
3. Copy the mini-dump files out onto your Desktop
4. Do not use Winzip, use the built in facility in Windows
5. Select those files on your Desktop, right click them and choose 'Send to' - Compressed (zipped) folder
6. Upload the zip file to the Cloud (OneDrive, DropBox . . . etc.)
7. Then post a link here to the zip file, so we can take a look for you . . .

what are specs of the PC?

And another note, recently I clean installed my drivers, and I am currently running the latest drivers.

 

[gardenman]

Hi, I ran the dump file through the debugger and got the following information: https://jsfiddle.net/3g85s04b/show This link is for anyone wanting to help. You do not have to view it. It is safe to "run the fiddle" as the page asks.

File information:	011822-7890-01.dmp (Jan 18 2022 - 02:25:55)
Bugcheck:	BugCheck 5000000C, {23bab66e0, 1, fffff8044caadd63, ffffde8c8278cf70} (5000000C)
Probably caused by:	ntkrnlmp.exe (Process running at time of crash: MSIAfterburner)
Uptime:	1 Day(s), 23 Hour(s), 36 Min(s), and 10 Sec(s)

Comments:

• This is an unknown bugcheck.
• The overclocking driver "RTCore64.sys" was found on your system. (MSI Afterburner)
• The GPU tweaking driver "iomap64.sys" was found on your system. (AI Suite or GPU Tweak 2 or Armoury Crate)

Possible Motherboard page: https://www.msi.com/Motherboard/z370-gaming-plus

This information can be used by others to help you. Someone else will post with more information. Please wait for additional answers. Good luck.

 

[Colif]

So dump text isn't very revealing

Its possibly one of these drivers, since anything prior to June 2015 may not be a win 10 driver (it might be, all it takes is company sending a driver to Microsoft for testing and digital signature.

Feb 15 2010	vrtaucbl.sys	Virtual Audio Cable (NTONYX Ltd.)
Jul 01 2010	ScreamingBAudio64.sys	Screaming Bee Audio driver http://www.screamingbee.com/
May 31 2011	VCam_WDM.sys	VCam SDK WDM driver
Aug 22 2012	AsIO.sys	ASUS Input Output driver http://www.asus.com/
Dec 25 2012	ambakdrv.sys	Aomei driver (Aomei Technology Co)
Dec 25 2012	ammntdrv.sys	AOMEI Backupper driver (Aomei Technology Co.) http://www.aomeitech.com/
Dec 29 2012	speedfan.sys	SpeedFan http://www.almico.com/sfdownload.php
May 05 2013	ScpVBus.sys	Scarlet.Crush Productions Scp Dual Shock 3 Virtual Bus driver http://forums.pcsx2.net/
Dec 04 2013	mcaudrv_x64.sys	ManyCam Virtual Microphone driver
Aug 14 2014	vbaudio_cable64_win7.sys	VB Virtual Audio Device driver https://www.vb-audio.com/

Drivers I know that are probably okay above
Asus Input Output driver (common on every Asus mb)
Speedfan (shame they don't update this anymore)
Scarlet crush (drivers for Gaming controllers) - I have seen this cause BSOD before though.

Its possible GPU drivers were the cause, even though you have the newest NVIDIA ones
Try running DDU in safe mode and reinstall them - https://forums.tomshardware.com/faq...n-install-of-your-video-card-drivers.2402269/

its difficult to say when I don't know what BSOD description is. Dumps blame a win 8 driver but that is wrong, or should I say, needs expansion as it can be a win 10 or 11 driver too, description just needs an update. Hardly important really. It is also not something I can rely one.

 

[MercyPrevails]

So dump text isn't very revealing

Its possibly one of these drivers, since anything prior to June 2015 may not be a win 10 driver (it might be, all it takes is company sending a driver to Microsoft for testing and digital signature.

Feb 15 2010	vrtaucbl.sys	Virtual Audio Cable (NTONYX Ltd.)
Jul 01 2010	ScreamingBAudio64.sys	Screaming Bee Audio driver http://www.screamingbee.com/
May 31 2011	VCam_WDM.sys	VCam SDK WDM driver
Aug 22 2012	AsIO.sys	ASUS Input Output driver http://www.asus.com/
Dec 25 2012	ambakdrv.sys	Aomei driver (Aomei Technology Co)
Dec 25 2012	ammntdrv.sys	AOMEI Backupper driver (Aomei Technology Co.) http://www.aomeitech.com/
Dec 29 2012	speedfan.sys	SpeedFan http://www.almico.com/sfdownload.php
May 05 2013	ScpVBus.sys	Scarlet.Crush Productions Scp Dual Shock 3 Virtual Bus driver http://forums.pcsx2.net/
Dec 04 2013	mcaudrv_x64.sys	ManyCam Virtual Microphone driver
Aug 14 2014	vbaudio_cable64_win7.sys	VB Virtual Audio Device driver https://www.vb-audio.com/

Drivers I know that are probably okay above
Asus Input Output driver (common on every Asus mb)
Speedfan (shame they don't update this anymore)
Scarlet crush (drivers for Gaming controllers) - I have seen this cause BSOD before though.

Its possible GPU drivers were the cause, even though you have the newest NVIDIA ones
Try running DDU in safe mode and reinstall them - https://forums.tomshardware.com/faq...n-install-of-your-video-card-drivers.2402269/

its difficult to say when I don't know what BSOD description is. Dumps blame a win 8 driver but that is wrong, or should I say, needs expansion as it can be a win 10 or 11 driver too, description just needs an update. Hardly important really. It is also not something I can rely one.

I'll do that again when I get home, thanks so much for your contribution. I have another dump of the same issue if that helps, but there was a different 'victim process' as well as different arguments I believe.

I also wanna note, that the only two non-used or non-recognized drivers that most likely weren't updated by their devs or were installed long ago are the ManyCam one, or the VCam_WDM.sys driver.

Thanks.

 

[Colif]

Are you seeing the BSOD on screen? Curious if it has a description since its so new, its not on web yet. Often they have a code like 0x5000000c but also a word description such as "WHEA error" (just an example) which might give me an idea where to start looking.

 

[MercyPrevails]

Are you seeing the BSOD on screen? Curious if it has a description since its so new, its not on web yet. Often they have a code like 0x5000000c but also a word description such as "WHEA error" (just an example) which might give me an idea where to start looking.

I did see it on screen when it happened, but I cannot recall what it said unfortunately. If or when it happens again, I will note the screen.

 

[Colif]

i can't do anything until you show us dump files so no point bumping posts (and you just get in trouble doing it)

its possible error code is HAL Initialization failed which could be a hardware or software error
https://docs.microsoft.com/en-us/wi...hal-initialization-failed?redirectedfrom=MSDN that doesn't tell me anything either.

seems it can be a driver error.

did you change any of the drivers I mentioned?

 

[MercyPrevails]

i can't do anything until you show us dump files so no point bumping posts (and you just get in trouble doing it)

its possible error code is HAL Initialization failed which could be a hardware or software error
https://docs.microsoft.com/en-us/wi...hal-initialization-failed?redirectedfrom=MSDN that doesn't tell me anything either.

seems it can be a driver error.

did you change any of the drivers I mentioned?

-----------------------------------
Here's the dropbox

So that first dump file I've linked doesn't offer much, I need to get a second is what you're requesting?

And yes, the two I'm certain I don't recognize are gone from my machine.

 

[Colif]

only if you get another BSOD. If you aren't crashing, it could just be a rare occurrence.

Don't try to make PC crash.