Share via

Help with BSOD

Anonymous
2023-10-17T00:16:01+00:00

My computer recently has been having BSOD with the error IRQL NOT LESS OR EQUAL. Here's a copy of the dump file's most recent error. Could someone help me fix this?

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: 00000000000007b8, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff80460ef808f, address which referenced memory

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

*** WARNING: Check Image - Checksum mismatch - Dump: 0x11b52, File: 0x954c - C:\ProgramData\Dbg\sym\hal.dll\1A7BE8E96000\hal.dll

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 3328

    Key  : Analysis.Elapsed.mSec
    Value: 4635

    Key  : Analysis.IO.Other.Mb
    Value: 23

    Key  : Analysis.IO.Read.Mb
    Value: 15

    Key  : Analysis.IO.Write.Mb
    Value: 45

    Key  : Analysis.Init.CPU.mSec
    Value: 468

    Key  : Analysis.Init.Elapsed.mSec
    Value: 30496

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

    Key  : Bugcheck.Code.KiBugCheckData
    Value: 0xd1

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0xd1

    Key  : Failure.Bucket
    Value: AV_rt640x64!unknown_function

    Key  : Failure.Hash
    Value: {2e96e72d-48ac-dceb-22bd-11e71513e43e}

    Key  : Hypervisor.Enlightenments.Value
    Value: 0

    Key  : Hypervisor.Enlightenments.ValueHex
    Value: 0

    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: 1020000

    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: 0

    Key  : SecureKernel.HalpHvciEnabled
    Value: 0

    Key  : WER.OS.Branch
    Value: vb_release

    Key  : WER.OS.Version
    Value: 10.0.19041.1

BUGCHECK_CODE:  d1

BUGCHECK_P1: 7b8

BUGCHECK_P2: 2

BUGCHECK_P3: 0

BUGCHECK_P4: fffff80460ef808f

FILE_IN_CAB:  MEMORY.DMP

READ_ADDRESS:  00000000000007b8 

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXPNP: 1 (!blackboxpnp)

BLACKBOXWINLOGON: 1

PROCESS_NAME:  System

TRAP_FRAME:  ffffc48e4f0306b0 -- (.trap 0xffffc48e4f0306b0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff8045be58098 rbx=0000000000000000 rcx=fffff8045bdb2a70
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80460ef808f rsp=ffffc48e4f030840 rbp=ffffc48e4f030940
 r8=0000000000000000  r9=0000000000000000 r10=fffff8045932b8a0
r11=ffffc48e4f030780 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
rt640x64+0x2808f:
fffff804`60ef808f 4a8b94efb8070000 mov     rdx,qword ptr [rdi+r13*8+7B8h] ds:00000000`000007b8=????????????????
Resetting default scope

STACK_TEXT:  
ffffc48e`4f030568 fffff804`59411729     : 00000000`0000000a 00000000`000007b8 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
ffffc48e`4f030570 fffff804`5940d2e3     : 00000000`00000001 ffff9e85`63d20760 00000000`00000000 fffff804`5cb9c0c6 : nt!KiBugCheckDispatch+0x69
ffffc48e`4f0306b0 fffff804`60ef808f     : 00000000`00000000 fffff804`5bdb2b30 ffffc48e`4f030940 00000000`00000000 : nt!KiPageFault+0x463
ffffc48e`4f030840 fffff804`60ed3571     : fffff804`5bdb2a70 fffff804`5bdb2a70 ffff9e85`6072f000 00000000`00000004 : rt640x64+0x2808f
ffffc48e`4f0309a0 fffff804`5c626df8     : 00000000`00000000 ffff9e85`63859010 00000000`00000000 ffff9e85`00000000 : rt640x64+0x3571
ffffc48e`4f030a10 fffff804`5c6272ec     : ffff9e85`638593f8 00000000`0000000a 00000000`00000001 00000000`00000000 : ndis!ndisMiniportDpc+0xf0
ffffc48e`4f030aa0 fffff804`5c617dfb     : ffff9e85`599bf020 ffff9e85`599bf020 ffffc48e`4f030ba9 fffff804`5c5f7100 : ndis!ndisQueuedMiniportDpcWorkItem+0x11c
ffffc48e`4f030b40 fffff804`5930e6f5     : ffff9e85`5ffcc040 ffff9e85`5ffcc040 fffff804`5c5f7130 00000000`00000000 : ndis!ndisReceiveWorkerThread+0x20ccb
ffffc48e`4f030c10 fffff804`59406278     : ffff8d01`0785d180 ffff9e85`5ffcc040 fffff804`5930e6a0 00000000`00000000 : nt!PspSystemThreadStartup+0x55
ffffc48e`4f030c60 00000000`00000000     : ffffc48e`4f031000 ffffc48e`4f02b000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28

SYMBOL_NAME:  rt640x64+2808f

MODULE_NAME: rt640x64

IMAGE_NAME:  rt640x64.sys

STACK_COMMAND:  .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET:  2808f

FAILURE_BUCKET_ID:  AV_rt640x64!unknown_function

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {2e96e72d-48ac-dceb-22bd-11e71513e43e}

Followup:     MachineOwner
---------
Windows for home | Windows 10 | Performance and system failures

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments

1 answer

Sort by: Most helpful
  1. Nao Tomori 6,520 Reputation points
    2023-10-17T01:16:03+00:00

    Hi Travis, I will try to help you solve this problem together!

    From the dmp file, it looks like the network-related driver RT640x64.sys caused BSOD.

    recommendations

    1. Download the network card driver from the official website of the equipment supplier and install it, including wired, wireless and Bluetooth drivers. Do not use third party driver installers.
    2. Perform system file repair Right-click the Start button (the button of the Microsoft icon) →"Windows PowerShell(I)(Administrator)(A)" → Enter:

    Dism /Online /Cleanup-Image /ScanHealth(press Enter)

    Dism /Online /Cleanup-Image /CheckHealth(press Enter)

    DISM /Online /Cleanup-image /RestoreHealth(press Enter)

    When you are done, restart the computer and type again: sfc /SCANNOW (press Enter)

    1. Check and uninstall system optimization applications
    2. Confirm whether it is caused by system update. It is recommended to pause the update for a period of time.

    I hope the above advice helps you! If not resolved, please click "Reply" to feed back relevant information and pictures

    [The following is not a reply]

    I am not a Microsoft employee or customer service worker and my response will be within 24 hours.

    Was this answer helpful?

    0 comments No comments