Frequent Win10 BSOD on netwtw14.sys / Intel Wi-Fi BE200 320MHz / ThinkPad P1G7

[ajkessel]

Driver 23.40.0.4, Windows 10 22H2, Thinkpad P1G7 (2024 model), frequent BSOD on netwtw14.sys.

Is this the best place to report that? I don't see any place to file bug reports directly with Intel.

I've attached an SSU and windbg output, also pasted below. I have a full ~3GB MEMORY.DMP if that would be helpful, too.

BSOD is SYSTEM_THREAD_EXCEPTION_NOT_HANDLED on Netwtw14.sys.

*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED (7e)
This is a very common BugCheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff801a659cff0, The address that the exception occurred at
Arg3: ffffd10b3aaa7598, Exception Record Address
Arg4: ffffd10b3aaa6dd0, Context Record Address

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

KEY_VALUES_STRING: 1

Key : AV.Dereference
Value: NullClassPtr

Key : AV.Fault
Value: Read

Key : Analysis.CPU.mSec
Value: 4109

Key : Analysis.Elapsed.mSec
Value: 4225

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

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

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

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

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

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

Key : Bugcheck.Code.KiBugCheckData
Value: 0x7e

Key : Bugcheck.Code.LegacyAPI
Value: 0x7e

Key : Bugcheck.Code.TargetModel
Value: 0x7e

Key : Failure.Bucket
Value: AV_Netwtw14!unknown_function

Key : Failure.Hash
Value: {9cecd452-9765-c26a-c871-ea518a6e234e}

Key : Hypervisor.Enlightenments.Value
Value: 68673420

Key : Hypervisor.Enlightenments.ValueHex
Value: 417df8c

Key : Hypervisor.Flags.AnyHypervisorPresent
Value: 1

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

Key : Hypervisor.Flags.DeprecateAutoEoi
Value: 1

Key : Hypervisor.Flags.DynamicCpuDisabled
Value: 1

Key : Hypervisor.Flags.Epf
Value: 0

Key : Hypervisor.Flags.ExtendedProcessorMasks
Value: 1

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

Key : Hypervisor.Flags.Phase0InitDone
Value: 1

Key : Hypervisor.Flags.PowerSchedulerQos
Value: 0

Key : Hypervisor.Flags.RootScheduler
Value: 0

Key : Hypervisor.Flags.SynicAvailable
Value: 1

Key : Hypervisor.Flags.UseQpcBias
Value: 0

Key : Hypervisor.Flags.Value
Value: 21631230

Key : Hypervisor.Flags.ValueHex
Value: 14a10fe

Key : Hypervisor.Flags.VpAssistPage
Value: 1

Key : Hypervisor.Flags.VsmAvailable
Value: 1

Key : Hypervisor.RootFlags.AccessStats
Value: 1

Key : Hypervisor.RootFlags.CrashdumpEnlightened
Value: 1

Key : Hypervisor.RootFlags.CreateVirtualProcessor
Value: 1

Key : Hypervisor.RootFlags.DisableHyperthreading
Value: 0

Key : Hypervisor.RootFlags.HostTimelineSync
Value: 1

Key : Hypervisor.RootFlags.HypervisorDebuggingEnabled
Value: 0

Key : Hypervisor.RootFlags.IsHyperV
Value: 1

Key : Hypervisor.RootFlags.LivedumpEnlightened
Value: 1

Key : Hypervisor.RootFlags.MapDeviceInterrupt
Value: 1

Key : Hypervisor.RootFlags.MceEnlightened
Value: 1

Key : Hypervisor.RootFlags.Nested
Value: 0

Key : Hypervisor.RootFlags.StartLogicalProcessor
Value: 1

Key : Hypervisor.RootFlags.Value
Value: 1015

Key : Hypervisor.RootFlags.ValueHex
Value: 3f7

Key : SecureKernel.HalpHvciEnabled
Value: 0

Key : WER.OS.Branch
Value: vb_release

Key : WER.OS.Version
Value: 10.0.19041.1

BUGCHECK_CODE: 7e

BUGCHECK_P1: ffffffffc0000005

BUGCHECK_P2: fffff801a659cff0

BUGCHECK_P3: ffffd10b3aaa7598

BUGCHECK_P4: ffffd10b3aaa6dd0

FILE_IN_CAB: MEMORY.DMP

FAULTING_THREAD: ffff858e5be29040

EXCEPTION_RECORD: ffffd10b3aaa7598 -- (.exr 0xffffd10b3aaa7598)
ExceptionAddress: fffff801a659cff0 (Netwtw14+0x000000000011cff0)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: 0000000000000028
Attempt to read from address 0000000000000028

