View Full Version : Stability

2005-01-11, 13:19
How is the box connected, wireless or hard wired (what is the complete
network topology from the server to the Squeezebox)? What other processes
are running on the server? How much RAM does the server have and does the
amount of available memory decrease the longer the Slim software is running?

Are there any messages in the windows event viewer about the server


From: discuss-bounces (AT) lists (DOT) slimdevices.com
[mailto:discuss-bounces (AT) lists (DOT) slimdevices.com] On Behalf Of Ralph Edington
Sent: Tuesday, January 11, 2005 1:11 PM
To: Slim Devices Discussion
Subject: [slim] Stability

Since I got my first Squeezebox about a week ago, I've been trying to
"stress test" its stability and reliability. I've been doing things like
leaving a radio station or playlist playing all night. So far, the results
are not good. I don't think it's made it through a single night.

Night before last, the Squeezebox went to the dreaded "black screen of
death". Upon checking my server (Windows, slim 5.4.1, hardwired to SBox),
the slimserver process was running away with the CPU, and I had to manually
"kill" the slim.exe process -- it wouldn't shut down normally.

This morning, after awaking to the BSOD again, the server looked fine, but I
restarted it anyway. No good, SBox won't communicate with the server.
Manually shut down slim.exe, restarted it -- SBox still can't talk to the
server. The only thing that worked was unplugging power from the SBox and
running through the setup again, which finally brought it back to life.
That particular problem has happened at least twice in one week, possibly
more, I can't remember.

So, I'm confused as to whether this might be a software, hardware or
firmware problem.

If this is a software problem, then I don't really care. I'm sure we'll all
be going through so many versions and builds that somewhere along the line
y'all will knock this problem out.

However, I'm concerned about the lockups that require a "hard reset" of the
SBox. That would seem to be a shortcoming in hardware or firmware, and a
more serious problem.

I'm open to suggestions. I'm trying to not just complain here. Any debug
things I should turn on and check out/send in? Should I keep a log of
failures and symptoms? Is this kind of thing happening to everyone? I'm
willing to do any troubleshooting or debugging that I can, in order to help
resolve these stability issues.

Any ideas?