Build 9926 - Upgrade - VIDEO_DXG_KRNL_FATAL_ERROR


Recommended Posts

I've done a few attempts to upgrade from my current Win 10 Build (9879), but after 90 minutse, I keep getting a blue screen of death while PC settings are being applied (so yes, devices are already supposed to be ready).  The error indicates: VIDEO_DXG_KRNL_FATAL_ERROR

 

After the second try, Windows Update offered me about 10 driver updates - previously not available, and I always have the latest drivers from the Dell website. Oh, I'm using x64, with a Dell Inspiron 17, 5000-series.

 

Will I have to wait for proper Windows 10 drivers from Dell? Or how to avoid this error? After rebooting, I can't try a safe-mode solution, it immediately restores the previous build from which I was upgrading.

 

Will I have to wait for proper Windows 10 drivers from Dell? Or how to avoid this error? After rebooting, I can't try a safe-mode solution, it immediately restores the previous build from which I was upgrading.

 

Waiting for Dell to release drivers ... Nice Joke.

 

Which graphics cards do you have?

 

Did you obtain the latest drivers?

I'll try with the latest nVidia driver I could find on nVidia.

 

As for Intel, it claims my system doesn't meet the minimum requirements - but I'm expecting it's an OS issue (I've tried to run it in compatibilitiy mode). I also noticed that the integrated Intel driver only supports DirectX 11 so far. But I don't think that *should* be an issue?

 

- Alternative: what would happen if I actually try to uninstall those specific drivers completely?

I would expect the latest Nvidia Beta driver to work at the very least.

 

The Intel that gets installed by MS might already be updated and good to go!

 

Only having DX11 won't be an issue. I guess at some point Intel will enable DX12 support on your HD 4400!

 

Then you have the whole thing with optimus going on. 

 

If you clean your drivers with a tool such as DDU then the Windows Standard Display drivers should activate*

I would like to avoid a clean install. I've only tried the upgrade path so far, which I hoped would work from the 9879 bulid.

 

The upgrade seems to go well, "getting ready for devices" goes well, but the error comes up somewhere a bit after 80% "applying PC settings".

You are making it unnecessary hard for yourself as this is not RTM : ).

 

Now you have tried the obvious:

 

Removing the drivers (Intel and AMD) with DDU prior to upgrade.

 

However:

 

Recently we came across a bug where AMD APU devices (PXAA) would crash during AMD driver install on the latest Win build.

 

The solution was to set the UEFI to Legacy boot (BIOS). It removed the error 43 in Device Manager and allowed the graphics card to work.

 

This was happening because MS is making some changes to their driver backend.

 

 

