Wireless
Participate in insightful discussions regarding issues related to Intel® Wireless Adapters and technologies
8521 Discussions

Blue Screen Errors occurs randomly after install AX200

Wooseong
Beginner
‎12-03-2024 05:35 PM
975 Views

Blue screen error occurs randomly after replacing the wireless LAN on my laptop with an AX200.

The WLAN driver version is 23.90.0.2, below is MEMORY.DMP.

 

For analysis of this file, run !analyze -vnt!KeBugCheckEx:
fffff802`625fe580 48894c2408      mov     qword ptr [rsp+8],rcx ss:0018:ffff8309`49f5c190=000000000000000a
2: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        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: fffff8026692d4b8, address which referenced memory

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


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 3406

    Key  : Analysis.Elapsed.mSec
    Value: 3499

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

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

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

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

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

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

    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.KiBugCheckData
    Value: 0xd1

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0xd1

    Key  : Bugcheck.Code.TargetModel
    Value: 0xd1

    Key  : Failure.Bucket
    Value: AV_NETIO!StreamInvokeCalloutAndNormalizeAction

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

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

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

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

    Key  : Hypervisor.Flags.ValueHex
    Value: 0

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

BUGCHECK_P2: 2

BUGCHECK_P3: 0

BUGCHECK_P4: fffff8026692d4b8

FILE_IN_CAB:  MEMORY.DMP

FAULTING_THREAD:  ffffb888dda1c080

READ_ADDRESS: unable to get nt!PspSessionIdBitmap
 0000000000000008 

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

PROCESS_NAME:  a2service.exe

TRAP_FRAME:  ffff830949f5c2d0 -- (.trap 0xffff830949f5c2d0)NOTE: The trap frame does not contain all registers.Some register values may be zeroed or incorrect.rax=0000000000000000 rbx=0000000000000000 rcx=ffff830949f5c5d8
rdx=ffffb888d8370790 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8026692d4b8 rsp=ffff830949f5c460 rbp=ffff830949f5c4d9
 r8=ffffb888d8370790  r9=0000000000000002 r10=ffffb888dd0bf590
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
NETIO!StreamInvokeCalloutAndNormalizeAction+0x5c:
fffff802`6692d4b8 488b4808        mov     rcx,qword ptr [rax+8] ds:00000000`00000008=????????????????
Resetting default scope

