BSOD since 2020, tried to fix it multiple times

[Eliav]

Hello, I built a custom PC in 2020 heres the specs:

 

Ryzen 5 3500x

Asus ROG b-450f gaming

Asus ROG rtx3060

PNY cs2130 500gb ssd

HyperX predator 2933mhz 2x8gb

Two Samsung 3200mhz 8gb from a pre built pc of a friend

Asus ROG 550W 

 

I went multiple times back to the store where I bought the parts, and asked a repair, and first time they said there was nothing, but second time they said the problem was the SSD so they changed it but that didn't fix the problem so I went back and they said it's the GPU the problem so I changed it too from a AMD GPU to a 3060 and it just didn't fix anything and they didn't want anymore to help me.. but until now, it didn't bother me so much because i didn't get any bsod when a game was running, but after 4 years, I just thought about it that I think it's killing my PC just to run a game everytime I turn it on so it wouldn't crash.. I get all sorts of bsod types here some of them:

"Irql_not_less_or_equal" "clock_watchdog_timeout"

"dpc_watchdog_violation"

"attempted_execute_of _noexecute

_memory"

"Invalid_mdl_range"

"Hypervisor_error"

 

I think based on everything that happened until now, the only option for the source of the problem is or the motherboard (if it's even possible) or the CPU or the PSU, so I would just like to get help find the source of the problem so I'll just replace it.. 

 

Thank you in advance

 

[PDifolco]

3 minutes ago, Eliav said:

Hello, I built a custom PC in 2020 heres the specs:

 

Ryzen 5 3500x

Asus ROG b-450f gaming

Asus ROG rtx3060

PNY cs2130 500gb ssd

HyperX predator 2933mhz 2x8gb

Asus ROG 550W 

 

I went multiple times back to the store where I bought the parts, and asked a repair, and first time they said there was nothing, but second time they said the problem was the SSD so they changed it but that didn't fix the problem so I went back and they said it's the GPU the problem so I changed it too from a AMD GPU to a 3060 and it just didn't fix anything and they didn't want anymore to help me.. but until now, it didn't bother me so much because i didn't get any bsod when a game was running, but after 4 years, I just thought about it that I think it's killing my PC just to run a game everytime I turn it on so it wouldn't crash.. I get all sorts of bsod types here some of them:

"Irql_not_less_or_equal" "clock_watchdog_timeout"

 

I think based on everything that happened until now, the only option for the source of the problem is or the motherboard (if it's even possible) or the CPU or the PSU, so I would just like to get help find the source of the problem so I'll just replace it.. 

 

Thank you in advance

 

It's past time to upgrade the CPU anyway, so drop a 5700X or 5700X3D in and check if it crashes

[Mumintroll]

The clock_watchdog_timeout BSOD usually points to the cpu.

 

If you know a friend that you can borrow a compatible cpu to test it that would be great, just to be sure it is actually the cpu causing it.

And test your cpu in his pc.

 

Then you can decide if you need to buy a new cpu, or perhaps a motherboard, or both.

[Eliav]

29 minutes ago, Mumintroll said:

The clock_watchdog_timeout BSOD usually points to the cpu.

 

If you know a friend that you can borrow a compatible cpu to test it that would be great, just to be sure it is actually the cpu causing it.

And test your cpu in his pc.

 

Then you can decide if you need to buy a new cpu, or perhaps a motherboard, or both.

Ok thanks I will see if I can borrow from someone and try with it

[Bagzie]

Have you tried doing a cmos reset and running it at complete stock settings for a bit.

 

Don't even use EXPO.

[Eliav]

5 minutes ago, Bagzie said:

Have you tried doing a cmos reset and running it at complete stock settings for a bit.

 

Don't even use EXPO.

I tried everything, I tried updating the bios, I tried repairing windows, I tried redownloading windows, I tried a memory test, and it's already on stock settings.. 

[Eliav]

49 minutes ago, Mumintroll said:

The clock_watchdog_timeout BSOD usually points to the cpu.

 

If you know a friend that you can borrow a compatible cpu to test it that would be great, just to be sure it is actually the cpu causing it.

And test your cpu in his pc.

 

Then you can decide if you need to buy a new cpu, or perhaps a motherboard, or both.

Just one more question, if the CPU is the problem, do you have any idea why i doesn't get any bsod when a game is running? Even when it's like multiversus or another game that isn't heavy, and I don't play I just wait in the lobby, I won't get any bsod. so if it is the CPU what's the reason?

[Mumintroll]

36 minutes ago, Eliav said:

Just one more question, if the CPU is the problem, do you have any idea why i doesn't get any bsod when a game is running? Even when it's like multiversus or another game that isn't heavy, and I don't play I just wait in the lobby, I won't get any bsod. so if it is the CPU what's the reason?

 

That specific BSOD message usually points to the cpu, but it's not 100% sure it is the cpu.

I don't know why it acts like that only when outside a game.

 

So that's why I want you to troubleshoot before buying something.

 

Hmm

Didn't I read somewhere that some AMD cpus had problems with core parking?

Perhaps disable core parking, either from bios or an app, like ParkControl.

[Mark Kaine]

6 hours ago, Mumintroll said:

The clock_watchdog_timeout BSOD usually points to the ram.

FTFY

 

 

[Mark Kaine]

4 hours ago, Mumintroll said:

That specific BSOD message usually points to the cpu

basically it does, its just usually caused by ram incompatibilities on Ryzen systems, so new ram (preferably b-die) could possibly fix this (been there done that tbh and it wasn't the cpu, it was the ram)

[Mark Kaine]

5 hours ago, Eliav said:

I tried everything

ok, but did you actually try without XMP? 

[Eliav]

2 hours ago, Mark Kaine said:

ok, but did you actually try without XMP? 

What is exactly XMP? 

[Eliav]

2 hours ago, Mark Kaine said:

basically it does, its just usually caused by ram incompatibilities on Ryzen systems, so new ram (preferably b-die) could possibly fix this (been there done that tbh and it wasn't the cpu, it was the ram)

But I did a windows memory diagnosis and nothing was wrong.. maybe because the problem is the incompatibility it didn't show any problem?

[Mark Kaine]

1 hour ago, Eliav said:

What is exactly XMP? 

the bios setting that makes your ram run at its rated speed (2933mhz?)

 

is that on y/n?

 

 

1 hour ago, Eliav said:

But I did a windows memory diagnosis and nothing was wrong.. maybe because the problem is the incompatibility it didn't show any problem?

exactly ram might not show errors in tests... cpu memory controller might still struggle... hence to test this you should get different ram, preferably Samsung B-die. 

[Eliav]

24 minutes ago, Mark Kaine said:

the bios setting that makes your ram run at its rated speed (2933mhz?)

 

is that on y/n?

 

 

exactly ram might not show errors in tests... cpu memory controller might still struggle... hence to test this you should get different ram, preferably Samsung B-die. 

I will check when I get home

[Mumintroll]

6 hours ago, Mark Kaine said:

basically it does, its just usually caused by ram incompatibilities on Ryzen systems, so new ram (preferably b-die) could possibly fix this (been there done that tbh and it wasn't the cpu, it was the ram)

 

I've always used Intel cpus so I have no experience myself about AMD's memory controllers. I've read that AMD cpus can be picky when it comes to ram.

[lafrente]

14 hours ago, Eliav said:

Just one more question, if the CPU is the problem, do you have any idea why i doesn't get any bsod when a game is running? Even when it's like multiversus or another game that isn't heavy, and I don't play I just wait in the lobby, I won't get any bsod. so if it is the CPU what's the reason?

Sometimes such issues occur when cores ramp up from idle. I too think it is the processor.

 

Try to set all core OC at not dangerous levels of voltage (1.2 or below) and see if it occurs again. This won't make it run hot, it will just keep the cores at whatever clock you set. Make sure to not set too high clocks for the given voltage otherwise you'll get BSOD again.

[Mark Kaine]

3 hours ago, Mumintroll said:

I've read that AMD cpus can be picky when it comes to ram.

yup, extremely picky, im always surprised people don't know this after all those years and buy "corsair ram" which on average is probably the worst, and nowadays ddr4 is cheap there's no reason not get b-dies imo, even Samsung OEM (can be overclocked through hell and back lol) 

 

 

1 hour ago, lafrente said:

Sometimes such issues occur when cores ramp up from idle. I too think it is the processor.

nah, its the ram...

 

I had 3 Ryzen system and its always the ram... not with my last one cause i already had b-dies then, zero issues.  

[Bagzie]

1 hour ago, Mark Kaine said:

yup, extremely picky, im always surprised people don't know this after all those years and buy "corsair ram" which on average is probably the worst, and nowadays ddr4 is cheap there's no reason not get b-dies imo, even Samsung OEM (can be overclocked through hell and back lol) 

 

 

nah, its the ram...

 

I had 3 Ryzen system and its always the ram... not with my last one cause i already had b-dies then, zero issues.  

Ironically it's reversed on AM5.... B-die is the worst and you really want Hynix.

 

I toiled for hours to get 6000mhz cl 34 to work in my old 7800X3D.

 

Now I have hynix A-die and I casually slapped 6000mhz cl28 in and it just works didn't even need to change the base expo voltages.

[Bjoolz]

Go to C:\Windows\Minidump and check if you have any minidump files. If you do, go back to the Windows folder and copy the Minidump folder itself to the Downloads folder (You can use the desktop if you don't have OneDrive syncing files). Zip the copied folder and attach it to a post. Please follow the instructions to the letter as Windows doesn't like you messing with files in this location.

[Eliav]

11 hours ago, Mark Kaine said:

the bios setting that makes your ram run at its rated speed (2933mhz?)

 

is that on y/n?

 

 

exactly ram might not show errors in tests... cpu memory controller might still struggle... hence to test this you should get different ram, preferably Samsung B-die. 

I searched XMP in the bios and nothing came up.. then I went on Google and searched how to disable it on my bios, and in a video, I saw that in the same place in my bios, instead of XMP I got D.O.C.P, so is it the same thing? Because if it is, it was off

[Eliav]

6 hours ago, lafrente said:

Sometimes such issues occur when cores ramp up from idle. I too think it is the processor.

 

Try to set all core OC at not dangerous levels of voltage (1.2 or below) and see if it occurs again. This won't make it run hot, it will just keep the cores at whatever clock you set. Make sure to not set too high clocks for the given voltage otherwise you'll get BSOD again.

After I changed the CPU core voltage from auto (≈1.4) to 1.2, I couldn't load windows and there was only a black screen so I changed it back again to auto

[lafrente]

23 minutes ago, Eliav said:

After I changed the CPU core voltage from auto (≈1.4) to 1.2, I couldn't load windows and there was only a black screen so I changed it back again to auto

You should've also set the cores properly as I've said in my reply. To 3600 at first then increase it till it starts crashing.

[Eliav]

2 hours ago, Bjoolz said:

Go to C:\Windows\Minidump and check if you have any minidump files. If you do, go back to the Windows folder and copy the Minidump folder itself to the Downloads folder (You can use the desktop if you don't have OneDrive syncing files). Zip the copied folder and attach it to a post. Please follow the instructions to the letter as Windows doesn't like you messing with files in this location.

 

Minidump.zip

[Eliav]

52 minutes ago, lafrente said:

You should've also set the cores properly as I've said in my reply. To 3600 at first then increase it till it starts crashing.

but how does it help me?