If you get a WHEA error you can look up the details in Event Viewer under Windows Logs/System (the 'processor' indicated may be 0-based thread number, i.e. I advise turning on the option that detects errors and stops the test, this may help you catch it before a full crash that loses the screen. RAM can take a long time to heat up and reveal errors - I used this test and had to tweak it down from 1.25V to 1.17V but at the end it took 30min to hit 80C and reveal a crash. Graphics, power and memory tests can also be useful. For thread cycling I think Auto just keeps all threads running, you can try with combinations of one, two or three CPUs (probably best both threads) in various patterns, this will help with checking for voltage dips.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |