[griebel]

I tried the WD SSD drive, but like with the MX500 drive, the BM5 crashes about once a week and I have to do a mains reset to make it work again.

Has anyone experienced this issue when having replaced the original HDD by an SSD? If yes how can it be solved? Thanks

[Rendboell]

Hello griebel,

My system runs very smooth without any crashes since installing on an WD Blue SSD with correct alignment for SSD drives. It’s up and running in 2 seconds from standby and the wheel have no hiccups searching music. Only when turning the wheel very fast searching the 30.000 radio stations it has small hiccups for a couple of seconds, but is fast back on track.

For a couple of weeks I had BM5 installed on an old Samsung SSD without correct alignment for SSD drives and had a few crashes. For correct alignment see my guides in the BM5 ServiceTool download.

I have attached some of the updated guides here and included all the updated guides in the download:

https://1drv.ms/u/s!AvyICKrRk1dflLEkQs3K36JxF2p_EQ

Did you make at ‘clean’ clone installation or make a clone the old system? I recommend to make a clean installation. Backup your music to from the network drive of BM5 on another computer.

It could be a sign of the BM5 motherboard getting old (have been too hot) and need repair from an electronics or computer service.

Most of the times, it is the capacitors around the processor that are out of specs. You could try to replace these with new Panasonic:

1500uF 10V 105 Low ESR 30mOhm FR Panasonic 8×20

https://www.ebay.com/itm/142049643235

Kind regards,

Jens

[Luc]

griebel wrote:

I tried the WD SSD drive, but like with the MX500 drive, the BM5 crashes about once a week and I have to do a mains reset to make it work again. Has anyone experienced this issue when having replaced the original HDD by an SSD? If yes how can it be solved? Thanks

Does it crash during operation? Or do you find it unresponsive with a blinking red light or …?
Is this completely new since the switch – did you never experience this before with the HDD?

In my case this unresponsiveness is related to failed automatic reboots that are scheduled on a weekly basis in the standard setup. The reason for the reboot failures is not 100% clear, it might be related to having connected USB devices that are not fully compatible with the old Windows XP system? (see also this post https://beoworld.dev.idslogic.net/forums/topic/beosound-5-wont-startup-anymore/#post-30834).

My solution has been to inhibit these (useless) weekly reboots via the registry settings => since then my BM5 doesn’t weekly reboot anymore (or only once a month…) and thus hasn’t ‘crashed’ anymore either ?

[griebel]

I never experienced this problem with the original HDD. Can’t tell when it happens exactly; seems random, but it’s about once a week or so. Need to check the led on the BM5 when it crashes.

There is a USB hub connected to the BM5. OK I will remove it and see.

I did a clean installation and just copied the music. Will see if the alignment can fix the problem.

The motherboard is not the cause; it was replaced recently for the third time since I have an SSD drive. The crashes occurred with the 3 motherboards.

[Rendboell]

I have tried SSD alignment after installation with no success. After alignment BM5 would not restart. I don’t know why, but I could only make alignment working by doing a clean installation with Hirens Boot CD and Norton Ghost to load the ServiceTool.

[Luc]

griebel wrote:

I never experienced this problem with the original HDD. Can’t tell when it happens exactly; seems random, but it’s about once a week or so. Need to check the led on the BM5 when it crashes. There is a USB hub connected to the BM5. OK I will remove it and see. I did a clean installation and just copied the music. Will see if the alignment can fix the problem. The motherboard is not the cause; it was replaced recently for the third time since I have an SSD drive. The crashes occurred with the 3 motherboards.

In my opinion your problem is related with the hub you have had connected. Just disconnecting it doesn’t guarantee to solve the issue. You can check in your Device Manager if an ‘unknown USB device’ still appears – from time to time.

Such a device can randomly appear and disappear and I think this can make the startup fail. You can permanently remove it via a Recovery (fresh reinstall) without connecting the hub (or other potentially suspect USB devices) anymore afterwards of course.

Your BM5 normally restarts once a week – you can check when the next restart will happen in your BM-Share/Log/RebootHandler_0.log file. You can adapt this reboot frequency/time in your RebootDay/RebootTime values in the registry. For me it was originally every Monday (day 1) at 5am (see below)

I changed RebootDay to 30 and RebootTime to 1400 so now my automatic reboots only happen every 30 days at 2pm.

[griebel]

The problem seems to be more serious I thought. Since today, the BM5 crashes about every 5 min. Both the motherboard and the hard drive were replaced. I’m a bit clueless now…

[Rendboell]

Hello griebel,

I am sorry to hear you have such big troubles.

I have had similar crashes when the beomaster did not install correctly. Did you let the installation finish with two restarts and startup of the beomaster? Could it be a faulty motherboard? Did you allign to SSD after installation, which wiil not work? Did you reset / secure errase the SSD to factory default? Check versions and serial number of bios, motherboard og SSD with ServiceTool.

Kind regards,

Jens

[Luc]

griebel wrote:

The problem seems to be more serious I thought. Since today, the BM5 crashes about every 5 min. Both the motherboard and the hard drive were replaced. I’m a bit clueless now…

I would connect (only) a (sufficiently ‘old’) keyboard and go immediately to Recovery after the restart. It should return to normal operation after that?

[Author]

Posts