STACK_TEXT:  
ffff8309`49f5c188 fffff802`62612da9     : 00000000`0000000a 00000000`00000008 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
ffff8309`49f5c190 fffff802`6260e778     : ffffb888`dc1e7c02 00000000`0000014c ffff8309`49f5c4c0 fffff802`7a14e800 : nt!KiBugCheckDispatch+0x69
ffff8309`49f5c2d0 fffff802`6692d4b8     : ffffb888`d8370790 ffff8309`49f5c4d9 ffff8309`49f5c5a0 ffffb888`d8370790 : nt!KiPageFault+0x478
ffff8309`49f5c460 fffff802`6692d1c4     : ffff8309`49f5c8c0 ffffb888`d8370790 00000000`00000000 ffffb888`d8370790 : NETIO!StreamInvokeCalloutAndNormalizeAction+0x5c
ffff8309`49f5c530 fffff802`6692c7cf     : 00000000`00000014 fffff802`7a141310 ffffb888`00000001 ffff8309`49f5d060 : NETIO!StreamProcessCallout+0x3fc
ffff8309`49f5c660 fffff802`6692962b     : 0000ff02`00000014 ffff8309`49f5d060 ffff8309`49f5d090 ffff8309`49f5cd90 : NETIO!ProcessCallout+0x76f
ffff8309`49f5c7e0 fffff802`669281ca     : ffffb888`dd715ae0 ffffb888`d1074960 00000000`00000000 0000fe48`00000014 : NETIO!ArbitrateAndEnforce+0x71b
ffff8309`49f5c940 fffff802`6697ab9a     : 00000000`00000000 ffff8309`49f5d150 00000000`00000000 ffff8309`49f5d320 : NETIO!KfdClassify+0x37a
ffff8309`49f5cd40 fffff802`6694eefe     : ffffb888`dd0c1b30 ffff8309`49f5cf60 ffffb888`deb1dbd0 ffffb888`d9633010 : NETIO!StreamInternalClassify+0x106
ffff8309`49f5ce60 fffff802`669274fa     : ffff8309`49f5d3b0 ffffb888`d1043c20 ffffb888`deb1dbd0 00000000`00000000 : NETIO!StreamClassify+0x278ae
ffff8309`49f5d000 fffff802`66926e0d     : 00000000`00000002 ffffb888`df594420 fffff802`66922710 00000000`00000000 : NETIO!StreamCommonInspect+0x282
ffff8309`49f5d3f0 fffff802`66a5723f     : ffffb888`deb1db00 ffffb888`deaf7000 ffffb888`deaf71c8 ffffb888`deaf7010 : NETIO!WfpStreamInspectReceive+0x18d
ffff8309`49f5d480 fffff802`66a5618f     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : tcpip!TcpTcbFastDatagram+0xe1f
ffff8309`49f5d650 fffff802`66a5552f     : 00000000`00000028 00000000`00000000 00000000`000102e1 ffffb888`d80492e0 : tcpip!TcpTcbReceive+0x18f
ffff8309`49f5d8a0 fffff802`66a546fd     : 00000000`00000000 ffffb888`d10fc9e0 00000000`bc2364a7 00000000`7f000001 : tcpip!TcpMatchReceive+0x51f
ffff8309`49f5db50 fffff802`66a819b2     : ffffb888`d1210c10 00000000`00000001 ffffffff`00000002 ffffb888`d8049201 : tcpip!TcpReceive+0x44d
ffff8309`49f5dc40 fffff802`66a4a9dc     : ffffb888`deb1dbd0 ffffb888`da218040 00000000`49f50100 ffffb888`ceffe4c0 : tcpip!TcpNlClientReceiveDatagrams+0x22
ffff8309`49f5dc80 fffff802`66a470ba     : 00000000`00000000 ffffb888`d80492e0 00000000`00000000 fffff802`66bf9a70 : tcpip!IppProcessDeliverList+0xcc
ffff8309`49f5dd60 fffff802`66a4783f     : 00000000`00000001 00000000`00000000 fffff802`66bf9a70 ffff8309`49f5df10 : tcpip!IppReceiveHeaderBatch+0x3aa
ffff8309`49f5de60 fffff802`66a474b8     : 00000000`00000000 00000000`00000000 00000000`00000000 ffff8309`4aea661a : tcpip!IppLbIndicatePackets+0x26f
ffff8309`49f5df10 fffff802`62602dee     : ffffb888`d11f7220 ffff8309`49f5dfd0 ffffb888`dda1c080 ffff8309`4d963580 : tcpip!IppLbTransmitStackCallout+0x2a8
ffff8309`49f5df80 fffff802`62602dac     : ffff8309`49f5dfd0 ffffb888`dda1c080 ffff8309`49f5e000 fffff802`62490d4d : nt!KxSwitchKernelStackCallout+0x2e
ffff8309`4d963580 fffff802`62490d4d     : ffff8309`49f5dfd0 ffffb888`dda1c080 ffff8309`4d96361a 00000000`00000000 : nt!KiSwitchKernelStackContinue
ffff8309`4d9635a0 fffff802`62490b42     : fffff802`66a47210 ffff8309`4d963810 ffff8309`00000002 00000000`00000002 : nt!KiExpandKernelStackAndCalloutOnStackSegment+0x19d
ffff8309`4d963640 fffff802`624909a3     : ffff8309`4d963860 ffffb888`d11f7220 00000000`00000002 00000000`00000000 : nt!KiExpandKernelStackAndCalloutSwitchStack+0xf2
ffff8309`4d9636b0 fffff802`6249095d     : fffff802`66a47210 ffff8309`4d963810 ffffb888`d11761e0 00000000`00000001 : nt!KeExpandKernelStackAndCalloutInternal+0x33
ffff8309`4d963720 fffff802`66a48699     : ffffb888`d11f7220 ffffb888`d11761e0 ffffb888`deb1dbd0 ffffb888`ceffe4c0 : nt!KeExpandKernelStackAndCalloutEx+0x1d
ffff8309`4d963760 fffff802`66a4624b     : ffffb888`d116b8a8 00000000`00000080 00000000`00000000 ffff8309`4d963a29 : tcpip!IppLoopbackEnqueue+0x729
ffff8309`4d9639c0 fffff802`66a45c38     : ffffb888`d116b8a8 00000000`00000000 00000000`00000000 00000000`0000cd7a : tcpip!IppDispatchSendPacketHelper+0x35f
ffff8309`4d963a90 fffff802`66a443d7     : ffffb888`d116b8a8 00000000`00000007 00000000`00000000 ffffb888`d116b8a8 : tcpip!IppPacketizeDatagrams+0x2e8
ffff8309`4d963bc0 fffff802`66a42eed     : 00000000`00000001 00000000`00000000 fffff802`66bf9a70 ffffb888`d8d40ce0 : tcpip!IppSendDatagramsCommon+0x497
ffff8309`4d963d40 fffff802`66a11eff     : ffffb888`da218040 ffff8309`00000014 00000000`00000000 ffffb888`d8d40ce0 : tcpip!IpNlpFastSendDatagram+0x34d
ffff8309`4d963e00 fffff802`66a10244     : ffffb888`d109bbd0 00000000`00989680 ffffb888`d800f4e0 00000012`148a6d0c : tcpip!TcpTcbSend+0x173f
ffff8309`4d964190 fffff802`66a0feae     : 00000000`00000000 00000000`00000000 ffff8309`4d9643f0 fffff802`66a0fe80 : tcpip!TcpEnqueueTcbSend+0x374
ffff8309`4d9642d0 fffff802`624909e8     : ffffb888`de25f001 00000000`00000000 00000000`00000000 00000000`00000001 : tcpip!TcpTlConnectionSendCalloutRoutine+0x2e
ffff8309`4d964310 fffff802`6249095d     : fffff802`66a0fe80 ffff8309`4d9643f0 ffffb888`d7827cc0 00000000`00000000 : nt!KeExpandKernelStackAndCalloutInternal+0x78
ffff8309`4d964380 fffff802`66a79560     : 00000000`00000000 00000000`00000000 ffffb888`d12fd240 fffff802`7a2821d0 : nt!KeExpandKernelStackAndCalloutEx+0x1d
ffff8309`4d9643c0 fffff802`7a27fd00     : ffffb888`d7827cc0 ffffb888`de25f050 00000000`00000002 ffffb888`d7827cc0 : tcpip!TcpTlConnectionSend+0x80
ffff8309`4d964430 fffff802`7a27fb2a     : ffffb888`de25f050 ffff8309`4d964c00 ffffb888`de2ca810 ffffb888`d7827d80 : afd!AfdTLStartBufferedVcSend+0xa0
ffff8309`4d9644e0 fffff802`7a265130     : ffffb888`d7827cc0 fffff802`62450952 ffffb888`00000002 ffff8309`4d9649d0 : afd!AfdFastConnectionSend+0x2a2
ffff8309`4d9645b0 fffff802`62831cd6     : 00000000`00000000 00000000`00000000 ffff8309`4d964c00 ffffb888`de3571c0 : afd!AfdFastIoDeviceControl+0xf90
ffff8309`4d964950 fffff802`62831536     : 00000000`00000000 00000000`00000f98 00000000`00000000 00000000`00000000 : nt!IopXxxControlFile+0x786
ffff8309`4d964aa0 fffff802`62612505     : 00000000`00000000 00000000`00000001 00000000`00000000 ffffb888`da51ffe0 : nt!NtDeviceIoControlFile+0x56
ffff8309`4d964b10 00007ffa`c958d5d4     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x25
00000000`0ddcf538 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffa`c958d5d4