You could try that if your Dell has this functional in the UEFI.

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • AltSendme 0.4.1 by Razvan Serea AltSendme is a minimal, cross-platform application designed for fast, secure, and private peer-to-peer file transfers. It allows users to send files or entire directories directly between devices without relying on cloud servers, accounts, or any personal information. Everything is encrypted end-to-end using modern protocols like QUIC and TLS 1.3, ensuring both strong security and low-latency performance. Transfers are verified with BLAKE3 for data integrity, and interrupted downloads automatically resume, making the experience reliable even on unstable connections. You can transfer anything—images, videos, documents, and more. Integrity checks are performed on both ends, so your files are automatically verified for correctness during both sending and receiving. AltSendme works seamlessly across local networks or long-distance links, capable of saturating multi-gigabit connections for extremely fast delivery. With built-in NAT traversal and encrypted relay fallback, it connects devices almost anywhere. The app integrates with the Sendme CLI and will soon support mobile and web platforms. Fully free and open-source, AltSendme offers a lightweight, privacy-first alternative to traditional cloud-based services, removing size limits, upload costs, and unnecessary data exposure. AltSendme 0.4.1 changelog: Release Highlights Self-hosted relays: Run your own iroh relay so transfers don't rely on public infrastructure. Includes a full deployment template in deploy/relay/ with Docker Compose for a VPS and configuration examples for production use. Fly.io support: One-click deploy template for Fly.io, including a quick-start config (fly.dev.toml) for testing without a custom domain, plus production setup with Let's Encrypt and your own hostname. Relay settings UI: New Settings → Network panel to choose how AltSendme connects: automatic public relays, custom self-hosted URLs (with optional auth token), or disabled. Test connections, verify latency, and see live relay status in the footer. Disable relays: Turn off relay servers entirely when you only need same-network transfers (e.g. LAN). Direct connections only. No relay hop required when devices can reach each other. Android graduates from beta: Android is now part of the regular release cycle alongside desktop. APKs ship with each version (universal, arm64, and armv7). Other improvements Private relay access control via shared auth token Relay fallback notifications when a custom relay is unreachable Broadcast mode toggle in sharing settings Android release build fixes (split-per-ABI APKs, universal APK preservation) UI polish: mobile safe-area insets, dropzone layout, transfer progress animation Bug fixes for minification-related serialization issues and system tray icon loading What's Changed feat(relay): add relay status functionality and settings UI (a120cdf) feat(relay): implement custom relay server configuration and verification (51276c7) feat(relay): add configuration for private relay access and enhance observability features (48fbabf) feat(relay): enhance relay URL validation, display connection status (d4fffa0) feat(relay): add RelayChangeGuard component and enhance relay-related translations (16ba514) feat(broadcast): add toggle setting for broadcast mode in sharing UI (ca6d977) fix(relay): correct QUIC discovery port, pin image, templatize fly.dev (52a2ba5) fix: More broken serialization due to minification (67491a9) fix(android): preserve true universal APK across per-ABI builds (e9f256f) fix(ui): conditional safe-area insets padding on mobile (1182f0e) refactor(transfer): CircularRing component animation fix (944572b) chore(android): drop x86 and x86_64 release APKs, keep universal+arm64+armv7 (34ada0b) Download: AltSendme 0.4.1 | ARM64 | ~9.0 MB (Open Source) Download: AltSendme for MacOS | Android Links: AltSendme Home Page | GitHub | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • You are mostly right about the ephemeral nature of it. As I mention in the article, if you dont add a second device or take a backup of your account before uninstalling it, then yes you will lose access to your account. That said, in terms of actual user experience when you sync multiple devices your message history carries across and there's also a Saved Messages chat like there is on Telegram to send messages and attachments between your installs. But yh, what you point out are correct and its not trying to emulate Messenger or Telegram.
    • OK so SearXNG is a meta search engine that you can install locally or use via a public instance. It scrapes other search engines which you choose and then sorts the results. Not as complicated as multiple relays
    • The only difference here is that you think you came up with these reasons. You didn't. These age old fearmongering lies (that were NEVER true) were funded by and the anger stoked by Putin through proxies like Farage (and later in the USA, Trump) and filtered down through the skinheads, Neonazis, etc. until it reached the uninformed, ignorant, and gullible -- never realizing they were being played for fools against their own best interests. Even now, despite all of the EVIDENCE proving that Brexit was a terrible mistake for ALL citizens of the UK and that its supporters were tricked by Putin's proxies into sabotaging their own nation, you're still here defending these well-known lies as if they were ever true. Not only are they not true. They NEVER were. So, when are you going to realize that you were lied to and actually get angry at the liars and charlatans who lied to you, instead of blaming the innocent people they lied to you about?
    • Dupe of "Microsoft further improving Windows 11 Taskbar with latest builds", published <20 minutes apart
  • Recent Achievements

    • Week One Done
      flexorcist earned a badge
      Week One Done
    • One Month Later
      Woland13 earned a badge
      One Month Later
    • Week One Done
      Woland13 earned a badge
      Week One Done
    • One Year In
      bernmeister earned a badge
      One Year In
    • Week One Done
      Scoobystu earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      495
    2. 2
      +Edouard
      225
    3. 3
      PsYcHoKiLLa
      152
    4. 4
      Steven P.
      75
    5. 5
      FloatingFatMan
      71
  • Tell a friend

    Love Neowin? Tell a friend!