BSOD 0x000000d1

Question

BSOD 0x000000d1

Cj Singleton 0

Hello. For a while now my computer keeps crashing and i don't know why, I use WinDbg to read the bug check but I can't pinpoint what the problem is. Here the Memery.Dmp. All help is appreciated.

*******************************************************************************
*                                                                             *
*                        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: 0000000000000000, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000008, value 0 = read operation, 1 = write operation
Arg4: 0000000000000000, address which referenced memory
Debugging Details:
------------------
KEY_VALUES_STRING: 1
    Key  : Analysis.CPU.mSec
    Value: 2390
    Key  : Analysis.Elapsed.mSec
    Value: 2506
    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: 734
    Key  : Analysis.Init.Elapsed.mSec
    Value: 3680
    Key  : Analysis.Memory.CommitPeak.Mb
    Value: 106
    Key  : Analysis.Version.DbgEng
    Value: 10.0.27920.1001
    Key  : Analysis.Version.Description
    Value: 10.2506.23.01 amd64fre
    Key  : Analysis.Version.Ext
    Value: 1.2506.23.1
    Key  : Bugcheck.Code.KiBugCheckData
    Value: 0xd1
    Key  : Bugcheck.Code.LegacyAPI
    Value: 0xd1
    Key  : Bugcheck.Code.TargetModel
    Value: 0xd1
    Key  : Dump.Attributes.AsUlong
    Value: 0x21000
    Key  : Dump.Attributes.DiagDataWrittenToHeader
    Value: 1
    Key  : Dump.Attributes.ErrorCode
    Value: 0x0
    Key  : Dump.Attributes.LastLine
    Value: Dump completed successfully.
    Key  : Dump.Attributes.ProgressPercentage
    Value: 100
    Key  : Failure.Bucket
    Value: AV_CODE_AV_NULL_IP_nt!KiPageFault
    Key  : Failure.Hash
    Value: {4ce35ff9-c5cf-d66d-0323-0f05e33f6692}
    Key  : Faulting.IP.Type
    Value: Null
    Key  : Hypervisor.Enlightenments.Value
    Value: 0
    Key  : Hypervisor.Enlightenments.ValueHex
    Value: 0x0
    Key  : Hypervisor.Flags.AnyHypervisorPresent
    Value: 0
    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: 0
    Key  : Hypervisor.Flags.DeprecateAutoEoi
    Value: 0
    Key  : Hypervisor.Flags.DynamicCpuDisabled
    Value: 0
    Key  : Hypervisor.Flags.Epf
    Value: 0
    Key  : Hypervisor.Flags.ExtendedProcessorMasks
    Value: 0
    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: 0
    Key  : Hypervisor.Flags.Phase0InitDone
    Value: 0
    Key  : Hypervisor.Flags.PowerSchedulerQos
    Value: 0
    Key  : Hypervisor.Flags.RootScheduler
    Value: 0
    Key  : Hypervisor.Flags.SynicAvailable
    Value: 0
    Key  : Hypervisor.Flags.UseQpcBias
    Value: 0
    Key  : Hypervisor.Flags.Value
    Value: 16908288
    Key  : Hypervisor.Flags.ValueHex
    Value: 0x1020000
    Key  : Hypervisor.Flags.VpAssistPage
    Value: 0
    Key  : Hypervisor.Flags.VsmAvailable
    Value: 0
    Key  : Hypervisor.RootFlags.AccessStats
    Value: 0
    Key  : Hypervisor.RootFlags.CrashdumpEnlightened
    Value: 0
    Key  : Hypervisor.RootFlags.CreateVirtualProcessor
    Value: 0
    Key  : Hypervisor.RootFlags.DisableHyperthreading
    Value: 0
    Key  : Hypervisor.RootFlags.HostTimelineSync
    Value: 0
    Key  : Hypervisor.RootFlags.HypervisorDebuggingEnabled
    Value: 0
    Key  : Hypervisor.RootFlags.IsHyperV
    Value: 0
    Key  : Hypervisor.RootFlags.LivedumpEnlightened
    Value: 0
    Key  : Hypervisor.RootFlags.MapDeviceInterrupt
    Value: 0
    Key  : Hypervisor.RootFlags.MceEnlightened
    Value: 0
    Key  : Hypervisor.RootFlags.Nested
    Value: 0
    Key  : Hypervisor.RootFlags.StartLogicalProcessor
    Value: 0
    Key  : Hypervisor.RootFlags.Value
    Value: 0
    Key  : Hypervisor.RootFlags.ValueHex
    Value: 0x0
    Key  : SecureKernel.HalpHvciEnabled
    Value: 0
    Key  : WER.OS.Branch
    Value: ge_release
    Key  : WER.OS.Version
    Value: 10.0.26100.1
    Key  : WER.System.BIOSRevision
    Value: 5.17.0.0
