All Discussions > Steam Forums > Hardware and Operating Systems > Topic Details
Halal Poogie Meat 19 Aug @ 1:22am
CRITICAL PROCESS DIED 0xef bsod svchost.exe image name ntkrnlmp
i dont know what to do please help. Tried a DMIM or whatever cleanup in the command prompt and sv. i didnt do any safe boots yet though

CRITICAL_PROCESS_DIED (ef)
A critical system process died
Arguments:
Arg1: ffff9704a187e080, Process object or thread object
Arg2: 0000000000000000, If this is 0, a process died. If this is 1, a thread died.
Arg3: ffff9704a187e080, The process object that initiated the termination.
Arg4: 0000000000000000, Additional triage data.

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


KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 1875

Key : Analysis.Elapsed.mSec
Value: 3434

Key : Analysis.IO.Other.Mb
Value: 0

Key : Analysis.IO.Read.Mb
Value: 1

Key : Analysis.IO.Write.Mb
Value: 0

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

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

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

Key : Analysis.Version.DbgEng
Value: 10.0.27871.1001

Key : Analysis.Version.Description
Value: 10.2505.01.02 amd64fre

Key : Analysis.Version.Ext
Value: 1.2505.1.2

Key : Bugcheck.Code.LegacyAPI
Value: 0xef

Key : Bugcheck.Code.TargetModel
Value: 0xef

Key : CriticalProcessDied.ExceptionCode
Value: 0xa2ef2080

Key : CriticalProcessDied.Process
Value: svchost.exe

Key : Dump.Attributes.AsUlong
Value: 0x21808

Key : Dump.Attributes.DiagDataWrittenToHeader
Value: 1

Key : Dump.Attributes.ErrorCode
Value: 0x0

Key : Dump.Attributes.KernelGeneratedTriageDump
Value: 1

Key : Dump.Attributes.LastLine
Value: Dump completed successfully.

Key : Dump.Attributes.ProgressPercentage
Value: 0

Key : Failure.Bucket
Value: 0xEF_svchost.exe_BUGCHECK_CRITICAL_PROCESS_a2ef2080_nt!PspCatchCriticalBreak

Key : Failure.Hash
Value: {296df6bc-5186-c5df-a543-bddee77007a5}

Key : Hypervisor.Enlightenments.ValueHex
Value: 0x7417df84

Key : Hypervisor.Flags.AnyHypervisorPresent
Value: 1

Key : Hypervisor.Flags.ApicEnlightened
Value: 0

Key : Hypervisor.Flags.ApicVirtualizationAvailable
Value: 1

Key : Hypervisor.Flags.AsyncMemoryHint
Value: 0

Key : Hypervisor.Flags.CoreSchedulerRequested
Value: 0

Key : Hypervisor.Flags.CpuManager
Value: 1

Key : Hypervisor.Flags.DeprecateAutoEoi
Value: 1

Key : Hypervisor.Flags.DynamicCpuDisabled
Value: 1

Key : Hypervisor.Flags.Epf
Value: 0

Key : Hypervisor.Flags.ExtendedProcessorMasks
Value: 1

Key : Hypervisor.Flags.HardwareMbecAvailable
Value: 1

Key : Hypervisor.Flags.MaxBankNumber
Value: 0

Key : Hypervisor.Flags.MemoryZeroingControl
Value: 0

Key : Hypervisor.Flags.NoExtendedRangeFlush
Value: 0

Key : Hypervisor.Flags.NoNonArchCoreSharing
Value: 1

Key : Hypervisor.Flags.Phase0InitDone
Value: 1

Key : Hypervisor.Flags.PowerSchedulerQos
Value: 0

Key : Hypervisor.Flags.RootScheduler
Value: 0

Key : Hypervisor.Flags.SynicAvailable
Value: 1

Key : Hypervisor.Flags.UseQpcBias
Value: 0

Key : Hypervisor.Flags.Value
Value: 55185662

Key : Hypervisor.Flags.ValueHex
Value: 0x34a10fe

Key : Hypervisor.Flags.VpAssistPage
Value: 1

Key : Hypervisor.Flags.VsmAvailable
Value: 1

Key : Hypervisor.RootFlags.AccessStats
Value: 1

Key : Hypervisor.RootFlags.CrashdumpEnlightened
Value: 1

Key : Hypervisor.RootFlags.CreateVirtualProcessor
Value: 1

