my laptop keeps crashing when running seti@home


log in

Advanced search

Questions and Answers : Windows : my laptop keeps crashing when running seti@home

Author Message
wayne
Send message
Joined: 5 Jul 13
Posts: 1
Credit: 82,326
RAC: 0
United Kingdom
Message 1430835 - Posted: 19 Oct 2013, 18:25:48 UTC

it happens regularly. I don't know a lot about computerthingymibobs so answers in plain English appreciated

rob smithProject donor
Volunteer tester
Send message
Joined: 7 Mar 03
Posts: 8535
Credit: 59,469,510
RAC: 86,445
United Kingdom
Message 1430836 - Posted: 19 Oct 2013, 18:29:56 UTC

Others will ask for more details, but as an observation - recently you have been having a number of errors reported when running work on the GPU, this can often (but not always) be attributed to things getting too hot under the bonnet.
____________
Bob Smith
Member of Seti PIPPS (Pluto is a Planet Protest Society)
Somewhere in the (un)known Universe?

Profile BilBg
Volunteer tester
Avatar
Send message
Joined: 27 May 07
Posts: 2806
Credit: 6,330,137
RAC: 7,450
Bulgaria
Message 1431007 - Posted: 20 Oct 2013, 6:21:56 UTC - in response to Message 1430835.
Last modified: 20 Oct 2013, 6:43:06 UTC


Try to use TThrottle to limit the temperatures (especially on GPU as the errors/crashes are for 'AstroPulse v6 v6.06 (opencl_ati_100)')
http://setiathome.berkeley.edu/results.php?hostid=7035190&offset=0&show_names=0&state=6&appid=

TThrottle:
http://www.efmer.eu/boinc/

"Select a temperature, check "Auto active" and TThrottle handles the rest" -
type 2 values: for CPU temperature ('Set Core') and GPU temperature ('Set GPU'),
e.g. 60°C 70°C - these are the Max temperatures You allow for BOINC apps to heat your CPU/GPU (TThrottle will lower the CPU/GPU usage% when/if these temperatures are reached)

(at the first start TThrottle may appear to hang/lag the computer for a few minutes during tests it does to determine the number of sensors in your CPU (this may be fixed in later versions - TThrottle 6.10 was the version I used a year ago when this happened at first start on new CPU))


____________



- ALF - "Find out what you don't do well ..... then don't do it!" :)

PsiKoPatH
Avatar
Send message
Joined: 4 Sep 99
Posts: 6
Credit: 618,610
RAC: 0
Netherlands
Message 1437453 - Posted: 3 Nov 2013, 19:07:38 UTC - in response to Message 1430835.

I have installed boinc today on a w7 64 bits machine I use for gaming. After about an hour I got a blue screen and a system reboot. Started boinc again, and after about 2 hours the same thing. This is when simultaneously playing Perfect World (Which is graphic heavy) and Tribal Wars (simple browser game). I use Chrome for browsing at the moment and am connected to facebook, the browser game and Youtube. Not much else running, only the occasional movie I watch at night using vlc player. I was not doing that during the two blue screens so...

I only run Seti@home, and do not use my gpu's as they tend to become hot fast due to unfortunate placement next to the soundcard. So only run on my normal processor which is a Intel(R) Core(TM) i7 CPU 975 @ 3.33GHz.

No overclocking on anything. I have set processor at 90 percent when not busy for Seti.

Any advice? I run boinc on my osx machine without problems. No gpu there obviously but runs even faster than on the windows machine even though it's older. I've seen recommendations for temperature settings earlier in this thread. Is that also possible for the main processor? Honestly, you'd think that a program like this would figure that out for itself and not overwork the cpu.
Maybe I should try to dial down cpu usage from 90 to 60 percent or so and see if that works.

I'd like to continue to contribute on the w7 machine as well but if this continues I'm afraid to loose data and/or will have to re-install. At that point it's no longer worth it for me.

Thx.

Profile Ageless
Avatar
Send message
Joined: 9 Jun 99
Posts: 12327
Credit: 2,632,842
RAC: 1,201
Netherlands
Message 1437599 - Posted: 4 Nov 2013, 1:36:53 UTC - in response to Message 1437453.
Last modified: 4 Nov 2013, 1:37:34 UTC

After about an hour I got a blue screen and a system reboot.

So what did the blue screen say?
When in doubt, you can use Blue Screen View to see what it, or they, said. And post that info here, of course.

Also, even though you may want to run BOINC at the same time as a game, it's best to not do so. Or you can, as long as you let BOINC pause the game automatically. You can do so using the <exclusive_app> tags in a client configuration file (cc_config.xml).

