Scan Triggers Motherboard Alarm

[Tad Ghostal]

Abit AW8-MAX, and Pentium D830.

I have no idea where to start with the troubleshooting. The first time this ever happened is 20 minutes ago after installing squeezecenter (have had slimserver for a couple of years on the same machine) while it was running the scan.

Not knowing it was related to squeezecenter, I opened uguru to check all the system vitals and there was nothing wrong anywhere. All the temps were a good 20C lower than the upper threshold, no issues with the voltage, nothing. Stumped, I was searching the Abit forums for anything that might provide a clue, and the alarm randomly stopped.

There were 10 open and running programs, so it wasn't clear what had caused the alarm to trigger, or to shut down. After a few more minutes of checking and double-checking the machine was OK, I dropped the issue, ripped a couple of discs, and then decided to re-scan the library.

Within 30 seconds, the motherboard alarm went off. It dawned on me that there may be a relationship, and aborted the scan. The alarm stopped. To confirm, I started the scan and the symptom returned. I aborted the scan again, and the alarm stopped.

Just to be sure, I turned off the machine, gave it a few minutes to cool off, and then re-started it. Opening just one tab in Firefox, with squeezecenter opened, I started the re-scan. The motherboard alarm went off again. And it stays on the entire time during the scan.

Weird.

Does anybody have a clue as to why this may be happening?

[radish]

I'm assuming you're referring to a temperature alarm? I'm guessing it's CPU load related. Download cpuburn (or something equivalent for your OS) and try that. It may well be that your CPU cooling is insufficient when running at 100%.

[Tad Ghostal]

I'm assuming you're referring to a temperature alarm? I'm guessing it's CPU load related. Download cpuburn (or something equivalent for your OS) and try that. It may well be that your CPU cooling is insufficient when running at 100%.

Right, that would be the natural thing to check! And I did, but that wasn't the problem. I checked both the CPU load and the temp while the alarm was active. CPU usage was in the mid 40% range, and CPU temp was at 48.0C. The limit on the CPU is 78.0C. Abit's utility called uguru shows real time temps for CPU, system, and all the memory slots as well as status of the cooling fans--rpms, OK/Warning, mode, etc. Everything was and remains normal if not very low. Across the board, actual temps were no more than 60% of their high limit (high limit being the trigger for the alarm).

Again, strange. Given that it was the motherboard alarm, it seems most likely that it would in fact be hardware related. But is there *any* chance it could be software related?

I ask only because its a custom box, highly overbuilt for how I use it, and the monitoring/reporting software is showing everything operating well within conservative limits. No strange sounds, no difference in perceived heat or performance, and the only time the alarm goes off is during the scan.

But again, the scan uses a fraction of the CPU and less than 300k of 4gb ram.

[Tad Ghostal]

Opened the box yesterday to give everything a thorough once over, and it's grand. All the fans are working, the temps are low, and there is no reason for the alarm.

It is something about squeezecenter.

Since its irritating as hell to hear that alarm go off every time new music is added, the version is going to get rolled back to the latest version of slimserver.

Assuming I can find it.

[hball]

Did you ever figure out what this was about? I am having the same problem with my brand new Duet. I was not computer savvy enough to realize what was going on, I just knew that my PC was making a very loud beeping noise when I tried to scan my music library. I called Logitech customer support so they could hear it, but they had no answers for me.

For me, the alarm went off when the SqueezeCenter was scanning my playlists. I deactivated that feature (no file listed for playlists), and the alarm problem stopped.

My new problem is that the library scan will not run all the way through. It scans the directory, but seems to stall on the next step (Merge Various Artists). The clock keeps running, but the process doesn't finish.

Any ideas?

[Phil Leigh]

Did you ever figure out what this was about? I am having the same problem with my brand new Duet. I was not computer savvy enough to realize what was going on, I just knew that my PC was making a very loud beeping noise when I tried to scan my music library. I called Logitech customer support so they could hear it, but they had no answers for me.

For me, the alarm went off when the SqueezeCenter was scanning my playlists. I deactivated that feature (no file listed for playlists), and the alarm problem stopped.

My new problem is that the library scan will not run all the way through. It scans the directory, but seems to stall on the next step (Merge Various Artists). The clock keeps running, but the process doesn't finish.

Any ideas?

try temporarily disabling any anti-virus software...

[hball]

Thanks, Phil. I found another thread that recommended setting McAfee to ignore .myi and .myd files. This seemed to do the trick. I now can complete a scan. Unfortunately, the problem I hoped to solve by getting through a full scan has not been solved.

Certain albums (maybe 10% of my collection) will show up in the library, but not play. They are .wma files, not encoded. Any suggestions on this one?

[Phil Leigh]

Thanks, Phil. I found another thread that recommended setting McAfee to ignore .myi and .myd files. This seemed to do the trick. I now can complete a scan. Unfortunately, the problem I hoped to solve by getting through a full scan has not been solved.

Certain albums (maybe 10% of my collection) will show up in the library, but not play. They are .wma files, not encoded. Any suggestions on this one?

How were they created? - did you use Windows Media Player? They may have DRM on them in which case SC won't play them but WMP will.

[davesax36]

this alarm happened to me tonight, too. strange. I've never had that happen from anything before (i didn't know what it was until I read this thread)

any ideas about what's doing it?