Category published:  Uncategorized Deployment VMWare   Click on the Category button to get more articles regarding that product.

W11 VMWARE Workstation white screen crash when you open EDGE Browser and Nvidia

Posted by admin on 02.11.2025

image

Not fixed date 06.11.2025 with 17.6.4 BUILD 24832109

W11 24H2 and 25H2 same behavior. Started 4-5 months ago. VMWARE Pro Update did not resolve.

What happens

You have VMWARE Workstation PRO running a machine open

When you open a NEW EDGE Browser suddenly the W11 freezes and hangs for a few ticks then comes back.

After that the VMWARE shows a blank white screen. You can’t Turn off the VM with VM commands and sometimes you have to kill process or reboot

Problem

On Windows 11 24H2 or 25H2, opening Microsoft Edge while a VMware Workstation VM is running can cause a short system freeze. After that, VMware Workstation shows a white screen and the VM becomes unresponsive.

Cause

A conflict between Edge’s hardware acceleration (Chromium GPU rendering) and VMware Workstation’s 3D acceleration (DirectX / WDDM) triggers a GPU context reset. This began after recent Windows 11 graphics stack updates.

Solutions pathway:

1. Disable Hardware Acceleration in Edge

Open Edge → Settings → System and Performance

image

image

Disable Use hardware acceleration when available

Restart Edge.

2. Disable 3D Acceleration in VMware

In VMware Workstation, select the VM → Edit virtual machine settings → Display

Uncheck Accelerate 3D graphics

image

Start the VM again.

3. Change VMware Graphics Engine Mode

Edit → Preferences → Display

Switch hardware acceleration mode from Auto to another setting and test.

Update to VMware Workstation 17.5.2 or newer if available.

 

4. Update GPU Drivers

Install the latest graphics driver directly from the GPU vendor (NVIDIA, AMD, Intel). Reboot after installation.

