Jump to content

Screen goes black, no IO, power/reset buttons don't work - causes?

hihihi8

Hi all, I'm trying to diagnose some random crashes I've been experiencing with my new PC. They happen out of nowhere, once every few hours, mostly at idle or light use, and require a hard reset of the PSU switch to fix. The screen suddenly goes black, no IO, power/reset buttons don't work, motherboard Q-Code says "00"

 

- ROG Crosshair 8 Dark Hero

- 5950x

- Reference 6900XT

- 64GB Quad-stick DDR4

- Sabrent Rocket 4

- AX1500i new/refurbished.

 

What causes this type of crash?

 

1. My first thought was PSU since I felt that it might've been an interruption in DC power. I pulled out the AX1500i, disconnected everything, and the self-test turns green and fan spins if I hold the self-test button down for ~0.5s. If i just tap the self-test button, nothing happens, is that normal?

 

2. My main question: Is a bad memory OC/bad RAM known to cause this type of crash? I've always associated bad RAM with random BSODs and refusal to boot, but this thing boots without a hitch and has never BSOD'd on me except that one time I went wayyy too unstable on the ram-OC and it BSOD'd on boot. It crashes the same way every time as described above, prolly 5-6 times now. The RAM has passed overnight memtest86 twice now (4-pass runs), even with an beyond-XMP OC.

For now, I've removed even XMP, and am just testing at pure stock 2666MHz 20-19-19-43 with a brand new HX850i. 

 

3. Motherboard? Ugh that would be a PITA.

 

4. GPU drivers? It's a new install, but I haven't ruled it out yet.

PC 0: Pinky 2.0

Ryzen 9 5950x — 64GB G.Skill Ripjaws 5 @3600Mhz CL14-13-13-28-288 — ROG Crosshair 8 Dark Hero — RX 6900 XT — Hardline Loop — Sabrent Rocket 4.0 2TB — Samsung PM961 1TB  WD Blue 4TB HDD — Corsair AX1500i — Thermaltake Core P5 

 

PC 1: Pinky (Yes that is her name) Here's the build

Xeon E5-1680V3 — 64GB G.Skill Ripjaws 4 @2400Mhz — MSi X99A Godlike Gaming — GTX 980Ti SLI (2-WAY) — Hardline Loop — Samsung 950Pro 512GB — Seagate 2TB HDD — Corsair RM1000 — Thermaltake Core P5

 

PC 1.1: Pinky (Mom Edition) Here's the build

i7-5960X — 64GB G.Skill Ripjaws 4 @2400Mhz — MSi X99A Godlike Gaming — GTX 980Ti SLI (2-WAY) — Hardline Loop — Sabrent Rocket 3 1TB — Samsung Q 870 Evo 4TB — Corsair HX850i — InWin S-Frame #190

 

PC 2: Red Box/Scarlet Overkill (Dual Xeon)

Xeon E5-2687W x2 — 96GB Kingston DDR3 ECC REG @1333Mhz — EVGA Classified SR-X Dual CPU — GTX 1070 SLI (2-WAY) —Hardline Loop — Samsung 750 EVO 256GB — Seagate 2TB 2.5" HDD x3 — Self-Built Case

Link to comment
Share on other sites

Link to post
Share on other sites

What bios version are you using? But yes a bad oc could do this.

CPU: Ryzen 5800X3D | Motherboard: Gigabyte B550 Elite V2 | RAM: G.Skill Aegis 2x16gb 3200 @3600mhz | PSU: EVGA SuperNova 750 G3 | Monitor: LG 27GL850-B , Samsung C27HG70 | 
GPU: Red Devil RX 7900XT | Sound: Odac + Fiio E09K | Case: Fractal Design R6 TG Blackout |Storage: MP510 960gb and 860 Evo 500gb | Cooling: CPU: Noctua NH-D15 with one fan

FS in Denmark/EU:

Asus Dual GTX 1060 3GB. Used maximum 4 months total. Looks like new. Card never opened. Give me a price. 

