**************************************************...
Создано: 20 февраля 2025 г.
Отвечено с использованием O3 Mini High от Chat01
Создано: 20 февраля 2025 г.
Отвечено с использованием O3 Mini High от Chat01
*
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: fffff80265a47618, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000008, value 0 = read operation, 1 = write operation
Arg4: fffff80265a47618, address which referenced memory
KEY_VALUES_STRING: 1
textKey : Analysis.CPU.mSec Value: 3953 Key : Analysis.Elapsed.mSec Value: 4000 Key : Analysis.IO.Other.Mb Value: 4 Key : Analysis.IO.Read.Mb Value: 1 Key : Analysis.IO.Write.Mb Value: 9 Key : Analysis.Init.CPU.mSec Value: 734 Key : Analysis.Init.Elapsed.mSec Value: 34460 Key : Analysis.Memory.CommitPeak.Mb Value: 86 Key : Analysis.Version.DbgEng Value: 10.0.27725.1000 Key : Analysis.Version.Description Value: 10.2408.27.01 amd64fre Key : Analysis.Version.Ext Value: 1.2408.27.1 Key : Bugcheck.Code.LegacyAPI Value: 0xd1 Key : Bugcheck.Code.TargetModel Value: 0xd1 Key : Dump.Attributes.AsUlong Value: 21008 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_PAGED_IP_RTKVHD64!unknown_function Key : Failure.Hash Value: {7de95530-a788-fa1c-8c95-ad3d348828b4}
BUGCHECK_CODE: d1
BUGCHECK_P1: fffff80265a47618
BUGCHECK_P2: 2
BUGCHECK_P3: 8
BUGCHECK_P4: fffff80265a47618
FILE_IN_CAB: 022025-7531-01.dmp
DUMP_FILE_ATTRIBUTES: 0x21008
Kernel Generated Triage Dump
FAULTING_THREAD: ffffd40eaa627040
READ_ADDRESS: Unable to get size of nt!_MMPTE - probably bad symbols
unable to get nt!MmSpecialPagesInUse
fffff80265a47618
IP_IN_PAGED_CODE:
RTKVHD64+147618
fffff802`65a47618 ?? ???
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1
CUSTOMER_CRASH_COUNT: 1
TRAP_FRAME: ffffac88f5d898e0 -- (.trap 0xffffac88f5d898e0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000300 rbx=0000000000000000 rcx=ffffffff0004001c
rdx=0000000000000070 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80265a47618 rsp=ffffac88f5d89a78 rbp=0000000000000000
r8=fffff802659c4600 r9=0000000000000000 r10=ffffc180b28c0180
r11=0000000000003700 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
RTKVHD64+0x147618:
fffff802`65a47618 ?? ???
Resetting default scope
FAILED_INSTRUCTION_ADDRESS:
RTKVHD64+147618
fffff802`65a47618 ?? ???
STACK_TEXT:
ffffac88f5d89798 fffff802
b468cee9 : 000000000000000a fffff802
65a47618 0000000000000002 00000000
00000008 : nt!KeBugCheckEx
ffffac88f5d897a0 fffff802
b46881a8 : ffffac88f5d89908 ffffd40e
9cd3483c ffffd40e9cd31000 00000000
00000000 : nt!KiBugCheckDispatch+0x69
ffffac88f5d898e0 fffff802
65a47618 : fffff80265999a58 ffffd40e
a058b000 ffffd40ebc59bd40 00000000
00000000 : nt!KiPageFault+0x468
ffffac88f5d89a78 fffff802
65999a58 : ffffd40ea058b000 ffffd40e
bc59bd40 0000000000000000 00000000
00000000 : RTKVHD64+0x147618
ffffac88f5d89a80 ffffd40e
a058b000 : ffffd40ebc59bd40 00000000
00000000 0000000000000000 00000000
00000300 : RTKVHD64+0x99a58
ffffac88f5d89a88 ffffd40e
bc59bd40 : 0000000000000000 00000000
00000000 0000000000000300 00000000
00000fff : 0xffffd40ea058b000 ffffac88
f5d89a90 0000000000000000 : 00000000
00000000 0000000000000300 00000000
00000fff 0000000000000000 : 0xffffd40e
bc59bd40
STACK_COMMAND: .thread /r /p 0xffffd40eaa627040 ; kb
SYMBOL_NAME: RTKVHD64+147618
MODULE_NAME: RTKVHD64
IMAGE_NAME: RTKVHD64.sys
BUCKET_ID_FUNC_OFFSET: 147618
FAILURE_BUCKET_ID: AV_CODE_AV_PAGED_IP_RTKVHD64!unknown_function
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {7de95530-a788-fa1c-8c95-ad3d348828b4}
PROCESS_NAME: Unknown
Followup: MachineOwner
This blue screen—Bugcheck DRIVER_IRQL_NOT_LESS_OR_EQUAL (0xd1)—indicates that a driver tried to access memory that wasn’t safe to touch at its current interrupt request level (IRQL). In this case, the crash points to the module RTKVHD64.sys.
Invalid Memory Access at High IRQL:
The error shows that an attempt was made to access a memory address (fffff80265a47618) that is either paged out or otherwise invalid while the CPU was running at IRQL 2 (which is too high for accessing pageable memory). Normally, pageable memory can only be safely accessed at lower IRQLs.
Faulty Driver (RTKVHD64.sys):
The call stack indicates the failure occurred within RTKVHD64.sys. This driver is not part of the core Windows kernel; it belongs to a third-party component (typically associated with Realtek hardware). The driver appears to have improperly handled memory access, which resulted in the bugcheck.
Bugcheck Arguments:
Call Stack Analysis:
The stack trace begins with the system’s bugcheck handler (nt!KeBugCheckEx) and passes through the page fault handling routines before reaching the RTKVHD64.sys module. This progression shows that the error originated when the driver attempted to perform an invalid memory operation at an inappropriate IRQL.
Update or Reinstall the Driver:
Since RTKVHD64.sys is likely part of a Realtek driver package, the first step is to check for any available updates from your hardware manufacturer or Realtek’s official website. An updated driver may have corrected this memory handling issue.
Driver Verifier:
Running Windows’ Driver Verifier can help confirm if RTKVHD64.sys is the culprit. However, be cautious—Driver Verifier can stress drivers and cause additional blue screens if the problematic driver is still in use.
Check for Conflicts or Corruption:
If updating doesn’t help, consider uninstalling the driver to see if the system stabilizes. Sometimes, reinstalling or even disabling the problematic hardware (if it’s non-critical) can resolve the issue.
System and Memory Diagnostics:
Although the dump points to a driver issue, it’s also useful to run system file and memory diagnostics to ensure there’s no underlying hardware or system corruption.
This crash is a strong indication of a driver bug where RTKVHD64.sys is accessing memory in an unsafe manner. Addressing it typically involves updating or reinstalling the driver, or in some cases, adjusting system settings to prevent the problematic driver from loading.
If you need further assistance with updating drivers or running diagnostics, let me know, and I can provide more detailed steps.
用中文回答
该蓝屏错误(Bugcheck DRIVER_IRQL_NOT_LESS_OR_EQUAL,错误码 0xd1)表明,在当前中断请求级别(IRQL)下,某个驱动程序试图访问一个不允许访问的内存地址,导致系统崩溃。错误信息中显示问题出在 RTKVHD64.sys 模块。
非法内存访问
系统在 IRQL 2 的高优先级下尝试访问内存地址(fffff80265a47618)。通常,可分页内存只能在较低 IRQL 下安全访问,因此这种操作是不允许的。
问题驱动程序 – RTKVHD64.sys
RTKVHD64.sys 通常属于 Realtek 驱动程序,错误调用栈表明该驱动在内存访问时处理不当,从而导致了系统崩溃。
Bugcheck 参数解释:
调用栈分析:
调用栈显示,系统先通过 nt!KeBugCheckEx 进入错误处理,再经过页面错误处理流程,最后在 RTKVHD64.sys 模块中发生错误。这进一步确认了问题出在该驱动上。
更新或重装驱动程序
使用 Driver Verifier 工具
系统和内存诊断
该蓝屏错误主要由 Realtek 驱动(RTKVHD64.sys)在高 IRQL 下非法访问内存引起。通过更新驱动、使用 Driver Verifier 检测问题、以及进行系统和内存检查,通常可以定位并解决这一问题。
如需更详细的操作步骤或其他帮助,请继续提问。
用中文回答
该蓝屏错误(DRIVER_IRQL_NOT_LESS_OR_EQUAL,错误码 0xd1)表明系统在高中断请求级别(IRQL)下试图访问不可用的内存地址,这通常是由于驱动程序错误导致的。
非法内存访问
系统在 IRQL 2 下试图访问地址 fffff80265a47618,而可分页内存只能在较低 IRQL 下安全访问。因此,该操作被视为非法,触发了蓝屏。
问题驱动程序 RTKVHD64.sys
调用栈显示错误发生在 RTKVHD64.sys 模块,该驱动程序通常属于 Realtek 硬件驱动。驱动程序在高IRQL下使用了不适当的内存地址,导致内存访问异常。
Bugcheck 参数说明:
调用栈信息:
从 nt!KeBugCheckEx 到 RTKVHD64.sys 的调用路径表明,问题在驱动程序执行时出现,最终导致系统通过内核错误处理机制触发蓝屏。
更新或重装驱动程序
前往 Realtek 或计算机厂商官网,下载并安装最新版本的驱动程序,可能可以解决驱动程序中存在的内存访问错误。
使用 Driver Verifier 工具
Windows 内置的 Driver Verifier 可以帮助检测有问题的驱动程序。但使用时请谨慎,因为它会加大系统负荷,建议在备份数据后使用。
进行系统与硬件检测
sfc /scannow
检查并修复系统文件。该蓝屏错误主要是由 Realtek 驱动程序(RTKVHD64.sys)在高IRQL下非法访问内存引起的。通过更新或重装驱动、使用 Driver Verifier 检查问题,并对系统和硬件进行全面诊断,一般可以解决此问题。
如果需要进一步操作的详细步骤或其他帮助,请继续提问。