Maximus XIII Hero WiFi Drivers causing BSOD

[CRVCKER]

Every version that I have come across so far has seemed to give me a bloody BSOD.
EDIT: I am considering rolling my BIOS version back to 1601 from 1701. I'm using a 3080 Ti anyways. Not sure though yet. If I can find some answers here before I jump ship, that would be appreciated.

I wanted to add this info as well to this error report.

Device PCI\VEN_8086&DEV_2725&SUBSYS_00248086&REV_1A\4&646b8d4&0&00DF had a problem starting.

Driver Name: oem68.inf
Class Guid: {4d36e972-e325-11ce-bfc1-08002be10318}
Service: Netwtw12
Lower Filters:
Upper Filters: vwifibus
Problem: 0x15
Problem Status: 0x0

The description for Event ID 6062 from source Netwtw12 cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.
If the event originated on another computer, the display information had to be saved with the event.
The following information was included with the event:
\Device\NDMP1
Intel(R) Wi-Fi 6E AX210 160MHz
The message resource is present but the message was not found in the message table

Is there any info on what would be the most stable driver that is currently out for this MOBO? Event viewer will give me this error before the eventual Black Screen BSOD. MSDBUG Shows the process running and the driver that caused the BSOD

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: 0000000000000031, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, value 0 = read operation, 1 = write operation
Arg4: fffff8023b343e46, address which referenced memory

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


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 3343

    Key  : Analysis.DebugAnalysisManager
    Value: Create

    Key  : Analysis.Elapsed.mSec
    Value: 9177

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

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

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

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

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

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

    Key  : Bugcheck.Code.DumpHeader
    Value: 0xd1

    Key  : Bugcheck.Code.Register
    Value: 0xa

    Key  : WER.OS.Branch
    Value: vb_release

    Key  : WER.OS.Timestamp
    Value: 2019-12-06T14:06:00Z

    Key  : WER.OS.Version
    Value: 10.0.19041.1


FILE_IN_CAB:  022823-5421-01.dmp

BUGCHECK_CODE:  d1

BUGCHECK_P1: 31

BUGCHECK_P2: 2

BUGCHECK_P3: 1

BUGCHECK_P4: fffff8023b343e46

WRITE_ADDRESS: fffff802098fb390: Unable to get MiVisibleState
Unable to get NonPagedPoolStart
Unable to get NonPagedPoolEnd
Unable to get PagedPoolStart
Unable to get PagedPoolEnd
unable to get nt!MmSpecialPagesInUse
 0000000000000031 

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  BF2042.exe

TRAP_FRAME:  ffffb10b708e4e30 -- (.trap 0xffffb10b708e4e30)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=ffff9e09f770bea8 rbx=0000000000000000 rcx=ffff9e09f770bea8
rdx=ffff9e0a0579a7b0 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8023b343e46 rsp=ffffb10b708e4fc8 rbp=ffffb10b708e5150
 r8=0000000000000028  r9=0000000000000028 r10=fffff80208f64ac0
r11=ffff9e0a0579a7b0 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na pe nc
Netwtw12+0x373e46:
fffff802`3b343e46 d17309          sal     dword ptr [rbx+9],1 ds:00000000`00000009=????????
Resetting default scope

