Question BSOD - Bugcheck 0x00000139 Windows 11

Toggle sidebar Toggle sidebar
M

Michu

Jan 4, 2025
7
0
10
Hi, I ran into a problem on windows 11. BSODs began to appear periodically, at random points in time. I would be very grateful if you could help me solve this problem.
All I managed to do
was check the RAM using memtest86 (I didn't save the dump, but the program wrote that the RAM was fine)
I also looked at the minidump file -
- <Event xmlns=" ">
- <System>
<Provider Name="Microsoft-Windows-WER-SystemErrorReporting" Guid="{abce23e7-de45-4366-8631-84fa6c525952}" />
<EventID>1001</EventID>
<Version>1</Version>
<Level>2</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x8000000000000000</Keywords>
<TimeCreated SystemTime="2025-01-04T22:34:09.9549145Z" />
<EventRecordID>38975</EventRecordID>
<Correlation />
<Execution ProcessID="752" ThreadID="748" />
<Channel>System</Channel>
<Computer>DESKTOP-K8BI75D</Computer>
<Security UserID="S-1-5-18" />
</System>
- <EventData>
<Data Name="param1">0x0000013a (0x0000000000000011, 0xffffca8889802140, 0xffffca88a10aea80, 0x0000000000000000)</Data>
<Data Name="param2">C:\WINDOWS\Minidump\010525-7781-01.dmp</Data>
<Data Name="param3">5c4606f0-b832-4304-a2e9-b3ae115cff84</Data>
</EventData>
</Event>
I also included a full dump (I'm not sure what it's called correctly) so after the next BSOD I will be able to attach it.
components:
PSU - Deepcool PF600, 600W, 80+ Standart or Deepcool PF650 650W (I'm not sure because I need to take out the PSU completely to see); 3-4 ages; it was purchased in a store and immediately installed on a PC.
Disk drivers -
1. Transcend 256 GB SATA TS256GSSD370S; capacity - 236,4; 37,4 - free (windows is installed here)
2. Western Digital 1 TB WD10EZEX-08RKKA0; capacity - 930,8 in total but it is divided into two parts: 1 - 832 GB / 83,8 - free; 2 - 98,8 GB / 1,64 - free
OS - Microsoft Windows 11 Pro; Multiprocessor Free (64-bit); version - 10.0.22631.4602; date of installation - 24.06.2024
Attached peripherals - keyboard, mouse, headphones, graphics tablet
CPU - HexaCore Intel Core i5-11400F, 4300 MHz (43 x 100)
Motherboard - MSI H510M Pro-E (MS-7D23) (2 PCI-E x1, 1 PCI-E x16, 2 DDR4 DIMM, Audio, Video, Gigabit LAN)
VRAM - DIMM1(2): Kingston Fury KF3200C16D4/8GX 8 GB DDR4-3000 DDR4 SDRAM
BIOS - AMI (04/06/2022)
GPU - NVIDIA GeForce RTX 3060 (12 GB)
 
Last edited:
Sort by date Sort by votes
A couple of things from the update:

1) The PSU, especially if 3 - 4 years old, may be starting to falter and fail. The 650 watts may be a bit low for the system especially at times of peak power demand.

2) Disk drives: My general rule of thumb is that any given disk drive should always have about 20 - 30% free space.

The C: drive is down to about 15.8% (37.4/236.4). I would want more free space on my boot drive if at all possible.

The partitioned 1 TB Western Digital drive is also low: Part 1 = 10% (83.8/832) and Part 2 = 1.7% (1.64/98.8).

System disk space is limited and low overall provided that I correctly understood and calculated the values. Do check to be sure.

3) RAM: not at all sure about installed RAM and VRAM. Appears that there is mixed RAM installed - needs clarification. Please clarify the physical RAM installation and configuration.

Open the Disk Management window and expand so that all can be seen.

Take a screenshot and post the screenshot here via imgur (www.imgur.com).

Start thinking about how more disk space can be freed up. Run Disk Cleaner to look but do not immediately execute any cleaning.

Ensure that all important data is backed up at least 2 x to locations away from the host computer in question. Verify that backups are recoverable and readable.

There may be other comments and suggestions.
 
Upvote 0 Downvote
Ralston18 said:
A couple of things from the update:

1) The PSU, especially if 3 - 4 years old, may be starting to falter and fail. The 650 watts may be a bit low for the system especially at times of peak power demand.

2) Disk drives: My general rule of thumb is that any given disk drive should always have about 20 - 30% free space.

The C: drive is down to about 15.8% (37.4/236.4). I would want more free space on my boot drive if at all possible.

The partitioned 1 TB Western Digital drive is also low: Part 1 = 10% (83.8/832) and Part 2 = 1.7% (1.64/98.8).

System disk space is limited and low overall provided that I correctly understood and calculated the values. Do check to be sure.

3) RAM: not at all sure about installed RAM and VRAM. Appears that there is mixed RAM installed - needs clarification. Please clarify the physical RAM installation and configuration.

Open the Disk Management window and expand so that all can be seen.

Take a screenshot and post the screenshot here via imgur (www.imgur.com).

Start thinking about how more disk space can be freed up. Run Disk Cleaner to look but do not immediately execute any cleaning.

Ensure that all important data is backed up at least 2 x to locations away from the host computer in question. Verify that backups are recoverable and readable.

There may be other comments and suggestions.
Click to expand...
Thanks for your help, I will try to solve the problem with the disks, if it helps or not, I will write here. About RAM (I got something mixed up in the post, apparently) here's a link to imgur
https://imgur.com/a/S6uBJLH
View: https://imgur.com/a/S6uBJLH
https://imgur.com/a/MY84I1z
View: https://imgur.com/a/MY84I1z

- this is a screenshot from AIDA64 - I'm not quite sure why, but it shows that one die is on 1 slot and the other on 3, although I have only 2 slots on the motherboard.
 
Upvote 0 Downvote
Ralston18 said:
This motherboard?

https://download-2.msi.com/archive/mnu_exe/mb/M7D23v1.0.pdf

[Do verify that I found the applicable User Guide.]

Run CPU-Z and determine what RAM CPU-Z reports.

Refer to the User Guide to reread and review that all installed components are supported and correctly configured.

Especially RAM. Pull and check specs if questions/problems continue.
Click to expand...
Yes, it's that motherboard. I found a couple of oddities related to RAM, in CPU-Z it says that the frequency is 1200 on both, although the manufacturer stated it to be 3200 Mhz. Plus, in the manual that you send, it says that the motherboard does not support such frequencies at all. As for the fact that one bar is displayed in 1 slot, and the second in 3 - I think this is due to the fact that I have 2-channel mode enabled (but maybe I'm wrong)
https://imgur.com/a/EKdkNNd
View: https://imgur.com/a/EKdkNNd
there are 3 screenshots
 
Last edited:
Upvote 0 Downvote
Only one immediate suggestion.

Instead of third party utilities, take a look at RAM via the Command Prompt or Powershell.

FYI:

https://www.windowscentral.com/how-...-size-type-part-number-form-factor-windows-10

Example results from my computer:


PS C:\WINDOWS\system32> wmic memorychip list full


BankLabel=
Capacity=8589934592
DataWidth=64
Description=Physical Memory
DeviceLocator=DIMM1
FormFactor=8
HotSwappable=
InstallDate=
InterleaveDataDepth=1
InterleavePosition=1
Manufacturer=029E000080AD
MemoryType=0
Model=
Name=Physical Memory
OtherIdentifyingInfo=
PartNumber=CMK16GX4M2B3000C15
PositionInRow=1
PoweredOn=
Removable=
Replaceable=
SerialNumber=00000000
SKU=
Speed=2133
Status=
Tag=Physical Memory 0
TotalWidth=64
TypeDetail=128
Version=


BankLabel=
Capacity=8589934592
DataWidth=64
Description=Physical Memory
DeviceLocator=DIMM2
FormFactor=8
HotSwappable=
InstallDate=
InterleaveDataDepth=1
InterleavePosition=2
Manufacturer=029E000080AD
MemoryType=0
Model=
Name=Physical Memory
OtherIdentifyingInfo=
PartNumber=CMK16GX4M2B3000C15
PositionInRow=1
PoweredOn=
Removable=
Replaceable=
SerialNumber=00000000
SKU=
Speed=2133
Status=
Tag=Physical Memory 1
TotalWidth=64
TypeDetail=128
Version=

