Crashing after an hour of idle

Trojan Horse · 14 May 2020 at 01:05

My PC crashes, the display goes black and does not BSOD as I cannot see the screen. I have to hold the power and shut down manually.

Could this be a RAM issue? I ran memtest 86+ overnight with no errors showing. I am ordering a replacement kit to test this tomorrow.

Joxeon · 14 May 2020 at 02:19

Maybe the Gpu?

Jamin280672 · 14 May 2020 at 12:14

System specs would help please.

For instance if your running a Ryzen 3000, it could be the fabric.
If it's a newer AMD GPU, could be the driver, they had a lot of trouble with screens going black, I think it's fixed with the latest driver.
It could also be windows power plan, sleep / hibernate.

benjii · 14 May 2020 at 13:17

Jamin280672 said:
It could also be windows power plan, sleep / hibernate.

That would be my guess. An unstable CPU voltage crashing the system when it hibernates.

As well as system specs, have you overclocked anything?

Trojan Horse · 14 May 2020 at 17:21

benjii said:
That would be my guess. An unstable CPU voltage crashing the system when it hibernates.

As well as system specs, have you overclocked anything?

Ryzen 3600 + Vega 64 everything on stock
I wanted to OC the new ram to their advertised speeds, 3000 CL15 (
Crucial Ballistix RGB BL2K8G30C15U4BL) do you know how I can find out which die these are? Crucial E-die? any reviews so I can plug in correct numbers for DRAM calc

Trojan Horse · 14 May 2020 at 17:22

Jamin280672 said:
System specs would help please.

For instance if your running a Ryzen 3000, it could be the fabric.
If it's a newer AMD GPU, could be the driver, they had a lot of trouble with screens going black, I think it's fixed with the latest driver.
It could also be windows power plan, sleep / hibernate.

I have the latest 24.0.2 drivers AMD and AMD power plan hibernate is turned off and once it has been an hour it crashes and if you immediately boot it will crash again after it goes past lock screen

Mr Mcgoo · 14 May 2020 at 17:40

have you tried opening cmd with admin rights. then type in sfc /scannow and seeing if it finds any error and corrects them as this is always my first step to fixing errors?

Jamin280672 · 14 May 2020 at 18:00

Also to find out which chips are on your ram, download Thaiphoon burner, 3000mhz at C15 are most likely going to be some sort of Hynix though: http://www.softnology.biz/files.html Run it as admin, once its opened, select the read button, there will be 2 options for yuou in there, they are both your sticks of ram, so just select one, read SPD on SMbus...........mine are Hynix CJR: https://imgur.com/vdJ3TZh

If your ram is running at 3000mhz, make sure you hard lock your FCLK in the bios to half of that, so 1500, I personally wouldnt leave it at auto, also, do you have your ram in the correct slots, it needs to be slots 2 and 4 from the CPU ?

Trojan Horse · 14 May 2020 at 19:25

Jamin280672 said:
Also to find out which chips are on your ram, download Thaiphoon burner, 3000mhz at C15 are most likely going to be some sort of Hynix though: http://www.softnology.biz/files.html Run it as admin, once its opened, select the read button, there will be 2 options for yuou in there, they are both your sticks of ram, so just select one, read SPD on SMbus...........mine are Hynix CJR: https://imgur.com/vdJ3TZh

If your ram is running at 3000mhz, make sure you hard lock your FCLK in the bios to half of that, so 1500, I personally wouldnt leave it at auto, also, do you have your ram in the correct slots, it needs to be slots 2 and 4 from the CPU ?

Thankfully they are Micron e-die
Yes my RAM is in slots 2 and 4

I will lock in my BIOS at half that, should I just leave it on XMP 3000 or something like that or manually tune it like DRAM calc

RAM -
https://i.imgur.com/DASagva.png

Trojan Horse · 14 May 2020 at 19:28

Mr Mcgoo said:
have you tried opening cmd with admin rights. then type in sfc /scannow and see if it finds any error and corrects them as this is always my first step to fixing errors?

wow, dude this actually did something! I totally forgot about this because it never fixes stuff for me. it found corrupt files and successfully repaired them. were they corrupt if I crash and force shut down instead of wait around?

Mr Mcgoo · 15 May 2020 at 16:18

Trojan Horse said:
wow, dude this actually did something! I totally forgot about this because it never fixes stuff for me. it found corrupt files and successfully repaired them. were they corrupt if I crash and force shut down instead of wait around?

Not necessarily. Could have been an issue that happened long ago and overtime has gotten worse and produce the issue your having. Did it fix your issue however?

Trojan Horse · 15 May 2020 at 16:55

Mr Mcgoo said:
Not necessarily. Could have been an issue that happened long ago and overtime has gotten worse and produce the issue your having. Did it fix your issue however?

I am not sure as the RAM came in after I did this fix but I think it was the RAM that fixed it... now I've got to find a cheap way to post 2 sticks to Czech lol