F5F Stay Refreshed Hardware Desktop Need assistance with commonly occurring BSoD issues.

Need assistance with commonly occurring BSoD issues.

Need assistance with commonly occurring BSoD issues.

S
STEVEJasonson
Member
Find
171
04-19-2025, 03:22 AM
#1
Currently I am having frequently BDOS, once a week. All happen when I surf website using Edge browser
This is my dump text and mini dump file
Hope someone can help me with this
Minidump file:
https://pixeldrain.com/u/Rh3j1HQA
*******************************************************************************
* *
* 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: fffff00216e2c760, memory referenced
Arg2: 000000000000000d, IRQL
Arg3: 0000000000000008, value 0 = read operation, 1 = write operation
Arg4: fffff00216e2c760, address which referenced memory
Debugging Details:
------------------
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 1655
Key : Analysis.Elapsed.mSec
Value: 9370
Key : Analysis.IO.Other.Mb
Value: 4
Key : Analysis.IO.Read.Mb
Value: 0
Key : Analysis.IO.Write.Mb
Value: 21
Key : Analysis.Init.CPU.mSec
Value: 249
Key : Analysis.Init.Elapsed.mSec
Value: 67484
Key : Analysis.Memory.CommitPeak.Mb
Value: 99
Key : Bugcheck.Code.LegacyAPI
Value: 0xd1
Key : Bugcheck.Code.TargetModel
Value: 0xd1
Key : Dump.Attributes.AsUlong
Value: 1008
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
Key : Failure.Bucket
Value: AV_CODE_AV_BAD_IP_nt!KiPageFault
Key : Failure.Hash
Value: {73cd60cc-83fa-6b76-df08-1961c31d7403}
BUGCHECK_CODE: d1
BUGCHECK_P1: fffff00216e2c760
BUGCHECK_P2: d
BUGCHECK_P3: 8
BUGCHECK_P4: fffff00216e2c760
FILE_IN_CAB: 082124-16500-01.dmp
DUMP_FILE_ATTRIBUTES: 0x1008
Kernel Generated Triage Dump
FAULTING_THREAD: ffffa10e2abc8040
READ_ADDRESS: fffff8021791c470: Unable to get MiVisibleState
Unable to get NonPagedPoolStart
Unable to get NonPagedPoolEnd
Unable to get PagedPoolStart
Unable to get PagedPoolEnd
unable to get nt!MmSpecialPagesInUse
fffff00216e2c760
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: System
TRAP_FRAME: ffffa10e2abc8040 -- (.trap 0xffffa10e2abc8040)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000000
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=0000000000000000 rsp=0002000200000000 rbp=ffffa10e2abc8040
r8=0000000000000000 r9=0000000000000000 r10=0000000000000000
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up di pl nz na pe nc
00000000`00000000 ?? ???
Resetting default scope
IP_IN_FREE_BLOCK: 0
FAILED_INSTRUCTION_ADDRESS:
+0
fffff002`16e2c760 ?? ???
STACK_TEXT:
ffffd601`ca979c88 fffff802`1702bc29 : 00000000`0000000a fffff002`16e2c760 00000000`0000000d 00000000`00000008 : nt!KeBugCheckEx
ffffd601`ca979c90 fffff802`17027089 : 00000000`00000014 ffffd601`ca979ef8 00000000`00400a02 ffffa10e`2b0cd600 : nt!KiBugCheckDispatch+0x69
ffffd601`ca979dd0 fffff002`16e2c760 : fffff802`16eb76bc ffffa10e`2ab93dc0 fffff802`16e566fc ffffd601`ca9e0000 : nt!KiPageFault+0x489
ffffd601`ca979f68 fffff802`16eb76bc : ffffa10e`2ab93dc0 fffff802`16e566fc ffffd601`ca9e0000 ffffa10e`2ab8a040 : 0xfffff002`16e2c760
ffffd601`ca979f70 fffff802`17017eba : ffff8380`7f54f4b0 ffffa10e`2ab93dc0 ffffa10e`5fb520c0 00000000`00000000 : nt!KiCallInterruptServiceRoutine+0x9c
ffffd601`ca979fb0 fffff802`17018787 : 00000043`8f42575c fffff802`3f7a3257 00000043`8f06265f 00000000`00000000 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa
ffff8380`7f54f430 fffff802`1701ac7a : 00000000`00000000 00000000`00000000 ffffa10e`2abc8040 ffffa10e`501d80c0 : nt!KiInterruptDispatchNoLockNoEtw+0x37
ffff8380`7f54f5c0 00000000`00000000 : ffff8380`7f550000 ffff8380`7f549000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x5a
SYMBOL_NAME: nt!KiPageFault+489
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
IMAGE_VERSION: 10.0.22621.4036
STACK_COMMAND: .process /r /p 0xfffff80217948f40; .thread 0xffffa10e2abc8040 ; kb
BUCKET_ID_FUNC_OFFSET: 489
FAILURE_BUCKET_ID: AV_CODE_AV_BAD_IP_nt!KiPageFault
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {73cd60cc-83fa-6b76-df08-1961c31d7403}
Followup: MachineOwner
---------
Reply
Reply
S
STEVEJasonson
04-19-2025, 03:22 AM #1

Currently I am having frequently BDOS, once a week. All happen when I surf website using Edge browser
This is my dump text and mini dump file
Hope someone can help me with this
Minidump file:
https://pixeldrain.com/u/Rh3j1HQA
*******************************************************************************
* *
* 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: fffff00216e2c760, memory referenced
Arg2: 000000000000000d, IRQL
Arg3: 0000000000000008, value 0 = read operation, 1 = write operation
Arg4: fffff00216e2c760, address which referenced memory
Debugging Details:
------------------
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 1655
Key : Analysis.Elapsed.mSec
Value: 9370
Key : Analysis.IO.Other.Mb
Value: 4
Key : Analysis.IO.Read.Mb
Value: 0
Key : Analysis.IO.Write.Mb
Value: 21
Key : Analysis.Init.CPU.mSec
Value: 249
Key : Analysis.Init.Elapsed.mSec
Value: 67484
Key : Analysis.Memory.CommitPeak.Mb
Value: 99
Key : Bugcheck.Code.LegacyAPI
Value: 0xd1
Key : Bugcheck.Code.TargetModel
Value: 0xd1
Key : Dump.Attributes.AsUlong
Value: 1008
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
Key : Failure.Bucket
Value: AV_CODE_AV_BAD_IP_nt!KiPageFault
Key : Failure.Hash
Value: {73cd60cc-83fa-6b76-df08-1961c31d7403}
BUGCHECK_CODE: d1
BUGCHECK_P1: fffff00216e2c760
BUGCHECK_P2: d
BUGCHECK_P3: 8
BUGCHECK_P4: fffff00216e2c760
FILE_IN_CAB: 082124-16500-01.dmp
DUMP_FILE_ATTRIBUTES: 0x1008
Kernel Generated Triage Dump
FAULTING_THREAD: ffffa10e2abc8040
READ_ADDRESS: fffff8021791c470: Unable to get MiVisibleState
Unable to get NonPagedPoolStart
Unable to get NonPagedPoolEnd
Unable to get PagedPoolStart
Unable to get PagedPoolEnd
unable to get nt!MmSpecialPagesInUse
fffff00216e2c760
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: System
TRAP_FRAME: ffffa10e2abc8040 -- (.trap 0xffffa10e2abc8040)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000000
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=0000000000000000 rsp=0002000200000000 rbp=ffffa10e2abc8040
r8=0000000000000000 r9=0000000000000000 r10=0000000000000000
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up di pl nz na pe nc
00000000`00000000 ?? ???
Resetting default scope
IP_IN_FREE_BLOCK: 0
FAILED_INSTRUCTION_ADDRESS:
+0
fffff002`16e2c760 ?? ???
STACK_TEXT:
ffffd601`ca979c88 fffff802`1702bc29 : 00000000`0000000a fffff002`16e2c760 00000000`0000000d 00000000`00000008 : nt!KeBugCheckEx
ffffd601`ca979c90 fffff802`17027089 : 00000000`00000014 ffffd601`ca979ef8 00000000`00400a02 ffffa10e`2b0cd600 : nt!KiBugCheckDispatch+0x69
ffffd601`ca979dd0 fffff002`16e2c760 : fffff802`16eb76bc ffffa10e`2ab93dc0 fffff802`16e566fc ffffd601`ca9e0000 : nt!KiPageFault+0x489
ffffd601`ca979f68 fffff802`16eb76bc : ffffa10e`2ab93dc0 fffff802`16e566fc ffffd601`ca9e0000 ffffa10e`2ab8a040 : 0xfffff002`16e2c760
ffffd601`ca979f70 fffff802`17017eba : ffff8380`7f54f4b0 ffffa10e`2ab93dc0 ffffa10e`5fb520c0 00000000`00000000 : nt!KiCallInterruptServiceRoutine+0x9c
ffffd601`ca979fb0 fffff802`17018787 : 00000043`8f42575c fffff802`3f7a3257 00000043`8f06265f 00000000`00000000 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa
ffff8380`7f54f430 fffff802`1701ac7a : 00000000`00000000 00000000`00000000 ffffa10e`2abc8040 ffffa10e`501d80c0 : nt!KiInterruptDispatchNoLockNoEtw+0x37
ffff8380`7f54f5c0 00000000`00000000 : ffff8380`7f550000 ffff8380`7f549000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x5a
SYMBOL_NAME: nt!KiPageFault+489
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
IMAGE_VERSION: 10.0.22621.4036
STACK_COMMAND: .process /r /p 0xfffff80217948f40; .thread 0xffffa10e2abc8040 ; kb
BUCKET_ID_FUNC_OFFSET: 489
FAILURE_BUCKET_ID: AV_CODE_AV_BAD_IP_nt!KiPageFault
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {73cd60cc-83fa-6b76-df08-1961c31d7403}
Followup: MachineOwner
---------