MISALIGNED_IP: 
Netwtw12+373e46
fffff802`3b343e46 d17309          sal     dword ptr [rbx+9],1

STACK_TEXT:  
ffffb10b`708e4ce8 fffff802`0900e129     : 00000000`0000000a 00000000`00000031 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
ffffb10b`708e4cf0 fffff802`09009ce3     : 418ebd93`93ecdc8b 6581a5e0`a55ca945 b91db24e`7c59ffa6 34691c2b`fe388d84 : nt!KiBugCheckDispatch+0x69
ffffb10b`708e4e30 fffff802`3b343e46     : fffff802`3b339f0f ffff9e0a`03518a00 fffff802`08f5beaf ffff9e0a`0e353340 : nt!KiPageFault+0x463
ffffb10b`708e4fc8 fffff802`3b339f0f     : ffff9e0a`03518a00 fffff802`08f5beaf ffff9e0a`0e353340 00000000`00000000 : Netwtw12+0x373e46
ffffb10b`708e4fd0 ffff9e0a`03518a00     : fffff802`08f5beaf ffff9e0a`0e353340 00000000`00000000 ffffb10b`708e5150 : Netwtw12+0x369f0f
ffffb10b`708e4fd8 fffff802`08f5beaf     : ffff9e0a`0e353340 00000000`00000000 ffffb10b`708e5150 fffff802`3b06c554 : 0xffff9e0a`03518a00
ffffb10b`708e4fe0 fffff802`3b06cb55     : 00000000`00000028 00000000`00000001 ffff9e09`f770c020 00000000`00000000 : nt!KeQueryPerformanceCounter+0x5f
ffffb10b`708e5010 00000000`00000028     : 00000000`00000001 ffff9e09`f770c020 00000000`00000000 00000000`00000000 : Netwtw12+0x9cb55
ffffb10b`708e5018 00000000`00000001     : ffff9e09`f770c020 00000000`00000000 00000000`00000000 fffff5de`6f078965 : 0x28
ffffb10b`708e5020 ffff9e09`f770c020     : 00000000`00000000 00000000`00000000 fffff5de`6f078965 00000000`00000000 : 0x1
ffffb10b`708e5028 00000000`00000000     : 00000000`00000000 fffff5de`6f078965 00000000`00000000 fffff802`3b01720e : 0xffff9e09`f770c020


SYMBOL_NAME:  Netwtw12+373e46

MODULE_NAME: hardware

IMAGE_NAME:  hardware

STACK_COMMAND:  .cxr; .ecxr ; kb

FAILURE_BUCKET_ID:  IP_MISALIGNED_Netwtw12.sys

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {51f33ad1-da27-491b-2ac2-fd5b82d0aab4}

Followup:     MachineOwner

[PerpetualCycle]

Are you overclocking the CPU or memory? The reason I ask is that is a common crash from overclocking. If you are OCing, turn the OC off and see if you still have the issue. It can be that your previous BIOS settings are not stable in the new BIOS.

The second bit of information (IRQ LT or EQ to) is not part of your issue. I get them too and they appear innocuous.

[CRVCKER]

geneo wrote:
Are you overclocking the CPU or memory? The reason I ask is that is a common crash from overclocking. If you are OCing, turn the OC off and see if you still have the issue. It can be that your previous BIOS settings are not stable in the new BIOS.

The second bit of information (IRQ LT or EQ to) is not part of your issue. I get them too and they appear innocuous.

I am currently overclocked. I am not entirely sure though how to turn it off in extreme tweak though. The only settings I have are
Auto
Manual
XMP1
XMP2

There is no OFF setting that I can find. I turned on OC to begin with was so that my RAM would run at the advertised speeds of 3200Mhz. Without it my ram is clocked at 1900Mhz

[PerpetualCycle]

Save your current settings to a profile to go back to.

Auto

Set "ASUS Multicore Enhancement" to "DISABLED, enforce all limits"

reboot

The latter will make the settings follow the Intel specs.

[CRVCKER]

geneo wrote:
Save your current settings to a profile to go back to.

Auto

Set "ASUS Multicore Enhancement" to "DISABLED, enforce all limits"

reboot

The latter will make the settings follow the Intel specs.

Much appreciated brother.

[PerpetualCycle]

good luck

[Saltgrass]

Does it only happen with Battlefield 2042?

I have that motherboard and my Wi-Fi has never given me problems. I do get a warning for the netwtw12 but only when I wake my system.

Maybe change a power setting in the Bios in the advanced section. Current Wi-Fi driver is 22.200.0.6.

[PerpetualCycle]

Also another way, probably better, to get default settings is load optimize defaults in the BIOS by pressing F5.

[CRVCKER]

So the thing that fixed my BSOD problems was literally the Overclock itself. Since I reverted everything back to default settings, I've had no issues. I had to make sure that PCIExpress Dedicated Power Management was turned off else my game would crash.

[PerpetualCycle]

Well that is good to hear!