Link to comment
Share on other sites

Link to post
Share on other sites

@DoctorNickNewest v3202. And yup, stock RAM hasn't crashed on me yet, but it's only been a few hours and the crashes happen randomly, so I'll keep an eye on it for the next few days. I did change 2 variables at once (HX850i + Stock RAM), so if I don't get any more crashes i'll try stock RAM+put my AX1500i back in.

 

The few similar cases I could find pointed in all sorts of directions, with some claiming new RAM fixed it, others concluding a faulty CPU, and some pointing to the Mobo since the power/reset buttons no longer worked.

 

Everything's new on this system so I have no idea at this point. The only known good I can test with it is my old RM1000 PSU.

PC 0: Pinky 2.0

Ryzen 9 5950x — 64GB G.Skill Ripjaws 5 @3600Mhz CL14-13-13-28-288 — ROG Crosshair 8 Dark Hero — RX 6900 XT — Hardline Loop — Sabrent Rocket 4.0 2TB — Samsung PM961 1TB  WD Blue 4TB HDD — Corsair AX1500i — Thermaltake Core P5 

 

PC 1: Pinky (Yes that is her name) Here's the build

Xeon E5-1680V3 — 64GB G.Skill Ripjaws 4 @2400Mhz — MSi X99A Godlike Gaming — GTX 980Ti SLI (2-WAY) — Hardline Loop — Samsung 950Pro 512GB — Seagate 2TB HDD — Corsair RM1000 — Thermaltake Core P5

 

PC 1.1: Pinky (Mom Edition) Here's the build

i7-5960X — 64GB G.Skill Ripjaws 4 @2400Mhz — MSi X99A Godlike Gaming — GTX 980Ti SLI (2-WAY) — Hardline Loop — Sabrent Rocket 3 1TB — Samsung Q 870 Evo 4TB — Corsair HX850i — InWin S-Frame #190

 

PC 2: Red Box/Scarlet Overkill (Dual Xeon)

Xeon E5-2687W x2 — 96GB Kingston DDR3 ECC REG @1333Mhz — EVGA Classified SR-X Dual CPU — GTX 1070 SLI (2-WAY) —Hardline Loop — Samsung 750 EVO 256GB — Seagate 2TB 2.5" HDD x3 — Self-Built Case

Link to comment
Share on other sites

Link to post
Share on other sites

wow what dumb, unfortunate luck. I updated the BIOS the day i got the motherboard, downloading the version marked "3204" from asus' website. Turns out someone fumbled the file upload and uploaded the unstable beta bios 3202 instead to their website. 3202 doesn't even exist on their website!

 

Now i've gone back and reupgraded to the proper 3204 BIOS. Here's to hoping that this solves all my random black screens! fingers crossed.

PC 0: Pinky 2.0

Ryzen 9 5950x — 64GB G.Skill Ripjaws 5 @3600Mhz CL14-13-13-28-288 — ROG Crosshair 8 Dark Hero — RX 6900 XT — Hardline Loop — Sabrent Rocket 4.0 2TB — Samsung PM961 1TB  WD Blue 4TB HDD — Corsair AX1500i — Thermaltake Core P5 

 

PC 1: Pinky (Yes that is her name) Here's the build

Xeon E5-1680V3 — 64GB G.Skill Ripjaws 4 @2400Mhz — MSi X99A Godlike Gaming — GTX 980Ti SLI (2-WAY) — Hardline Loop — Samsung 950Pro 512GB — Seagate 2TB HDD — Corsair RM1000 — Thermaltake Core P5

 

PC 1.1: Pinky (Mom Edition) Here's the build

i7-5960X — 64GB G.Skill Ripjaws 4 @2400Mhz — MSi X99A Godlike Gaming — GTX 980Ti SLI (2-WAY) — Hardline Loop — Sabrent Rocket 3 1TB — Samsung Q 870 Evo 4TB — Corsair HX850i — InWin S-Frame #190

 

PC 2: Red Box/Scarlet Overkill (Dual Xeon)

