HDX 4500 Reboot during Video Call / ERROR, bad module ptr 0x111ac968

[Anonymous]

Hi Community,

i have searched the forum for unknown reboots during call, but there was no Solution given, other than call polycom support. My device is fairly old, and does not have an active polycom support contract.

Did anyone in this community was ever able to solve this rebooting issue?

HDX 4500

HW-Version A

Release - 3.1.12-54021

Multipoint license.

From the log:

Spoiler

2018-03-16 12:26:13 DEBUG avc: pc[0]: Pending[0]: VideoRouteStateUpdate: Updating vout1
2018-03-16 12:26:13 DEBUG avc: pc[0]: uimsg: [A1ca1: 20000 screenlayoutnotify mon mon1 cp 100]
2018-03-16 12:26:13 DEBUG avc: pc[0]: appcom: NC_COMMAND_STR, MsgSendCmd returns 0
2018-03-16 12:26:13 DEBUG avc: pc[0]: uimsg: [A1ca2: 20000 videoborder set hs01 all 67 166 91]
2018-03-16 12:26:13 DEBUG avc: pc[0]: appcom: NC_COMMAND_STR, MsgSendCmd returns 0
2018-03-16 12:26:13 DEBUG avc: pc[0]: uimsg: [A1ca3: 20000 videoborder set hs01 vinp 152 72 160]
2018-03-16 12:26:13 DEBUG avc: pc[0]: appcom: NC_COMMAND_STR, MsgSendCmd returns 0
2018-03-16 12:26:13 DEBUG avc: pc[0]: ChainCtrl[0]: FindVideoChain: Looking for hs01, role unknown, spec unknown
2018-03-16 12:26:17 INFO avc: last message repeated 1 times
2018-03-16 12:26:17 INFO avc: pc[0]: RTPRxChan[0]: (AudioRx) sending empty UDP Keep Alive
2018-03-16 12:26:18 INFO avc: pc[0]: RTPRxChan[2]: (FECCRx) sending empty UDP Keep Alive
2018-03-16 12:26:18 WARNING avc: pc[0]: RTPRxChan[0]: (AudioRx) error receiving RTP packet. Error No. 0
2018-03-16 12:26:18 WARNING avc: pc[0]: RTPRxChan[2]: (FECCRx) error receiving RTP packet. Error No. 0
2018-03-16 12:26:19 DEBUG avc: pc[0]: ERROR, bad module ptr 0x111ac968
2018-03-16 12:26:20 DEBUG avc: pc[0]: in assert 0
2018-03-16 12:26:20 CRITICAL avc: pc[0]: assert: ../../../src/Common/framework/proxy.c:1605: ProxyReturnBufServer: Assertion `0' failed.
2018-03-16 12:26:20 CRITICAL avc: Caught assert (SIGABRT).  Exiting.
2018-03-16 12:26:20 DEBUG avc: pc[0]: signalLogWriterThread received signal 6
2018-03-16 12:26:20 DEBUG avc: tm[1]: Audio: no speaker
2018-03-16 12:26:28 INFO watchdogd: proc 0 not responding 2
2018-03-16 12:26:29 INFO watchdogd: proc 0 not responding 1
2018-03-16 12:26:35 CRITICAL watchdogd: proc 0 not responding, sync and reboot

is it possible, that there is a faulty memory chip in the device?

Thanks in advance and best regards,

Markus