I was overclocking my E8400 3.0GHz to 4.2GHz. Worked fine. My nature instinct say lets hit 4.4GHz for fun. BSOD. I reboot and reset the clock back to the stable 4.2GHz. I started up VMware to resume my work and this is what I have received.
Click full size so you can read the VMware errors.
I erased everything; reinstalled vmware player and notfreds, but the same issue came back.
Please help me figure out how to get my duo core pumping out some more science!
That's a networking problem. Do you connect to some network hub or directly to the Internet?
I've had that before, and what I usually do is disable and reenable the network adapters (essentially playing around with the network settings until it works).
I don't use Intel processors, but going from 3.0 to 4.2 seems quite high to me. Have you ran a stress test like StressCPU2 yet (viewtopic.php?f=14&t=52). Windows-stable does not imply FAH-stable.
I never had to disable/reenable network device in the vm ( don't ask about needing to reset the router to my isp though ).
But that end of trace looks familiar, how much ram are you allocating for the vm? What project was it running when it gave the error and when did the error occur preciesly? If you allocated enough ram, and the error has not been from a restart ( which might indicate a bad flash drive? ) I would run memtest to concentrate on ram, and not as toTow adviced stresscpu2 as it's more probable memory related then cpu.
I had forgot my VMware was running while trying some overclocks. I hit a barrier at 4.4GHz. After the reboot I had that network issue which I don't receive anymore but now I get the trace error every time I open VM. I have restarted, reinstalled it, seems like everything. I'm stable at 4.2GHz (prime95), but I can't resume the WU. I'm not sure which WU it was on at the time.
Try lowering your clocks even further, probably even back to your original ones to see if the problem goes away.
By the way, we generally don't recommend prime95 as a stress tester because it doesn't stress the CPU enough. Try the utilities on the tools page. As said, try StressCPU2. It comes from the developers of Gromacs and stresses your CPU similar to FAH.
I've been running StressCPU2 for a couple hours now at 4.2GHz. Everything seems rock solid except the CPU temperature is at 65c. The max for this CPU is 72c. I'm not too concerned, but if that is the reason my SMP is giving me an End Trace Error than I'll clock down to 4.05GHz.
I'm also wondering how I can completely remove any trace of VMware and SMP Folding from my computer so I can start fresh. It seems like just a regular unstallation and deletion of remaining files might leave something behind to trigger my Trace error. I'm pretty lost looking for a solution at the moment.
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).
Passing StressCPU v2.0 does not exactly equal the clock speed that will run the SMP client without error. Take your top passing speed, and then back down the GHZ by 10-15% (or slightly more) and that should be about the right speed to shoot for. Of course, that recommendation was from the previous generation of Intel chips, so your mileage my vary.
Are we also forgetting that stresscpu2 is bad at picking up memory errors compared to memtest86+ ...
End of trace somehow makes an alarm go off which says 'check memory' for me personally though I can't remember the exact reference I'm quite positive this is more ram related then cpu.