This never solved it for us ;-(

image

 

5. Turn Off Edge “Startup Boost”

Edge → Settings → System and Performance

Disable Startup boost.

 

6. Optional: Force OpenGL Renderer in VMware

Edit
%AppData%\VMware\preferences.ini
Add:

mks.enableDX11Renderer = "FALSE"
mks.enableGLRenderer = "TRUE"

Save and restart VMware Workstation.

 Result

After these adjustments, opening Edge no longer freezes the host or turns VMware Workstation windows white. The conflict between Edge and VMware’s GPU pipelines is eliminated.Problem

 Evidence of error:

image

 

System Event ID 153
The description for Event ID 153 from source nvlddmkm 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\Video1
Restarting TDR occurred on GPUID:100

The message resource is present but the message was not found in the message table

TDR is Windows detecting that the GPU stopped responding and tried to recover.

  • \Device\Video1 is the GPU device that failed.
  • Restarting TDR occurred on GPUID:100 means the GPU driver crashed briefly and was restarted by Windows.

Analyse of some crash dump: C:\Windows\LiveKernelReports\WATCHDOG-20251105-0847.dmp

0: kd> !analyze -v
Loading Kernel Symbols
...............................................................
................................................................
................................................................
.................................
Loading User Symbols

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

VIDEO_ENGINE_TIMEOUT_DETECTED (141)
One of the display engines failed to respond in timely fashion.
(This code can never be used for a real BugCheck; it is used to identify live dumps.)
Arguments:
Arg1: ffff8081794f1010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff8015d704580, The pointer into responsible device driver module (e.g. owner tag).
Arg3: 0000000000000000, The secondary driver specific bucketing key.
Arg4: ffff80816cd680c0, Optional internal context dependent data.

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

Unable to load image \SystemRoot\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_fe5f369669db2f36\nvlddmkm.sys, Win32 error 0n2
Page 801891 not present in the dump file. Type ".hh dbgerr004" for details

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 2484

    Key  : Analysis.Elapsed.mSec
    Value: 5927

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

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

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

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

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

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

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

    Key  : Bugcheck.Code.TargetModel
    Value: 0x141

    Key  : Dump.Attributes.AsUlong
    Value: 0x10

    Key  : Failure.Bucket
    Value: LKD_0x141_IMAGE_nvlddmkm.sys

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

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

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

    Key  : Failure.Hash
    Value: {341dd0b3-9ebd-47a8-9de8-23f4b00fabbc}

    Key  : Faulting.IP.Type
    Value: Paged

    Key  : Hypervisor.Enlightenments.Value
    Value: 0

    Key  : Hypervisor.Enlightenments.ValueHex
    Value: 0x0

    Key  : Hypervisor.Flags.AnyHypervisorPresent
    Value: 0

    Key  : Hypervisor.Flags.ApicEnlightened
    Value: 0

    Key  : Hypervisor.Flags.ApicVirtualizationAvailable
    Value: 0

    Key  : Hypervisor.Flags.AsyncMemoryHint
    Value: 0

    Key  : Hypervisor.Flags.CoreSchedulerRequested
    Value: 0

    Key  : Hypervisor.Flags.CpuManager
    Value: 0

    Key  : Hypervisor.Flags.DeprecateAutoEoi
    Value: 0

    Key  : Hypervisor.Flags.DynamicCpuDisabled
    Value: 0

    Key  : Hypervisor.Flags.Epf
    Value: 0

    Key  : Hypervisor.Flags.ExtendedProcessorMasks
    Value: 0

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

    Key  : Hypervisor.Flags.Phase0InitDone
    Value: 0

    Key  : Hypervisor.Flags.PowerSchedulerQos
    Value: 0

    Key  : Hypervisor.Flags.RootScheduler
    Value: 0

    Key  : Hypervisor.Flags.SynicAvailable
    Value: 0

    Key  : Hypervisor.Flags.UseQpcBias
    Value: 0

    Key  : Hypervisor.Flags.Value
    Value: 131072

    Key  : Hypervisor.Flags.ValueHex
    Value: 0x20000

    Key  : Hypervisor.Flags.VpAssistPage
    Value: 0

    Key  : Hypervisor.Flags.VsmAvailable
    Value: 0

    Key  : Hypervisor.RootFlags.AccessStats
    Value: 0

    Key  : Hypervisor.RootFlags.CrashdumpEnlightened
    Value: 0

    Key  : Hypervisor.RootFlags.CreateVirtualProcessor
    Value: 0

    Key  : Hypervisor.RootFlags.DisableHyperthreading
    Value: 0

    Key  : Hypervisor.RootFlags.HostTimelineSync
    Value: 0

    Key  : Hypervisor.RootFlags.HypervisorDebuggingEnabled
    Value: 0

    Key  : Hypervisor.RootFlags.IsHyperV
    Value: 0

    Key  : Hypervisor.RootFlags.LivedumpEnlightened
    Value: 0

    Key  : Hypervisor.RootFlags.MapDeviceInterrupt
    Value: 0

    Key  : Hypervisor.RootFlags.MceEnlightened
    Value: 0

    Key  : Hypervisor.RootFlags.Nested
    Value: 0

    Key  : Hypervisor.RootFlags.StartLogicalProcessor
    Value: 0

    Key  : Hypervisor.RootFlags.Value
    Value: 0

    Key  : Hypervisor.RootFlags.ValueHex
    Value: 0x0

    Key  : SecureKernel.HalpHvciEnabled
    Value: 0

    Key  : WER.OS.Branch
    Value: ge_release

    Key  : WER.OS.Version
    Value: 10.0.26100.1

    Key  : WER.System.BIOSRevision
    Value: 18.0.0.0


BUGCHECK_CODE:  141

BUGCHECK_P1: ffff8081794f1010

BUGCHECK_P2: fffff8015d704580

BUGCHECK_P3: 0

BUGCHECK_P4: ffff80816cd680c0

FILE_IN_CAB:  WATCHDOG-20251105-0847.dmp

DUMP_FILE_ATTRIBUTES: 0x10
  Live Generated Dump

FAULTING_THREAD:  ffff808154461080

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


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

PROCESS_OBJECT: ffff80816cd680c0

PROCESS_NAME:  msedge.exe

IP_IN_PAGED_CODE: 
nvlddmkm+1a44580
fffff801`5d704580 488b05d9298aff  mov     rax,qword ptr [nvlddmkm+0x12e6f60 (fffff801`5cfa6f60)]

