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

soumik.so123415c602ec said:
Awesome . I did the same thing. Let's see what happens. This thing has bugged me for a long time now.
Click to expand...
edwin.arend155402d2 said:
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.
Click to expand...



Update :

Using the NVIDIA driver 581.15 fixes the issue completely:
www.nvidia.com

Driver Details | NVIDIA

Download the <dd~LanguageName> <dd~Name> for <dd~OSName> systems. Released <dd~ReleaseDateTime>
www.nvidia.com
Correction
Previously, I mentioned that BIOS version E15M3IMS.112 did not have this issue.
At that time, I was actually using the NVIDIA 581.15 driver — which is why the problem did not occur.
So the absence of the issue was due to the driver, not the BIOS version.
Current System Versions
BIOS: E15M3IMS.114
VBIOS: 98.05.56.00.0B
Additional Notes
The power-state issue that exists in the factory NVIDIA driver (573.22) is not present in the official NVIDIA driver 581.15.
Please test this driver on your side as well.
I used DDU in Safe Mode (Option 4) to completely remove the previous driver before installing NVIDIA 581.15.
If this driver fully resolves the issue on all affected systems, then we should report this formally to NVIDIA so they can investigate and apply a permanent fix.

 

Attachments

  • NVIDIA System Information 12-07-2025 12-07-31.txt
    3.7 KB · Views: 69
  • Screenshot 2025-12-07 121842.png
    Screenshot 2025-12-07 121842.png
    196.9 KB · Views: 81
  • Screenshot 2025-12-07 121933.png
    Screenshot 2025-12-07 121933.png
    428.6 KB · Views: 71
edwin.arend155402d2 said:
I've used DDU to remove the 573.22 and installed 581.15, put the computer to sleep and woke it up, no issues.
Also my power state issue is gone, I can see the light turns white.

Yes, all issues are resolved in 581.15
Click to expand...
Then it seems the problem was with the NVIDIA drivers, and I’m glad the issue is resolved now.


However, we should still report this to NVIDIA so they can properly fix it in future driver versions.
Otherwise, we might be forced to use older drivers again if the issue returns.
 
edwin.arend155402d2 said:
I've used DDU to remove the 573.22 and installed 581.15, put the computer to sleep and woke it up, no issues.
Also my power state issue is gone, I can see the light turns white.

Yes, all issues are resolved in 581.15
Click to expand...
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff800`b46f6880 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffffde01`c4c6dc20=0000000000000133
WARNING: Whitespace at end of path element
Error: Empty Path.
WARNING: Whitespace at end of path element
1: kd> !analyze -v
Loading Kernel Symbols
...............................................................
................................................................
................................................................
................................................................
.
Loading User Symbols

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

DPC_WATCHDOG_VIOLATION (133)
The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL
or above.
Arguments:
Arg1: 0000000000000001, The system cumulatively spent an extended period of time at
DISPATCH_LEVEL or above.
Arg2: 0000000000001e00, The watchdog period (in ticks).
Arg3: fffff800b51c43b0, cast to nt!DPC_WATCHDOG_GLOBAL_TRIAGE_BLOCK, which contains
additional information regarding the cumulative timeout
Arg4: 0000000000000000

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

*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: TickPeriods ***
*** ***
*************************************************************************

KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 2671

Key : Analysis.Elapsed.mSec
Value: 29053

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

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

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

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

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

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

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

Key : Bugcheck.Code.TargetModel
Value: 0x133

Key : Failure.Bucket
Value: 0x133_ISR_nvlddmkm!unknown_function

Key : Failure.Hash
Value: {f97493a5-ea2b-23ca-a808-8602773c2a86}

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 : Stack.Pointer
Value: ISR

Key : WER.OS.Branch
Value: ge_release

Key : WER.OS.Version
Value: 10.0.26100.1

Key : WER.System.BIOSRevision
Value: 1.20.0.0


BUGCHECK_CODE: 133

BUGCHECK_P1: 1

BUGCHECK_P2: 1e00

BUGCHECK_P3: fffff800b51c43b0

BUGCHECK_P4: 0

FILE_IN_CAB: 120725-14296-01.dmp

FAULTING_THREAD: ffff960c345ab2c0

DPC_TIMEOUT_TYPE: DPC_QUEUE_EXECUTION_TIMEOUT_EXCEEDED