SYMBOL_NAME:  NETIO!StreamInvokeCalloutAndNormalizeAction+5c

MODULE_NAME: NETIO

IMAGE_NAME:  NETIO.SYS

STACK_COMMAND:  .process /r /p 0xffffb888d7bf2080; .thread 0xffffb888dda1c080 ; kb

BUCKET_ID_FUNC_OFFSET:  5c

FAILURE_BUCKET_ID:  AV_NETIO!StreamInvokeCalloutAndNormalizeAction

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

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

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

0 Kudos

Link Copied

5 Replies
RandyT_Intel
Moderator
‎01-15-2025 08:05 PM
885 Views

Hi Wooseong,

 

Could you please let us know the reason for this change? The error you are encountering is expected. Kindly check this article for more information: Why Doesn't My Laptop Recognize My New Intel® Wireless... & Regulatory Information Regarding Wireless Hardware Installation or...

 

Replacing an adapter associated with specific wireless software and a different adapter type may cause connection issues or software error messages. For example, if you replace a Wi-Fi/WiMAX adapter with a Wi-Fi adapter, you may receive WiMAX error messages and lose connectivity to the WiMAX network.

 

Best regards, 

 

Randy T. 

Intel Customer Support Technician 


0 Kudos
Copy link
RandyT_Intel
Moderator
‎01-21-2025 12:54 PM
808 Views

