Coming from Milkyway but SETI is BSOD'ing, help please.

Message boards : Number crunching : Coming from Milkyway but SETI is BSOD'ing, help please.

To post messages, you must log in.

AuthorMessage
Quagmir

Send message
Joined: 29 Mar 12
Posts: 8
Credit: 23,529
RAC: 0
United States
Message 1226494 - Posted: 3 May 2012, 2:38:32 UTC

Been running Milkyway for over a month now on a AMD 8 core 4.2 GHz 16 Gig 2200MHz 560TI.

I run wide open on the CPU at 110-120 degrees F, well below anything to worry about.

My GPU only hits 70 and sometiems a quick jump to 90 but pretty steady at 70% useage and run 130 to even 160 degrees F at times under that load. I had even manually turned up the fan to keep it under 130 degrees and had the same results.

I then switch over to SETI to run some stuff with them and after 20-30 minutes I BSOD with an error code pointing towards overheating(not the issue) or the second CPU (in this case GPU) hanging up causing the crash.

I still run 185.xx nvidia drivers because there is problems with the newer so I tried running Lunatics for SETi which ended up in the same results and finally a complete deinstall and reinstall. All still grabbing BSOD's while running SETI.

I am now running GPU only to see if it will BSOD on me but I thought I would ask and see if anyone had any ideas before I just go back to Milkyway.

GPU currently at 130 degrees F (55C) on GPU only.
ID: 1226494 · Report as offensive
Profile Gary CharpentierCrowdfunding Project Donor
Volunteer tester
Avatar

Send message
Joined: 25 Dec 00
Posts: 18653
Credit: 21,502,485
RAC: 19,066
United States
Message 1226508 - Posted: 3 May 2012, 3:28:13 UTC - in response to Message 1226494.  

Been running Milkyway for over a month now on a AMD 8 core 4.2 GHz 16 Gig 2200MHz 560TI.

I run wide open on the CPU at 110-120 degrees F, well below anything to worry about.

My GPU only hits 70 and sometiems a quick jump to 90 but pretty steady at 70% useage and run 130 to even 160 degrees F at times under that load. I had even manually turned up the fan to keep it under 130 degrees and had the same results.

I then switch over to SETI to run some stuff with them and after 20-30 minutes I BSOD with an error code pointing towards overheating(not the issue) or the second CPU (in this case GPU) hanging up causing the crash.

I still run 185.xx nvidia drivers because there is problems with the newer so I tried running Lunatics for SETi which ended up in the same results and finally a complete deinstall and reinstall. All still grabbing BSOD's while running SETI.

I am now running GPU only to see if it will BSOD on me but I thought I would ask and see if anyone had any ideas before I just go back to Milkyway.

GPU currently at 130 degrees F (55C) on GPU only.

Seti hits the CPU harder that most any other project. It may run 10C hotter than MW. Because it takes a while to happen it sounds very much like a thermal issue.

As to pointing at the second CPU are you sure it is pointing at the GPU and not core 2 on the CPU? Not overclocked? Voltage okay? Do all your MW work units verify? (Had one box that was getting ready to die have about 2% of the work units fail, box died about a month later.) If you are seeing failure's to verify are they CPU or GPU work?

Might try MW on the GPU and Seti on the CPU and see if that helps or hurts. Then try flipping, MW on CPU and Seti on GPU. Of course you can try GPU only and CPU only as well.

ID: 1226508 · Report as offensive
Quagmir

Send message
Joined: 29 Mar 12
Posts: 8
Credit: 23,529
RAC: 0
United States
Message 1226592 - Posted: 3 May 2012, 7:18:23 UTC - in response to Message 1226508.  

I noticed it did run a little hotter so i turned up the CPU fan. Brought it back down to temp.

Looks like i did have 2 errored CPU's.

Not Oc'ed. I'll turn the turbo off and run it at 3.6 only and see what happens.

Everything is new within 6 months, so if it is about to die. needs to happen now:)

Running at the base freq. and workign back up shoul dtell me if the CPU is power starved. Thanks for the help.
ID: 1226592 · Report as offensive
Profile Mike
Volunteer tester
Avatar

Send message
Joined: 17 Feb 01
Posts: 29590
Credit: 49,144,648
RAC: 17,275
Germany
Message 1226619 - Posted: 3 May 2012, 12:20:40 UTC
Last modified: 3 May 2012, 12:21:18 UTC

Running a FX in Turbo mode often causes trouble.
The motherboard increases voltage thats what a FX dont like in long term.
A FX needs to be undervolted.
I´m running my FX 8150 @4,4 GHZ with only 1.32V.
Full load 24/7 but this needs a very good mainboard with strong voltage converters.
With each crime and every kindness we birth our future.
ID: 1226619 · Report as offensive
Quagmir

Send message
Joined: 29 Mar 12
Posts: 8
Credit: 23,529
RAC: 0
United States
Message 1227829 - Posted: 5 May 2012, 13:50:11 UTC - in response to Message 1226619.  

Yeah I tried different combo's. It just doesnt like SETI.

Running @ 4.2 and 1.26v 24/7 on Milkyway with no problems.

I was mistaken before. I wasnt in Turbo mode. Seems Asus was nice enough to OC it for me. Downloaded AMD overdrive to turn off the Turbo and it was already off heh.

Using an ASUS M5A99X EVO Motherboard. A small step down from the Sabertooth since I didnt need dual PCI X16 slots. X8 and X8 works for my applications.

I even turned my water cooling down so I was sure it wasnt over heating. It wont go above 54C even with it on the lowest setting.

Milkyway and everything else runs like a champ. Something about my PC just doesnt like something about SETI. Even put my laptop on SETI to test it and no problems.

Thanks for your input though.
ID: 1227829 · Report as offensive
Profile Karsten Vinding
Volunteer tester

Send message
Joined: 18 May 99
Posts: 140
Credit: 17,503,422
RAC: 2,056
Denmark
Message 1227844 - Posted: 5 May 2012, 14:25:02 UTC - in response to Message 1227829.  

On my FX8150 running Seti, I had a short period where the machine would randomly BSOD, and reboot itself, sometimes several times a day.

I run it at 4.5Ghz with 1.325Vcore with watercooling, on an ASUS Sabertooth 990FX.

For some time I messed around with voltages to the CPU, only to see heat increase, but not stability.

Increasing voltage to the ram didn't seem to help either.

I ended up increasing the voltage for the HTT & PCI-E busses one notch, and voila, the system was completely stable, and has been since. I havent had one crash for ~2 weeks.

So there are other places to look for stability, especially if you are pushing things a bit.
ID: 1227844 · Report as offensive

Message boards : Number crunching : Coming from Milkyway but SETI is BSOD'ing, help please.


 
©2016 University of California
 
SETI@home and Astropulse are funded by grants from the National Science Foundation, NASA, and donations from SETI@home volunteers. AstroPulse is funded in part by the NSF through grant AST-0307956.