Project 922
It seems as if my computer is BSODing while running project 922, and once with 917. This is perplexing, as I DID just install the RAID array, but the computer is up w/o a single hiccup when F@H isn't running (for 11 hours, anyways).
Has anyone else had similar problems? How did you fix them?
Last night the computer managed to reboot itself nearly 10 times while I slept (I know cause of the F@H logs). If that keeps up, I'll never get a WU out, not to mention the stress the rest of te system is put under from the constant reboots.
I removed the -forcesse switch, so I'll see if this fixes the problem. If not, I may have to stop running F@H on this (my fastest folder) machine, so I could narrow down the problem. Thanks to the BIOS incident 2 weeks ago, my points are already down, and I'm not looking forward to it...
Has anyone else had similar problems? How did you fix them?
Last night the computer managed to reboot itself nearly 10 times while I slept (I know cause of the F@H logs). If that keeps up, I'll never get a WU out, not to mention the stress the rest of te system is put under from the constant reboots.
I removed the -forcesse switch, so I'll see if this fixes the problem. If not, I may have to stop running F@H on this (my fastest folder) machine, so I could narrow down the problem. Thanks to the BIOS incident 2 weeks ago, my points are already down, and I'm not looking forward to it...
0
Comments
/me shudders.
Oh, and yes... The CPU is the one in my sig.
So what's the plan csimon?
(Since ditching 95/98/ME . . . with those O/Ss all I had to do was move the mouse and I might have been greeted with a BSOD)
Not when I was accessing the forums with my Sidekick... I never got the notice.
Anyways, I'm starting SSE again to see if the problem returns. If it does, I'll go check out this beta.
You see, to solve my RAID escapade I ended up having to flash to a previous BIOS version (previous RAID BIOS as well). Course, this cleared my CMOS, leaving me to put everything back by memory, and set the VDIMM to 1.8V, when it needs 1.9V to make a FSB of 210 (Great for Kingston HyperX 3500, huh? pfft...) and now things seem ok, even with SSE enabled (or so it has been for the past 6 hours, 8 minutes).
Makes since, as SSE has always worked fine beforehand. Although I wont be fully convinced the problem has been solved 'till around 4PM, provided it can keep from rebooting.
Looks like it's time to look into that beta.
EDIT: Nevermind, looks like it barfed when not using it as well. I'll bring the VCore up a touch, and see if that helps.