I currently have a host computer. When I start it with the packaged dev package, there is a probability that a fatal error will occur. However, there are no issues after a normal startup. Moreover, when it crashes, there is no output in the log file. Only a dmp file is generated.
************* Preparing the environment for Debugger Extensions Gallery repositories **************
ExtensionRepository : Implicit
UseExperimentalFeatureForNugetShare : true
AllowNugetExeUpdate : true
NonInteractiveNuget : true
AllowNugetMSCredentialProviderInstall : true
AllowParallelInitializationOfLocalRepositories : true
EnableRedirectToChakraJsProvider : false
– Configuring repositories
----> Repository : LocalInstalled, Enabled: true
----> Repository : UserExtensions, Enabled: true
> > > > > > > > > > > > > Preparing the environment for Debugger Extensions Gallery repositories completed, duration 0.000 seconds
************* Waiting for Debugger Extensions Gallery to Initialize **************
> > > > > > > > > > > > > Waiting for Debugger Extensions Gallery to Initialize completed, duration 0.016 seconds
> > > > > > > > > > > > > ----> Repository : UserExtensions, Enabled: true, Packages count: 0
> > > > > > > > > > > > > ----> Repository : LocalInstalled, Enabled: true, Packages count: 43
Microsoft (R) Windows Debugger Version 10.0.27793.1000 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\Administrator\Desktop\1.dmp]
User Mini Dump File: Only registers, stack and portions of memory are available
************* Path validation summary **************
Response Time (ms) Location
Deferred srv*
Symbol search path is: srv*
Executable search path is:
Windows 10 Version 19045 MP (16 procs) Free x64
Product: WinNt, suite: SingleUserTS
Edition build lab: 19041.1.amd64fre.vb_release.191206-1406
Debug session time: Fri Mar 21 15:51:08.000 2025 (UTC + 8:00)
System Uptime: 0 days 5:02:40.357
Process Uptime: not available
…
This dump file has an exception of interest stored in it.
The stored exception information can be accessed via .ecxr
(110c.3c68): Illegal instruction - code c000001d (first/second chance not available)
For analysis of this file, run !analyze -v
ntdll!NtWaitForSingleObject+0x14:
00007fff`cf90d574 c3 ret
0:005> !analyze -v
Exception Analysis
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 281
Key : Analysis.Elapsed.mSec
Value: 480
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: 156
Key : Analysis.Init.Elapsed.mSec
Value: 3524
Key : Analysis.Memory.CommitPeak.Mb
Value: 92
Key : Analysis.Version.DbgEng
Value: 10.0.27793.1000
Key : Analysis.Version.Description
Value: 10.2410.02.02 amd64fre
Key : Analysis.Version.Ext
Value: 1.2410.2.2
Key : Failure.Bucket
Value: ILLEGAL_INSTRUCTION_c000001d_TestVersionError.exe!Unknown
Key : Failure.Exception.Code
Value: 0xffffffffc000001d
Key : Failure.Exception.IP.Address
Value: 0x7ff64044ae0b
Key : Failure.Exception.IP.Module
Value: TestVersionError
Key : Failure.Exception.IP.Offset
Value: 0x111ae0b
Key : Failure.Hash
Value: {22bd327b-bfe5-8186-2752-17c05883415c}
Key : ProblemClass.Collapse.After.BUCKET_ID
Value: ILLEGAL_INSTRUCTION
Key : ProblemClass.Collapse.After.DEFAULT_BUCKET_ID
Value: ILLEGAL_INSTRUCTION
Key : ProblemClass.Collapse.After.PRIMARY_PROBLEM_CLASS
Value: ILLEGAL_INSTRUCTION
Key : ProblemClass.Collapse.Before.BUCKET_ID
Value: APPLICATION_FAULT
Key : ProblemClass.Collapse.Before.DEFAULT_BUCKET_ID
Value: APPLICATION_FAULT
Key : ProblemClass.Collapse.Before.PRIMARY_PROBLEM_CLASS
Value: APPLICATION_FAULT
Key : Timeline.OS.Boot.DeltaSec
Value: 18160
Key : WER.OS.Branch
Value: vb_release
Key : WER.OS.Version
Value: 10.0.19041.1
Key : WER.Process.Version
Value: 5.4.4.0
FILE_IN_CAB: 1.dmp
CONTEXT: (.ecxr)
rax=00003cea8066d0e8 rbx=00000000000002cf rcx=fffffc0000003fff
rdx=0000000000003cea rsi=00003cea8066cdcb rdi=000000808e4ff710
rip=00007ff64044ae0b rsp=000000808e4ff5f0 rbp=0000000000000000
r8=000000808e4ff701 r9=0000000000000035 r10=0000000000000002
r11=000001bde23e1800 r12=0000000000000035 r13=0000000000000000
r14=000001bde00fd280 r15=00000000000002cf
iopl=0 nv up ei pl nz na pe cy
cs=0033 ss=002b ds=002b es=002b fs=0053 gs=002b efl=00010203
TestVersionError+0x111ae0b:
00007ff6`4044ae0b 66410faef5 tpause r13d
Resetting default scope
EXCEPTION_RECORD: (.exr -1)
ExceptionAddress: 00007ff64044ae0b (TestVersionError+0x000000000111ae0b)
ExceptionCode: c000001d (Illegal instruction)
ExceptionFlags: 00000000
NumberParameters: 0
PROCESS_NAME: TestVersionError.exe
ERROR_CODE: (NTSTATUS) 0xc000001d - { }
EXCEPTION_CODE_STR: c000001d
STACK_TEXT:
00000080`8e4ff5f0 00007ff6`4efa9f48 : 000001bd`ffffffff 000001bd`e0e11000 00007ff6`40456c0b 00007ff6`4ef9ea00 : TestVersionError+0x111ae0b
00000080`8e4ff5f8 000001bd`ffffffff : 000001bd`e0e11000 00007ff6`40456c0b 00007ff6`4ef9ea00 00007ff6`4044f979 : TestVersionError+0xfc79f48
00000080`8e4ff600 000001bd`e0e11000 : 00007ff6`40456c0b 00007ff6`4ef9ea00 00007ff6`4044f979 00000000`00000000 : 0x000001bd`ffffffff 00000080`8e4ff608 00007ff6`40456c0b : 00007ff6`4ef9ea00 00007ff6`4044f979 00000000`00000000 000001bd`e00fd280 : 0x000001bd`e0e11000
00000080`8e4ff610 00007ff6`4ef9ea00 : 00007ff6`4044f979 00000000`00000000 000001bd`e00fd280 000001bd`dd955ee0 : TestVersionError+0x1126c0b
00000080`8e4ff618 00007ff6`4044f979 : 00000000`00000000 000001bd`e00fd280 000001bd`dd955ee0 00000000`00000000 : TestVersionError+0xfc6ea00
00000080`8e4ff620 00000000`00000000 : 000001bd`e00fd280 000001bd`dd955ee0 00000000`00000000 00007ff6`4ef9ea00 : TestVersionError+0x111f979
STACK_COMMAND: ~5s; .ecxr ; kb
FAILED_INSTRUCTION_ADDRESS:
TestVersionError+111ae0b
00007ff6`4044ae0b 66410faef5 tpause r13d
SYMBOL_NAME: TestVersionError+111ae0b
MODULE_NAME: TestVersionError
IMAGE_NAME: TestVersionError.exe
FAILURE_BUCKET_ID: ILLEGAL_INSTRUCTION_c000001d_TestVersionError.exe!Unknown
OS_VERSION: 10.0.19041.1
BUILDLAB_STR: vb_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
IMAGE_VERSION: 5.4.4.0
FAILURE_ID_HASH: {22bd327b-bfe5-8186-2752-17c05883415c}
## Followup: MachineOwner
So later on, I packaged a new FPS C++ template, and this issue still occurs with a certain probability. There is no problem when using 5.1, but it does happen when using 5.4. How should I solve this problem?