MSI A2XWHX TDR Crash

E

edwin.arend155402d2

New member
Joined
Nov 29, 2025
Messages
24
Hello all,

I'm trying to figure out if there is a solution for this here. I'm honestly thinking about sending it back because I feel i tried almost everything.

So, I bought a A2XWHX 2 weeks ago and every once in a while it crashes, it has a VIDEO_TDR_FAILURE and either freezes up or restarts the laptop.
What i've tried so far:
- Update the NVIDIA drivers to the latest 581.80 version
- Update the Intel drivers
- I've turned the "Link state power management" off
- I've put the "Power management mode" in the NVIDIA control panel to "Prefer maximum performance"
- When that didn't work I reset windows with a clean install
- When that didn't work I reinstalled windows from USB and cleared the partitions so there was no default MSI software present.
- I've ran Memtest86 and the memory is fine
- I've ran Furmark and it runs fine
- Running games is fine for hours on end
- Disabled hardware acceleration in the browser (this is already something that i feel shouldn't be an issue.)
- I ran OCCT on the NVIDIA GPU and it's running fine
- I started OCCT on the Intel GPU and it ran fine, although last time i got a TDR while stopping that test.

Sometimes, from nowhere it gives a VIDEO_TDR_FAILURE. Not when the laptop is very busy, but more when i'm browsing images or videos.

I still am able to return the laptop for 2 more weeks without a reason before that stops. I love the performance, but i hate this crash.
Does anyone have an idea of anything that I might be able to do?

Thanks for your help in advance.
 
To give some more information I opened the minidump file (which is too large to attach here). I ran an analyze on it, and this is the outcome:

0: 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_MEMORY_MANAGEMENT_INTERNAL (10e)
The video memory manager encountered a condition that it can't recover from. By crashing,
the video memory manager is attempting to get enough information into the minidump such that
somebody can pinpoint what lead to this condition.
Arguments:
Arg1: 000000000000002d, The subtype of the BugCheck:
Arg2: ffff808959696b30
Arg3: ffff80895f6f9830
Arg4: ffffa98b8bb3efd0

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


KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 937

Key : Analysis.Elapsed.mSec
Value: 1246

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

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

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

Key : Analysis.Version.DbgEng
Value: 10.0.29457.1000

Key : Analysis.Version.Description
Value: 10.2506.23.01 amd64fre

Key : Analysis.Version.Ext
Value: 1.2506.23.1

Key : Bugcheck.Code.LegacyAPI
Value: 0x10e

Key : Bugcheck.Code.TargetModel
Value: 0x10e

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: 0x10e_2d_dxgmms2!VIDMM_PAGE_TABLE_BASE::GetCpuVisibleAddress

Key : Failure.Hash
Value: {ca00cb12-3ce5-2e41-c763-7f0f8a8fbadd}

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: 10e

BUGCHECK_P1: 2d

BUGCHECK_P2: ffff808959696b30

BUGCHECK_P3: ffff80895f6f9830

BUGCHECK_P4: ffffa98b8bb3efd0

FILE_IN_CAB: 112925-16828-01.dmp

TAG_NOT_DEFINED_202b: *** Unknown TAG in analysis list 202b


DUMP_FILE_ATTRIBUTES: 0x21808
Kernel Generated Triage Dump

FAULTING_THREAD: ffff9705b2ea2180

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1 (!blackboxwinlogon)


CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System

STACK_TEXT:
ffffa98b`8bb3eed8 fffff806`2c281316 : 00000000`0000010e 00000000`0000002d ffff8089`59696b30 ffff8089`5f6f9830 : nt!KeBugCheckEx
ffffa98b`8bb3eee0 fffff806`316bb18e : ffff8089`5f1f6540 ffff8089`59696b30 ffff8089`61e71c30 ffff9705`b2a72920 : watchdog!WdLogSingleEntry5+0x156
ffffa98b`8bb3ef70 fffff806`316ba15a : ffff8089`00010000 ffff9705`b2a72920 ffffa98b`8bb3f150 ffff8089`646aec70 : dxgmms2!VIDMM_PAGE_TABLE_BASE::GetCpuVisibleAddress+0x57e
ffffa98b`8bb3f050 fffff806`316b9fe0 : ffffc13d`347490f0 00000000`00000002 ffff8089`5f690100 ffff9705`b604b000 : dxgmms2!VIDMM_PAGE_TABLE_BASE::GetDriverUpdateAddress+0x66
ffffa98b`8bb3f0c0 fffff806`316cf240 : 00000000`00000000 00000000`00000000 00000000`00000057 00000000`00000200 : dxgmms2!VIDMM_PAGE_TABLE::UpdatePageTableInvalidate+0x50
ffffa98b`8bb3f190 fffff806`316d0247 : ffffa98b`8bb3f650 ffff8089`5f690100 ffffa98b`8bb3f650 00000000`00000000 : dxgmms2!VIDMM_PAGE_TABLE::CommitVirtualAddressRange+0xa30
ffffa98b`8bb3f280 fffff806`316d03ef : 00000000`00000002 ffff8089`5f690100 ffffa98b`8bb3f650 00000000`00000000 : dxgmms2!VIDMM_PAGE_DIRECTORY::CommitVirtualAddressRange+0xcf7
ffffa98b`8bb3f400 fffff806`316bece7 : 00000000`40000000 ffff8089`5f690100 ffffa98b`8bb3f650 00000000`00000000 : dxgmms2!VIDMM_PAGE_DIRECTORY::CommitVirtualAddressRange+0xe9f
ffffa98b`8bb3f580 fffff806`316f86ed : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : dxgmms2!CVirtualAddressAllocator::CommitVirtualAddressRange+0x9b7
ffffa98b`8bb3f710 fffff806`316dda50 : 00000000`00000000 00000000`00000000 00000000`00000000 ffff8089`5f68f110 : dxgmms2!VIDMM_GLOBAL::InitPagingProcessVaSpace+0x211
ffffa98b`8bb3f8b0 fffff806`316dbe7f : ffff8089`5f4af540 ffff8089`5f68fce0 ffff8089`5f68fce0 00000000`00000000 : dxgmms2!VIDMM_GLOBAL::ProcessSystemCommand+0x500
ffffa98b`8bb3f9b0 fffff806`316f1dff : ffff8089`5f68fce0 ffffa98b`8bb3fac9 fffff806`3165e2d0 ffff9705`b6054c20 : dxgmms2!VidMmSubmitPacket+0x15f
ffffa98b`8bb3fa10 fffff806`9a8815ea : ffff9705`b2ea2101 fffff806`316f1700 fffff806`2b2f1100 066fe47f`b19bbd02 : dxgmms2!VidMmWorkerThreadProc+0x69f
ffffa98b`8bb3fb30 fffff806`9aa9fd74 : fffff806`2b2f1180 ffff9705`b2ea2180 fffff806`9a881590 38808b49`2a79c984 : nt!PspSystemThreadStartup+0x5a
ffffa98b`8bb3fb80 00000000`00000000 : ffffa98b`8bb40000 ffffa98b`8bb39000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x34


SYMBOL_NAME: dxgmms2!VIDMM_PAGE_TABLE_BASE::GetCpuVisibleAddress+57e

MODULE_NAME: dxgmms2

IMAGE_NAME: dxgmms2.sys

IMAGE_VERSION: 10.0.26100.7171

STACK_COMMAND: .process /r /p 0xffff9705894e1040; .thread 0xffff9705b2ea2180 ; 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}