CONTEXT: ffffd10b3aaa6dd0 -- (.cxr 0xffffd10b3aaa6dd0)
rax=0000000000000000 rbx=fffff801a68e2000 rcx=fffff801a68e2000
rdx=ffff858e6ec63150 rsi=ffff9f8b45d32b60 rdi=ffff858e6ec63150
rip=fffff801a659cff0 rsp=ffffd10b3aaa77d0 rbp=0000000000000000
r8=ffffd10b3aaa7964 r9=7ffff8006ee454e0 r10=fffff801a659cef0
r11=0000000000000000 r12=000000000000fffe r13=0000000000000000
r14=ffffd10b3aaa7964 r15=ffff9f8b45d32b00
iopl=0 nv up ei pl zr na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00050246
Netwtw14+0x11cff0:
fffff801`a659cff0 488b4d28 mov rcx,qword ptr [rbp+28h] ss:0018:00000000`00000028=????????????????
Resetting default scope

PROCESS_NAME: System

READ_ADDRESS: unable to get nt!PspSessionIdBitmap
0000000000000028

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%p referenced memory at 0x%p. The memory could not be %s.

EXCEPTION_CODE_STR: c0000005

EXCEPTION_PARAMETER1: 0000000000000000

EXCEPTION_PARAMETER2: 0000000000000028

EXCEPTION_STR: 0xc0000005

STACK_TEXT:
ffffd10b`3aaa77d0 fffff800`6e90ea87 : ffff9f8b`48547b10 00000000`00000000 00000000`00000000 fffff800`6e45b6d9 : Netwtw14+0x11cff0
ffffd10b`3aaa7890 fffff800`6e90cd59 : ffffd10b`3aaa79b8 00000000`00000000 ffff9f8b`48548410 ffff858e`57ac3bf8 : nt!PnpNotifyDriverCallback+0x97
ffffd10b`3aaa7940 fffff800`6e90c07a : ffff9f8b`45d32a50 ffff9f8b`45d32a00 ffff858e`00000110 ffff858e`00000000 : nt!PnpNotifyTargetDeviceChange+0x171
ffffd10b`3aaa7a00 fffff800`6e907bed : ffff9f8b`45d32a50 ffff858e`402bdc00 ffffd5e1`00000000 00000000`00000000 : nt!PnpProcessCustomDeviceEvent+0x42
ffffd10b`3aaa7a30 fffff800`6e422525 : ffff858e`5be29040 ffff858e`5be29040 ffff858e`402bdc20 ffff858e`6db8a9d0 : nt!PnpDeviceEventWorker+0x20d
ffffd10b`3aaa7ab0 fffff800`6e5299a5 : ffff858e`5be29040 00000000`00000080 ffff858e`40302080 002fe47f`b19bbdff : nt!ExpWorkerThread+0x105
ffffd10b`3aaa7b50 fffff800`6e6072a8 : ffffb081`ce9c0180 ffff858e`5be29040 fffff800`6e529950 00000101`0004fffe : nt!PspSystemThreadStartup+0x55
ffffd10b`3aaa7ba0 00000000`00000000 : ffffd10b`3aaa8000 ffffd10b`3aaa1000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28

SYMBOL_NAME: Netwtw14+11cff0

MODULE_NAME: Netwtw14

IMAGE_NAME: Netwtw14.sys

STACK_COMMAND: .cxr 0xffffd10b3aaa6dd0 ; kb

BUCKET_ID_FUNC_OFFSET: 11cff0

FAILURE_BUCKET_ID: AV_Netwtw14!unknown_function

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {9cecd452-9765-c26a-c871-ea518a6e234e}

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

[NormanS_Intel]

Hello ajkessel,

Thank you for posting in the community!

I have a few questions to help further investigate this issue. Could you please provide the following information:

1. When did this issue first occur?

2. Were there any recent changes made before this issue started?

3. What troubleshooting steps have you tried so far to resolve this issue?

4. Is the bluescreen occurring randomly, or is there a specific scenario that triggers it?

Additionally, you may refer to our article on Blue Screen Error (BSOD) While Using Intel® Wi-Fi Cards for detailed troubleshooting steps.

Best regards,

Norman S.

Intel Customer Support Engineer

[NormanS_Intel]

Hello ajkessel,

I wanted to check if you had the chance to review the questions I posted. Please let me know at your earliest convenience so that we can determine the best course of action to resolve this matter. 

Best regards,

Norman S.

Intel Customer Support Engineer

[ajkessel]

I haven't seen a netwtw14.sys BSOD for quite a while now. I'm on 23.100.0.4 so perhaps the issue was fixed somewhere along the way.

[NormanS_Intel]

Hello ajkessel,

Thank you for your response. I'm glad to hear that everything is working fine now. Upon reviewing the logs you shared, it appears that an outdated driver might have been the root cause of the issue. For additional troubleshooting, please refer to our Blue Screen Error (BSOD) While Using Intel® Wi-Fi Cards article attached in this thread. If you need further assistance, feel free to reach out to us. I will close this inquiry for now. Should you need further help, please submit a new question as this thread will no longer be monitored.

Best regards,

Norman S.

Intel Customer Support Engineer