I came back from holiday (vacation 😛) to find my machine had bluescreened whilst I was away.
I tried everything software wise and thought it must be a hardware problem, so I rebuilt the machine to eliminate the possibility of a contact problem somewhere. The problem is less evident (I think) - where the machine used to bluescreen as W2k logon screen was appearing I can now get into the OS.
The thing which gets me is that running the SETI client now causes the machine to bluescreen. I have run the machine for 48 hours without the seti client running (ie just my Seti Q and other small apps) without a problem. Every time I set the client to run, the machine will bluescreen within around 1.5 hours - occasionally more but by the time I get to the machine the next morning it has always bluescreened.
Thoughts:
This could be CPU load related, or memory related I think. Other occurances of bluescreens (although they are rare) are when I have a lot of operations going simultaniously - so could it be that intensive RAM access could trip a bluescreen?
Any ideas guys? I wouldnt mind being able to run Seti at say 50% CPU load to experiment, then upwards if that was successful.
CPU/mobo temps are not an issue I would imagine. Cheap CPU cooler, northbridge cooler and 2 x 80mm fans keep it alright (it has been running for about a year 24/7 with no problems apart from this, and it was fine throughout August where temps were highest.)
Help!!
I tried everything software wise and thought it must be a hardware problem, so I rebuilt the machine to eliminate the possibility of a contact problem somewhere. The problem is less evident (I think) - where the machine used to bluescreen as W2k logon screen was appearing I can now get into the OS.
The thing which gets me is that running the SETI client now causes the machine to bluescreen. I have run the machine for 48 hours without the seti client running (ie just my Seti Q and other small apps) without a problem. Every time I set the client to run, the machine will bluescreen within around 1.5 hours - occasionally more but by the time I get to the machine the next morning it has always bluescreened.
Thoughts:
This could be CPU load related, or memory related I think. Other occurances of bluescreens (although they are rare) are when I have a lot of operations going simultaniously - so could it be that intensive RAM access could trip a bluescreen?
Any ideas guys? I wouldnt mind being able to run Seti at say 50% CPU load to experiment, then upwards if that was successful.
CPU/mobo temps are not an issue I would imagine. Cheap CPU cooler, northbridge cooler and 2 x 80mm fans keep it alright (it has been running for about a year 24/7 with no problems apart from this, and it was fine throughout August where temps were highest.)
Help!!