Author Topic: Musicbee has stopped working  (Read 2146 times)

9ido

  • Full Member
  • ***
  • Posts: 201
I get Musicbee has stopped working a lot since the last release candidate before 3.1 final. It happens often when I am not around, the program is running but not playing. Before that point it almost never happened.

Steven

  • Administrator
  • Sr. Member
  • *****
  • Posts: 34346
if you are using WebRoot security software, it is removing MusicBeeXBox.dll so you will need to restore that file using WebRoot
otherwise check the windows system event viewer for details on why the MusicBee.exe process is stopping. I doubt i will be able to help

9ido

  • Full Member
  • ***
  • Posts: 201
Thank you for your reply, Steven.

First I decided to go back a couple of beta's, to a point that I am certain the issue did not occur. It still crashes. So as it turns out it's not the musicbee update.

I did lookup the event viewer, and found the following recent entry with Musicbee, also ntdll.dll seems to have something to do with it. Does it tell you anything useful? Is there anything that you or I can do to fix this?

Log Name:      Application
Source:        Application Error
Date:          21-Sep-17 14:21:35
Event ID:      1000
Task Category: (100)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      GDOPC
Description:
Faulting application name: MusicBee.exe, version: 3.1.6445.32424, time stamp: 0x599f0693
Faulting module name: ntdll.dll, version: 10.0.15063.608, time stamp: 0x802f667e
Exception code: 0xc0000005
Fault offset: 0x0005da74
Faulting process id: 0x25ac
Faulting application start time: 0x01d3325e38541902
Faulting application path: C:\Program Files (x86)\MusicBee\MusicBee.exe
Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll
Report Id: 2c8afc50-3180-4233-9470-2efb17b93f49
Faulting package full name:
Faulting package-relative application ID:

ps. I am not using webroot.

Steven

  • Administrator
  • Sr. Member
  • *****
  • Posts: 34346
i expect it will be some other software recently installed or updated.
you could google this: 0xc0000005 ntdll.dll
but there are many reasons/ solutions