JCS server memory / core dump issue: ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%p referenced memory at 0x%p. The memory could not be %s
search cancel

JCS server memory / core dump issue: ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%p referenced memory at 0x%p. The memory could not be %s

book

Article ID: 263735

calendar_today

Updated On:

Products

CA Identity Suite

Issue/Introduction

The java process is crashing under heavy load.  It may be due to interference with other system processes like McAfee. Our tasks are getting stuck because of this.

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%p referenced memory at 0x%p. The memory could not be %s,

 

Cause

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%p referenced memory at 0x%p. The memory could not be %s.

We noticed in the Windows event logs that a VMware Update status always started at the time of the crash. 

The crash can occur with interference from malware, another imposing application, etc. So it seems feasible that the VMware update or backup applications we saw in the event viewer may be responsible.

Resolution

Resolve by addressing the offending application that causes the unexpected memory spike. If a regular software update or backup, for example, moving the time of the process to less memory intense time of day, or resolved in this case by simply increasing the amount of memory (RAM) on the server.