• Some users have recently had their accounts hijacked. It seems that the now defunct EVGA forums might have compromised your password there and seems many are using the same PW here. We would suggest you UPDATE YOUR PASSWORD and TURN ON 2FA for your account here to further secure it. None of the compromised accounts had 2FA turned on.
    Once you have enabled 2FA, your account will be updated soon to show a badge, letting other members know that you use 2FA to protect your account. This should be beneficial for everyone that uses FSFT.

temperature question

jws2346

[H]ard|Gawd
Joined
Feb 28, 2007
Messages
1,768
If this is a topic that has been discussed already, please ignore it. I'm currently folding 24/7 with 2x E6600's (OC'ed to a mild 3 GHz, FSB 333), a E6420 (OC'ed to an even milder 2.4 GHz) and a E6400 (no case, sitting on my desk, stock clock). Being temperature "anal" I like to have at least my cpu temp displayed in the task bar (I know they're only approximates). My problem on all 4x rigs is they run SpeedFan and (the E6400 only) TAT no problems while folding , but when I bring up Core Temp on any of them I get a BSOD while folding, without folding everything is copacetic. I do the WinSMP client, the two E6600's are presently in Bioster TForce P965 boards, the E6420 is in a AW9D-MAX and the E6400 is in an "el cheapo" Asrock 775DUAL-VSTA mobo. All but the E6400 has PC6400 RAM, one E6600 has 3 GB's, one has 2 GB's, the E6420 has 2 GB's and the E6400 has 2 GB's of 667 DDR2. (when I get more energy I'll throw the E6400 in a Asus P5B Deluxe board I have in the closet) Like I said if this is an old problem and has been answered a "thousand" times please ignore it. If anybody is not ignoring it and has a solution please post it.
 
IMHO, ask this in the Overclocking & Cooling section since it is more related to the temp software and not a folding client issue.

However, I can tell that with some motherboards, it is possible that some software will cause crashes due to a issue with the smbus driver. In fact, my file server, which is running on a Abit AN8-SLI and I can't run SpeedFan on it without crashes and reboots. I just ditched it and ran CoreTemp.

If you are able to run SpeedFan, you can trust it since it has the same core temps feature as CoreTemp so it's also pretty accurate.

 
IMHO, ask this in the Overclocking & Cooling section since it is more related to the temp software and not a folding client issue.


Not to be a wise a$$ or anything, but this is a FOLDING question. Like I said in my post Core Temp works fine without running the WinSMP client folding at the same time as I try to bring the Core Temp program up. Besides the E6400 is not OC'ed :rolleyes:
 
Is it possible to have it stop the auto-reset on the BSOD and get what info you can from it? That might help you find out the problem.
 
IMHO, ask this in the Overclocking & Cooling section since it is more related to the temp software and not a folding client issue.


Not to be a wise a&& or anything, but this is a FOLDING question. I have been able to bring up the Core Temp program as long as I'm not folding using the WinSMP client. Besides the E6400 on my desk is not OC'ed. :rolleyes:

Edit: Oh yeah, when I run Orthos on either rig my temps from Core Temp correspond (they're the same) to my SpeedFan core temps
 
Is it possible to have it stop the auto-reset on the BSOD and get what info you can from it? That might help you find out the problem.

I agree, do this and report the STOP message since this will tell you what is the possible cause.

I indeed misread it a bit and I find it very weird that with the SMP client, it crash. However, I can bring a possible explanation : Without the client, the pc is idling so it is running fine but when you start folding, it is stressing the computer causing it to crash.

Are you able to run the WinSMP client alone for 24 hours without crashes ?

 
Sorry about the double post :mad: I fold 24/7 with all these rigs fine as long as I don't try to bring the Core Temp program up. With the Orthos stress program I thought you were stressing the machine, but not as much as folding. I can bring up Core Temp just fine using the Orthos program, but when I fold I get a BSOD from Core Temp. No biggy, I'll just use SpeedFan. (I can't seem to adjust the font in Core Temp anyway)

Edit: On the reset thing, I prefer the BIOS reset instead of powering off. I think my Asus P5B DLX, Biostar Tforce's and my AW9D-MAX reset themselves, but I haven't figured out how to get the Asrock to do a reset without a power off. I'm obviously new to OC'ing and I don't OC' to an extreme, just 3 GHz or so on my E6600's. I use a 1.35v vcore and I want cool and dependable rigs for 24/7 folding. (yeah I know THIS belongs in the OC'ing section)
 
Read my article at http://www.hardforum.com/showthread.php?t=1201813 and you will see the issues of overclocking on folding ;)

Myself, I had a computer making me pull my own hair for weeks on end till someone tell me to relax on ram timings. After doing this, it is folding fine... Orthos isn't good enough to prove a folding machine is stable. I even included a link to a good one or pick the Gromacs option in the latest Orthos (5th one in the pull-down list).

 
Man, that's one "dynamite" article you wrote about folding. One thing I did notice in the begining you talked about the dreaded "EUE" thing. I fold 24/7 with absolutely no problems. What's got me at "wits end" is when I try and bring up Core Temp while folding all the freakin' machines BSOD on me. Like I said as long as me and SpeedFan get along I'm cool. Thanks for your help and especially trhanks for the "heads up" on the folding artricle. :D
 
Man, that's one "dynamite" article you wrote about folding. One thing I did notice in the begining you talked about the dreaded "EUE" thing. I fold 24/7 with absolutely no problems. What's got me at "wits end" is when I try and bring up Core Temp while folding all the freakin' machines BSOD on me. Like I said as long as me and SpeedFan get along I'm cool. Thanks for your help and especially trhanks for the "heads up" on the folding artricle. :D

With the computer I had problems, I never get any EUE, only problems starting and stopping the 4 FahCore_a1.exe threads so it's not always a EUE who determine if it is stable or not.

Thank you for your comment :)

 
Ok. This part is confusing.
Edit: On the reset thing, I prefer the BIOS reset instead of powering off. I think my Asus P5B DLX, Biostar Tforce's and my AW9D-MAX reset themselves, but I haven't figured out how to get the Asrock to do a reset without a power off. I'm obviously new to OC'ing and I don't OC' to an extreme, just 3 GHz or so on my E6600's. I use a 1.35v vcore and I want cool and dependable rigs for 24/7 folding. (yeah I know THIS belongs in the OC'ing section)

You keep stating the the system will BSOD. Blue Screen of Death.

People hated BSOD in Win98. So Microsoft (infinate marketing knowledge) setup WinXP so that whenever the system has a BSOD, it automatically resets the computer before the information with the BSOD is displayed. Thus eliminating BSOD from the end user. It is still happening though, it just isn't noticed by the end user.

Is the system just locking up when you try to access this program or are you legitimately getting a BSOD stop error in Windows XP?
 
Ok. This part is confusing.


You keep stating the the system will BSOD. Blue Screen of Death.

People hated BSOD in Win98. So Microsoft (infinate marketing knowledge) setup WinXP so that whenever the system has a BSOD, it automatically resets the computer before the information with the BSOD is displayed. Thus eliminating BSOD from the end user. It is still happening though, it just isn't noticed by the end user.

Is the system just locking up when you try to access this program or are you legitimately getting a BSOD stop error in Windows XP?

I've just about given up any concern about the BSOD trying to bring up Core Temp while folding 24/7 with the WinSMP client, as long as everything goes along as accurate as possible (just as a reference, I know SW programs are inaccurate) in SpeedFan I'll just use that program. Now as far as this legitimate BSOD thing goes (what's a illegitimate BSOD?) I thought when a machine stopped and gave you a blue screen telling you windose has stopped it was a legitimate BSOD. Not only is the machine locked up, it won't do anything until either you soft or hard reboot the machine and then, depending on the type of reboot, motherboard or BIOS you might have to set you're FSB and OC'ing stuff again. To my understanding when the monitor screen shows all blue with white lettering giving you an error code it was called a BSOD (blue screen of death). I haven't used the Win98, ME or any older M$ OS (non NT ?) in many years. As soon as a SP comes out for VISTA I'll probably give that OS a try. I'm currently using WinXP with SP #2 . Once again I've got to thank the helpful members on this forum, especially the "heads up" on the article about folding.

Oh yeah, I think even people in WinXP are a little adverse to the BSOD.

Edit: I almost forgot. I like the convienience of windose, but I have done some Linus SMP'ing with Ubuntu (my latest was Fiesty Fawn, SP). I find the Linux SMP client to be a shade faster than the WinSMP client. If all goes to plan and I get a Q6600 (with good WC'ing) after the July 22nd price cuts I'm going to see how much faster Linux SMP is over WinSMP. It seems the Conical people make installing the "dual" boot system so much easier.
 
I've thought about the dual boot as well. The only problem I see with dual boot is that the deadlines are SO tight on the SMP units that flipping from one OS to the other will most likely force the client that is currently not running to miss its deadline when you switch back over. Only way to avoid it that I see is to shut down one client after it finishes but before it loads a new WU and then switch over for a while. It just didn't really make much sense in my eyes.

edit: Besides, I play too many games to spend much time in linux. :)
 
Yeah, I agree completely with the SMP WU's being so tight on the deadlines. I think to be able to run both the Linux SMP and the WinSMP you'd have to have a fast rig (probably at least a 3 GHz cpu) and monitor it constantly. Personally I don't do that much gaming, but I still like the convienience of WinXP or when M$ issues the first SP, I'll probably go with VISTA. I've only got 3 GB's PC6400 RAM, from what I understand I'll need at least another 1 GB :confused: . I have currently built a WC'ing loop (Apoogee GT WB, MCP350 WP, MCR220 RAD, etc) so when the 22nd July price cuts become a reality I hope to go with a Q6600 and OC' it to 3.0 GHz (333 FSB) From my understanding the quad runs hot and WC'ing is the best alternative for 24/7 folding. Just off the wall though, from my limited exposure to the Linux OS it seems to be an up and comer, M$ better look out.
 
Back
Top