• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Reboot problem with TR

Page 2 - Seeking answers? Join the AnandTech community: where nearly half-a-million members share solutions and discuss the latest tech.
I have killed two of those power supplies. Just saying.
Well, I don't know how you did that. I have a house full of AX1200's, AX850's, one AX1200i and one 860i, and some are as old as 10 years or more. NEVER have I had a Corsair PSU fail, and remember, ALL my boxes run 100% load 24/7/365 for DC.

BTW, the system that started this thread has now been up for 48 hours with no problems.
 
I guess if it were me........ I read someplace you are doing most F@H DC work on that machine? Couldn't linux do that as well? Not sure about finding stable driver for Nvid 1080 cards, maybe they have them by now?

Anyway, might be worth an effort to make a few boot partitions and boot into linux and see how stable it is working with DC. I found running linux was way more stable than microsoft crunching with Seti. If your system still crashes, I'd suspect RAM or PS or Video Card.

Would suck if Thread Ripper was causing windows to become unstable... Just a thought you could try not crunching with GPU and see if the system becomes more stable? That less than or equal error could basically mean "ANYTHING". I once had it and solved it by reloading and updating the video drivers.
 
Wish I had seen this post early. Nvidia released drivers recently that caused a 750ti I had to artifact in game and also lockup (video card driver not responding) in windows. I almost ripped my hair out trying to figure out what was happening as I just recently installed it. I went back to nvidia's webpage some days later and they released a new driver update within a week of the prior one that fixed the issue. No more artifacts or crashes. So, head to Nvidia and find the dates of the two recent driver releases. One is a dud and the other likely fixes it.
 
Back
Top