Issue need help

Kevin Matthews · 8 Oct 2020 at 14:58

Hi Guys,

Just went on to start computer but didnt come on GPU wasnt lit up and monitor didnt come on, had red light on mobo so powered down and retried again and it started sucessfully any idea what could have caused it?

Also its only about year old all new parts too.

Thanks
Kevin

bremen1874 · 8 Oct 2020 at 16:01

Not really worth worry about unless it does it again.

Does the motherboard have diagnostic indicators?

Plec · 8 Oct 2020 at 16:42

Hey @Kevin Matthews - i remember your spec thread and then subsequent memory clocking.

What was your memory set at - and i would go into the BIOS and check it's present settings or use CPUz - as it may have reset itself, depending on your settings?

Kevin Matthews · 8 Oct 2020 at 17:09

I never have no issues apart this I've upgraded the to 4x16gb of the team vulcan and upgraded the cpu cooler too and also upgraded the PSU and GPU to Nitro special edition but that would a been 6 months.

Mobo have diagnostic it was red when it didn't switch on but I could say if it RAM or CPU..

Currently cleaning it now. I'm going to reset using the Jumper JBAT.

Strange that it happened I had an error in Windows update. Scary lol

Plec · 8 Oct 2020 at 17:25

Kevin Matthews said:
I never have no issues apart this I've upgraded the to 4x16gb of the team vulcan and upgraded the cpu cooler too and also upgraded the PSU and GPU to Nitro special edition but that would a been 6 months.

So you now have 4 sticks of 3200MHz memory?

Were they running at 3200MHz?

Kevin Matthews · 8 Oct 2020 at 18:28

Plec said:
So you now have 4 sticks of 3200MHz memory?

Were they running at 3200MHz?

Had them oc to 3600 but never had no issue and all ram stability was fine by tests..

I started computer failed to start twice 4th red light on mobo it seemed.

Plec · 8 Oct 2020 at 18:38

Kevin Matthews said:
Had them oc to 3600 but never had no issue and all ram stability was fine by tests..

I started computer failed to start twice 4th red light on mobo it seemed.

Doesn't mean it wasn't due to the clock.

Check to see if your memory has reset. If so, suggest running at stock, 3200MHz, and then bump up again if your system remains stable. If the fault reappears once clock reinput - drop back to 3200MHz and stick to it as only marginal performance gains at 3600MHz - and not worth instability issues.

Kevin Matthews · 8 Oct 2020 at 18:41

Okay strange that was working fine last night. Everything is back to default now too maybe just enable XMP for 3200?

Plec · 8 Oct 2020 at 18:47

Kevin Matthews said:
Okay strange that was working fine last night. Everything is back to default now too maybe just enable XMP for 3200?

I would clear the CMOS - load defaults - and then set the XMP (or just set the XMP for speed).

Running 4 sticks of that memory @3600MHz - i'm amazed you haven't had issues before (unless you changed sticks?).

Kevin Matthews · 8 Oct 2020 at 18:58

Plec said:
I would clear the CMOS - load defaults - and then set the XMP (or just set the XMP for speed).

Running 4 sticks of that memory @3600MHz - i'm amazed you haven't had issues before (unless you changed sticks?).

No issues at all.. Was working great lol I have set XMP to Profile 1 instead of 2?

Hopefully it's not a serious problem strange how it could work great all day yesterday till 1am last night.

Plec · 8 Oct 2020 at 19:40

Kevin Matthews said:
Hopefully it's not a serious problem strange how it could work great all day yesterday till 1am last night.

If the memory is clocked over spec - it's really not. Clocks can suddenly become unstable over time - but you can adjust voltages, timings or drop clock to compensate. In this instance the difference in memory performance is so negligible that running at XMP is worth the assurance of stability (if it's the problem).

Kevin Matthews · 8 Oct 2020 at 19:51

Plec said:
If the memory is clocked over spec - it's really not. Clocks can suddenly become unstable over time - but you can adjust voltages, timings or drop clock to compensate. In this instance the difference in memory performance is so negligible that running at XMP is worth the assurance of stability (if it's the problem).

Okay mate thank you for the help also I just checked my phone images it wasnt 3600 it was 3800 oc my mistake

Plec · 8 Oct 2020 at 20:17

Kevin Matthews said:
Okay mate thank you for the help also I just checked my phone images it wasnt 3600 it was 3800 oc my mistake

Do you have different memory to what we originally specced? That or you fluked the jackpot (and ideally 3733MHZ 1:1 with IF - but unimportant now).

Could you confirm your memory.

Kevin Matthews · 8 Oct 2020 at 20:29

Plec said:
Do you have different memory to what we originally specced? That or you fluked the jackpot (and ideally 3733MHZ 1:1 with IF - but unimportant now).

Could you confirm your memory.

Yeah course Team Group Vulcan T-Force 16GB (4x8GB) DDR4 PC4-25600C16 3200MHz Dual Channel Kit

Had it OC to 3800 1900.

Owner from computerbase.de help me OC