OCCT - Error on Core#0

George Dirac · Mar 8, 2015

Hello, I bought i5 4670k recently, and on default bios settings, without any overclocking, I ran OCCT 4.4.1 few times already, and few minutes in, I get errors on different cores like - Stopped: Error detected on Core#0.

Does this mean that my chip is damaged somehow?

I currently Have ASUS B85M-E motherboard (I have Z97-A but waiting on new cooler to arrive, so I can change mobo).

Karsten75 · Mar 8, 2015

Is OCCT even a thing anymore? It's the most fickle and dangerous of all burn-in/stress test tools out there.

Did you even update the BIOS on that old B85 chipset? And there is no reason you can't run the same cooler/CPU on the new mobo.

George Dirac · Mar 8, 2015

Karsten75 :

Hey, thanks for reply, I updated bios to latest. Are you saying that I shouldn't worry about what OCCT even says? I ran RealBench stress test just now for 15 minutes (Will run it for much longer later) and I had no problems. I hope that error was OCCT's fault. Can you tell me software for that is proper for stress testing?

I know I can change mobo without new cooler, but since I will be changing the heatsink, I thought I would wait few more days when my noctua nh-d15 arrives and I wanted to change mobo with new cpu cooler.

Karsten75 · Mar 8, 2015

You should real all of this - carefully! Computronix has gone to great lengths to compile all the info in that thread and to show which stress tests are likely to yield best, consistent results without damage to your components.

http://www.tomshardware.com/forum/id-1800828/intel-temperature-guide.html

Search

OCCT - Error on Core#0

George Dirac

Reputable

Karsten75

Karsten75

Judicious

George Dirac

Reputable

Karsten75

Judicious

TRENDING THREADS

Latest posts

Moderators online

Share this page