Originally Posted by pegnose
No, misunderstanding. Really.
I had reported two things here: the eventual hard lock, and the issue that my display wouldn't reactivate on boot CD memtest(s). I just wasn't sure which one you meant.
I wanted to suggest: let's not talk about this display-off problem during the boot CD memtest(s). I think this is a side issue, unrelated to the other thing.
The screen lock is particular to memtest boot cd (video driver is basic) - this should not be an issue for this thread - best done at the HCI forum if that;s still bugging you.
The ability to crash or boot-hang a rig following significant abuse is not likely a hardware problem per se, IF the system can withstand a proper set of stability test:
1) CPU : x264 20 loops, IBT 10 loops, and OCCT 30-60min (or more). 4 and 6 core: p95 28.7 custom blend, 5min/FFT for at lewast 1 hour, best is 2+ hours. (these are conducted with all other components at stock)
2) Ram: 1000% HCI memtest run according to the author's instructions. Commit at least 85% of total ram or 85% of available ram.
Set an OC if you are inclined
Repeat 1 and 2 above.
3) AID 64 Cache stress test for at least 2 hours
4) Realbench for 1+ hours.
5) Run a series of bencharks (futuremark, unigine etc... )
After that - if the system crashes during that cluster-**** you ran earlier, I think you know what the cause is.
note regarding LatMon - any software polling hardware is an interrupt/dpc. run latmon directly after a fresh boot has set idle for 5 min.Edited by Jpmboy - 1/24/16 at 4:14pm