Key : Hypervisor.RootFlags.DisableHyperthreading
Value: 0

Key : Hypervisor.RootFlags.HostTimelineSync
Value: 1

Key : Hypervisor.RootFlags.HypervisorDebuggingEnabled
Value: 0

Key : Hypervisor.RootFlags.IsHyperV
Value: 1

Key : Hypervisor.RootFlags.LivedumpEnlightened
Value: 1

Key : Hypervisor.RootFlags.MapDeviceInterrupt
Value: 1

Key : Hypervisor.RootFlags.MceEnlightened
Value: 1

Key : Hypervisor.RootFlags.Nested
Value: 0

Key : Hypervisor.RootFlags.StartLogicalProcessor
Value: 1

Key : Hypervisor.RootFlags.Value
Value: 1015

Key : Hypervisor.RootFlags.ValueHex
Value: 0x3f7


BUGCHECK_CODE: ef

BUGCHECK_P1: ffff9704a187e080

BUGCHECK_P2: 0

BUGCHECK_P3: ffff9704a187e080

BUGCHECK_P4: 0

FILE_IN_CAB: 081825-21125-01.dmp

TAG_NOT_DEFINED_202b: *** Unknown TAG in analysis list 202b


DUMP_FILE_ATTRIBUTES: 0x21808
Kernel Generated Triage Dump

FAULTING_THREAD: ffff9704a2ef2080

PROCESS_NAME: svchost.exe

CRITICAL_PROCESS: svchost.exe

ERROR_CODE: (NTSTATUS) 0xa2ef2080 - <Unable to get error code text>

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

STACK_TEXT:
ffffd808`476aec28 fffff803`bd76f1f0 : 00000000`000000ef ffff9704`a187e080 00000000`00000000 ffff9704`a187e080 : nt!KeBugCheckEx
ffffd808`476aec30 fffff803`bd8e0a6f : ffff9704`a187e080 00000000`00000001 00000000`00000001 fffff803`bd49b9b5 : nt!PspCatchCriticalBreak+0x128
ffffd808`476aecd0 fffff803`bd91f1ef : ffff9704`a187e080 ffff9704`a187e248 ffff9704`a187e080 00000000`00000000 : nt!PspTerminateAllThreads+0x27b
ffffd808`476aed50 fffff803`bda76f0a : ffff9704`a187e080 00000000`00000001 ffff9704`a2ef2080 ffff9704`a187e080 : nt!PspTerminateProcess+0xf7
ffffd808`476aed90 fffff803`bd6b7c55 : ffff9704`a187e080 ffff9704`a2ef2080 01dc1082`2231b6ff 00c40000`0000001a : nt!NtTerminateProcess+0xca
ffffd808`476aee10 fffff803`bd6a6100 : fffff803`bd2f67c5 ffffffff`ffffffff 00000090`ddcfebe0 ffffd808`476af660 : nt!KiSystemServiceCopyEnd+0x25
ffffd808`476aefa8 fffff803`bd2f67c5 : ffffffff`ffffffff 00000090`ddcfebe0 ffffd808`476af660 fffff780`00000604 : nt!KiServiceLinkage
ffffd808`476aefb0 fffff803`bd6b8c06 : 00000000`00000000 00000000`00000000 ffffd808`476afa20 00000000`00000001 : nt!KiDispatchException+0xc85
ffffd808`476af840 fffff803`bd6b6828 : 00007ff9`bff791a0 00007ff9`bff791a0 00007ff9`bff791a0 00000000`00000000 : nt!KiFastFailDispatch+0xc6
ffffd808`476afa20 00007ff9`bff3104a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiRaiseSecurityCheckFailure+0x368
00000090`ddcfebe0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ff9`bff3104a


SYMBOL_NAME: nt!PspCatchCriticalBreak+128

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

IMAGE_VERSION: 10.0.26100.4946

STACK_COMMAND: .process /r /p 0xffff9704a187e080; .thread 0xffff9704a2ef2080 ; kb

BUCKET_ID_FUNC_OFFSET: 128

FAILURE_BUCKET_ID: 0xEF_svchost.exe_BUGCHECK_CRITICAL_PROCESS_a2ef2080_nt!PspCatchCriticalBreak

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {296df6bc-5186-c5df-a543-bddee77007a5}

