hihihi8

Coolant temp is kept under 45c. The loop is controlled using an aquaero based off coolant-ambient delta. Certainly no overheating. imo there is no excuse for this to happen within 15 days of filling. Everything is gonna have to be disassembled fully and wiped down. F.

My recent upgrade also involved a loop rebuild, during which pretty much overhauled the entire loop. My old loop used deionized with a silver kill coil, and I never had any real issues with it worth mentioning - coolant stayed clean and temps were good. - EK ROG CH8 Dark Hero Monoblock (new) - EK Monarch X4 RAM blocks (reused but with full disassembly cleaning) - EK 6900XT full-cover block (new) - Alphacool NexXxos UT60 480 RAD (reused, thorough flushed, left to dry fully before being refilled) - Primochill RSX Fittings - Primochill Res (new 360mm, forgot e

just one of those radiators would be enough

same for me. disabling c-states fixed it for me.

im more concerned about the CPU's PHY degrading with those voltages since the VDDQ output buffer shares the same voltage as VDIMM and there's no way to change that.

According to some feedback i've received, seems like this setup is pretty rough on the IMC – quad stick, quad rank b-die, tight timings

does it reboot on idle? or under load? or both? Try disabling global C-states in the bios, you might need to dig around for that setting.

Not sure about dead on arrival, but certainly a lot of ryzen 5000s that are plagued with instability and crashes. Check out the 40-page long post on the AMD forum, as well as the plethora of issues on the ROG forums regarding ryzen CPUs, 5000s included. It seems a lot of ryzen 5000s are not quite dead on arrival, but faulty and unstable. My 5950x will not stand global C-states being enabled. With C-states enabled, it will randomly crash to a black screen with post code 00 and power/reset buttons unresponsive during idle/low load every 30mins-3hours or so (with newest BIOS, everyth

Aight, final update: disabling global C-states in the 3204 bios fixed it. 3204 out of the box was noticeably more stable compared to 3202, but still crashed on me a few times. Hypothesis: with C-states enabled, when the system is at low load or idle, the CPU aggressively undervolts the CPU to the point where one of the CCD's becomes unstable (since 5950x's all have one good-binned CCX and one poorer/average binned CCX -1usmus), hence explaining why the system only crashed at low load/idle and never under load. Disabling C-states has fixed the issue, or so it seem

Report 7: I've got it pretty satisfactory and stable at the following: Global C-states disabled (or else this system crashes randomly and frequently when idling – prolly faulty CPU but whatever) Dram Voltage: 1.485v CPU_SOC: 1.15v Dram Freq: 3600 FCLK: 1800 tCL: 14 tRCDRD: 13 tRCDWR: 13 tRP: 13 tRAS: 28 tRC: 42 tRRDs: 4 tRRDl: 6 tFAW: 16 tWTRs: 4 tWTRl: 10 tWR: 12 tRDRDsCL: 3 tWRWRsCL: 3 tRFC: 288 tCWL: 14 tRTP: 8 tRDWR: 8 tWRRD: 4 tWRWRsc: 1 tWRW

Has anyone tested to see if there is a difference between voltage probe points on motherboards and actual back-of-the-socket voltages? Don't have access to the PC currently.

Ok so the memory OC wasnt the culprit of my instability after all. It was a bad beta BIOS. latest BIOS has been solid so far, will put the OC back in soon.

F4-3600C14Q-64GVK is a quad-stick 3600mhz 64GB kit at CL14-15-15-15-35-1T

nvm, it was in beta testing for a brief while and people reported instability so they retracted it, I probably just happened to download it by chance thinking it was the newest stable release, and ended up with a bunch of mysterious crashes. More importantly, 3204 still needs to prove to me that it's the solution to my woes.

use the bios flashback usb port in the back along with a fat16 usb with the correctly named bios .cap file inside to flash the bios so that it supports 5000 series ryzen CPUs. I believe the only asus board that supports 5000 cpus out of the box is the Dark Hero. insert the fat16 USB with the bios cap file into the USB port labeled "bios" and hold the flashback button on the rear IO panel for ~3s until it starts blinking. if it successfully finds the bios file and starts the flashing process, it will blink for a while (~5 mins). If it blinks a couple times and goes solid, then it failed to find