Panic

[Kenjo]

Hey guys ! 

Something very very odd just happened earlier today.. i was reading some stuff online and all off a sudden my monitor / keyboard /mouse went black normally the mouse and keyboard are lit up red (static) and the monitor said "no signal" the pc itself was on and the Phanteks LeD strip i could use the button on the case to toggle the different colour modes no problem but the Reset button didnt work ... i had to power it off and back on by unplugging the powercord at the back ! 

Its been running fine for the last 2-3 hours 

Any help would be appreciated

System spec: 

AoC 1080p 60hz monitor 27"

Phanteks P400 TG Silent (case) 
Msi X470 Gaming Plus 
1x 256gb samsung nvme M.2 ssd (boot
1x 500gb Samsung M.2 SSD
MSI Gtx 1080 Ti Armor 
2x 8gb ballistix 2666mhz
Ryzen 7 2700x 
Fractal S36 AiO 

Coolermaster keyboard and mouse

Cpu clock 4.2ghz 1.35vcore 
Memory 3000mhz non XMP 

Only time this has happened was today other days its been fine and its 6months old 

Kind Regards 

[H4X3R]

Revert the overclocks.

[Kenjo]

1 minute ago, H4X3R said:

Revert the overclocks.

So what your saying is that running the Ryzen 7 2700x Under stock value would prevent the keyboard/monitor/mouse to die and reset button not working ? 

R7 2700x stock turbo is 4.35ghz @ 1.47vcore ... hence why i locked it to 4.2ghz at 1.35vcore to prevent the insane vcore

 

[samcool55]

7 minutes ago, Kenjo said:

So what your saying is that running the Ryzen 7 2700x Under stock value would prevent the keyboard/monitor/mouse to die and reset button not working ? 

R7 2700x stock turbo is 4.35ghz @ 1.47vcore ... hence why i locked it to 4.2ghz at 1.35vcore to prevent the insane vcore

 

That's not exactly how it works.

It does 4.35 on 1 core, not all of them.

Your OC is applied to all cores so you are pushing 1-2 cores less hard than stock, but the 6-7 other ones harder than they would be if it ran stock.

More cores with more clockspeed = more power but also risking a less stable system.

[Kenjo]

Just now, samcool55 said:

That's not exactly how it works.

It does 4.35 on 1 core, not all of them.

Your OC is applied to all cores so you are pushing 1-2 cores less hard than stock, but the 6-7 other ones harder than they would be if it ran stock.

More cores with more clockspeed = more power but also risking a less stable system.

It runs 4.35ghz on 2 cores .. 1 core on Corepackage 1 and 1 core on package 2 with the infinity fabric highway But yes you are right im downclocking 2 cores while overclocking 6 cores.... 

We are talking 6 months from store to now with a mild OC on 6 core´s with reasonable Vcore.. i have never seen a system do that kind of "hickup" randomly where the actual pc is still on but keyboard/mouse/monitor "dies" and you cant reset or hold down power button to turn off ... not even in the day of the k6 or the  core2 duo

 

[samcool55]

1 minute ago, Kenjo said:

It runs 4.35ghz on 2 cores .. 1 core on Corepackage 1 and 1 core on package 2 with the infinity fabric highway But yes you are right im downclocking 2 cores while overclocking 6 cores.... 

We are talking 6 months from store to now with a mild OC on 6 core´s with reasonable Vcore.. i have never seen a system do that kind of "hickup" randomly where the actual pc is still on but keyboard/mouse/monitor "dies" and you cant reset or hold down power button to turn off ... not even in the day of the k6 or the  core2 duo

 

It happens, usually when a system is borderline stable it does the most derpy stuff because like a small part only derped and everything gets out of whack.

Compare that to perfectly stable (no problem) or clearly unstable (a nice fat crash) is something that should have less problems.

 

Random example: buildzoid was overclocking ram, when it was stable, it's fine. When it was clearly unstable, the system would notice it and reset itself to default. If it was borderline stable, the whole thing would derp and needed to be reset manually because it was like "i"m stable, but actually unstable, but stable enough" so it was in this sort of weird area between stable and unstable and it didn't know what to do.

[Kenjo]

1 minute ago, samcool55 said:

It happens, usually when a system is borderline stable it does the most derpy stuff because like a small part only derped and everything gets out of whack.

Compare that to perfectly stable (no problem) or clearly unstable (a nice fat crash) is something that should have less problems.

 

Random example: buildzoid was overclocking ram, when it was stable, it's fine. When it was clearly unstable, the system would notice it and reset itself to default. If it was borderline stable, the whole thing would derp and needed to be reset manually because it was like "i"m stable, but actually unstable, but stable enough" so it was in this sort of weird area between stable and unstable and it didn't know what to do.

Odd thing is though i did a massive whole day stability test on the system about 1 week ago .. Aida64Extreme cinebenchr15 3dmark looping etc and it was perfectly fine no high temps no crashing absolutly nothing.... 

I did however install the latest Nvidia fail drivers today... im guessing they wherent as stable as they claimed
 

[samcool55]

2 minutes ago, Kenjo said:

Odd thing is though i did a massive whole day stability test on the system about 1 week ago .. Aida64Extreme cinebenchr15 3dmark looping etc and it was perfectly fine no high temps no crashing absolutly nothing.... 

I did however install the latest Nvidia fail drivers today... im guessing they wherent as stable as they claimed
 

That's a possibility, you can try to downgrade and see if that's stable but it's also possible there's some form of degration going on (which means it used to be stable, but no longer is because stuff gets worn out when you use more voltage)

[Kenjo]

Just now, samcool55 said:

That's a possibility, you can try to downgrade and see if that's stable but it's also possible there's some form of degration going on (which means it used to be stable, but no longer is because stuff gets worn out when you use more voltage)

I know about the degredation but 6months is way to short of a time for that to happen unless i was given a homeless chip

 

[samcool55]

1 minute ago, Kenjo said:

I know about the degredation but 6months is way to short of a time for that to happen unless i was given a homeless chip

 

Eh, it's possible.

I've experienced it before, system was stable, 4 months later it was completely ruined.

I basically killed a ram stick hard and only ran fine at stock speeds, any OC would cause it to crash.

 

It's rare, i will give you that, but not impossible.

[Kenjo]

1 minute ago, samcool55 said:

Eh, it's possible.

I've experienced it before, system was stable, 4 months later it was completely ruined.

I basically killed a ram stick hard and only ran fine at stock speeds, any OC would cause it to crash.

 

It's rare, i will give you that, but not impossible.

Ah well.. its all under warranty