Hello all,
I'm quite fresh here, but I believe here's the best place to ask that question.
I'm having issues with my PC running Windows 11 22H2. Everything started when I enabled Hyper-V and WSL features in settings. I had the Critial_Process_Died BSODs and tried to fix it, but without any luck - even restore points did not work.
So then, I reinstalled Windows from scratch - formatted the primary system drive and installed it. Updated each and every driver, enabled Hyper-V and WSL and it happened again - not a BSOD this time, but my PC came into a reboot loop - I could hear the Win11 welcome sound at the beginning, but it was interrupted and the restart happened. As you can guess, after 3 reboots my PC displayed the "It looks like Windows didn't load correctly" and I had two options - advanced recovery options (which dissapointed me last time, so I didn't want to fight it anymore) and reboot. So I tried the latter option and after 1-3 more reboots the Windows starts properly and works without any issue, like nothing happened.
So now, I have the issue that my PC is sometimes stuck in the reboot loop (1-5 times) and starts properly - especially after a reboot from Windows menu. When I perform a fresh start, it most likely starts properly (sometimes needs several reboots).
As you can imagine, it's a big pain. I've seen a similar thread (https://forums.tomshardware.com/threads/win11-bsod-ntoskrnl-exe-416b40-unsure-what-cause.3762290/), but I can see that even a small difference in a minidump/dump makes a difference here, so I can't count on the same solution.
As the author of mentioned thread, I'm also tech savvy as I work as an architect, but I'm not that into Windows. I've tried debugging dumps with WinDgb and BlueScreenView, but I can't find the root cause.
What is also worth mentioning is that I haven't had any of those problems before enabling Hyper-V and WSL features. Unfortunately, WSL requires Hyper-V enabled, which requires SVM Mode (virtualization) enabled in BIOS.
I would be really grateful if there's anyone who could help me finding a root cause and fixing it. I will provide all the needed details/files as soon as possible. Any help appreciated!
kd !analyze -v results:
I'm quite fresh here, but I believe here's the best place to ask that question.
I'm having issues with my PC running Windows 11 22H2. Everything started when I enabled Hyper-V and WSL features in settings. I had the Critial_Process_Died BSODs and tried to fix it, but without any luck - even restore points did not work.
So then, I reinstalled Windows from scratch - formatted the primary system drive and installed it. Updated each and every driver, enabled Hyper-V and WSL and it happened again - not a BSOD this time, but my PC came into a reboot loop - I could hear the Win11 welcome sound at the beginning, but it was interrupted and the restart happened. As you can guess, after 3 reboots my PC displayed the "It looks like Windows didn't load correctly" and I had two options - advanced recovery options (which dissapointed me last time, so I didn't want to fight it anymore) and reboot. So I tried the latter option and after 1-3 more reboots the Windows starts properly and works without any issue, like nothing happened.
So now, I have the issue that my PC is sometimes stuck in the reboot loop (1-5 times) and starts properly - especially after a reboot from Windows menu. When I perform a fresh start, it most likely starts properly (sometimes needs several reboots).
As you can imagine, it's a big pain. I've seen a similar thread (https://forums.tomshardware.com/threads/win11-bsod-ntoskrnl-exe-416b40-unsure-what-cause.3762290/), but I can see that even a small difference in a minidump/dump makes a difference here, so I can't count on the same solution.
As the author of mentioned thread, I'm also tech savvy as I work as an architect, but I'm not that into Windows. I've tried debugging dumps with WinDgb and BlueScreenView, but I can't find the root cause.
What is also worth mentioning is that I haven't had any of those problems before enabling Hyper-V and WSL features. Unfortunately, WSL requires Hyper-V enabled, which requires SVM Mode (virtualization) enabled in BIOS.
- What did I discover so far? (detailed outputs at the end of the post)
- Bugcheck string - UNEXPECTED_KERNEL_MODE_TRAP
- Bugcheck code - 0x1000007f
- Caused by - ntoskrnl.exe
- Arg1 that indicates the double fault - 0000000000000008, EXCEPTION_DOUBLE_FAULT
- Tried the following:
- sfc /scannow - fixed some corrupted files
- chkdsk - no issues here
- SMART on all 3 SSDs - no bad sectors and issues
- MemTest86+ v6.0 - 9 full runs with 10 tests each (14hrs) and no errors
- updated BIOS and tried default settings (I have a little OC memory)
- updated low-level drivers (chipset, etc.), directly from the manufacturer site
- PC specs:
- CPU: AMD Ryzen 5 3600X
- RAM: 4x8GB 3066MHz
- GPU: NVIDIA GeForce RTX 3070
- MB: GIGABYTE B550 AORUS PRO
- OS: Microsoft Windows 11 Education (x64) Build 22621.755
- SSD: 1xNVMe + 2xSATA
I would be really grateful if there's anyone who could help me finding a root cause and fixing it. I will provide all the needed details/files as soon as possible. Any help appreciated!
kd !analyze -v results:
Code:
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
UNEXPECTED_KERNEL_MODE_TRAP_M (1000007f)
This means a trap occurred in kernel mode, and it's a trap of a kind
that the kernel isn't allowed to have/catch (bound trap) or that
is always instant death (double fault). The first number in the
BugCheck params is the number of the trap (8 = double fault, etc)
Consult an Intel x86 family manual to learn more about what these
traps are. Here is a *portion* of those codes:
If kv shows a taskGate
use .tss on the part before the colon, then kv.
Else if kv shows a trapframe
use .trap on that value
Else
.trap on the appropriate frame will show where the trap was taken
(on x86, this will be the ebp that goes with the procedure KiTrap)
Endif
kb will then show the corrected stack.
Arguments:
Arg1: 0000000000000008, EXCEPTION_DOUBLE_FAULT
Arg2: fffff80714245e70
Arg3: ffffc48363839000
Arg4: fffff8071641a9c9
Debugging Details:
------------------
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 1015
Key : Analysis.DebugAnalysisManager
Value: Create
Key : Analysis.Elapsed.mSec
Value: 2051
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: 234
Key : Analysis.Init.Elapsed.mSec
Value: 7768
Key : Analysis.Memory.CommitPeak.Mb
Value: 98
Key : Bugcheck.Code.DumpHeader
Value: 0x1000007f
Key : Bugcheck.Code.Register
Value: 0x7f
Key : Dump.Attributes.AsUlong
Value: 1808
Key : Dump.Attributes.DiagDataWrittenToHeader
Value: 1
Key : Dump.Attributes.ErrorCode
Value: 0
Key : Dump.Attributes.KernelGeneratedTriageDump
Value: 1
Key : Dump.Attributes.LastLine
Value: Dump completed successfully.
Key : Dump.Attributes.ProgressPercentage
Value: 0
FILE_IN_CAB: 110222-10453-01.dmp
TAG_NOT_DEFINED_202b: *** Unknown TAG in analysis list 202b
DUMP_FILE_ATTRIBUTES: 0x1808
Kernel Generated Triage Dump
BUGCHECK_CODE: 7f
BUGCHECK_P1: 8
BUGCHECK_P2: fffff80714245e70
BUGCHECK_P3: ffffc48363839000
BUGCHECK_P4: fffff8071641a9c9
STACK_OVERFLOW: Stack Limit: ffffc48363839000. Use (kF) and (!stackusage) to investigate stack usage.
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: csrss.exe
STACK_TEXT:
ffffc483`63839000 fffff807`1641a8b5 : 69570000`00000000 577c4950`4132336e 4e207377`6f646e69 00000000`00000000 : nt!KiSearchForNewThreadOnProcessor+0x59
ffffc483`638393c0 fffff807`164c7c3e : 00000000`00000000 fffff807`16f0e3c0 ffffc483`63839890 ffffc483`63839520 : nt!KiSearchForNewThreadOnSubNode+0xe5
ffffc483`63839420 fffff807`164c6c20 : ffffc58f`d31ee820 00000000`00000000 fffff807`12fad180 00000000`00000002 : nt!KiSearchForNewThread+0x91e
ffffc483`63839810 fffff807`164c8287 : ffffc58f`d31ee0c0 656c6f6f`00000000 7070614d`00006e61 00000000`00000000 : nt!KiSwapThread+0x8c0
ffffc483`63839960 fffff807`164ca8d6 : 50413233`00000000 5320656c`00000001 7546206d`00000011 00000000`0847da87 : nt!KiCommitThreadWait+0x137
ffffc483`63839a10 fffff807`1655928f : 30353962`00000002 fffff807`16f48940 fffff807`16f489a0 00000000`00000000 : nt!KeWaitForSingleObject+0x256
ffffc483`63839db0 fffff807`164c4882 : fffff807`16f48940 ffffc483`63839e78 00000000`00010244 fffff807`1657f0b0 : nt!ExpWaitForResource+0x6b
ffffc483`63839e40 fffff807`164c3a59 : fffff807`16f48940 00000000`00000000 00000000`00000001 00000000`00000001 : nt!ExpAcquireResourceSharedLite+0x5f2
ffffc483`63839ee0 fffff807`16ce11d1 : 000000b9`ffff0000 00000000`00000000 00001200`44490000 00000000`00000000 : nt!ExAcquireResourceSharedLite+0x39
ffffc483`63839f20 fffff807`168b60ea : 0000005d`00000142 b9ffff00`00000b00 00002008`02000000 000000fa`0000008b : nt!CmpLockRegistry+0x41
ffffc483`63839f50 fffff807`168b9265 : 00000000`0000001c ffffc483`6383a490 ffffc483`6383a418 00000000`00000000 : nt!CmpDoParseKey+0x3fa
ffffc483`6383a3a0 fffff807`168c0d37 : fffff807`168b8f01 ffffc58f`00000000 ffffc58f`d0bc95f0 00000000`00000000 : nt!CmpParseKey+0x2e5
ffffc483`6383a590 fffff807`168c0162 : ffffc58f`d0bc95f0 ffffc483`6383a7c0 00000000`00000240 ffffc58f`c7dfe6c0 : nt!ObpLookupObjectName+0x697
ffffc483`6383a730 fffff807`168bb188 : 00000000`00000000 ffffc58f`c7dfe6c0 ffffc483`6383ace8 00000000`00000000 : nt!ObOpenObjectByNameEx+0x1f2
ffffc483`6383a860 fffff807`1699f688 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!CmOpenKey+0x2c8
ffffc483`6383aab0 fffff807`1663a968 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!NtOpenKeyEx+0x48
ffffc483`6383ab00 fffff807`1662c8b0 : fffff807`169145d4 00000000`00000000 00000000`00000010 ffffd78d`8ca3bdb0 : nt!KiSystemServiceCopyEnd+0x28
ffffc483`6383ac98 fffff807`169145d4 : 00000000`00000000 00000000`00000010 ffffd78d`8ca3bdb0 00000000`00000004 : nt!KiServiceLinkage
ffffc483`6383aca0 fffff807`169144fa : ffffffff`800000a0 00000000`00000000 ffffd78d`93967510 ffffffff`800000a0 : nt!_RegRtlOpenKeyTransacted+0xc4
ffffc483`6383ad40 fffff807`16913ee9 : 00000000`00000086 00000000`00000000 00000000`00000100 00000000`00000001 : nt!SysCtxRegOpenKey+0x3a
ffffc483`6383ad80 fffff807`16913cd8 : ffffd78d`94188100 ffffc58f`ca48f2a0 00000000`0000005d 00000000`00000000 : nt!_CmOpenDeviceRegKeyWorker+0x1b9
ffffc483`6383ae40 fffff807`1691351a : 00000000`00000000 ffffc483`6383afa0 ffffc483`6383b140 00000000`00000000 : nt!_CmOpenDeviceRegKey+0xdc
ffffc483`6383aea0 fffff807`16913397 : 00000000`00000000 00000000`00000000 00000000`00000000 ffffc483`6383b144 : nt!_CmGetDeviceRegPropWorker+0x102
ffffc483`6383aff0 fffff807`1691664c : ffffd78d`94179000 fffff807`164d2615 00000000`00000100 00000000`00000401 : nt!_CmGetDeviceRegProp+0xff
ffffc483`6383b100 fffff807`1691691f : 00000000`00042cc0 ffffc483`6383b2c1 00000000`00000000 ffffc483`6383b430 : nt!_CmGetDeviceSoftwareKey+0x74
ffffc483`6383b210 fffff807`1691422e : 00000000`52504e50 fffff807`164d192f 00000000`00000012 00000000`000000f0 : nt!_CmGetDeviceSoftwareKeyPath+0x5b
ffffc483`6383b310 fffff807`16913dfe : 00000000`00000000 fffff807`16c9a68d 00000000`00000100 00000000`00000001 : nt!_CmGetDeviceRegKeyPath+0xba
ffffc483`6383b360 fffff807`16913cd8 : ffffd78d`94188480 ffffc58f`ca48f2a0 00000000`00000000 00000000`00000000 : nt!_CmOpenDeviceRegKeyWorker+0xce
ffffc483`6383b420 fffff807`16916ba2 : 00000000`00000012 00000000`00020019 ffffc58f`ca5240a0 fffff807`16c9a68d : nt!_CmOpenDeviceRegKey+0xdc
ffffc483`6383b480 fffff807`432721d3 : 00000000`00020019 ffffc483`6383b531 00000000`00000000 00000000`00000002 : nt!IoOpenDeviceRegistryKey+0xc2
ffffc483`6383b4d0 00000000`00020019 : ffffc483`6383b531 00000000`00000000 00000000`00000002 fffff807`42d8db40 : nvlddmkm+0xf621d3
ffffc483`6383b4d8 ffffc483`6383b531 : 00000000`00000000 00000000`00000002 fffff807`42d8db40 fffff807`423a2734 : 0x20019
ffffc483`6383b4e0 00000000`00000000 : 00000000`00000002 fffff807`42d8db40 fffff807`423a2734 00000000`00000003 : 0xffffc483`6383b531
SYMBOL_NAME: nt!KiSearchForNewThreadOnProcessor+59
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
IMAGE_VERSION: 10.0.22621.755
STACK_COMMAND: .cxr; .ecxr ; kb
BUCKET_ID_FUNC_OFFSET: 59
FAILURE_BUCKET_ID: 0x7f_8_nt!KiSearchForNewThreadOnProcessor
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {27f4e8d4-5014-6cef-bdf1-bb6ec72b9ac0}
Followup: MachineOwner
---------
Last edited:
really appreciate
Facebook
Twitter
Instagram