STACK_TEXT:  
ffff9104`992efe70 fffff801`c1f94c65     : 00000000`00000000 00000000`00000000 ffff9104`992eff40 ffff8081`54461080 : nt!IopLiveDumpCollectPages+0xd9
ffff9104`992efec0 fffff801`c2550ccf     : 00000000`00000000 ffff8081`54461080 ffff9104`992eff40 00000000`00000002 : nt!IopLiveDumpEndMirroringCallback+0x55
ffff9104`992efef0 fffff801`c1f9428a     : 00000000`00000000 00000000`00000000 ffff8081`7aa80010 ffff9104`992f03b8 : nt!MmDuplicateMemory+0x2e7
ffff9104`992eff80 fffff801`c1f9436c     : 00000000`00000000 fffff801`c209f910 00000000`00000000 00000000`00000000 : nt!IopLiveDumpCapture+0x86
ffff9104`992effe0 fffff801`c1ee0e88     : ffff8081`7aa80010 ffff8081`7aa80010 ffff8081`7aa804c0 00000000`00000000 : nt!IopLiveDumpCaptureMemoryPages+0x50
ffff9104`992f0120 fffff801`c249259d     : 00000000`00000000 ffff8081`5a273300 00000000`00000038 ffffe38a`e76593c0 : nt!IoCaptureLiveDump+0x428
ffff9104`992f0350 fffff801`c20fac98     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!DbgkpWerCaptureLiveFullDump+0x181
ffff9104`992f03b0 fffff801`c24a1e6a     : ffffe38a`00000003 00000000`00000000 00000000`00000000 fffff801`5399190c : nt!DbgkpWerProcessPolicyResult+0x30
ffff9104`992f03e0 fffff801`c24a1c69     : 00000000`00000001 ffff9104`992f05c0 ffff8081`794f1010 ffff8081`68203090 : nt!DbgkWerCaptureLiveKernelDump2+0x1ea
ffff9104`992f0440 fffff801`53ceca99     : ffffe38a`e72f3900 ffffe38a`e72f3900 ffffe38a`f11267bf ffff8081`59e1d000 : nt!DbgkWerCaptureLiveKernelDump+0x69
ffff9104`992f04c0 fffff801`668a829a     : 00000000`00000006 00000000`00000006 ffff8081`59ef2000 ffff8081`59e1f000 : dxgkrnl!TdrCollectDbgInfoStage1+0xd29
ffff9104`992f0680 fffff801`669061e6     : ffff8081`59ef2000 ffff8081`59ef2000 ffff8081`59e1f000 00000000`00000000 : dxgmms2!VidSchiResetEngine+0x36e
ffff9104`992f0870 fffff801`6690ebf6     : ffff9104`00000000 ffff8081`59e1f000 ffff9104`992f09f9 00000000`00000000 : dxgmms2!VidSchiResetEngines+0xea
ffff9104`992f08c0 fffff801`66883c4f     : ffff8081`59e1f000 00000000`00000000 ffff9104`992f09f9 00000000`0000cf68 : dxgmms2!VidSchiCheckHwProgress+0x316
ffff9104`992f0950 fffff801`6690f5b2     : ffff8081`59e1f000 ffff8081`5a5df010 ffff8081`6cd0c520 ffff8081`775f06e0 : dxgmms2!VidSchiScheduleCommandToRun+0x5f
ffff9104`992f0a60 fffff801`669063d1     : ffff8081`59e1f500 ffff8081`59e1f000 fffff801`669062f0 ffff8081`59e1f000 : dxgmms2!VidSchiRun_PriorityTable+0x42
ffff9104`992f0ab0 fffff801`c1e81afa     : ffff8081`54461080 fffff801`00000001 ffff9280`4ee69180 024fa4ef`bd9bbfff : dxgmms2!VidSchiWorkerThread+0xe1
ffff9104`992f0af0 fffff801`c209ef84     : ffff9280`4ee69180 ffff8081`54461080 fffff801`c1e81aa0 00690074`00630065 : nt!PspSystemThreadStartup+0x5a
ffff9104`992f0b40 00000000`00000000     : ffff9104`992f1000 ffff9104`992ea000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x34


SYMBOL_NAME:  nvlddmkm+1a44580

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

STACK_COMMAND: .process /r /p 0xffff80813a6b9040; .thread 0xffff808154461080 ; kb

FAILURE_BUCKET_ID:  LKD_0x141_IMAGE_nvlddmkm.sys

OS_VERSION:  10.0.26100.1

BUILDLAB_STR:  ge_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {341dd0b3-9ebd-47a8-9de8-23f4b00fabbc}

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

 

 


 Category published:  Uncategorized Deployment VMWare   Click on the Category button to get more articles regarding that product.

Related Post

Unable to migrate Trellix Endpoint ENS 10.7.19, Event 1000, MSVCP140.dll, mfeesp.exe, Error communicating with the Event Log

WSUS Out of Band Patch Installer – CVE-2025-59287 for all OS automatic

Packet loss older NIC VMWARE 1.9.11.0 on ESXi 8.0.2

Template theme: Newsup by Themeansar (External Link, you will leave www.butsch.ch).