Error code 0x00000139 appears to be a hardware or driver issue.
Error code 0x00000139 appears to be a hardware or driver issue.
My computer froze and shut down briefly while I was away (about five minutes, normal...). After restarting, it stayed idle. The issue isn’t clear—no prior occurrences, over a year of stable use. It created a DMP file but I’m not sure what to do with it. There’s an error code 0x00000139 that points to a possible driver problem. I haven’t updated drivers or made any hardware changes recently. Could be unrelated to the Nvidia drivers I’ve heard about. Yesterday was a regular Windows update Tuesday, installed without issues. Are there problems with the June 2025 update (KB5060842)? Might be connected to the Nvidia drivers. Right now I’m running version 576.40, which is the last stable release before that. I’ve never had issues with 572.xx or 576.xx versions. My specs are: Asus Prime B760-Plus D4 Intel i5 13400 (Intel says i3 and non-K i5 of Raptor Lake aren’t affected). RAM: 4x 8GB DDR4 Corsair Vengeance, CMK16GX4M2E3200C16, running at 2133MHz without XMP. GPU: RTX 4060, 8GB from Palit Kingston Fury Renegade 2TB NVMe. Storage: OS drive – Kingston NV2 1TB NVMe; Games – DISM found no corruption. sfc /scannow reported no errors. Memory tested with various apps and tools—no faults. SMART status is normal, media/data integrity intact. I’ve uploaded the DMP file. The last change was the Tuesday Windows update. @Bjoolz suggested network drivers might be involved. I’ve downloaded the newest Asus drivers and installed them. Fingers crossed that fixed it, but results will come later. Also updated chipset and other Asus drivers. Updated Microsoft hotfix 24 hours after the update. Read more about this fix here: https://www.windowslatest.com/2025/06/11...-and-more/ 061125-6468-01.dmp
Absolutely, exactly what you're saying. It's like each time Windows or Nvidia updates, it feels as though something unpredictable is happening, similar to playing Russian roulette with an automatic.
I made the change shortly after 7pm Swedish time, right after the Microsoft release. The article mentions the update was throttled to replace it with a different version. Could this mean I went too quickly and received a poorly delivered update? Damn mess.
Analyzing data from a single dump file may lead to misleading results since some problems can unfairly point to random drivers. With many Windows networking drivers involved, updating one might not resolve the issue—especially if corruption occurred. It's difficult to be certain based on just one dump. You could attempt DISM followed by SFC, but I haven't seen much success with Windows repair tools, even when they claim to have fixed it and new scans show nothing. Having 3-5 dump files provides a solid basis for troubleshooting.
I changed the drivers in September last year on the Asus website, keeping the files in the download folder and verifying the dates. I double-checked on the Asus site and noticed a new driver released two days after my last check… lol I updated the network drivers now. It seems the June 2025 update might not have worked with the previous network driver version—hope it fixed it. I’ll keep the thread open for about a month. DISM didn’t detect any corruption, and I also refreshed chipset and other Asus drivers.
It hasn't been identified such issues by the Q&A team before the scheduled monthly patch Tuesday during the beta preview. This should have been addressed earlier. Frustrating for Microsoft.
We encountered many users experiencing the same issue, and these crashes appeared distinct. Below are examples of what those crashes looked like: Here’s how your crash appeared: It’s possible they’re connected, but it seems the recent patch might have affected other areas beyond just EAC. I don’t see clear evidence linking this to EAC specifically.
War Thunder previously used EAC, but I couldn't even access 24H2 at one point because Microsoft removed it for players with it. Over time, the developers switched their anti-cheat method, and soon I received 24H2 again. It's possible the June patch might have caused issues with other anti-cheats too, or something else broke during that update. Everything seemed fine before the patch, so it's likely a bug introduced with it. As long as I haven't experienced any more bluescreens, I'm good. I've updated my network and chipset drivers, and also installed the latest KB update the next day.