Reply
Reply
K
Karybdus09
Junior Member
Find
30
04-19-2025, 03:22 AM
#2
Welcome to the forums, newcomer! Have you experimented with different browsers such as Chrome or Firefox?
Reply
Reply
K
Karybdus09
04-19-2025, 03:22 AM #2

Welcome to the forums, newcomer! Have you experimented with different browsers such as Chrome or Firefox?

Reply
Reply
X
x7000
Member
Find
53
04-19-2025, 03:22 AM
#3
OS and drivers are current? Sometimes using a browser and disabling hardware acceleration helps, but it suggests driver or hardware problems. IRQL NOT LESS OR EQUAL errors often stem from memory issues, whether in system or video memory. You can test this with memtestx86 and standard GPU tests (Furmark, 3D Mark).
Reply
Reply
X
x7000
04-19-2025, 03:22 AM #3

OS and drivers are current? Sometimes using a browser and disabling hardware acceleration helps, but it suggests driver or hardware problems. IRQL NOT LESS OR EQUAL errors often stem from memory issues, whether in system or video memory. You can test this with memtestx86 and standard GPU tests (Furmark, 3D Mark).

Reply
Reply
T
Thatolddog
Junior Member
Find
15
04-19-2025, 03:22 AM
#4
Hello, thank you for your welcome!
I haven't tried it before, but I think I'll use Chrome this time. Appreciate your advice.
Reply
Reply
T
Thatolddog
04-19-2025, 03:22 AM #4

