PC gets hang while Is in idle

[Rumman]

My PC shows BSOD and got stuck on and then need to do a force restart. I have attached the screenshot and also the log file. Pls help me. could it be possible due to the new AMD driver installation?

 

Recently changed the GPU. This problem also showed during my previous GPU. Thought that this was happening due to a faulty GPU.

 

R5 3600x

Gigabyte 450M S2H

32 Gb Skill RAM

RX 6800 Asus
Corsair TX 650W

Windows 11 24H2

Samsung 970 EVO

other 3 HDD

 

 

critical.evtx Error.evtx Error1.evtx

[jaslion]

Full specs please

[Rumman]

42 minutes ago, Rumman said:

My PC shows BSOD and got stuck on and then need to do a force restart. I have attached the screenshot and also the log file. Pls help me. could it be possible due to the new AMD driver installation?

 

Recently changed the GPU. This problem also showed during my previous GPU. Thought that this was happening due to a faulty GPU.

 

 

critical.evtx 68 kB · 0 downloads Error.evtx 68 kB · 0 downloads Error1.evtx 68 kB · 0 downloads

R5 3600x

Gigabyte 450M S2H

32 Gb Skill RAM

RX 6800 Asus
Corsair TX 650W

Windows 11 24H2

Samsung 970 EVO

other 3 HDD

[jaslion]

What speed are you putting the ram at?

 

 

[Rumman]

31 minutes ago, jaslion said:

What speed are you putting the ram at?

 

 

XMP. at 3200Mhz

[jaslion]

1 minute ago, Rumman said:

XMP. at 3200Mhz

Try 2133 just to see if it helps with stability

[Bjoolz]

It could just be some bug with Insider. Beta software isn't always stable. If not, storage would be my main suspect because it's not able to create dump files. There are several reasons why it might not be able to create one, but faulty storage is the main one. The other being not enough room on the storage (It dumps all content from RAM so you need your amount of RAM + 3-4GB). Because it dumps this to the page file, if you have manually set a page file size it needs to be that big as well. If you encrypt the storage like via Bitlocker, that would prevent it from accessing the drive to dump data because the dump process is outside of Windows.

 

If you have any of the other points, fix it and see if you get any dump files.

 

The glitched BSOD screen is just a visual bug in Windows that can happen if you use a monitor with a resolution higher than 1080p. It has no relation to why it crashed.

 

You have lots of drives and the main suspect is the drive with the page file (Because it can't create dump files when it crashes). That is usually the drive with C:, but it can be any drive. If you aren't sure which drive it's one, you can run this command in Powershell: 

 

Get-CimInstance -ClassName Win32_PageFileUsage -Property *

We are only interested in the location here, nothing else. So if it says "C:\pagefile.sys", it's on C:. So the drive that has C: is the main suspect