Jump to content

Call traces error and memory error


Dr_Pippin

Recommended Posts

My unRAID's log showed memory issues 3 days ago, so I powered down my server, removed every RAM module (8x4GB), cleaned all the contacts with rubbing alcohol, and reseated them.  Now I received the call traces error this morning:

 

Quote

 

Your server has issued one or more call traces. This could be caused by a Kernel Issue, Bad Memory, etc. You should post your diagnostics and ask for assistance on the unRaid forums

 

I've included two diagnostic logs - one from February 8th when I had the memory issues, and one from February 11th when I had the call traces error

 

Call traces error log:

tower-diagnostics-20180211-1109.zip

 

Memory error log:

tower-diagnostics-20180208-1157.zip

 

Screenshot of the memory errors from 3 days ago (February 8th):

Memory errors.PNG

Link to comment

Almost identical error from my post (link below).  Seems odd that out of 16 sticks of RAM we're getting the same error on the same DIMM.  

 

Feb  6 18:03:48 someflix-unraid kernel: mce: [Hardware Error]: Machine check events logged
Feb  6 18:03:48 someflix-unraid kernel: EDAC sbridge MC1: HANDLING MCE MEMORY ERROR
Feb  6 18:03:48 someflix-unraid kernel: EDAC sbridge MC1: CPU 10: Machine Check Event: 0 Bank 9: 8c000047000800c0
Feb  6 18:03:48 someflix-unraid kernel: EDAC sbridge MC1: TSC 19b588d990bfb 
Feb  6 18:03:48 someflix-unraid kernel: EDAC sbridge MC1: ADDR 98932a000 
Feb  6 18:03:48 someflix-unraid kernel: EDAC sbridge MC1: MISC 1221080008000e8c 
Feb  6 18:03:48 someflix-unraid kernel: EDAC sbridge MC1: PROCESSOR 0:306e4 TIME 1517961828 SOCKET 1 APIC 20
Feb  6 18:03:48 someflix-unraid kernel: EDAC MC1: 1 CE memory scrubbing error on CPU_SrcID#1_Ha#0_Chan#0_DIMM#1 (channel:0 slot:1 page:0x98932a offset:0x0 grain:32 syndrome:0x0 -  area:DRAM err_code:0008:00c0 socket:1 ha:0 channel_mask:1 rank:4)

 

 

Link to comment

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...