question

SyedAhmed-3578 avatar image
0 Votes"
SyedAhmed-3578 asked SyedAhmed-3578 edited

Getting Fatal error 0x000000d1 or 0x0000000a

Hi,
I am working in an ARM processor running in Windows 10 IOT. When I triggered a software reset, the board reboots properly. But sometimes, before completing the boot, it crashes with the following error log. Solutions for this issue are available only for x86 or x64.
If I doubt the drivers I am included in the build, these crashes were not happening in EMMC boot. It happens only in SD boot.

*** Fatal System Error: 0x000000d1
(0x00000000,0x000000FF,0x00000008,0x00000000)

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.

Connected to Windows 10 17763 ARM (NT) Thumb-2 target at (Thu Jun 3 18:15:03.483 2021 (UTC + 5:30)), ptr64 FALSE
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
..Unable to enumerate user-mode unloaded modules, Win32 error 0n30


Bugcheck Analysis


Use !analyze -v to get detailed debugging information.

BugCheck D1, {0, ff, 8, 0}

Probably caused by : ntkrnlmp.exe ( nt!KiCommonMemoryManagementAbort+13c )

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

nt!DbgBreakPointWithStatus:
81442980 defe __debugbreak
0: kd> !analyze -v


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: 00000000, memory referenced
Arg2: 000000ff, IRQL
Arg3: 00000008, value 0 = read operation, 1 = write operation
Arg4: 00000000, address which referenced memory

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

KEY_VALUES_STRING: 1

STACKHASH_ANALYSIS: 1

TIMELINE_ANALYSIS: 1

DUMP_CLASS: 1

DUMP_QUALIFIER: 0

BUILD_VERSION_STRING: 17763.253.armfre.rs5_release_svc_prod1.181231-1749

DUMP_TYPE: 0

BUGCHECK_P1: 0

BUGCHECK_P2: ff

BUGCHECK_P3: 8

BUGCHECK_P4: 0

READ_ADDRESS: 00000000

CURRENT_IRQL: 2

FAULTING_IP:
+0
00000000 ?? ???

PROCESS_NAME: System

CPU_COUNT: 2

CPU_MHZ: 318

CPU_VENDOR: A

CPU_FAMILY: 7

CPU_MODEL: c09

CPU_STEPPING: 20a

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

BUGCHECK_STR: AV

ANALYSIS_SESSION_HOST: DESKTOP-47GNOU6

ANALYSIS_SESSION_TIME: 06-03-2021 18:15:39.0270

ANALYSIS_VERSION: 10.0.17763.1 x86fre

TRAP_FRAME: 83003ae8 -- (.trap 0x83003ae8)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
r0=ffc00570 r1=00000000 r2=fffffff2 r3=00000002 r4=00000000 r5=00000000
r6=00000000 r7=00000000 r8=00000000 r9=00000000 r10=00000000 r11=83003cd8
r12=555aa5cb sp=83003c88 lr=81a204f5 pc=00000000 psr=800f0093 N---- ARM
00000000 ?? ???
Resetting default scope

IP_IN_FREE_BLOCK: 0

LAST_CONTROL_TRANSFER: from 8147d3a2 to 81442980

FAILED_INSTRUCTION_ADDRESS:
+0
00000000 ?? ???

STACK_TEXT:
83003770 8147d3a2 : 81690f88 8160ccc0 830037a0 81542997 : nt!DbgBreakPointWithStatus
83003770 8147dfb0 : 81690f88 8160ccc0 830037a0 81542997 : nt!KiBugCheckDebugBreak+0x1a
830037b8 8147e298 : 00000000 000000ff 00000008 00000000 : nt!KeBugCheck2+0x5f4
83003a98 814414fa : 00000000 00000000 00000008 ffc00470 : nt!KeBugCheckEx+0x14
83003ab0 81440b6c : 00000000 81a1c97d 00000000 00000000 : nt!KiBugCheckDispatch+0x12
83003ae8 00000000 : 8115c530 00000008 00000000 81440420 : nt!KiCommonMemoryManagementAbort+0x13c

THREAD_SHA1_HASH_MOD_FUNC: ca5f7c3e9ee982160aa9610676708cf3d8314983

THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 78786dea09e87ee45d67f1c06808585a0fa91c96

THREAD_SHA1_HASH_MOD: ee8fcf1fb60cb6e3e2f60ddbed2ec02b5748a693

FOLLOWUP_IP:
nt!KiCommonMemoryManagementAbort+13c
81440b6c f04f00ff mov r0,#0xFF

FAULT_INSTR_CODE: fff04f

SYMBOL_STACK_INDEX: 5

SYMBOL_NAME: nt!KiCommonMemoryManagementAbort+13c

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 61b3113c

IMAGE_VERSION: 10.0.17763.253

STACK_COMMAND: .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET: 13c

FAILURE_BUCKET_ID: AV_CODE_AV_NULL_IP_nt!KiCommonMemoryManagementAbort

BUCKET_ID: AV_CODE_AV_NULL_IP_nt!KiCommonMemoryManagementAbort

PRIMARY_PROBLEM_CLASS: AV_CODE_AV_NULL_IP_nt!KiCommonMemoryManagementAbort

TARGET_TIME: 2021-06-03T09:53:25.000Z

OSBUILD: 17763

OSSERVICEPACK: 253

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK: 272

PRODUCT_TYPE: 1

OSPLATFORM_TYPE: arm

OSNAME: Windows 10

OSEDITION: Windows 10 WinNt TerminalServer SingleUserTS

OS_LOCALE:

USER_LCID: 0

OSBUILD_TIMESTAMP: 2021-12-10 14:05:08

BUILDDATESTAMP_STR: 181231-1749

BUILDLAB_STR: rs5_release_svc_prod1

BUILDOSVER_STR: 10.0.17763.253.armfre.rs5_release_svc_prod1.181231-1749

ANALYSIS_SESSION_ELAPSED_TIME: 1f42

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:av_code_av_null_ip_nt!kicommonmemorymanagementabort

FAILURE_ID_HASH: {53c856cc-237b-f9fc-d93d-22719a25a3b8}

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


windows-hardwarewindows-iot-10core
· 1
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Can anyone help with this issue? I can share any additional information needed.

0 Votes 0 ·

0 Answers