I have never had this problem with my system when running torrents or Steam downloads overnight, and I left it on with a CPU straining program last night to check the system wasn't simply unstable.
According to my bandwidth monitor, on both nights the download was running for 4-5 hours before it began slowly losing speed, dropping to half speed over about 20-30 minutes, and then completely dropping out.
The Windows system log records this at the same time the slow down began:
The browser has forced an election on network \Device\NetBT_Tcpip_{EF98F42F-9E4E-4064-896A-E4FB2100122B} because a master browser was stopped.
The Computer Browser service was successfully sent a stop control.
The reason specified was: 0x40030011 [Operating System: Network Connectivity (Planned)]
These three information messages were recorded within 10 seconds of each other after three hours of no entries.The Computer Browser service entered the stopped state.
The system then recorded a series of errors between 15 and 30 minutes after the slowdown began:
An I/O operation initiated by the Registry failed unrecoverably.The Registry could not flush hive (file): '\SystemRoot\System32\Config\SOFTWARE'.
An I/O operation initiated by the Registry failed unrecoverably.The Registry could not flush hive (file): ''.
An I/O operation initiated by the Registry failed unrecoverably.The Registry could not flush hive (file): '\SystemRoot\System32\Config\SOFTWARE'.
An I/O operation initiated by the Registry failed unrecoverably.The Registry could not flush hive (file): '\??\C:\Users\USERNAME\ntuser.dat'.
An I/O operation initiated by the Registry failed unrecoverably.The Registry could not flush hive (file): ''.
The second last error message coincided with the downloading stopping completely. The DNS service then started and stopped itself repeatedly until I rebooted the system.An I/O operation initiated by the Registry failed unrecoverably.The Registry could not flush hive (file): '\SystemRoot\System32\Config\SOFTWARE'.
I realise this is an odd problem and is probably being caused by an undiagnosable software/hardware glitch, but I thought I'd ask anyway. Any ideas what the problem could be?
Cheers