BUGCHECK_CODE:  d1
BUGCHECK_P1: 0
BUGCHECK_P2: 2
BUGCHECK_P3: 8
BUGCHECK_P4: 0
FILE_IN_CAB:  MEMORY.DMP
DUMP_FILE_ATTRIBUTES: 0x21000
FAULTING_THREAD:  ffffc00d2074e280
READ_ADDRESS:  0000000000000000 
PROCESS_NAME:  System
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1 (!blackboxwinlogon)
FAILED_INSTRUCTION_ADDRESS: 
+0
STACK_TEXT:  
ffffbe05`f3661488 fffff804`f00b39e9     : 00000000`0000000a 00000000`00000000 00000000`00000002 00000000`00000008 : nt!KeBugCheckEx
ffffbe05`f3661490 fffff804`f00aeca8     : ffffe601`2ab484a0 ffffe601`2ab48030 ffffc00d`22603050 00000000`00000000 : nt!KiBugCheckDispatch+0x69
ffffbe05`f36615d0 00000000`00000000     : ffffc00d`222f4100 00000000`00000000 00000000`00000000 fffff804`efc74512 : nt!KiPageFault+0x468
SYMBOL_NAME:  nt!KiPageFault+468
MODULE_NAME: nt
IMAGE_NAME:  ntkrnlmp.exe
STACK_COMMAND: .process /r /p 0xfffff804f09cef80; .thread 0xffffc00d2074e280 ; kb
BUCKET_ID_FUNC_OFFSET:  468
FAILURE_BUCKET_ID:  AV_CODE_AV_NULL_IP_nt!KiPageFault
OS_VERSION:  10.0.26100.1
BUILDLAB_STR:  ge_release
OSPLATFORM_TYPE:  x64
OSNAME:  Windows 10
FAILURE_ID_HASH:  {4ce35ff9-c5cf-d66d-0323-0f05e33f6692}
Followup:     MachineOwner
---------
2: kd> !dpcs
CPU Type      KDPC       Function
dpcs: no pending DPCs found
2: kd> !dpcwatchdog
Not a DPC_WATCHDOG_VIOLATION issue
All durations are in seconds (1 System tick = 15.625000 milliseconds)
Circular Kernel Context Logger history: !logdump 0x2
DPC and ISR stats (total since boot): !intstats /d
DPC and ISR stats (during DPC watchdog period): !intstats /w
--------------------------------------------------
CPU#0
--------------------------------------------------
Current DPC: No Active DPC
Pending DPCs:
----------------------------------------
CPU Type      KDPC       Function
dpcs: no pending DPCs found
--------------------------------------------------
CPU#1
--------------------------------------------------
Current DPC: No Active DPC
Pending DPCs:
----------------------------------------
CPU Type      KDPC       Function
dpcs: no pending DPCs found
--------------------------------------------------
CPU#2
--------------------------------------------------
Current DPC: storport!RaidpAdapterRedirectDpcRoutine (Normal DPC)
Debugger Saved IRQL: 2
Cumulative DPC Time Limit: 120.000 seconds
Current Cumulative DPC Time: 0.000 seconds
Single DPC Time Limit: 20.000 seconds
Current Single DPC Time: 0.000 seconds
Pending DPCs:
----------------------------------------
CPU Type      KDPC       Function
dpcs: no pending DPCs found
--------------------------------------------------
CPU#3
--------------------------------------------------
Current DPC: No Active DPC
Pending DPCs:
----------------------------------------
CPU Type      KDPC       Function
dpcs: no pending DPCs found
--------------------------------------------------
CPU#4
--------------------------------------------------
Current DPC: No Active DPC
Pending DPCs:
----------------------------------------
CPU Type      KDPC       Function
dpcs: no pending DPCs found
--------------------------------------------------
CPU#5
--------------------------------------------------
Current DPC: No Active DPC
Pending DPCs:
----------------------------------------
CPU Type      KDPC       Function
dpcs: no pending DPCs found
--------------------------------------------------
CPU#6
--------------------------------------------------
Current DPC: No Active DPC
Pending DPCs:
----------------------------------------
CPU Type      KDPC       Function
dpcs: no pending DPCs found
--------------------------------------------------
CPU#7
--------------------------------------------------
Current DPC: No Active DPC
Pending DPCs:
----------------------------------------
CPU Type      KDPC       Function
dpcs: no pending DPCs found
--------------------------------------------------
CPU#8
--------------------------------------------------
Current DPC: No Active DPC
Pending DPCs:
----------------------------------------
CPU Type      KDPC       Function
dpcs: no pending DPCs found
--------------------------------------------------
CPU#9
--------------------------------------------------
Current DPC: No Active DPC
Pending DPCs:
----------------------------------------
CPU Type      KDPC       Function
dpcs: no pending DPCs found
--------------------------------------------------
CPU#10
--------------------------------------------------
Current DPC: No Active DPC
Pending DPCs:
----------------------------------------
CPU Type      KDPC       Function
dpcs: no pending DPCs found
--------------------------------------------------
CPU#11
--------------------------------------------------
Current DPC: No Active DPC
Pending DPCs:
----------------------------------------
CPU Type      KDPC       Function
dpcs: no pending DPCs found
--------------------------------------------------
CPU#12
--------------------------------------------------
Current DPC: No Active DPC
Pending DPCs:
----------------------------------------
CPU Type      KDPC       Function
dpcs: no pending DPCs found
--------------------------------------------------
CPU#13
--------------------------------------------------
Current DPC: No Active DPC
Pending DPCs:
----------------------------------------
CPU Type      KDPC       Function
dpcs: no pending DPCs found
--------------------------------------------------
CPU#14
--------------------------------------------------
Current DPC: No Active DPC
Pending DPCs:
----------------------------------------
CPU Type      KDPC       Function
dpcs: no pending DPCs found
--------------------------------------------------
CPU#15
--------------------------------------------------
Current DPC: No Active DPC
Pending DPCs:
----------------------------------------
CPU Type      KDPC       Function
dpcs: no pending DPCs found