Xeon E5-2687W x2 — 96GB Kingston DDR3 ECC REG @1333Mhz — EVGA Classified SR-X Dual CPU — GTX 1070 SLI (2-WAY) —Hardline Loop — Samsung 750 EVO 256GB — Seagate 2TB 2.5" HDD x3 — Self-Built Case

Link to comment
Share on other sites

Link to post
Share on other sites

19 minutes ago, hihihi8 said:

Turns out someone fumbled the file upload and uploaded the unstable beta bios 3202 instead to their website

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.

PC 0: Pinky 2.0

Ryzen 9 5950x — 64GB G.Skill Ripjaws 5 @3600Mhz CL14-13-13-28-288 — ROG Crosshair 8 Dark Hero — RX 6900 XT — Hardline Loop — Sabrent Rocket 4.0 2TB — Samsung PM961 1TB  WD Blue 4TB HDD — Corsair AX1500i — Thermaltake Core P5 

 

PC 1: Pinky (Yes that is her name) Here's the build

Xeon E5-1680V3 — 64GB G.Skill Ripjaws 4 @2400Mhz — MSi X99A Godlike Gaming — GTX 980Ti SLI (2-WAY) — Hardline Loop — Samsung 950Pro 512GB — Seagate 2TB HDD — Corsair RM1000 — Thermaltake Core P5

 

PC 1.1: Pinky (Mom Edition) Here's the build

i7-5960X — 64GB G.Skill Ripjaws 4 @2400Mhz — MSi X99A Godlike Gaming — GTX 980Ti SLI (2-WAY) — Hardline Loop — Sabrent Rocket 3 1TB — Samsung Q 870 Evo 4TB — Corsair HX850i — InWin S-Frame #190

 

PC 2: Red Box/Scarlet Overkill (Dual Xeon)

Xeon E5-2687W x2 — 96GB Kingston DDR3 ECC REG @1333Mhz — EVGA Classified SR-X Dual CPU — GTX 1070 SLI (2-WAY) —Hardline Loop — Samsung 750 EVO 256GB — Seagate 2TB 2.5" HDD x3 — Self-Built Case

Link to comment
Share on other sites

Link to post
Share on other sites

  • 3 weeks later...

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 seems, after going through 2 weeks of not having a single crash.

 

memory OC has been put back in place too with no issues so far.

PC 0: Pinky 2.0

Ryzen 9 5950x — 64GB G.Skill Ripjaws 5 @3600Mhz CL14-13-13-28-288 — ROG Crosshair 8 Dark Hero — RX 6900 XT — Hardline Loop — Sabrent Rocket 4.0 2TB — Samsung PM961 1TB  WD Blue 4TB HDD — Corsair AX1500i — Thermaltake Core P5 

 

PC 1: Pinky (Yes that is her name) Here's the build

Xeon E5-1680V3 — 64GB G.Skill Ripjaws 4 @2400Mhz — MSi X99A Godlike Gaming — GTX 980Ti SLI (2-WAY) — Hardline Loop — Samsung 950Pro 512GB — Seagate 2TB HDD — Corsair RM1000 — Thermaltake Core P5

 

PC 1.1: Pinky (Mom Edition) Here's the build

i7-5960X — 64GB G.Skill Ripjaws 4 @2400Mhz — MSi X99A Godlike Gaming — GTX 980Ti SLI (2-WAY) — Hardline Loop — Sabrent Rocket 3 1TB — Samsung Q 870 Evo 4TB — Corsair HX850i — InWin S-Frame #190

 

PC 2: Red Box/Scarlet Overkill (Dual Xeon)

Xeon E5-2687W x2 — 96GB Kingston DDR3 ECC REG @1333Mhz — EVGA Classified SR-X Dual CPU — GTX 1070 SLI (2-WAY) —Hardline Loop — Samsung 750 EVO 256GB — Seagate 2TB 2.5" HDD x3 — Self-Built Case

Link to comment
Share on other sites

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×