Followup: MachineOwner
---------
< >
Showing 1-12 of 12 comments
Alice Liddell 19 Aug @ 6:04am 
dism /online /cleanup-image /restorehealth

sfc /scannow
#1
Halal Poogie Meat 19 Aug @ 11:25pm 
Originally posted by Alice Liddell:
dism /online /cleanup-image /restorehealth

sfc /scannow
yeah I did that. didn't fix anything kept BSODing. Should I try it in a safe boot or something? Read something like that online. and would a kernel dump help/ is recommended? if any1 knows
#2
emoticorpse 20 Aug @ 5:10am 
Can you do a cpu-z validate thing? (I don't know the exact link to that) Or a userbenchmark run? If you don't know how to do any of those things, nevermind.

So far looks like drivers/hardware but not sure where to start.
#3
Alice Liddell 20 Aug @ 6:36am 
The BSoD would show you if this is caused by a driver, as it lists the driver on the screen.

It is wise to take note of this because then if it is a driver, you can simply remove it but some are caused by system files so the driver will not be listed. Net Framework updates can really mess things up and there was one of those recently that messed my own system up.

But you run DISM and SFC and if any corruptions are found, always restart, which is what everyone does not understand but when you do solutions like these, you always restart.

'BlueScreenView' may help you dig further into the BSoD issue but your issue could very well be that attached Debugger, as I had that issue as well.
#4
Halal Poogie Meat 20 Aug @ 2:33pm 
Originally posted by Alice Liddell:
The BSoD would show you if this is caused by a driver, as it lists the driver on the screen.

It is wise to take note of this because then if it is a driver, you can simply remove it but some are caused by system files so the driver will not be listed. Net Framework updates can really mess things up and there was one of those recently that messed my own system up.

But you run DISM and SFC and if any corruptions are found, always restart, which is what everyone does not understand but when you do solutions like these, you always restart.

'BlueScreenView' may help you dig further into the BSoD issue but your issue could very well be that attached Debugger, as I had that issue as well.

no driver listed. All it says is Critical process died error code 0xef when it occurs. Usually after I exit a game not that much during gameplay. only happened once. I read the minidump with windbbg and it shows process died svchost.exe and then image name for whatever that means
#5
Halal Poogie Meat 20 Aug @ 2:34pm 
Originally posted by emoticorpse:
Can you do a cpu-z validate thing? (I don't know the exact link to that) Or a userbenchmark run? If you don't know how to do any of those things, nevermind.

So far looks like drivers/hardware but not sure where to start.
Sorry idk what it is. How will it help?
#6
HIVEmind 20 Aug @ 5:19pm 
It was caused by svchost. And it looks like win10
#7
HIVEmind 20 Aug @ 5:22pm 
Goto services.msc. and turn off stuff.
#8
Halal Poogie Meat 20 Aug @ 8:46pm 
Originally posted by HIVEmind:
It was caused by svchost. And it looks like win10
What does this mean? I have windows 11
#9
Halal Poogie Meat 19 hours ago 
Originally posted by HIVEmind:
Goto services.msc. and turn off stuff.
like what
#10
Obsessive Power 15 hours ago 
Originally posted by Halal Poogie Meat:
Originally posted by HIVEmind:
It was caused by svchost. And it looks like win10
What does this mean? I have windows 11

Nothing as that error can also occur under Windows 11. There is no definitive answer for this. It could be hardware or software issue.

If it's software try updating your drivers or clearing the Graphics driver using DDU and the installing the driver again.
#11
Illusion of Progress 12 hours ago 
A critical part of Windows itself died. If this is a recurring BSOD, you likely have an unstable system (or a very corrupted Windows install, usually as result of the other thing).

Do what reply #1 suggested firsy (this should rule out file corrupted), and if that doesn't help, then you need to move on to troubleshooting what is unstable with the hardware configuration.

At that point, do what reply #3 suggested and provide a CPU-Z validation.

If you're overclocking/undervolting anything, this is the point where you stop and revert to stock to see if the issue remains. This includes RAM profiles, so if it's running above BIOS defaults for RAM speed then stop for now.
#12
< >
Showing 1-12 of 12 comments
Per page: 1530 50

All Discussions > Steam Forums > Hardware and Operating Systems > Topic Details
Date Posted: 19 Aug @ 1:22am
Posts: 12
Start a New Discussion

Discussions Rules and Guidelines