Vector-16-HX-AI-A2XWHG - BSOD 0x116 on Wake (Discrete Mode) & BIOS .114 Regression

maneeshadulshanjan200155502d6 · Dec 6, 2025

Hi everyone,

I am experiencing a persistent VIDEO_TDR_FAILURE (0x00000116) BSOD on my MSI Vector 16 HX AI. I have performed extensive testing and isolated the issue to a specific scenario involving the MUX Switch, AC Power, and a suspected BIOS regression.

Here are my system details and findings:

System Information:

Model: Vector 16 HX AI A2XWX / A2XWHG
BIOS Version: E15M3IMS.114 (Current)
VBIOS Version: 98.05.56.00.0B (Latest)
OS: Windows 11

The Issue:The system crashes with a BSOD (0x116 - nvlddmkm.sys) when waking up from "Sleep" mode.

Crucial Isolation Step:This issue does NOT occur when using Integrated Graphics . It is exclusive to Discrete Graphics Mode via the MUX switch.

The issue does not occur only when using Integrated Graphics (Intel Graphics).
However, in MSHybrid mode, the problem does occur.

Steps to Reproduce:

Set the laptop to Discrete Graphics Mode (via MUX switch).
Connect the AC Power Adapter (Issue observed while plugged in; battery behavior not fully tested for this crash).
Put the laptop to Sleep.
Wake the laptop.
- Note: If the crash does not happen immediately on the first wake, put it back to sleep (using Fn + Sleep shortcut) and leave it for about 15 minutes.
Result: Upon waking, the system hangs and crashes with BSOD 0x116.

Driver & BIOS Observations:

1. With Latest Generic Nvidia Drivers (581.80, 591.44):

The system consistently crashes with the 0x116 BSOD upon waking up from sleep (especially after a 15-minute duration).

2. With MSI OEM Driver (573.22):

The BSOD does not occur.
HOWEVER: There is a power state bug. When plugged in and put to sleep, the DGPU does not fully power down. The Power LED remains Orange (indicating DGPU is active/awake).
Contrast: On battery mode with this driver, the Orange light turns off correctly.

Conclusion & Suspected Regression:It appears the GPU is failing to handle power state transitions (Sleep -> Wake) correctly while on AC power in Discrete Mode.

The OEM driver masks the issue by keeping the GPU "awake" (Orange light), preventing the crash but failing to save power.
The newer Nvidia drivers likely attempt a proper sleep cycle, which fails to wake up correctly, triggering the TDR crash.

I strongly suspect this is a regression in BIOS E15M3IMS.114. I do not recall experiencing this behavior on the previous BIOS version (E15M3IMS.112).

Has anyone else faced this with the .114 BIOS?

Thank you.

maneeshadulshanjan200155502d6 · Dec 6, 2025

edwin.arend155402d2 · Dec 6, 2025

Hello!

I have a less advanced version of the same laptop, and I had this issue as well in this topic: link to topic
What I can advise is update the BIOS and update the VBIOS (can be found here: link to firmware download)
Make sure you update all your drivers to the latest MSI drivers. There are chipset driver updates available, especially the Intel Platform Monitoring Technology Driver which has something to do with power consumption.
What I did, and I'm not sure if this is necessary, I used DDU to uninstall the NVIDIA driver and reinstall the 573.22 version (the version of MSI). I feel the 580 version is unstable.

If you have MSI Center installed you can use "Support -> Live Update" to see if all your drivers are up to date.
I have not seen the errors anymore after this.

Hope this helps!

maneeshadulshanjan200155502d6 · Dec 6, 2025

edwin.arend155402d2 said:
Hello!

I have a less advanced version of the same laptop, and I had this issue as well in this topic: link to topic
What I can advise is update the BIOS and update the VBIOS (can be found here: link to firmware download)
Make sure you update all your drivers to the latest MSI drivers. There are chipset driver updates available, especially the Intel Platform Monitoring Technology Driver which has something to do with power consumption.
What I did, and I'm not sure if this is necessary, I used DDU to uninstall the NVIDIA driver and reinstall the 573.22 version (the version of MSI). I feel the 580 version is unstable.

