Emergency Help!!!

Gabbatek

Gabbatek

Gabbatek

Associate
Joined
28 Feb 2011
Posts
1,689
Location
Norwich
Strange problem.

I put my computer to sleep and it woke up straight away.

Since then it's been suck at 0.2 ghz. This is an i7 5820k overclocked to 4.2 but I've reset the bios by removing the battery.

Serious performance death, I've removed all cables except keyboard mouse and monitor. How could standby on windows 10 do this?

Last month I got a corsair rmi1000 has it killed something?

What do I do
 
Just tried to load into safe mode and it crashed entering windows. Blue restate screen

Is this a cpu problem or memory fail.

Ideas?
 
Cpu is water poles never goes above 60c

Okay got into safe mode and all cores working and at 3.30 ghz

I'm going to memory test and hard drive check. Hmm
 
Does 1 stick at a time work with quad chan?

Okay now it's saying no errors after a sudden restart. This is confusing, it's working fine now. Memory testing time grrr.
 
Memory test came back fine, I'm going to put this down to not shutting down my pc and only using standby for ages and windows 10 being *insert generic swear of choice*

Now I'm going to be fearful of my pc randomly dying
 
overclock back up, stress testing is fine.

Seriously confused how resuming from windows can drop the cpu to 0.20 ghz and cause numerous blue screen restards
 
Well now an old problem is back

Computer sometimes fails to boot, dies then restarts into bios saying everything is back to default.

Im just using the premade overclock for my cpu (option says 5820k 4.2ghz) in the gigabyte bios and xmp.

why? :'(
 
You must log in or register to reply here.
Back
Top Bottom