Bluescreen with 0x00000139 code
55 minutes ago, Mumintroll said:My pc just bluescreened (while I was away for 5 minutes, typical....) and rebooted. It didn't do anything then, just being idle.
I'm unsure what caused the bluescreen, it hasn't happened before and my pc has been stable for over a year now. I built it in october 2023.
It did generate a dmp file but I'm not sure how to read through it. There is an error code 0x00000139 which when googling it seems to suggest a bad driver? I haven't updated any driver or done any hardware changes recently. But I don't know if it means something else.
Yesterday was the regular Windows update patch tuesday. It installed the update without any problems. Are there any issues with June 2025 update, KB5060842 ?
Could it be the dreaded Nvidia drivers?
At the moment I'm using 576.40, which is the previous drivers.
Although I've never encountered any problems at all with the 572.xx and 576.xx versions.
My hardware specs are
Asus Prime B760-Plus D4
Intel i5 13400 (according to Intel the i3 and non-K i5 of Raptor lakes are not affected by degradation so...)
4x 8gb DDR4 Corsair Vengeance, CMK16GX4M2E3200C16, but running without XMP so 2133mhz.
RTX 4060, 8gb from Palit
Kingston Fury Renegade 2tb nvme. (OS drive)
Kingston NV2 1tb nvme. (Games)
sfc /scannow didn't find any errors.
Have tested the memory with different apps, the memtest apps and Windows memory diagnostics. No errors.
The SMART values are all fine, no error on Media and Data integrity field.
I have uploaded the dmp file.
The latest change I could think of is the yesterday's Windows update....
I'm on Windows 11 Home 24H2.
Debugging from just one dump file can be inaccurate because certain issues can cause random drivers to be blamed.
This has lots of Windows networking drivers involved so you can try updating the driver for the network card, but chances are that you got some corruption to one of those Windows drivers (Unless it's one of those issues that causes random stuff to be blamed). Hard to say for sure from just one dump file. You can try running DISM and then SFC, but I've not had much luck with Windows' repair tools, even when it says that it fixed the issue and new scans don't find anything.
3-5 dump files is a good amount.

Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now