Hi Wooseong,

 

I wanted to follow up regarding the questions and information we shared with you recently. Have you had a chance to review them? Your feedback is invaluable in helping us determine the next best course of action. 

 

Please let me know if you have any thoughts or if there's anything else you need from us. 

Looking forward to your response! 

  

Best regards, 

 

Randy T. 

Intel Customer Support Technician 


0 Kudos
Copy link
RandyT_Intel
Moderator
‎01-26-2025 12:53 PM
762 Views

Hi Wooseong,


Since I have not received any response from you, I will proceed with closing this ticket. Please note that this case will no longer be monitored. 


If you have any new questions or inquiries, kindly submit another ticket, and we will be happy to assist you. 

 

Best regards, 


Randy T. 

Intel Customer Support Technician 


0 Kudos
Copy link
RandyT_Intel
Moderator
‎01-27-2025 02:37 PM
745 Views

Hi Wooseong,

 

The only retail wireless adapters currently supported by Intel are the Intel® Wi-Fi6 (Gig+) desktop kit. These retail products are intended to be installed in Desktop PC with the antennas bundled in the box. They are not intended for wireless adapter upgrade in laptop PC. If restore to previous wi-fi card and no BSOD issue then check with OEM hardware support for compatibility of AX200 card self-integration.

 

Kindly check this article for your reference: Blue Screen Error (BSOD) While Using Intel® Wi-Fi Cards

 

Best regards, 

 

Randy T. 

Intel Customer Support Technician 


0 Kudos
Copy link
Wooseong
Beginner
‎01-27-2025 04:08 PM
726 Views

Sorry for late reply.

I think Adguard and Emsisoft Anti-Malware were the cause of this problem.
No more errors have occurred since I disabled the use of the WFP Network Driver in Adguard.

0 Kudos
Copy link
Reply

Community support is provided Monday to Friday. Other contact methods are available here.

Intel does not verify all solutions, including but not limited to any file transfers that may appear in this community. Accordingly, Intel disclaims all express and implied warranties, including without limitation, the implied warranties of merchantability, fitness for a particular purpose, and non-infringement, as well as any warranty arising from course of performance, course of dealing, or usage in trade.

For more complete information about compiler optimizations, see our Optimization Notice.