DilipVasan
Member
I've seen people claiming that overclocking caused them huge repair bills is it so?
I've seen people claiming that overclocking caused them huge repair bills is it so?
This thread is a work in progress. The OP will be updated/amended to reflect information as made available by thread contributors.
HCI memtest is superior to LinX, Prime (large or small), and memtest86+ for determining memory stability.
- Launch one instance per thread supported by CPU (8 instances of HCI memtest for 2600K)
- Set each HCI instance to use an appropriate fraction of the memory...16GB on a 2600K means each HCI instance (there will be 8 instances) are to use 2048 MB.
- Stability Criterion: Must pass 200% coverage minimum, passing 1000% coverage is preferred (considered gold standard)
Looks like HCI memtest is a windows program, so in what ways is it superior to memtest86+, that comes with Linux Live CDs?
Not sure, I just have experience where memtest86+ fails to detect memory errors that HCI memtest does detect. But have never had HCI memtest fail to detect errors that memtest86+ detected.
Others have reported the same. So in light of the situation, better to rely on HCI memtest if you can.
I see... I was always under the impression that memtest86+ was the best memory tester.
Are there any better and free memory tester that is Linux based or with its own boot cd?
Deleted spam links.
Markfw900
World class overclockers there, we got a few here 🙄
What can we run instead of the OCCT GPU test? It will not run on a server os (the free edition).
It's my home system, checking stability.
One more thing. I runned 4 instances of HCI at the maximum memory setting of 2048 MB (I have 4 cores, no HT). From the 12 GB RAM I have, there was still 1.7GB available. What you do in this case? Run a fifth test allocating the 1.7 left? Also at this test the first test from the last test had an hour difference (65 hours vs 66 hours and ten minutes). This means the cores are not equal?
This thread is a work in progress. The OP will be updated/amended to reflect information as made available by thread contributors.
LinX (Intel burntest) is superior to Prime95 small FFT for determining CPU core logic stability.
Prime95 large FFT is superior to LinX for determining L3$/IMC stability.
- Must run with the IBT thread count set equal to the physical core count of the CPU.
- HT slows it down and reduces the ability to determine stability. Set to 4 threads on a 2600K.
- Set memory to "All".
- Stability Criterion: Must pass 5 cycles minimum, passing 20 cycles is preferred (considered gold standard)
HCI memtest is superior to LinX, Prime (large or small), and memtest86+ for determining memory stability.
- Must use large FFT, blend is insufficient. <- reports indicate this is false for AMD stability tests, see post #4
- HT is ok for this test.
- Stability Criterion: Must pass 2 hours minimum, passing 12 hours is preferred (considered gold standard)
OCCT GPU test w/error checking enabled is superior to Kombustor for determining GPU stability. (updated link to OCCT 4.0.0, thanks NoobyDoo!)
- Launch one instance per thread supported by CPU (8 instances of HCI memtest for 2600K)
- Set each HCI instance to use an appropriate fraction of the memory...16GB on a 2600K means each HCI instance (there will be 8 instances) are to use 2048 MB.
- Stability Criterion: Must pass 200% coverage minimum, passing 1000% coverage is preferred (considered gold standard)
- Error checking MUST be enabled by the user (check the box), otherwise you are leaving it up to your eyes to detect visual artifacts which renders the test entirely subjective.
- Stability Criterion: Must pass 20 minutes minimum, passing 1 hour is preferred (considered gold standard)