TRAP_FRAME: fffff58794e46f00 -- (.trap 0xfffff58794e46f00)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=ffff960c38ce9af0 rbx=0000000000000000 rcx=ffff960c38ce9e60
rdx=ffff960c3df5b980 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80061a53dda rsp=fffff58794e47090 rbp=fffff58794e47190
r8=ffff960c38ce9e50 r9=ffff960c3df5b980 r10=000000000008f42b
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na po nc
nvlddmkm+0x843dda:
fffff800`61a53dda 4885c0 test rax,rax
Resetting default scope

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1 (!blackboxwinlogon)


CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System

STACK_TEXT:
ffffde01`c4c6dc18 fffff800`b4559616 : 00000000`00000133 00000000`00000001 00000000`00001e00 fffff800`b51c43b0 : nt!KeBugCheckEx
ffffde01`c4c6dc20 fffff800`b4558b61 : 00000000`00000000 00000000`000d01f0 00000000`00000000 ffffde01`c4c51180 : nt!KeAccumulateTicks+0x596
ffffde01`c4c6dc90 fffff800`b455f00a : 0000001f`0333297d ffffde01`c4c51180 00000000`0000000f ffff960b`00000001 : nt!KiUpdateRunTime+0xb1
ffffde01`c4c6de50 fffff800`b455f99c : ffff960b`f2778360 ffff960b`f2778410 fffff800`b518ec70 ffffde01`00000001 : nt!KeClockInterruptNotify+0x41a
ffffde01`c4c6df40 fffff800`b48a0dbe : ffff960c`1cb32002 ffff960b`f2778360 0000253f`b9eb1bae 00000000`00000000 : nt!KiCallInterruptServiceRoutine+0x32c
ffffde01`c4c6dfb0 fffff800`b48a15cc : 00000000`00000000 fffff800`612f05d0 00000000`00000001 00000000`00000000 : nt!KiInterruptSubDispatchNoLockNoEtw+0x4e
fffff587`94e46f00 fffff800`61a53dda : ffff960c`1cb32050 00000000`00000004 ffff960c`1d390000 ffff960c`1d2cb000 : nt!KiInterruptDispatchNoLockNoEtw+0x3c
fffff587`94e47090 ffff960c`1cb32050 : 00000000`00000004 ffff960c`1d390000 ffff960c`1d2cb000 fffff587`94e47140 : nvlddmkm+0x843dda
fffff587`94e47098 00000000`00000004 : ffff960c`1d390000 ffff960c`1d2cb000 fffff587`94e47140 00000000`00000002 : 0xffff960c`1cb32050
fffff587`94e470a0 ffff960c`1d390000 : ffff960c`1d2cb000 fffff587`94e47140 00000000`00000002 00000000`00000000 : 0x4
fffff587`94e470a8 ffff960c`1d2cb000 : fffff587`94e47140 00000000`00000002 00000000`00000000 00000000`00000001 : 0xffff960c`1d390000
fffff587`94e470b0 fffff587`94e47140 : 00000000`00000002 00000000`00000000 00000000`00000001 00000000`00000001 : 0xffff960c`1d2cb000
fffff587`94e470b8 00000000`00000002 : 00000000`00000000 00000000`00000001 00000000`00000001 00000000`00000000 : 0xfffff587`94e47140
fffff587`94e470c0 00000000`00000000 : 00000000`00000001 00000000`00000001 00000000`00000000 01000000`00000004 : 0x2


SYMBOL_NAME: nvlddmkm+843dda

MODULE_NAME: nvlddmkm

IMAGE_NAME: nvlddmkm.sys

STACK_COMMAND: .process /r /p 0xffff960bf26ee040; .thread 0xffff960c345ab2c0 ; kb

BUCKET_ID_FUNC_OFFSET: 843dda

FAILURE_BUCKET_ID: 0x133_ISR_nvlddmkm!unknown_function

OS_VERSION: 10.0.26100.1

BUILDLAB_STR: ge_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {f97493a5-ea2b-23ca-a808-8602773c2a86}

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


Unfortunately, I got the BSOD again in battery mode 😓

Mini Dump BSOD :https://drive.google.com/file/d/10aeno0o2VIzP1gJq30o_cnI0QS1YM4Un/view?usp=sharing
 
maneeshadulshanjan200155502d6 said:
Update :

Using the NVIDIA driver 581.15 fixes the issue completely:
www.nvidia.com

Driver Details | NVIDIA

Download the <dd~LanguageName> <dd~Name> for <dd~OSName> systems. Released <dd~ReleaseDateTime>
www.nvidia.com
Correction
Previously, I mentioned that BIOS version E15M3IMS.112 did not have this issue.
At that time, I was actually using the NVIDIA 581.15 driver — which is why the problem did not occur.
So the absence of the issue was due to the driver, not the BIOS version.
Current System Versions
BIOS: E15M3IMS.114
VBIOS: 98.05.56.00.0B
Additional Notes
The power-state issue that exists in the factory NVIDIA driver (573.22) is not present in the official NVIDIA driver 581.15.
Please test this driver on your side as well.
I used DDU in Safe Mode (Option 4) to completely remove the previous driver before installing NVIDIA 581.15.
If this driver fully resolves the issue on all affected systems, then we should report this formally to NVIDIA so they can investigate and apply a permanent fix.

Click to expand...
Yeah . The 581.15 driver fixes the issue. TY
 
soumik.so123415c602ec said:
Yeah . The 581.15 driver fixes the issue. TY
Click to expand...
edwin.arend155402d2 said:
I've used DDU to remove the 573.22 and installed 581.15, put the computer to sleep and woke it up, no issues.
Also my power state issue is gone, I can see the light turns white.

Yes, all issues are resolved in 581.15
Click to expand...
To check whether the issue still exists in the 581.15 driver, try the following:


  1. Set the laptop to Discrete Mode.
  2. Unplug the charger to switch to battery mode.
  3. While running on battery, put the laptop to sleep.
  4. Wake the laptop again while still on battery.
  5. As soon as it starts waking up (for example, when Face Unlock appears), plug the charger back in.

Because the power source changes during the wake-up process, the familiar BSOD appears again.
 
maneeshadulshanjan200155502d6 said:
To check whether the issue still exists in the 581.15 driver, try the following:


  1. Set the laptop to Discrete Mode.
  2. Unplug the charger to switch to battery mode.
  3. While running on battery, put the laptop to sleep.
  4. Wake the laptop again while still on battery.
  5. As soon as it starts waking up (for example, when Face Unlock appears), plug the charger back in.

Because the power source changes during the wake-up process, the familiar BSOD appears again.
Click to expand...
Okay, but that's quite a specific edge case I would say. I know it's still not perfect, but things are a lot better than before.
I tried to find out how to create a ticket for NVIDIA, but i didn't see the option, i think the best fix for this are in the NVIDIA drivers.
 
Thank you to everyone involved in the investigation here, I was getting concerned with the persistence of this crash on my new laptop. As suggested here, reverting the driver to 581.15 has fixed the issue for me.

Did anyone report the issue to NVIDIA? I've just submitted a ticket with a link back to this thread. If anyone else wants to do so, it's here: https://nvidia.custhelp.com/app/ask
 
Hi! I’m experiencing a similar issue on the same laptop model. My setup is as follows:

Model: Vector 16 HX AI A2XWHG-275US
BIOS: E15M3IMS.116
VBIOS: 98.05.56.00.0B

Graphics Mode: MS Hybrid
Display Setup: Dual display — the built-in laptop screen and an external monitor connected via HDMI (ASUS VA24EFH, running at 100 Hz).

Regarding the GPU driver behavior:

- With the latest driver (version 591.86), the system consistently encounters BSODs (DPC_WATCHDOG_VIOLATION or VIDEO_TDR_FAILURE) after the laptop has been left idle for some time and is then woken up.
- Downgrading to driver version 581.15 improved stability, but BSODs still occurred occasionally. In some cases, the GPU driver would restart instead, although less frequently.
- After downgrading further to the OEM driver (573.22), the system has been stable with no BSODs or driver restarts.

However, with the OEM driver, I noticed that the power LED remains orange even when the laptop is put into sleep mode. This suggests that the wake/sleep logic may not be handled correctly by the driver or BIOS when the system is configured in Hybrid or Discrete graphics mode.
For now, I am staying on driver version 573.22, as system stability is more important for my use case. Since I typically use the laptop while connected to AC power, I prefer to avoid BSODs and can tolerate the power LED behavior until NVIDIA or MSI releases a fix.
 
maneeshadulshanjan200155502d6 said:
Update :

Using the NVIDIA driver 581.15 fixes the issue completely:
www.nvidia.com

Driver Details | NVIDIA

Download the <dd~LanguageName> <dd~Name> for <dd~OSName> systems. Released <dd~ReleaseDateTime>
www.nvidia.com
Correction
Previously, I mentioned that BIOS version E15M3IMS.112 did not have this issue.
At that time, I was actually using the NVIDIA 581.15 driver — which is why the problem did not occur.
So the absence of the issue was due to the driver, not the BIOS version.
Current System Versions
BIOS: E15M3IMS.114
VBIOS: 98.05.56.00.0B
Additional Notes
The power-state issue that exists in the factory NVIDIA driver (573.22) is not present in the official NVIDIA driver 581.15.
Please test this driver on your side as well.
I used DDU in Safe Mode (Option 4) to completely remove the previous driver before installing NVIDIA 581.15.
Si este controlador resuelve completamente el problema en todos los sistemas afectados, entonces deberíamos informarlo formalmente a NVIDIA para que puedan investigar y aplicar una solución permanente.

https://us.download.nvidia.com/Wind...-win10-win11-64bit-international-dch-whql.exe
Click to expand...
¿A qué altura aumenta tu temperatura cuando juegas con esa versión de BIOS y VBIOS?
 
¿Cuál es la mejor versión del BIOS y el BIOS y controlador de Nvidia para el MSI Vector 16HX AI A2XWHG que proporciona el mejor FPS sin aumentar significativamente la temperatura?
 
Was having the BSOD on wakeup from sleep somewhat regularly (couple times a week,) and finally wiped and re-installed Windows from scratch on April 9. Had it again same day, found this thread and rolled back to 581.83. Have not had the issue on wakeup since, but I did just today have the same crash today while actively using the device (Vector A16 HX A8WHG, BIOS version E15MMAMS.108) Not sure what that's about - hopefully not the start of a trend.

1777506027695.png
 
Drew.g said:
Was having the BSOD on wakeup from sleep somewhat regularly (couple times a week,) and finally wiped and re-installed Windows from scratch on April 9. Had it again same day, found this thread and rolled back to 581.83. Have not had the issue on wakeup since, but I did just today have the same crash today while actively using the device (Vector A16 HX A8WHG, BIOS version E15MMAMS.108) Not sure what that's about - hopefully not the start of a trend.

View attachment 211002
Click to expand...
Windows automatically updates the NVIDIA driver in Windows updates, what it does not update is the AUDIODG driver. I did this a couple of weeks ago and haven't had a crash/bluescreen yet. Now, if you go to device manager there's an audio processing object called 'intelliGo' and I have this driver version installed:
1777525854810.png


Windows won't automatically install this, so you go to https://catalog.update.microsoft.com/ and search for "intelliGo" then download the cab file.
Extract the cab file somewhere on your system, click update driver and point it to the directory you extracted the cab file in.

Hopefully this will stop your bluescreens.
 
I've been very reluctant to update windows recently because of such problems, so I did a group policy edit to avoid driver updates described as the following. Does this suffice to dodge such problems?
 

Attachments

  • group_policy_edit_to_avoid_driver_updates.png
    group_policy_edit_to_avoid_driver_updates.png
    67.1 KB · Views: 27
Windows automatically updates the NVIDIA driver in Windows updates, what it does not update is the AUDIODG driver. I did this a couple of weeks ago and haven't had a crash/bluescreen yet. Now, if you go to device manager there's an audio processing object called 'intelliGo' and I have this driver version installed:View attachment 211003
edwin.arend155402d2 said:
Windows won't automatically install this, so you go to https://catalog.update.microsoft.com/ and search for "intelliGo" then download the cab file.
Extract the cab file somewhere on your system, click update driver and point it to the directory you extracted the cab file in.

Hopefully this will stop your bluescreens.
Click to expand...
Thank you so much! I downloaded the intelliGo cab file, extracted it, and updated the driver exactly as you instructed. It actually worked perfectly! I haven't had a single BSOD or crash since doing this. Really appreciate you sharing this fix!
 
seabiscuit said:
I've been very reluctant to update windows recently because of such problems, so I did a group policy edit to avoid driver updates described as the following. Does this suffice to dodge such problems?
Click to expand...
Maybe, but i would truly advice to install the new AUDIODG driver as i instructed, it helped me a lot.
 
Back
Top