ASUS Pro WS WRX80E-SAGE SE WIFI, 4070 Ti Super and Win11 24H2 - Bootloops

Hardware Hub Motherboards
1

I’m hoping someone else on this forum has this combo of gear.

This board and card are stable on 23H2 and Fedora 41.

If I install 24H2, as soon as I load any NVidia driver (tested back to 560), including the 566.45 hotfix, I get a black screen and bootloops.

Eventually I can coax the system into safe mode and retrieve the minidump.

VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: ffff90832542a010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff8077e0d06a0, The pointer into responsible device driver module (e.g. owner tag).
Arg3: 0000000000000000, Optional error code (NTSTATUS) of the last failed operation.
Arg4: 000000000000000d, Optional internal context dependent data.

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

Unable to load image nvlddmkm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nvlddmkm.sys

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 1046

    Key  : Analysis.Elapsed.mSec
    Value: 1830

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

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

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

    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.LegacyAPI
    Value: 0x116

    Key  : Bugcheck.Code.TargetModel
    Value: 0x116

    Key  : Dump.Attributes.AsUlong
    Value: 21008

    Key  : Dump.Attributes.DiagDataWrittenToHeader
    Value: 1

    Key  : Dump.Attributes.ErrorCode
    Value: 0

    Key  : Dump.Attributes.KernelGeneratedTriageDump
    Value: 1

    Key  : Dump.Attributes.LastLine
    Value: Dump completed successfully.

    Key  : Dump.Attributes.ProgressPercentage
    Value: 0

    Key  : Failure.Bucket
    Value: 0x116_IMAGE_nvlddmkm.sys

    Key  : Failure.Hash
    Value: {c89bfe8c-ed39-f658-ef27-f2898997fdbd}

    Key  : Stack.Pointer
    Value: NMI


BUGCHECK_CODE:  116

BUGCHECK_P1: ffff90832542a010

BUGCHECK_P2: fffff8077e0d06a0

BUGCHECK_P3: 0

BUGCHECK_P4: d

FILE_IN_CAB:  010625-9781-01.dmp

DUMP_FILE_ATTRIBUTES: 0x21008
  Kernel Generated Triage Dump

FAULTING_THREAD:  ffff90831dea4480

VIDEO_TDR_CONTEXT: dt dxgkrnl!_TDR_RECOVERY_CONTEXT ffff90832542a010
Symbol dxgkrnl!_TDR_RECOVERY_CONTEXT not found.

PROCESS_OBJECT: 000000000000000d

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

DPC_STACK_BASE:  FFFFF180AE5A7FB0

STACK_TEXT:  
fffff180`ae007708 fffff807`6615942d     : 00000000`00000116 ffff9083`2542a010 fffff807`7e0d06a0 00000000`00000000 : nt!KeBugCheckEx
fffff180`ae007710 fffff807`6619e5b3     : fffff807`7e0d06a0 ffff9083`2542a010 fffff180`ae007839 00000000`00000316 : dxgkrnl!TdrBugcheckOnTimeout+0x101
fffff180`ae007750 fffff807`7c8dc5b8     : 00000000`00000316 01db601d`451dbfd0 00000000`00000316 fffff807`7c8de41e : dxgkrnl!TdrIsRecoveryRequired+0x1d3
fffff180`ae007780 fffff807`7c939b96     : ffff9083`00000000 ffff9083`1de38000 ffff9083`1de38000 00000000`00000000 : dxgmms2!VidSchiReportHwHang+0x658
fffff180`ae0078a0 fffff807`7c939069     : ffff9083`1de38000 00000000`00000000 ffffffff`ff676980 00000000`00000a90 : dxgmms2!VidSchiCheckHwProgress+0x3b6
fffff180`ae007930 fffff807`7c8b6152     : ffff9083`1de38000 ffff9083`1de38000 fffff180`ae007ab9 00000000`00000000 : dxgmms2!VidSchiWaitForSchedulerEvents+0x3f9
fffff180`ae007a00 fffff807`7c93a4b2     : ffff9083`1de38000 fffff180`ae007b70 ffff9082`fbc1a010 ffff9083`1de38000 : dxgmms2!VidSchiScheduleCommandToRun+0x2e2
fffff180`ae007b20 fffff807`7c93710c     : ffff9083`1de38500 ffff9083`1de38000 fffff807`7c937030 ffff9083`1de38000 : dxgmms2!VidSchiRun_PriorityTable+0x42
fffff180`ae007b70 fffff807`d365904a     : ffff9083`1dea4480 fffff807`00000001 ffff8080`8d1ce180 024fe47f`bcbbbdff : dxgmms2!VidSchiWorkerThread+0xdc
fffff180`ae007bb0 fffff807`d38741c4     : ffff8080`8d1ce180 ffff9083`1dea4480 fffff807`d3658ff0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff180`ae007c00 00000000`00000000     : fffff180`ae008000 fffff180`ae001000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x34


SYMBOL_NAME:  nvlddmkm+17006a0

Workstation boards are not worth it.

2

Oh wow. I actually do have this board (a WiFi II and a 4090, so almost the same), and have been running into the same major screwup with 24H2 updating.

In fact, even a freshly-installed Windows To Go from the latest ISO and Rufus version, when booted to the machine (never booted to any other one) and updated, also fails to boot. I’ve wasted a lot of time messing with it.

I don’t have a workaround or anything yet, but it’s good to know we aren’t alone.

3

Hey, so actually I found something interesting that was the cause in my case.

After a literal dozen+ reinstalls with nothing but trouble, I discovered that turning off the VGA header fixes the issue - the machine boots with 24H2, with video plugged into my 4090.

Interestingly, it also boots if I have nothing plugged into the 4090 and I use ONLY the VGA output

I can also boot with BOTH displays connected and working, with basic video in safe mode or while the driver is completely uninstalled.

Furthermore, both displays work fine under Windows 10, or earlier Windows 11.

This is a nasty regression, and I’m not sure what it is exactly. I’m a UNIX / Linux person and it has been crazy to me that I can’t seem to get verbose boot info displayed during boot, and not even in case of a fatal error!!! Advice is welcome.

I’m going to try installing the chipset drivers from ASUS, but am not sure if they actually contain newer software, or if the compatibility issue is even in the VGA driver at all.

2 Likes
4

OK, installing the latest ASPEED Display Driver fixes this.

Also if the 4090 is unplugged during boot with VGA, it works when plugged in after boot, even with the Microsoft Basic Display Driver.

I have more to share but wanted to update this for now.

1 Like
5

You are a genius.

What was the other stuff you were going to share?

6

How do you do this?

7

Confirming flipping the VGA switch off on the board made everything work again…

8

@voltagex & @iosengineer Thanks for posting this!! :pray: This was the exact problem I’ve been troubleshooting for about a week. I can confirm that turning off the VGA header works as well!!

9

I’m using 5995wx + M12SWA-TF + GTX 1030 and the system had exactly the same issue, which is now resolved thanks to your post and comments! Thank you all!