If you have MSI Center installed you can use "Support -> Live Update" to see if all your drivers are up to date.
I have not seen the errors anymore after this.

Hope this helps!

I followed everything you suggested, including updating BIOS, VBIOS, and all MSI-provided drivers. I also used DDU and reinstalled the MSI OEM NVIDIA driver (573.22).

However, there is still one issue:

2. With the MSI OEM NVIDIA Driver (573.22):

The BSOD no longer occurs.
BUT there is a power-state bug:
When the laptop is plugged in and put to sleep, the dGPU does not fully power down. The power LED stays orange, which means the dGPU is still active.
In battery mode, this doesn’t happen—the orange light turns off correctly.

Because this issue does not happen on BIOS version E15M3IMS.112, there is a high chance this is a BIOS-related problem.

I can’t share the minidump here because it contains sensitive information.

edwin.arend155402d2 · Dec 6, 2025

I had this issue on the 110 version of the bios as well, could be that there is a problem with the 114 version, but i think that means we just have to wait until it gets updated again.
I don't think there is a way to go back to 112?

But yes I believe you, my power led also stays orange which could indicate a power state issue. I'm less bothered with that though as the BSOD was way worse haha.

Could it be that you set the Link Power state management to "Off" and that could keep the GPU awake? I've done that.

maneeshadulshanjan200155502d6 · Dec 6, 2025

I do have a BIOS backup, but I don’t want to downgrade the BIOS because I already updated the VBIOS.
If necessary, I also have a backup of the old VBIOS.

MSI Vector 16 HX AI A2XWHG - Google Drive

drive.google.com

maneeshadulshanjan200155502d6 · Dec 6, 2025

Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading symbols.

.............................................................
................................................................
................................................................
.............................................................
Loading User Symbols

Loading unloaded module list
..............................
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff807`8bcf6880 48894c2408 mov qword ptr [rsp+8],rcx ss:ffffbc87`321c77e0=0000000000000116
13: kd> !analyze -v
Loading Kernel Symbols
..

Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading symbols.

.............................................................
................................................................
................................................................
.............................................................
Loading User Symbols

Loading unloaded module list
..............................
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: ffff9486491aa010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff8073b90a120, The pointer into responsible device driver module (e.g. owner tag).
Arg3: ffffffffc000009a, Optional error code (NTSTATUS) of the last failed operation.
Arg4: 0000000000000004, 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: 2078

Key : Analysis.Elapsed.mSec
Value: 15888

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

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

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

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

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

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

Key : Analysis.Version.DbgEng
Value: 10.0.29482.1003

Key : Analysis.Version.Description
Value: 10.2509.29.03 amd64fre

Key : Analysis.Version.Ext
Value: 1.2509.29.3

Key : Bugcheck.Code.LegacyAPI
Value: 0x116

Key : Bugcheck.Code.TargetModel
Value: 0x116

Key : Dump.Attributes.AsUlong
Value: 0x21808

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: 0x116_IMAGE_nvlddmkm.sys

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

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

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

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

Key : Faulting.IP.Type
Value: Paged

Key : Hypervisor.Enlightenments.ValueHex
Value: 0x7417df84

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

Key : Hypervisor.Flags.ValueHex
Value: 0x34a10fe

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

Key : WER.System.BIOSRevision
Value: 1.20.0.0

BUGCHECK_CODE: 116

BUGCHECK_P1: ffff9486491aa010

BUGCHECK_P2: fffff8073b90a120

BUGCHECK_P3: ffffffffc000009a

BUGCHECK_P4: 4

FILE_IN_CAB: 120625-13984-01.dmp

