Author

Topic: Logging for troubleshooting (Read 899 times)

full member
Activity: 210
Merit: 100
firstbits: 121vnq
June 09, 2011, 04:50:45 PM
#5
OC instability.

Sure it could have been fixed fiddling with the voltage, but an i5 is already overkill for what is essentially a mining machine and home file server/torrent machine/tor relay

full member
Activity: 154
Merit: 100
June 08, 2011, 04:48:37 PM
#4
thanks for tips.

was a processor overclock issue. figure i dont need the CPU overclocked right now anyway so just reverted to stock. GPUs have been running for 48 hrs without a problem, both overclocked about 15%

was it actual OC instability or CPU temp issues related to the OC?
full member
Activity: 210
Merit: 100
firstbits: 121vnq
June 08, 2011, 04:41:58 PM
#3
thanks for tips.

was a processor overclock issue. figure i dont need the CPU overclocked right now anyway so just reverted to stock. GPUs have been running for 48 hrs without a problem, both overclocked about 15%
full member
Activity: 154
Merit: 100
June 08, 2011, 04:38:12 PM
#2
check event viewer in computer management to start out. 

If you are getting bluescreens they will be reported there.

If it is something like a random lock or freeze that will be more difficult to pinpoint, but it often indicates a power or heat problem.  You can use realtemp to log temps, i think.
full member
Activity: 210
Merit: 100
firstbits: 121vnq
June 05, 2011, 01:55:27 PM
#1
I have a miner I have pieced together from CL parts. Seems somewhat stable so far, but occasionally restarts, locks up, or otherwise stops mining. It's running Windows 7 now, but will likely turn it into some flavor of linux over the next week. It's been a long long time since Ive poked around in the world of windoze. Anyone have good recommendations for logging tools I could use to find out what it crapping out and start trying to narrow down some causes? processor? GPU? heat? dog kicked out power cord? etc....

would like to at least get hardware stable under windows and be able to mine for a solid 24 hours at a time without any crapouts before I start trying to play with *nix drivers, etc
Jump to: