Emby Server crashes once a day

[reyes136 2]

I'm not sure if this is the same problem as one of the other threads but my emby server started to crash with out of memory errors a while back. Around the same time emby switched to the image viewer. The error i get is:

 

Exception of type 'System.OutOfMemoryException' was thrown.
 

 

I attached the log.

 

I also have another windows pc on my network that has the emby win8.1 app running and it now crashes. It also causes the pc running the app to crash. When I check my windows logs it says that the app crashed causing the pc to crash. If I disable the app the system stays up.

 

I'm currently trying Version 3.0.5595.23245 to see if it helps but I also tried 3.0.55.88.1 and the 2 released before that. I dont have a large collection only about 300 movies and about 100 tv recordings.

 

Any help would be appreciated.

unhandled_07ae6c89-fd1f-4fcb-9976-8e938c36b723.txt

[AgileHumor 123]

http://emby.media/community/index.php?/topic/19476-emby-out-of-memory-errors/?hl=%2Bout+%2Bmemory+%2Berrors 

[reyes136 2]

Thanks for the link, I have a related problem and did a little testing for a couple days to verify. I run my main pc compressing videos surfing the internet and watching videos and running memory test with no issues. But as soon as I start editing movie tags and images using my web browser "chrome" connecting to my emby server. My computer crashes. with the following memory.dmp error. I know that this error points to a hardware issue but what I dont understand is why it only happens when I start editing and downloading cover art images in the emby win8.1 app or html webpage.

 

 

 

BUGCHECK_STR:  0x124_GenuineIntel

 

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

 

PROCESS_NAME:  System

 

CURRENT_IRQL:  f

 

ANALYSIS_VERSION: 6.3.9600.17298 (debuggers(dbg).141024-1500) amd64fre

 

STACK_TEXT:  

ffffd001`333d0df8 fffff801`181e6213 : 00000000`00000124 00000000`00000000 ffffe001`24759028 00000000`f2000040 : nt!KeBugCheckEx

ffffd001`333d0e00 fffff801`17be0f2d : 00000000`00000001 ffffe001`22486480 ffffe001`22486480 ffffe001`24759028 : hal!HalBugCheckSystem+0xcf

ffffd001`333d0e40 fffff801`181e66a0 : 00000000`00000728 00000000`00000003 ffffd001`333d1230 00000000`00000000 : nt!WheaReportHwError+0x22d

ffffd001`333d0ea0 fffff801`181e6a0d : ffffe001`00000010 ffffe001`22486480 ffffd001`333d1048 ffffe001`22486480 : hal!HalpMcaReportError+0x50

ffffd001`333d0ff0 fffff801`181e68f8 : ffffe001`22485d50 00000000`00000001 00000000`00000003 00000000`00000000 : hal!HalpMceHandlerCore+0xe1

ffffd001`333d1040 fffff801`181e6b42 : 00000000`00000008 00000000`00000001 00000000`00000000 00000000`00000000 : hal!HalpMceHandler+0xe4

ffffd001`333d1080 fffff801`181e6ccf : ffffe001`22485d50 ffffd001`333d12b0 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0xce

ffffd001`333d10b0 fffff801`17b767bb : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40

ffffd001`333d10e0 fffff801`17b76571 : 00000000`00000000 fffff801`17b764f2 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x7b

ffffd001`333d1220 fffff801`ba9a9214 : fffff801`ba9a81f7 ffffe001`248bbf90 00000000`00000000 ffffe001`24e3f000 : nt!KiMcheckAbort+0x171

ffffd001`333f18e8 fffff801`ba9a81f7 : ffffe001`248bbf90 00000000`00000000 ffffe001`24e3f000 ffffd001`333c7180 : intelppm!MWaitIdle+0x18

ffffd001`333f18f0 fffff801`17a59df8 : ffffd001`333c7180 ffffd001`333f1a00 ffffd001`333f1a20 00000049`b05db277 : intelppm!AcpiCStateIdleExecute+0x17

ffffd001`333f1920 fffff801`17a59856 : ffffd001`333c7180 ffffd001`333f1b4c ffffd001`333f1b50 ffffd001`333f1b58 : nt!PpmIdleExecuteTransition+0x3e8

ffffd001`333f1b10 fffff801`17b6f7bc : ffffd001`333c7180 ffffd001`333c7180 ffffd001`333d33c0 00000000`003b11be : nt!PoIdle+0x2f6

ffffd001`333f1c60 00000000`00000000 : ffffd001`333f2000 ffffd001`333ec000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x2c

 

 

STACK_COMMAND:  kb

 

FOLLOWUP_NAME:  MachineOwner

 

MODULE_NAME: GenuineIntel

 

IMAGE_NAME:  GenuineIntel

 

DEBUG_FLR_IMAGE_TIMESTAMP:  0

 

IMAGE_VERSION:  

 

FAILURE_BUCKET_ID:  0x124_GenuineIntel__UNKNOWN

 

BUCKET_ID:  0x124_GenuineIntel__UNKNOWN

 

ANALYSIS_SOURCE:  KM

 

FAILURE_ID_HASH_STRING:  km:0x124_genuineintel__unknown

 

FAILURE_ID_HASH:  {d4ff8356-accf-463b-abb8-12a20b1a031a}

 

Followup: MachineOwner

---------

[reyes136 2]

Well it seems that my crashing on my remote pc was due to my virus software (Kaspersky). After one of the crashes the Kasperky log poped up so I completely uninstalled the software package and installed Macfee and I havent seen a crash after hours of updating movie images.