DUMP_FILE_ATTRIBUTES: 0x21808
Kernel Generated Triage Dump

FAULTING_THREAD: ffff94864a9d43c0

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

PROCESS_OBJECT: 0000000000000004

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXPNP: 1 (!blackboxpnp)

BLACKBOXWINLOGON: 1 (!blackboxwinlogon)

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System

IP_IN_PAGED_CODE:
nvlddmkm+19aa120
fffff807`3b90a120 488b05193781ff mov rax,qword ptr [nvlddmkm+0x11bd840 (fffff807`3b11d840)]

STACK_TEXT:
ffffbc87`321c77d8 fffff807`1d976d5d : 00000000`00000116 ffff9486`491aa010 fffff807`3b90a120 ffffffff`c000009a : nt!KeBugCheckEx
ffffbc87`321c77e0 fffff807`1dbe9156 : fffff807`3b90a120 ffff9486`33c947b0 00000000`00000004 ffff9486`491aa010 : dxgkrnl!TdrBugcheckOnTimeout+0x101
ffffbc87`321c7820 fffff807`1d985aa6 : 00000000`00000000 00000000`00002000 00000000`00000004 00000000`00000004 : dxgkrnl!ADAPTER_RENDER::Reset+0x232
ffffbc87`321c7850 fffff807`1d9be525 : ffff9486`00000100 00000000`00000000 ffffbc87`00000000 00000000`00000000 : dxgkrnl!DXGADAPTER::Reset+0x59a
ffffbc87`321c78e0 fffff807`1d9be682 : fffff807`1f001890 00000000`00000000 00000000`00000400 fffff807`8c7cfb40 : dxgkrnl!TdrResetFromTimeout+0x15
ffffbc87`321c7910 fffff807`8badb8ac : ffff9486`4a9d43c0 ffff9486`07735be0 ffff9486`07735b00 ffff9486`0d2f6070 : dxgkrnl!TdrResetFromTimeoutWorkItem+0x22
ffffbc87`321c7950 fffff807`8bc815ea : ffff9486`4a9d43c0 ffff9486`4a9d43c0 fffff807`8badb2c0 ffff9486`07735be0 : nt!ExpWorkerThread+0x5ec
ffffbc87`321c7b30 fffff807`8be9fd74 : ffffe680`73f21180 ffff9486`4a9d43c0 fffff807`8bc81590 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
ffffbc87`321c7b80 00000000`00000000 : ffffbc87`321c8000 ffffbc87`321c1000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x34

SYMBOL_NAME: nvlddmkm+19aa120

MODULE_NAME: nvlddmkm

IMAGE_NAME: nvlddmkm.sys

STACK_COMMAND: .process /r /p 0xffff9486076d1040; .thread 0xffff94864a9d43c0 ; kb

FAILURE_BUCKET_ID: 0x116_IMAGE_nvlddmkm.sys

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {c89bfe8c-ed39-f658-ef27-f2898997fdbd}

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

maneeshadulshanjan200155502d6 · Dec 6, 2025

Mini Dump File BSOD

120625-13984-01.dmp

drive.google.com

MSI Vector 16 HX AI A2XWHG - Google Drive

drive.google.com

edwin.arend155402d2 · Dec 6, 2025

Looks like the same crash I had.

Did you have a new crash after you updated drivers/vbios? Or was this information from the earlier crash?

soumik.so123415c602ec · Dec 6, 2025

I’ve encountered the same issue with NVIDIA driver 581.80 when running in Hybrid Mode.
The system crashes with a BSOD: VIDEO_MEMORY_MANAGEMENT_INTERNAL (0x10E) in dxgmms2.sys.

This only occurs in Hybrid Mode and is reproducible as follows:
- Run the laptop in Hybrid Mode
- Put the system into sleep mode or lock mode
- Unlock or wake the system after some time → crash occurs

It looks like the crash happens when the laptop tries to wake the dGPU from sleep — the GPU fails to resume properly and triggers the paging error.

The only reliable fix is to use the factory NVIDIA driver (573.22).
Issue reproduces across all BIOS versions tested.

Code:

SYMBOL_NAME:  dxgmms2!VIDMM_PAGE_TABLE_BASE::GetCpuVisibleAddress+57e
MODULE_NAME: dxgmms2
IMAGE_NAME:  dxgmms2.sys
IMAGE_VERSION:  10.0.26100.7019
STACK_COMMAND: .process /r /p 0xffff840e264c8040; .thread 0xffff840e521c3480 ; kb
BUCKET_ID_FUNC_OFFSET:  57e
FAILURE_BUCKET_ID:  0x10e_2d_dxgmms2!VIDMM_PAGE_TABLE_BASE::GetCpuVisibleAddress
OSPLATFORM_TYPE:  x64
OSNAME:  Windows 10
FAILURE_ID_HASH:  {ca00cb12-3ce5-2e41-c763-7f0f8a8fbadd}

Although the error codes differ (0x116 vs 0x10E), the common thread is that the dGPU fails to handle power state transitions correctly when resuming from sleep/lock. This strongly suggests a regression in BIOS/VBIOS or driver compatibility with Hybrid/Discrete GPU wake logic.

soumik.so123415c602ec · Dec 6, 2025

sent this thing in MSI ticket

edwin.arend155402d2 · Dec 6, 2025

So it's a driver compatibility issue, should report a ticket to MSI

maneeshadulshanjan200155502d6 · Dec 6, 2025

edwin.arend155402d2 said:
Looks like the same crash I had.

Did you have a new crash after you updated drivers/vbios? Or was this information from the earlier crash?

With the factory NVIDIA driver (573.22), the BSOD no longer happens, but the power-state issue is still present.

When using the official NVIDIA drivers, the previously mentioned power-state problem does not occur — but then I get BSODs.

maneeshadulshanjan200155502d6 · Dec 6, 2025

soumik.so123415c602ec said:
sent this thing in MSI ticket

I have already done the same on my side as well.

edwin.arend155402d2 · Dec 6, 2025

It would seem the power state issue is actually keeping the GPU alive preventing the error.

maneeshadulshanjan200155502d6 · Dec 6, 2025

edwin.arend155402d2 said:
It would seem the power state issue is actually keeping the GPU alive preventing the error.

Possibly, but the battery drains very fast because of it.

soumik.so123415c602ec · Dec 6, 2025

Although the error codes differ (0x116 vs 0x10E), the common thread is that the dGPU fails to handle power state transitions correctly when resuming from sleep/lock. This strongly suggests a regression in BIOS/VBIOS or driver compatibility with Hybrid/Discrete GPU wake logic.

soumik.so123415c602ec · Dec 6, 2025

maneeshadulshanjan200155502d6 said:
With the factory NVIDIA driver (573.22), the BSOD no longer happens, but the power-state issue is still present.

When using the official NVIDIA drivers, the previously mentioned power-state problem does not occur — but then I get BSODs.

It's their power state issue or some error in Hybrid/Discrete GPU wake logic.

edwin.arend155402d2 · Dec 6, 2025

I've had it with old BIOS and VBIOS in combination with the new NVIDIA driver, I feel that it's a compatibility issue with the wake logic.

I have now also created a ticket for this.

soumik.so123415c602ec · Dec 6, 2025

Awesome . I did the same thing. Let's see what happens. This thing has bugged me for a long time now.

Vector-16-HX-AI-A2XWHG - BSOD 0x116 on Wake (Discrete Mode) & BIOS .114 Regression

New member

New member

Attachments

New member

New member

2. With the MSI OEM NVIDIA Driver (573.22):​

New member

New member

New member

New member

New member

New member

New member

New member

New member

New member

New member

New member

New member

New member

New member

New member

2. With the MSI OEM NVIDIA Driver (573.22):