Skip to content

Fatal System Error: 0x000000d1 #52

@kouzhudong

Description

@kouzhudong
The SHV failed to initialize (0xFFFFFFFD) Failed CPU: 0
KDTARGET: Refreshing KD connection

*** Fatal System Error: 0x000000d1
                       (0xFFFFF8037ACA1FA0,0x00000000000000FF,0x0000000000000000,0xFFFFF8037ACA1FA0)

Driver at fault: 
***       shv.sys - Address FFFFF8037ACA1FA0 base at FFFFF8037ACA0000, DateStamp 00000000
.
Break instruction exception - code 80000003 (first chance)

A fatal system error has occurred.
Debugger entered on first try; Bugcheck callbacks have not been invoked.

A fatal system error has occurred.

For analysis of this file, run !analyze -v
nt!DbgBreakPointWithStatus:
fffff803`768312f0 cc              int     3
3: kd> !analyze -v
Connected to Windows 10 22621 x64 target at (Tue Jan 21 23:16:39.226 2025 (UTC + 8:00)), ptr64 TRUE
Loading Kernel Symbols
.............................

Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading symbols.

..................................
................................................................
...........................................................
Loading User Symbols

Loading unloaded module list
.........

************* Symbol Loading Error Summary **************
Module name            Error
SharedUserData         No error - symbol load deferred

You can troubleshoot most symbol related issues by turning on symbol loading diagnostics (!sym noisy) and repeating the command that caused symbols to be loaded.
You should also verify that your symbol search path (.sympath) is correct.
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: fffff8037aca1fa0, memory referenced
Arg2: 00000000000000ff, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff8037aca1fa0, address which referenced memory

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


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.Sec
    Value: 3

    Key  : Analysis.DebugAnalysisProvider.CPP
    Value: Create: 8007007e on CORREY

    Key  : Analysis.DebugData
    Value: CreateObject

    Key  : Analysis.DebugModel
    Value: CreateObject

    Key  : Analysis.Elapsed.Sec
    Value: 5

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

    Key  : Analysis.System
    Value: CreateObject


BUGCHECK_CODE:  d1

BUGCHECK_P1: fffff8037aca1fa0

BUGCHECK_P2: ff

BUGCHECK_P3: 0

BUGCHECK_P4: fffff8037aca1fa0

READ_ADDRESS: MAX_SYSTEM_VA_ASSIGNMENTS needs to be increased
 fffff8037aca1fa0 

IP_MODULE_UNLOADED: 
shv.sys+1fa0
fffff803`7aca1fa0 ??              ???

PROCESS_NAME:  System

TRAP_FRAME:  ffffb17e6cc059a0 -- (.trap 0xffffb17e6cc059a0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=000000000003000a rbx=0000000000000000 rcx=00000000400000b0
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8037aca1fa0 rsp=ffffb17e6cc05b30 rbp=0000000000000001
 r8=8000000000000000  r9=fffff78000000294 r10=fffff803767e1090
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up di pl nz na pe nc
<Unloaded_shv.sys>+0x1fa0:
fffff803`7aca1fa0 ??              ???
Resetting default scope

BAD_STACK_POINTER:  ffffb17e6cc05048

FAILED_INSTRUCTION_ADDRESS: 
shv.sys+1fa0
fffff803`7aca1fa0 ??              ???

STACK_TEXT:  
ffffb17e`6cc05048 fffff803`76978c12 : ffffb17e`6cc051b0 fffff803`766bbf60 ffffa180`b6596180 fffff803`7aca1f01 : nt!DbgBreakPointWithStatus
ffffb17e`6cc05050 fffff803`769782d3 : ffffa180`00000003 ffffb17e`6cc051b0 fffff803`76840f00 ffffb17e`6cc05760 : nt!KiBugCheckDebugBreak+0x12
ffffb17e`6cc050b0 fffff803`76827017 : 00000000`00000000 00000000`00000000 ffffa180`b6596180 00000000`00000000 : nt!KeBugCheck2+0xba3
ffffb17e`6cc05820 fffff803`7683ce29 : 00000000`0000000a fffff803`7aca1fa0 00000000`000000ff 00000000`00000000 : nt!KeBugCheckEx+0x107
ffffb17e`6cc05860 fffff803`76838289 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
ffffb17e`6cc059a0 fffff803`7aca1fa0 : 00000000`0002625a 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x489
ffffb17e`6cc05b30 00000000`0002625a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : <Unloaded_shv.sys>+0x1fa0
ffffb17e`6cc05b38 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x2625a


SYMBOL_NAME:  shv.sys+1fa0

MODULE_NAME: shv

IMAGE_NAME:  shv.sys

STACK_COMMAND:  .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET:  1fa0

FAILURE_BUCKET_ID:  AV_VRF_CODE_AV_STACKPTR_ERROR_UNLOADED_IP_shv.sys!unknown_function

OS_VERSION:  10.0.22621.1

BUILDLAB_STR:  ni_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {10b30f68-c16f-3af1-78be-3816ff9061e4}

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


Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions