Puzzling BSOD DRVIVER_IRQL_NOT_LESS_OR_EQUAL - NETIO.sys - W11/25H2 - WRX90

Hi guys

After dealing with this for like 6 months I’m completely at a loss about those quite regular BSOD on NETIO.sys. I’m really out of ideas.

Sfc /scannow produces no errors. DISM is up to date, no corrupted files, no errors and at 26200.8875 which is version I’m running. Intel drivers for X710 on my Asus WRX90 are up to date (31.2.2).

I’m not doing anything special. Fortunately yesterday it happened after I finished rendering and was just listening to music and light late gaming in Mass Effect Andromeda multiplayer. Previous one I was just watching YT video on the weekend. It’s all so unbelievably weird. It’s certainly no RAM overheating, hottest DIMM stick is now literally 48.5C and rendering now for nearly 7 hours.

All dumps are basically identical, only memory region changes. Below crash dump view from BlueScreenView. Memory dump analysis looks like:

Loading unloaded module list
.........
*******************************************************************************
*                                                                             *
*                        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: 0000000000000008, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff8010ecc3f88, address which referenced memory

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


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 781

    Key  : Analysis.Elapsed.mSec
    Value: 838

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

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

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

    Key  : Analysis.Version.DbgEng
    Value: 10.0.29617.1000

    Key  : Analysis.Version.Description
    Value: 10.2604.29.1 amd64fre

    Key  : Analysis.Version.Ext
    Value: 1.2604.29.1

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0xd1

    Key  : Bugcheck.Code.TargetModel
    Value: 0xd1

    Key  : Dump.Attributes.AsUlong
    Value: 0x21008

    Key  : Dump.Attributes.DiagDataWrittenToHeader
    Value: 1

    Key  : Dump.Attributes.ErrorCode
    Value: 0x0

    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_NETIO!StreamInvokeCalloutAndNormalizeAction

    Key  : Failure.Exception.IP.Address
    Value: 0xfffff8010ecc3f88

    Key  : Failure.Exception.IP.Module
    Value: NETIO

    Key  : Failure.Exception.IP.Offset
    Value: 0x23f88

    Key  : Failure.Hash
    Value: {c2ca2d1f-cfdc-88d5-c7bc-7693b8f0de04}

    Key  : Faulting.IP.Type
    Value: Paged

    Key  : WER.System.BIOSRevision
    Value: 13.17.0.0


BUGCHECK_CODE:  d1

BUGCHECK_P1: 8

BUGCHECK_P2: 2

BUGCHECK_P3: 0

BUGCHECK_P4: fffff8010ecc3f88

FILE_IN_CAB:  090826-20421-01.dmp

DUMP_FILE_ATTRIBUTES: 0x21008
  Kernel Generated Triage Dump

FAULTING_THREAD:  ffffb28a4d6f5300

READ_ADDRESS: fffff8017c1c54d8: Unable to get MiVisibleState
 0000000000000008 

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1 (!blackboxwinlogon) (!blackboxwinlogonnotify)


CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

IP_IN_PAGED_CODE: 
NETIO!StreamInvokeCalloutAndNormalizeAction+5c
fffff801`0ecc3f88 488b4808        mov     rcx,qword ptr [rax+8]

STACK_TEXT:  
ffff8406`46c6f6d8 fffff801`7b8bfbe9     : 00000000`0000000a 00000000`00000008 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
ffff8406`46c6f6e0 fffff801`7b8baea8     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
ffff8406`46c6f820 fffff801`0ecc3f88     : ffff8406`46c6fb02 00000000`00000000 ffffb28a`8dcd6ae0 ffffb28a`01a13250 : nt!KiPageFault+0x468
ffff8406`46c6f9b0 fffff801`0ecc398b     : ffffb28a`703eb320 ffffb28a`13b30001 ffffb28a`8dcd6ae0 ffffb28a`8dcd6ae0 : NETIO!StreamInvokeCalloutAndNormalizeAction+0x5c
ffff8406`46c6fab0 fffff801`0ecc2524     : ffff8406`410c5850 ffff8406`46c6fbf0 00000000`00000000 fffff801`27e51601 : NETIO!StreamCalloutProcessingLoop+0x147
ffff8406`46c6fb70 fffff801`0ecc08d1     : ffffb289`b2a40014 fffff801`31242cf0 ffff8406`00000004 ffff8406`410c5b18 : NETIO!StreamProcessCallout+0x2f4
ffff8406`46c6fca0 fffff801`0ecef2ef     : 00000000`00000001 ffff8406`410c5b18 ffff8406`410c5b30 ffff8406`410c5850 : NETIO!ProcessCallout+0x821
ffff8406`46c6fd90 fffff801`0ecf27ad     : 00000000`00000000 ffff8406`44ed5690 ffff8406`44ed5700 ffffb28a`570ce2c0 : NETIO!ArbitrateAndEnforce+0x5af
ffff8406`46c6ff00 fffff801`7b8ac98e     : ffff8406`46c6ffb0 ffff8406`44ed5161 ffffb28a`822e7080 00000000`00000000 : NETIO!ArbitrateAndEnforceCallout+0x4d
ffff8406`46c6ff60 fffff801`7b8ac94b     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxSwitchKernelStackCallout+0x2e
ffff8406`410c51e0 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSwitchKernelStackContinue


SYMBOL_NAME:  NETIO!StreamInvokeCalloutAndNormalizeAction+5c

MODULE_NAME: NETIO

IMAGE_NAME:  NETIO.SYS

IMAGE_VERSION:  10.0.26100.8875

STACK_COMMAND: .process /r /p 0xffffb289abae7040; .thread /r /p 0xffffb28a4d6f5300 ; kb

BUCKET_ID_FUNC_OFFSET:  5c

FAILURE_BUCKET_ID:  AV_NETIO!StreamInvokeCalloutAndNormalizeAction

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {c2ca2d1f-cfdc-88d5-c7bc-7693b8f0de04}

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

添加评论
点赞收藏
点踩分享查看原文
评论
?
参与讨论