0 comments

2 answers

Your answer

Answer 1

Ivan B 114.7K Independent Advisor

Hii,

BIOS update along with the new drivers chipset.

First, you'll need to disable Bitlocker to update the BIOS.

https://www.asus.com/support/faq/1047461/

Second, you will update the bios and then install the listed drivers.

https://download.msi.com/bos_exe/mb/7C91vAK1.zip

https://storage-asset.msi.com/files/pdf/How_to_flash_the_BIOS.pdf

Drivers:

https://download.msi.com/dvr_exe/mb/amd_chipset_drivers_am4_am5.zip

https://download.msi.com/dvr_exe/mb/realtek_audio_R.zip

Open the command prompt (admin) and run the commands: sfc /scannow and dism /online /cleanup-image /restorehealth, wait for the process to finish and restart the computer.

Then perform a clean boot and if you want to uninstall applications that you do not use.

https://support.microsoft.com/en-us/topic/how-to-execute-a-simple-boot-start-in-windows-da2f9573-6eec-00ad-2f8a-a97a1807f3dd

Note: This is a non-Microsoft website. The page appears to be providing accurate, safe information. Watch out for ads on the site that may advertise products frequently classified as a PUP (Potentially Unwanted Products). Thoroughly research any product advertised on the site before you decide to download and install it.

Thanks

Cj Singleton 0 Reputation points

2025-09-25T02:53:02.8533333+00:00

Wow thank you so much for the support and creating a list of steps to fix this.

I'll follow these steps and hopefully this fixes the issue.
Ivan B 114.7K Reputation points Independent Advisor

2025-09-25T03:25:59.1133333+00:00

Hi ,

Well, in this case, I've provided the solution based on the information from the minidump, remembering not to rule out the possibility of hardware.

I hope everything goes well; we're here to help.

Give feedback if the information was useful or not.

Thanks

Answer 2

Ivan B 114.7K Independent Advisor

Hi ,

If it is a laptop or desktop, if possible, could you provide the laptop model or your desktop configuration?

Well according to the minidumps the failure was not to identify the driver and could be Chipset

Thanks

Cj Singleton 0 Reputation points

2025-09-24T22:32:31.9666667+00:00

Hi, Thank for answering

It a desktop and it has a Mag b550 Tomahawk motherboard, AMD Ryzen 7 3800XT 8-Core Processor and GIGABYTE GeForce RTX 3080

Share via

BSOD 0x000000d1

2 answers

Your answer