You can exclude many programs. One per line. And do so that the whole of BOINC suspends with the <exclusive_app> option, or only the GPUs with the <exclusive_gpu_app> option. Below is all the games that stop my BOINC:
<cc_config> <log_flags> </log_flags> <options> <exclusive_app>BioShockInfinite.exe</exclusive_app> <exclusive_app>BurnoutParadise.exe</exclusive_app> <exclusive_app>Crysis.exe</exclusive_app> <exclusive_app>Crysis2.exe</exclusive_app> <exclusive_app>Crysis3.exe</exclusive_app> <exclusive_app>DarkAthena.exe</exclusive_app> <exclusive_app>DarkAthena_Launcher.exe</exclusive_app> <exclusive_app>DOOM3.exe</exclusive_app> <exclusive_app>DOOM3DED.exe</exclusive_app> <exclusive_app>dxhr.exe</exclusive_app> <exclusive_app>dxhrml.exe</exclusive_app> <exclusive_app>EFLC.exe</exclusive_app> <exclusive_app>FarCry2.exe</exclusive_app> <exclusive_app>fc3_blooddragon.exe</exclusive_app> <exclusive_app>fc3_blooddragon_d3d11.exe</exclusive_app> <exclusive_app>fc3bd.exe</exclusive_app> <exclusive_app>FUEL.exe</exclusive_app> <exclusive_app>hl2.exe</exclusive_app> <exclusive_app>iw3sp.exe</exclusive_app> <exclusive_app>iw4sp.exe</exclusive_app> <exclusive_app>iw5sp.exe</exclusive_app> <exclusive_app>LaunchEFLC.exe</exclusive_app> <exclusive_app>Launcher.exe</exclusive_app> <exclusive_app>nexus.exe</exclusive_app> <exclusive_app>nexus_DX9.exe</exclusive_app> <exclusive_app>NFS11.exe</exclusive_app> <exclusive_app>NFS13.exe</exclusive_app> <exclusive_app>oblivion.exe</exclusive_app> <exclusive_app>OFDR.exe</exclusive_app> <exclusive_app>OperationFlashpoint.exe</exclusive_app> <exclusive_app>Rage.exe</exclusive_app> <exclusive_app>RedRiver.exe</exclusive_app> <exclusive_app>RedRiverLauncher.exe</exclusive_app> <exclusive_app>skyrim4gb.exe</exclusive_app> <exclusive_app>SkyrimLauncher.exe</exclusive_app> <exclusive_app>SpecOpsTheLine.exe</exclusive_app> <exclusive_app>TESV.exe</exclusive_app> <exclusive_app>t6sp.exe</exclusive_app> <exclusive_app>TombRaider.exe</exclusive_app> <exclusive_gpu_app>FEAR.exe</exclusive_gpu_app> <exclusive_gpu_app>farcry3.exe</exclusive_gpu_app> <exclusive_gpu_app>FarCry.exe</exclusive_gpu_app> <exclusive_gpu_app>Bioshock.exe</exclusive_gpu_app> <exclusive_gpu_app>Bioshock2.exe</exclusive_gpu_app> <exclusive_gpu_app>DX2Main.exe</exclusive_gpu_app> <exclusive_gpu_app>dx2.exe</exclusive_gpu_app> <exclusive_gpu_app>GTAIV.exe</exclusive_gpu_app> <exclusive_gpu_app>MOHDW.exe</exclusive_gpu_app> <exclusive_gpu_app>HitmanBloodMoney.exe</exclusive_gpu_app> <exclusive_gpu_app>Hunted.exe</exclusive_gpu_app> <exclusive_gpu_app>Fallout3.exe</exclusive_gpu_app> <exclusive_gpu_app>googleearth.exe</exclusive_gpu_app> <exclusive_gpu_app>HitmanContracts.exe</exclusive_gpu_app> <exclusive_gpu_app>hitman2.exe</exclusive_gpu_app> <exclusive_gpu_app>S2DNG.exe</exclusive_gpu_app> <exclusive_gpu_app>S2DNGEditor.exe</exclusive_gpu_app> <exclusive_gpu_app>HMA.exe</exclusive_gpu_app> </options> </cc_config>


I only run Seti@home, and do not use my gpu's as they tend to become hot fast due to unfortunate placement next to the soundcard. So only run on my normal processor which is a Intel(R) Core(TM) i7 CPU 975 @ 3.33GHz.

Which is why you aborted all the work for the GPUs?
Have you in the mean time also set the project preferences not to use the ATI GPU? That way you won't get new work for the GPUs, that you then have to abort.

I have set processor at 90 percent when not busy for Seti.

And how did you do that?

Any advice?

Well, without knowing what the BSODs said, it's difficult.
When was the last time you cleaned out the machine, taken all the dust bunnies out?

Honestly, you'd think that a program like this would figure that out for itself and not overwork the cpu.

Honestly, the developers warned you about it in the Rules and policies: The applications run by SETI@home may cause some computers to overheat. If this happens, stop running SETI@home or use a utility program that limits CPU usage. Like TThrottle.
____________
Jord

Fighting for the correct use of the apostrophe, together with Weird Al Yankovic

PsiKoPatH
Avatar
Send message
Joined: 4 Sep 99
Posts: 6
Credit: 618,610
RAC: 0
Netherlands
Message 1437729 - Posted: 4 Nov 2013, 9:53:27 UTC

Yeah, when a game runs it pauses (I play only two). The mistake with the gpu tasks was that I didn't realize the settings you set on the website have the option to not use the gpu while I can't find that in the boinc manager. I've changed that and set cpu time to 60 percent in stead of 90.

As for cleaning the dust out, I also have cats so I use compressed air to blow the whole thing out about once a month :)

It has run for about 12 hrs now without problems so I'm going to leave it alone.

Profile ignorance is no excuse
Avatar
Send message
Joined: 4 Oct 00
Posts: 9529
Credit: 44,433,321
RAC: 0
Korea, North
Message 1437951 - Posted: 4 Nov 2013, 20:49:40 UTC

I suggest turning BOINC completely off when gaming. Most modern games require enough CPU and GPU time that the sharing becomes a problem with the BOINC processes causing stops, skips, and even crashes. Just restart BOINC when you are done playing
____________
In a rich man's house there is no place to spit but his face.
Diogenes Of Sinope

End terrorism by building a school

Questions and Answers : Windows : my laptop keeps crashing when running seti@home

Copyright © 2014 University of California