F@h is now the top computing platform on the planet and nothing unites people like a dedicated fight against a common enemy. This virus affects all of us. Lets end it together.
Hardware configuration: Intel i7-4770K @ 4.5 GHz, 16 GB DDR3-2133 Corsair Vengence (black/red), EVGA GTX 760 @ 1200 MHz, on an Asus Maximus VI Hero MB (black/red), in a blacked out Antec P280 Tower, with a Xigmatek Night Hawk (black) HSF, Seasonic 760w Platinum (black case, sleeves, wires), 4 SilenX 120mm Case fans with silicon fan gaskets and silicon mounts (all black), a 512GB Samsung SSD (black), and a 2TB Black Western Digital HD (silver/black).
Thank you both, MtM yes, I agree with you, I couldn't figure out from where it appeared to go wrong, I fully expected to be starting from zero % but decided to consult with you guys I wasn't sure if I should delete or leave well alone, I'm glad I left it now.
Jeese_v Thanks for the link some interesting stuff in there, I'm rather concerned about the line below the PC is little more than 3 months old
It can also be caused by faulty memory or a bad memory controller, so you should consider both possibilities.
7im wrote:Still accurate. Wouldn't hurt to double chech proper memory settings and run it through memtest
Thanks 7im how long would you suggest to run memtest for? TBH this PC has given me a few headaches but not so far enough to take it back, in the main the issues have related to the PC not picking up USB devices which means I need to plug out and return after which all is fine, annoyingly this doesn't happen all the time. Also I get the odd BSOD I could do with getting this sorted once and for all, are you aware of any freebie software that would test out the whole PC?
[23:46:33] Client-core communications error
[23:46:33] Deleting current work unit & continuing...
Folding@Home Client Shutdown at user request.
Folding@Home Client Shutdown.
printed only in the scenario that the wu 'failed' after the user quit the client ( in which case the client would stop the core which in this case isn't working nicely so you get a client-core communication error ). However since it can resume from checkpoint unless you happen to stop the client when its actually writing a checkpoint, this is a 'cosmetic' issue? It's an old core look at the last update time, it doesn't exit cleanly. Not that it would ever hurt anything except time to fold wu's if you're not sure and want to rule some hw problem out.
MtM I happened to be looking at the WU in progress immediately I saw the error I closed the WU down, because I wanted to complete a virgin windows install I copied the FAH folder to a USB stick and pasted this file back into C:/ after the install was completed, I was very surprised when I realised the client carried on from where it left off, I was fully expecting a complete new WU
Thanx Bruce, I didn't know that you had posted a reply, however you're bang on the nail, just checked it out on EOC it went up while I was sleeping last night.
I was about to feed this info back to the Guys on here, but you beat me to it.
Thank the Lord I wasn't too tempted to delete the WU before mentioning it on here first.