PS C:\WINDOWS\system32>

Your results will of course be different.

The objective being to compare what Windows "sees" to what AIDA64 and CPU-Z present along with what you know about the installed RAM and Motherboard information.

In the meantime there are several members here who are well versed in RAM and one or more of them may post observations, comments, and suggestions about the oddities.
 
Upvote 0 Downvote
BankLabel=BANK 0
Capacity=8589934592
DataWidth=64
Description=Physical Memory
DeviceLocator=Controller0-ChannelA-DIMM0
FormFactor=8
HotSwappable=
InstallDate=
InterleaveDataDepth=2
InterleavePosition=1
Manufacturer=Kingston
MemoryType=0
Model=
Name=Physical Memory
OtherIdentifyingInfo=
PartNumber=KF3200C16D4/8GX
PositionInRow=
PoweredOn=
Removable=
Replaceable=
SerialNumber=7C5D1216
SKU=
Speed=2400
Status=
Tag=Physical Memory 0
TotalWidth=64
TypeDetail=128
Version=


BankLabel=BANK 1
Capacity=8589934592
DataWidth=64
Description=Physical Memory
DeviceLocator=Controller0-ChannelB-DIMM0
FormFactor=8
HotSwappable=
InstallDate=
InterleaveDataDepth=2
InterleavePosition=2
Manufacturer=Kingston
MemoryType=0
Model=
Name=Physical Memory
OtherIdentifyingInfo=
PartNumber=KF3200C16D4/8GX
PositionInRow=
PoweredOn=
Removable=
Replaceable=
SerialNumber=775D1215
SKU=
Speed=2400
Status=
Tag=Physical Memory 2
TotalWidth=64
TypeDetail=128
Version=
 
Upvote 0 Downvote
Ralston18 said:
Only one immediate suggestion.

Instead of third party utilities, take a look at RAM via the Command Prompt or Powershell.

FYI:

https://www.windowscentral.com/how-...-size-type-part-number-form-factor-windows-10

Example results from my computer:


PS C:\WINDOWS\system32> wmic memorychip list full


BankLabel=
Capacity=8589934592
DataWidth=64
Description=Physical Memory
DeviceLocator=DIMM1
FormFactor=8
HotSwappable=
InstallDate=
InterleaveDataDepth=1
InterleavePosition=1
Manufacturer=029E000080AD
MemoryType=0
Model=
Name=Physical Memory
OtherIdentifyingInfo=
PartNumber=CMK16GX4M2B3000C15
PositionInRow=1
PoweredOn=
Removable=
Replaceable=
SerialNumber=00000000
SKU=
Speed=2133
Status=
Tag=Physical Memory 0
TotalWidth=64
TypeDetail=128
Version=


BankLabel=
Capacity=8589934592
DataWidth=64
Description=Physical Memory
DeviceLocator=DIMM2
FormFactor=8
HotSwappable=
InstallDate=
InterleaveDataDepth=1
InterleavePosition=2
Manufacturer=029E000080AD
MemoryType=0
Model=
Name=Physical Memory
OtherIdentifyingInfo=
PartNumber=CMK16GX4M2B3000C15
PositionInRow=1
PoweredOn=
Removable=
Replaceable=
SerialNumber=00000000
SKU=
Speed=2133
Status=
Tag=Physical Memory 1
TotalWidth=64
TypeDetail=128
Version=

PS C:\WINDOWS\system32>

Your results will of course be different.

The objective being to compare what Windows "sees" to what AIDA64 and CPU-Z present along with what you know about the installed RAM and Motherboard information.

In the meantime there are several members here who are well versed in RAM and one or more of them may post observations, comments, and suggestions about the oddities.
Click to expand...
it seems to be 2400 Mhz, is this the norm? the instructions say that the motherboard supports 2133/2666, but not 2400
 
Upvote 0 Downvote
I was hoping to spot something amiss in the results - not noting anything.

Perhaps another member will spot something....

= = = =

If all was well before I would expect that 2400 would be/was fine.

Caveat being that end users can configure RAM for what ever purposes or requirements might be in mind.

With the premise that you did not make (or knowingly make) any such configuration changes then the problem is likely elsewhere.

The next likely suspect being the PSU.

