Need Help with System Issues After Installing New Hardware

[ADanishWaffle]

Hi everyone,

I recently upgraded my system with two new components: a WD Black M.2 SSD and a Cooler Master 212 Halo cooler, which I got for Christmas. I was really excited to install them into my build. (For context, I built this system from scratch and have had no issues in the 4+ years I’ve been using it—until now.)

After carefully installing both the cooler and the M.2, I ran into a strange issue where RAM slots 3 and 4 worked, but 1 and 2 didn’t. After resetting the BIOS and replacing the 2023 CMOS battery, I managed to get slots 1 and 2 working again. I was relieved because it seemed like the issue was fixed.

However, two days later, while gaming, my computer suddenly froze. I heard an unusual noise from the system, and after waiting a minute or two, I restarted the PC. When it booted up, I encountered what seemed like a partial un normal blue Screen. (I've attached a picture for reference.)

At this point, I was worried I might need to replace the whole system. I decided to troubleshoot further:

1. I reset the CMOS again.
2. I tested the system with only one RAM stick installed.

With just one RAM stick, the system powers on, and I can access the BIOS. However, if I try using both RAM sticks, the system won’t boot, it just shows a blank screen with no indication of what's wrong.
I tried turning xmp both on and off but still can't get the system running with two ram sticks that i've never had any issues with.... 

*Update
I've also started to hear a high frequency sound coming from the PSU is that normal ? 
 

Does anyone have advice on what might be causing this or how to fix it? I’m at a loss and would greatly appreciate any help!

Pc part picker list of all the parts I have on my system currently.. 
https://pcpartpicker.com/list/gYQgBq 

[Mumintroll]

Hmm...

Since it started happening when you added the new nvme drive I would test to remove it.

Does the drive happen to be without any DRAM cache? I've read somewhere that some DRAM-less drives, especially Western Digital, can cause issues with 24h2 update.

 

The new CPU cooler you got, did you install it correctly?

It could otherwise make the CPU glitch, not be seated properly. In worst case a wrong installation of CPU cooler could damage the CPU and its pins, and the motherboard slot for it.

[ADanishWaffle]

14 minutes ago, Mumintroll said:

Hmm...

Since it started happening when you added the new nvme drive I would test to remove it.

Does the drive happen to be without any DRAM cache? I've read somewhere that some DRAM-less drives, especially Western Digital, can cause issues with 24h2 update.

I removed it and it's the same issue sadly.... 
the m.2 WD black sn850x has DRAM cache as I have read on the internet and the drives page.

Edit: 
Funny part is that it seem'd to work just fine for 2-3 days and got it loaded with all my files and games, soo im really confused on the part

[Mumintroll]

Just now, ADanishWaffle said:

I removed it and it's the same issue sadly.... 
the m.2 WD black sn850x has DRAM cache as I have read on the internet and the drives page.

The new CPU cooler you got, did you install it correctly?

It could otherwise make the CPU glitch, not be seated properly. In worst case a wrong installation of CPU cooler could damage the CPU and its pins, and the motherboard slot for it.

[ADanishWaffle]

3 minutes ago, Mumintroll said:

The new CPU cooler you got, did you install it correctly?

It could otherwise make the CPU glitch, not be seated properly. In worst case a wrong installation of CPU cooler could damage the CPU and its pins, and the motherboard slot for it.

Yes, the cpu was seated correctly and cleaned with 99% isopropyl alcohol before applying the new one, (as of 20 minutes ago I checked for bent pins again which I hardly can't spot any ) 

Also made sure not to overtighten it as I know overtighting can cause major issues... 

[Jsos16]

The sudden high pitched whining noise makes me think your power supply could be the culprit. Try an alt power supply and see if issues persist then.