Followup: MachineOwner
---------
 
I don't know why the dump shows Windows 10, i'm running Windows 11 25h2 I've also updated the bios to E15M3IMS.114
1764453635639.png
 
Have you tried clean installing Nvidia graphics driver into different versions? Maybe 581.80 is causing the issue.
 
Yes I've done clean installs using DDU, that didn't work.
However this VBIOS is looking good.

If the issue still occurs i will try an older Nvidia driver version, and/or set the GPU to discrete GPU using the MSI Center turning off the intel.
 
Sadly same error is still happening, although today the laptop didn't restart. It managed to restore within windows, it seems to be the handshake issue between the Intel GPU and NVIDIA GPU.
I attached an analysis of every dump file it created.

I'll give an older driver a try, or turn off the intel GPU. But it's starting to feel like a hardware issue to me.

Any other ideas are more than welcome.
 

Attachments

The intel driver was up-to-date. I downgraded the NVIDIA driver to 573.22 (MSI version) and found out that Intel Platform Monitoring Technology driver had a new version.
I'll monitor it in this state for a few days.

I don't think that CPU virtualization is part of the TDR crash, however I did notice that TDR might actually be hiding the true origin of the crash.
 
I've asked the store if I can return it, even though I don't have the original packaging, and I'm waiting for an answer.

I'm actually scared this is a hardware failure, not a software failure, and I'm not feeling comfortable with the laptop anymore.
 
For this kind of error, you can restore the drivers provided from MSI website first and check if the problem persists.
At least the drivers on MSI website have been tested internally, could be stabler than the generic versions.
 
Raju said:
For this kind of error, you can restore the drivers provided from MSI website first and check if the problem persists.
At least the drivers on MSI website have been tested internally, could be stabler than the generic versions.
Click to expand...
Thank you, i now installed everything to the version of MSI. Returning was not an option without the original packaging, but it's ok.
Hopefully it will become more stable.
 
Alright, small update for those interested.

Installed all the MSI default driver version, updated everything that was out-of-date, remained on NVIDIA driver 573.22...
Everything seems stable now, haven't had any weird stuff happen.
 
Raju said:
For this kind of error, you can restore the drivers provided from MSI website first and check if the problem persists.
At least the drivers on MSI website have been tested internally, could be stabler than the generic versions.
Click to expand...
I had the same issue with my Katana 15HX. After switching to the NVIDIA Graphics Driver (573.22) provided by MSI, the system has been completely stable. It’s been running under heavy load for more than two days now, whereas before it would crash every 10–14 hours. So I believe this is not only the right solution, but the only one that actually works.
 
A-Mekky said:
I had the same issue with my Katana 15HX. After switching to the NVIDIA Graphics Driver (573.22) provided by MSI, the system has been completely stable. It’s been running under heavy load for more than two days now, whereas before it would crash every 10–14 hours. So I believe this is not only the right solution, but the only one that actually works.
Click to expand...
You're correct, also we found out the NVIDIA 581.15 driver is completely stable if you want to upgrade.
 
You must log in or register to reply.
Back
Top