BSOD constantly, about to throw my pc into a blackhole.

[rockettman]

Giagbyte B650X AX (1.3)
32GB DDR5 RAM Corsair 
7800XT RED DEVIL 
FireCuda530 2TB heatsink
Deepcool AK620 ZERO DARK

I keep getting BSOD, the following:
Driver EQUAL OR NO LESS 
NTFS.SYS
DPC WATCHDOG VIOLATION
theres more, i forgor tho. 

I've reset drivers, wiped my entire OS and re-installed.
So it's a hardware issue????
what should i try first

[leclod]

I don't know about the message,

 

But you could take out the gpu and try with the igpu.

You could update your Bios and leave it at stock for now.

You could check your Ram with TestMem5 or Memtest86.

You could check your SSD health with Crystal Disk Info.

What's your PSU ?

 

 

 

Edited July 13, 2024 by leclod

[Dutch_Master]

Approach this systematically. First, determine if it's really hardware by performing some tests. Obtain a Linux Live-CD image and burn it to optical or USB drive. Boot from the disk. In the boot menu there's probably an item called MEMtest86 (or similar), choose that and perform a RAM test. It should pass, but it will take a while. When/if passed, this confirms the RAM is good and so is essentially the CPU and the rest of the hardware as you can see the results on screen. If there's no MEMtest86 item in the boot menu, or when completed, boot into the Linux distro itself. You should be able to use the mouse etc for basic functions. If this succeeds, your hardware is fine. That leaves Win-OS itself. As you say you've reinstalled from scratch that means the source is suspect. Which Win-OS version are you trying to use? Win7 certainly isn't supported for AM5 and I doubt Win10 will work too. And make sure you have an official version, not some random, cheap rip-off from the web.

[BetteBalterZen]

Those mentioned BSODs can happen because of drive related errors. 

I would make sure BIOS is updated and maybe try a whole different SSD if possible. 

[--SID--]

What's the SKU of the RAM?

 

What BIOS version is the motherboard running?

[rockettman]

On 7/13/2024 at 3:47 AM, --SID-- said:

What's the SKU of the RAM?

 

What BIOS version is the motherboard running?

On 7/13/2024 at 3:41 AM, BetteBalterZen said:

Those mentioned BSODs can happen because of drive related errors. 

I would make sure BIOS is updated and maybe try a whole different SSD if possible. 

On 7/13/2024 at 12:53 AM, leclod said:

I don't know about the message,

 

But you could take out the gpu and try with the igpu.

You could update your Bios and leave it at stock for now.

You could check your Ram with TestMem5 or Memtest86.

You could check your SSD health with Crystal Disk Info.

What's your PSU ?

 

 

 

 

On 7/13/2024 at 12:59 AM, Dutch_Master said:

Approach this systematically. First, determine if it's really hardware by performing some tests. Obtain a Linux Live-CD image and burn it to optical or USB drive. Boot from the disk. In the boot menu there's probably an item called MEMtest86 (or similar), choose that and perform a RAM test. It should pass, but it will take a while. When/if passed, this confirms the RAM is good and so is essentially the CPU and the rest of the hardware as you can see the results on screen. If there's no MEMtest86 item in the boot menu, or when completed, boot into the Linux distro itself. You should be able to use the mouse etc for basic functions. If this succeeds, your hardware is fine. That leaves Win-OS itself. As you say you've reinstalled from scratch that means the source is suspect. Which Win-OS version are you trying to use? Win7 certainly isn't supported for AM5 and I doubt Win10 will work too. And make sure you have an official version, not some random, cheap rip-off from the web.

Thank you all for a response, I've ran tests on my memory and SSD several times. They seem to be okay. I've reset my OS, got the ISO from microsoft themselfes, and still had BSOD issues, before i updated my bios it was semi updated to FA2, started having BSOD, updated to latest from AMD, still had BSOD issues, wiped my PC so that all drivers/updates/softwares, ect that could've been causing it were gone, still had issues. 

Haven't really been able to play games cause of BSOD :C, is there anything you could suggest with this additional info ^?

FA5e (1.3) BIOs version.
CORSAIR RMX Series RM850x PSU.

CORSAIR RMX Series RM850x. Never had issues with a semi-updated bios before, issues started happening then I updated bios to latest FA5e (1.3) and they continued. 
I've ran several tests on my meory and SSD, they're fine. 

[--SID--]

What's the SKU of the RAM?

[rockettman]

2 hours ago, --SID-- said:

What's the SKU of the RAM?

how would i go about finding this/what you're looking for? I know its a "Stock Keeping Unit", if im not wrong, do I need to go into windows to find what you want me to look for/take out my ram and look at something physical on it

[--SID--]

3 hours ago, rockettman said:

how would i go about finding this/what you're looking for? I know its a "Stock Keeping Unit", if im not wrong, do I need to go into windows to find what you want me to look for/take out my ram and look at something physical on it

You find the SKU on the label on the sticks.

[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.

[rockettman]

5 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.

dmp imper.zip

[Bjoolz]

10 hours ago, rockettman said:

dmp imper.zip 253.74 kB · 1 download

You only had one dump file? This looked storage related, but memory issues can look storage related because of the page file (And vice versa). If you haven't gotten dump files from the other crashes, storage would be the main suspect. 

[TheBeltboy]

I would suggest you assume memory or os storage, remove all but 1 stick (I'm assuming you have at least 2) and test, if you still get the issue move it, then try the next one, if it happens with all the sticks irrelevant of slot then move onto storage. 

 

If you have a spare HDD/SSD you can put in just to install and get drivers on it will at least let you prove that's the issue.