Hello, thank you for your welcome!
I haven't tried it before, but I think I'll use Chrome this time. Appreciate your advice.

Reply
Reply
M
myronvisser
Member
Find
188
04-19-2025, 03:22 AM
#5
I only install drivers from Lenovo Vantage or Microsoft Update. My NVIDIA driver is quite outdated compared to the newest version, but my friend says the one from Lenovo could work best for my laptop.
I tried Furmark briefly, though only for short periods, since I worry it might damage my GPU. I haven’t used memtestx86.
Appreciate your suggestions.
Reply
Reply
M
myronvisser
04-19-2025, 03:22 AM #5

I only install drivers from Lenovo Vantage or Microsoft Update. My NVIDIA driver is quite outdated compared to the newest version, but my friend says the one from Lenovo could work best for my laptop.
I tried Furmark briefly, though only for short periods, since I worry it might damage my GPU. I haven’t used memtestx86.
Appreciate your suggestions.

Reply
Reply
S
SNEEKFREAK
Junior Member
Find
17
04-19-2025, 03:22 AM
#6
The GPU should automatically reduce performance, but this is intended for a stress test to verify its functionality. Running it for too long isn't necessary. If it stops working right away, it likely indicates a hardware issue.

memtestx86 allows you to perform a memory check across the entire system. Issues may only become apparent when memory usage spikes significantly, making them harder to spot during normal operation.

Using the manufacturer's certified driver is somewhat reliable, but over time their support may end, potentially leaving you with inferior options. You can always switch to the latest driver and reinstall the Lenovo version later. Simply perform a clean installation using the Nvidia installer or remove it via Display Driver Uninstaller after trying it.
Reply
Reply
S
SNEEKFREAK
04-19-2025, 03:22 AM #6

The GPU should automatically reduce performance, but this is intended for a stress test to verify its functionality. Running it for too long isn't necessary. If it stops working right away, it likely indicates a hardware issue.

memtestx86 allows you to perform a memory check across the entire system. Issues may only become apparent when memory usage spikes significantly, making them harder to spot during normal operation.

Using the manufacturer's certified driver is somewhat reliable, but over time their support may end, potentially leaving you with inferior options. You can always switch to the latest driver and reinstall the Lenovo version later. Simply perform a clean installation using the Nvidia installer or remove it via Display Driver Uninstaller after trying it.

Reply
Reply