Bug Report - Random Reboots
Message boards : Number crunching : Bug Report - Random Reboots
| Author | Message | |
|---|---|---|
|
There seem to be some bug(s) that may be causing my computer to randomly reboot.
|
||
ID:
5300 | Rating: 0
| rate:
/
|
||
|
To clarify, "Random Reboot" is not the infamous "Blue Screen Of Death", which at least reports the probable cause of the problem. When one of these reboots happens, the screen simply goes black, and then the POST appears.
|
||
|
ID:
5301 | Rating: 0
| rate:
/
|
||
|
Try another co-project, POEM or Rosetta for example. Try to narrow the problem down, ie. if the problem is occuring with other co-running projects as well. A lot of the "optimised" stuff around is not 100% reliable across all hardware systems.
|
||
|
ID:
5302 | Rating: 0
| rate:
/
|
||
|
Try another co-project, POEM or Rosetta for example. Try to narrow the problem down, ie. if the problem is occuring with other co-running projects as well. A lot of the "optimised" stuff around is not 100% reliable across all hardware systems. I may try that after a while. I want to reduce the possibilities rather than increase them. The optimized code seems to be working fine. There have been zero reboots since I suspended the D@H tasks. So I have two time periods during which there were no reboots, and in both of those times, there were also no D@H tasks running. However, this second time period has been only about 1 day so I'll be letting it go on for a few more days to make sure. What about the debugging? ____________ 
|
||
|
ID:
5304 | Rating: 0
| rate:
/
|
||
|
By not doing so, you make the assumption that Docking is at fault and that SETI is fine. The thousands of other Docking users that do not have your problem must just be lucky? Rather then increasing the possibilities, the course of action I suggest narrows your problem. Turning Docking off achieves nothing.
|
||
|
ID:
5307 | Rating: 0
| rate:
/
|
||
|
There seem to be some bug(s) that may be causing my computer to randomly reboot. This is very odd. We haven't seen behaviour like this before, and would be interested to know if you can indeed find a direct correlation to our project and the reboots. Please keep us updated on your testing. |
||
|
ID:
5313 | Rating: 0
| rate:
/
|
||
|
It has been a week since my last post on this subject, and during that week D@H has not been running while S@H has been. Also, I have not had any spontaneous reboots during that week.
By not doing so, you make the assumption that Docking is at fault and that SETI is fine. The thousands of other Docking users that do not have your problem must just be lucky? Rather then increasing the possibilities, the course of action I suggest narrows your problem. Turning Docking off achieves nothing. What I have achieved is that now we know that it is very likely that D@H is involved. If S@H optimized code is the cause then at very least D@H is the catalyst. One or the other of these two projects may be stepping on the other in such a way that causes these reboots. It could also be that S@H is not involved at all. Something in my system is stepping on D@H, or vice-versa.
|
||
|
ID:
5317 | Rating: 0
| rate:
/
|
||
|
Docking is the only other BOINC project you have tried. My suggestion was to try others and see if they run okay or not. That could point you in the direction of the problem - all you know now is that SETI and Docking won't cohabit on your system.
|
||
|
ID:
5321 | Rating: 0
| rate:
/
|
||
|
Docking is the only other BOINC project you have tried. My suggestion was to try others and see if they run okay or not. That could point you in the direction of the problem - all you know now is that SETI and Docking won't cohabit on your system. I am not trying to point fingers, so chill. :D I wonder if anything can be done to help locate the problem other than trying a bunch of other projects? ____________
|
||
|
ID:
5323 | Rating: 0
| rate:
/
|
||
|
If you wont run other projects, then unload the new driver and try the existing project set without it. The problem with that approach is uninstalling, does whatever uninstall method used actually take everything the installer installed out? Since your problems started with that driver, it would seem the obvious target for suspicion.
|
||
|
ID:
5328 | Rating: 0
| rate:
/
|
||
|
Reverting the video driver is easy, but then, cannot really tell me what happened or why. If this method is successful, it will simply tell me that the video driver is involved because the problem will go away. Also, the CUDA code from S@H will not work with the older video driver, so that part of the situation will be changed as well as the video driver. I will
not
be testing just 1 change, but 2.
|
||
|
ID:
5329 | Rating: 0
| rate:
/
|
||
|
Docking is the only other BOINC project you have tried... You have made the assumption that SETI is fine and Docking is the problem - if that is what you want to believe, well I doubt we will change your mind. I could have just abandoned D@H, uninstalled all of its code, and happily gone on my way, with zero random reboots. Instead, I am still writing to this thread. This should suggest to you that I am interested in getting to the bottom of this and that I am not interested in just attaching blame to the easiest target. ____________
|
||
|
ID:
5330 | Rating: 0
| rate:
/
|
||
|
Docking is the only other BOINC project you have tried... You have made the assumption that SETI is fine and Docking is the problem - if that is what you want to believe, well I doubt we will change your mind. Does it happen too if you set in the preferences: Leave applications in memory while suspended? As I do not have problems do run, prime, seti (with optimized apps), docking, ABC, malaria and rosetta at the same time. Could you also try to run your system only with the windows provided drivers? |
||
|
ID:
5331 | Rating: 0
| rate:
/
|
||
|
Does it happen too if you set in the preferences: Leave applications in memory while suspended? I already have that option set. Should I unset it? Could you also try to run your system only with the windows provided drivers? The problem there is that the S@H CUDA code requires the nVidia video drivers. ____________
|
||
|
ID:
5332 | Rating: 0
| rate:
/
|
||
|
Does it happen too if you set in the preferences: Leave applications in memory while suspended? Yes, I'm aware that you need it for seti on cuda but to rule out that the problem is the nvidia driver you should disable the nvidia driver, reboot and run docking with the windows provided driver. As seti have fixed downtimes you can do that in that timeframe. |
||
|
ID:
5334 | Rating: 0
| rate:
/
|
||
|
Yes, I'm aware that you need it for seti on cuda but to rule out that the problem is the nvidia driver you should disable the nvidia driver, reboot and run docking with the windows provided driver. As seti have fixed downtimes you can do that in that timeframe. I know already that both the nVidia video driver and the D@H code are involved, because the problem began after I upgraded the nVidia video driver, and then it went away after I stopped running D@H. The S@H CUDA code may also be involved. It takes all of the components together to create the problem, because by removing just one (D@H) I have a stable system with the other two (nVidia and CUDA). Now that we know what the components are, can anything be done to make them all co-exist? Or do I just have to give up on running more than the one project? FYI, here is some of the info from the nVidia control panel. CPU Intel(R) Core(TM)2 Quad CPU Q6600 @ 2.40GHz Operating System Microsoft Windows XP Professional Service Pack 3, Build 2600 Motherboard Vendor NVIDIA Motherboard Version 2.0 Motherboard Model NVK84CRB DirectX 9.0c (5.3.2600.5512) Nforce Driver Package 6.03 Graphics Driver 190.38 (6.14.11.9038) Ethernet Driver 67.72 (1.00.02.06772) IDE Driver 9.99.0.8 nTune 6.03.12 GPU GeForce 8800 GT ____________
|
||
|
ID:
5335 | Rating: 0
| rate:
/
|
||
|
> Yes, I'm aware that you need it for seti on cuda but to rule out that the problem is the nvidia driver you should disable the nvidia driver, reboot and run docking with the windows provided driver. As seti have fixed downtimes you can do that in that timeframe. |
||
|
ID:
5337 | Rating: 0
| rate:
/
|
||
|
Garrrrg... the quoting is somewhat messed up. I have cleaned it up below (I hope) to show who said what in reply to which ...
Topolm said: Steven said: I am a lunatic Will try turning off the GPU and turning on D@H. Steven said: Steven said: As it took some doing to get a version of the nVidia drivers installed that would work with the optimized CUDA app, I'm not willing to go down that road again yet. Will start with checking to see if SETI and DOCKING will co-exist without CUDA because that is just a setting in options to turn off the use of the GPU, so I will not have to download and install all sorts of drivers and CUDA apps to find an older pair that will work together. Unfortunately, since the GPU can process about 3 WU per hour while the CPU does less than 1 per hour with each 4 of the processors, disabling the GPU will be a huge reduction in throughput. So I would rather find another way. ____________
|
||
|
ID:
5338 | Rating: 0
| rate:
/
|
||
|
Hi, on one of my Q6600' s, mildly OC'ed, a lot of
error's
occurred.
|
||
|
ID:
5342 | Rating: 0
| rate:
/
|
||
|
If the problem is a bluescreen then this tip might help you get a chance to see it!
|
||
|
ID:
5346 | Rating: 0
| rate:
/
|
||
David Ball
Forum moderator Volunteer tester 
Joined: Sep 18 06 Posts: 274 ID: 115 Credit: 1,634,401 RAC: 0 |
||
|
Are you running the BOINC screensaver on that system, Steven? If so, maybe it's the D@H screensaver interacting with the CUDA code.
|
||
|
ID:
5347 | Rating: 0
| rate:
/
|
||
|
Are you running the BOINC screensaver on that system, Steven? If so, maybe it's the D@H screensaver interacting with the CUDA code. No screen saver at all because that would cut into the CUDA through-put since the CUDA code by itself will peg the GPU at 100% usage. In any case, I decided to just run S@H Op Apps, for CPU and GPU, on the Q6600. The other comp is running S@H Op Apps for CPU and D@H. Since it has no CUDA-capable GPU, it is running with no CUDA. ... and no troubles. ____________
|
||
|
ID:
5360 | Rating: 0
| rate:
/
|
||
|
One of my computers is doing the same thing on this project with no other projects running. The computer just reboots (no blue screen of death). It does not do this in any other project or when this project is not running.
|
||
|
ID:
5461 | Rating: 0
| rate:
/
|
||
|
Had three reboots as described for the first time this week also.
|
||
|
ID:
5462 | Rating: 0
| rate:
/
|
||
|
I MAY have seen this problem, but only once, some time ago. Not enough information recorded to tell if a Docking@home workunit was running when the reboot occurred.
|
||
|
ID:
5551 | Rating: 0
| rate:
/
|
||
Message boards : Number crunching : Bug Report - Random Reboots
Database Error: The MySQL server is running with the --read-only option so it cannot execute this statement
array(3) {
[0]=>
array(7) {
["file"]=>
string(47) "/boinc/projects/docking/html_v2/inc/db_conn.inc"
["line"]=>
int(97)
["function"]=>
string(8) "do_query"
["class"]=>
string(6) "DbConn"
["object"]=>
object(DbConn)#30 (2) {
["db_conn"]=>
resource(108) of type (mysql link persistent)
["db_name"]=>
string(7) "docking"
}
["type"]=>
string(2) "->"
["args"]=>
array(1) {
[0]=>
&string(51) "update DBNAME.thread set views=views+1 where id=456"
}
}
[1]=>
array(7) {
["file"]=>
string(48) "/boinc/projects/docking/html_v2/inc/forum_db.inc"
["line"]=>
int(60)
["function"]=>
string(6) "update"
["class"]=>
string(6) "DbConn"
["object"]=>
object(DbConn)#30 (2) {
["db_conn"]=>
resource(108) of type (mysql link persistent)
["db_name"]=>
string(7) "docking"
}
["type"]=>
string(2) "->"
["args"]=>
array(3) {
[0]=>
object(BoincThread)#3 (16) {
["id"]=>
string(3) "456"
["forum"]=>
string(1) "2"
["owner"]=>
string(5) "12091"
["status"]=>
string(1) "0"
["title"]=>
string(27) "Bug Report - Random Reboots"
["timestamp"]=>
string(10) "1259044026"
["views"]=>
string(3) "432"
["replies"]=>
string(2) "24"
["activity"]=>
string(19) "2.1243102642813e-81"
["sufferers"]=>
string(1) "0"
["score"]=>
string(1) "0"
["votes"]=>
string(1) "0"
["create_time"]=>
string(10) "1249748056"
["hidden"]=>
string(1) "0"
["sticky"]=>
string(1) "0"
["locked"]=>
string(1) "0"
}
[1]=>
&string(6) "thread"
[2]=>
&string(13) "views=views+1"
}
}
[2]=>
array(7) {
["file"]=>
string(63) "/boinc/projects/docking/html_v2/user/community/forum/thread.php"
["line"]=>
int(184)
["function"]=>
string(6) "update"
["class"]=>
string(11) "BoincThread"
["object"]=>
object(BoincThread)#3 (16) {
["id"]=>
string(3) "456"
["forum"]=>
string(1) "2"
["owner"]=>
string(5) "12091"
["status"]=>
string(1) "0"
["title"]=>
string(27) "Bug Report - Random Reboots"
["timestamp"]=>
string(10) "1259044026"
["views"]=>
string(3) "432"
["replies"]=>
string(2) "24"
["activity"]=>
string(19) "2.1243102642813e-81"
["sufferers"]=>
string(1) "0"
["score"]=>
string(1) "0"
["votes"]=>
string(1) "0"
["create_time"]=>
string(10) "1249748056"
["hidden"]=>
string(1) "0"
["sticky"]=>
string(1) "0"
["locked"]=>
string(1) "0"
}
["type"]=>
string(2) "->"
["args"]=>
array(1) {
[0]=>
&string(13) "views=views+1"
}
}
}
query: update docking.thread set views=views+1 where id=456