As an immediate way to start looking into that possibility open Reliability History/Monitor and Event Viewer.

The objective simply being to check for error codes, warnings, and informational events of any sort that were captured just before or at the time of the BSODS.

Start with Reliability History/Monitor. Much more end user friendly and the timeline format may reveal some pattern.

Event Viewer requires more effort to navigate and understand.
To help with Event Viewer:

How To - How to use Windows 10 Event Viewer | Tom's Hardware Forum (tomshardware.com)

There may be other errors beyond what has been noted thus far via the dumps, AIDA64, etc..

And also look in Update History for any failed or problem updates.

= = = =

The next step, if necessary , will be to open the case to do some cleaning, reseating, and inspections.

Are you comfortable with doing that? Okay if not - but start thinking about some family member or friend who could help with that.
 
Upvote 0 Downvote
Ralston18 said:
I was hoping to spot something amiss in the results - not noting anything.

Perhaps another member will spot something....

= = = =

If all was well before I would expect that 2400 would be/was fine.

Caveat being that end users can configure RAM for what ever purposes or requirements might be in mind.

With the premise that you did not make (or knowingly make) any such configuration changes then the problem is likely elsewhere.

The next likely suspect being the PSU.

As an immediate way to start looking into that possibility open Reliability History/Monitor and Event Viewer.

The objective simply being to check for error codes, warnings, and informational events of any sort that were captured just before or at the time of the BSODS.

Start with Reliability History/Monitor. Much more end user friendly and the timeline format may reveal some pattern.

Event Viewer requires more effort to navigate and understand.
To help with Event Viewer:

How To - How to use Windows 10 Event Viewer | Tom's Hardware Forum (tomshardware.com)

There may be other errors beyond what has been noted thus far via the dumps, AIDA64, etc..

And also look in Update History for any failed or problem updates.

= = = =

The next step, if necessary , will be to open the case to do some cleaning, reseating, and inspections.

Are you comfortable with doing that? Okay if not - but start thinking about some family member or friend who could help with that.
Click to expand...
To be honest, there is no specific pattern, but there is an indirect one. Firstly, in the intervals between BSODs, an error appeared 2 times - "Initialization failed due to the inability to create a driver device. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface that failed initialization. The string represents the MAC address of the interface that failed initialization, or the global unique interface identifier (GUID) if NetBT failed to match the GUID to the MAC address. If neither the MAC address nor the GUID is available, then this string represents the name of the device in the cluster. " (the line is translated in the translator, so the error text may differ slightly from the original one) and "Initialization failed due to the inability to create a driver device. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface that failed initialization. The string represents the MAC address of the interface that failed initialization, or the global unique interface identifier (GUID) if NetBT failed to match the GUID to the MAC address. If neither the MAC address nor the GUID is available, then this string represents the name of the device in the cluster. ". There is also an error like this (they go in a row) "When updating secure boot, the secure boot variable could not be updated. Mistake: Secure Boot is not enabled on this computer.. For more information, see on the page https://go.microsoft.com/fwlink/?linkid=2169931 " and "The application-specific permission settings do not grant Local Launch permission for a COM server application with CLSID
Windows.SecurityCenter.SecurityAppBroker
and the APPID
Unavailable
to the NT AUTHORITY user\A SYSTEM with a security ID (S-1-5-18 ) and the LocalHost address (using LRPC) running in the application container is Unavailable with the Security ID (Unavailable). This security permission can be changed using the Component Services Administration tool.", there is also "Registration of the {server name} DCOM server failed during the allotted waiting time.", The TCP/IP IPv6 interface with index 10 could not bind to the provider.", judging by the last two, it has something to do with VPN However, there were no similar errors before that, plus they may have appeared due to the fact that my Internet connection was turned off. There are also driver updates specifically before the BSOD, but they are different every time + for some reason, the logs with the BSOD names disappeared, so I can't write specific names. Plus, I have a transcript of one of the BSODs (I'll attach a screenshot).
I found the same error (the screen was not saved)
https://learn.microsoft.com/en-us/a...ubleshooting-a-blue-screen-with-wrong-symbols
 
Last edited:
Upvote 0 Downvote
You must log in or register to reply here.

TRENDING THREADS

Latest posts

Share this page

COMPANY
RESOURCES
FOLLOW
Top Bottom