Emby Server Crashing

[Borsk 450]

My Emby server is crashing completely and just freezing a few minutes after launching, centres around a runtime error but I'm having trouble figuring out the cause.  Any ideas would be a great help, thanx

embyserver.txt

[Carlo 4561]

Hi,

The log just stops without any indication of a problem.

What runtime error are you getting?
Do you see anything being logged in Windows event log?

When you say crashing, is this the computer itself?  Does it blue screen?

[Borsk 450]

9 minutes ago, Carlo said:

Hi,

The log just stops without any indication of a problem.

What runtime error are you getting?
Do you see anything being logged in Windows event log?

When you say crashing, is this the computer itself?  Does it blue screen?

The computer itself does not crash just Emby Server, so no blue screens or anything like that.

Here is a copy of the error from the Windows Event Viewer, hopefully this can point you in the right direction.

If you need more info feel free to ask

Emby error.rtf

Edited October 14, 2024 by Borsk

[Carlo 4561]

exit code c0000005" is an access violation error that can occur when the computer is unable to process the files and settings required to run a program. This error can be caused by: Faulty RAM, PC file errors, PC setting issues, and Invalid interfaces used for virtual desktops.

It could be a corrupted file in the .NET framework as well.
Here are some suggestions for solutions:

Use the system repair command to repair:

using the following commands (Please run the command prompt as administrator ("Win" logo key + "Q", type "cmd", select "Run as administrator") and type the following commands one by one.).

sfc /scannow

DISM /Online /Cleanup-Image /RestoreHealth

 

Let us know if this finds or fixes anything.

[Borsk 450]

3 hours ago, Carlo said:

exit code c0000005" is an access violation error that can occur when the computer is unable to process the files and settings required to run a program. This error can be caused by: Faulty RAM, PC file errors, PC setting issues, and Invalid interfaces used for virtual desktops.

It could be a corrupted file in the .NET framework as well.
Here are some suggestions for solutions:

Use the system repair command to repair:

using the following commands (Please run the command prompt as administrator ("Win" logo key + "Q", type "cmd", select "Run as administrator") and type the following commands one by one.).

sfc /scannow

DISM /Online /Cleanup-Image /RestoreHealth

 

Let us know if this finds or fixes anything.

I replaced/upgraded the RAM about a week, I have already done everything suggested before I made the post but if you or anyone else on these forums has any other ideas I will be happy to try them to hopefully prevent me from formatting and re-installing windows, because I have a sneaking suspicion that some files probably a corrupted .NET file(s) that can't be repaired so brainstorm for a couple more days and then its wipe and rebuild lol.

[Carlo 4561]

Here's a list of things you can try.

Emby Server
Install the latest version of Emby Server

Run CHKDSK Scan
Press Windows + S to go to Windows Search and type cmd, then run it as Administrator.
At the elevated command prompt run this

chkdsk /f /r C:

Change the C if needed to your first drive letter
Repeat this command for each hard drive (changing the letter each time)

Windows Updates
Press Windows + S to go to Windows Search and type check for updates
Open it then select Advanced Options
Turn on Receive updates for other Microsoft products
Select any optional updates if present under Additional options
Click the left arrow top right to go back to the main Windows Update page
Click Check for Updates
Install all updates if present
Reboot if prompted
After reboot repeat this process again to make sure all updates have been installed

Check RAM
Memory corruption is one of the primary reasons behind this error; hence, check the RAM. You can run the Windows Memory Diagnostic tool to test your RAM. This Windows built-in utility checks for issues with the RAM (if any). Follow the given steps to run this tool:

Open the Windows Memory Diagnostic tool through Windows Search.
Select the 'Restart now and check for problems. The system will initiate the test after reboot.
Once the scan is done, you'll see the scan results on the screen. If it shows several RAM issues and instructions on how to fix them, follow the instructions.

Scan PC for Malware
Press Windows + S to go to Windows Search and type Windows Security, then run it.
select Virus & threat protection
Scroll down and click the Scan options, under Quick Scan.
Select Microsoft Defender Offline scan, then click Scan now.
Once done, reboot your system and see further instructions to remove the virus (if found).

Run SFC Scan & DISSM
Press Windows + S to go to Windows Search, type cmd
Select the option to run as Administrator
Run the following at the elevated command prompt:

SFC/scannow

after that completes run

DISM /Online /Cleanup-Image /RestoreHealth

Update Device Drivers
Press Windows + X and select Device Manager
Expand the Disk Drives category, right-click on the driver. Now, from the available options, choose Update driver.
Select Search automatically for drivers
If a new driver version is available, download it and reboot your system.
Repeat this ion each hard drive if you have multiple

Repeat this process for Network Drivers

Repeat this process for Display Adapters
If you have and AMD or Nvidia Graphic card, run the update software installed on your computer or check the manufacture website for the latest driver.
If you updated any drivers reboot Windows
Try running Emby Server again to see if the Exception is gone
If not try turning off DEP (below)

Turn off Data Execution Prevention (DEP)
Press Windows + S to go to Windows Search, type cmd
Select the option to run as Administrator
Run the following at the elevated command prompt:

bcdedit.exe /set {current} nx OptIn

then run

bcdedit.exe /set {current} nx AlwaysOff

Reboot Windows again
Try running Emby Server again to see if the Exception is gone

 

If still throwing an exception we could try running the server in safe mode, but I think we can skip that and setup windows to create a dump file on a program excepting. We can use that to determine what was happening.

Carlo

[Luke 42079]

@Borskhas this helped?

[Borsk 450]

On 10/17/2024 at 4:20 PM, Carlo said:

Here's a list of things you can try.

Emby Server
Install the latest version of Emby Server

Run CHKDSK Scan
Press Windows + S to go to Windows Search and type cmd, then run it as Administrator.
At the elevated command prompt run this

chkdsk /f /r C:

Change the C if needed to your first drive letter
Repeat this command for each hard drive (changing the letter each time)

Windows Updates
Press Windows + S to go to Windows Search and type check for updates
Open it then select Advanced Options
Turn on Receive updates for other Microsoft products
Select any optional updates if present under Additional options
Click the left arrow top right to go back to the main Windows Update page
Click Check for Updates
Install all updates if present
Reboot if prompted
After reboot repeat this process again to make sure all updates have been installed

Check RAM
Memory corruption is one of the primary reasons behind this error; hence, check the RAM. You can run the Windows Memory Diagnostic tool to test your RAM. This Windows built-in utility checks for issues with the RAM (if any). Follow the given steps to run this tool:

Open the Windows Memory Diagnostic tool through Windows Search.
Select the 'Restart now and check for problems. The system will initiate the test after reboot.
Once the scan is done, you'll see the scan results on the screen. If it shows several RAM issues and instructions on how to fix them, follow the instructions.

Scan PC for Malware
Press Windows + S to go to Windows Search and type Windows Security, then run it.
select Virus & threat protection
Scroll down and click the Scan options, under Quick Scan.
Select Microsoft Defender Offline scan, then click Scan now.
Once done, reboot your system and see further instructions to remove the virus (if found).

Run SFC Scan & DISSM
Press Windows + S to go to Windows Search, type cmd
Select the option to run as Administrator
Run the following at the elevated command prompt:

SFC/scannow

after that completes run

DISM /Online /Cleanup-Image /RestoreHealth

Update Device Drivers
Press Windows + X and select Device Manager
Expand the Disk Drives category, right-click on the driver. Now, from the available options, choose Update driver.
Select Search automatically for drivers
If a new driver version is available, download it and reboot your system.
Repeat this ion each hard drive if you have multiple

Repeat this process for Network Drivers

Repeat this process for Display Adapters
If you have and AMD or Nvidia Graphic card, run the update software installed on your computer or check the manufacture website for the latest driver.
If you updated any drivers reboot Windows
Try running Emby Server again to see if the Exception is gone
If not try turning off DEP (below)

Turn off Data Execution Prevention (DEP)
Press Windows + S to go to Windows Search, type cmd
Select the option to run as Administrator
Run the following at the elevated command prompt:

bcdedit.exe /set {current} nx OptIn

then run

bcdedit.exe /set {current} nx AlwaysOff

Reboot Windows again
Try running Emby Server again to see if the Exception is gone

 

If still throwing an exception we could try running the server in safe mode, but I think we can skip that and setup windows to create a dump file on a program excepting. We can use that to determine what was happening.

Carlo

Unfortunately none of this was successful it is on to Re-installing Windows but Thank you for your help.

[Borsk 450]

7 hours ago, Luke said:

@Borskhas this helped?

Unfortunately no.

[Carlo 4561]

21 hours ago, Borsk said:

Unfortunately none of this was successful it is on to Re-installing Windows but Thank you for your help.

Dang, wish you hadn't skipped to that step as getting a debug log would have been useful to see exactly where the issue was.

[Borsk 450]

17 hours ago, Carlo said:

Dang, wish you hadn't skipped to that step as getting a debug log would have been useful to see exactly where the issue was.

next time mention it and I will lol

Edited October 20, 2024 by Borsk

[Luke 42079]

@Borsk has there been a next time?