JVM is frequently crashing with a 0xc0000005 exception

Products

• Data Loss Prevention Network Monitor
• Data Loss Prevention
• Data Loss Prevention Core Package
• Data Loss Prevention Enforce
• Data Loss Prevention Enterprise Suite

Issue/Introduction

If the environment is having frequent restarts and the resulting JVM crashdumps (hs_err* files in Protect/bin) display an 0xc0000005 exception such as

Current thread (0x11f96c00):  JavaThread "Worker 3" daemon [_thread_in_native, id=8108, stack(0x12c20000,0x12c70000)]

siginfo: ExceptionCode=0xc0000005, reading address 0xfffffff8

  or 

Current thread (0x11b65400):  JavaThread "Worker 1" daemon [_thread_in_native, id=6392, stack(0x12c20000,0x12c70000)]

siginfo: ExceptionCode=0xc0000005, reading address 0x13feb003

Cause

0xc0000005 is often associated with Data Execution Prevention(DEP) , http://en.wikipedia.org/wiki/Data_Execution_Prevention)

Resolution

There may be several causes for this type of exception, but in most cases, this is related to enabled 

In that case you may want to turn off DEP to verify that the crashes no longer occur and then fine-tune the DEP exceptions in the environment.

How to turn DEP on or off can be found in http://technet.microsoft.com/en-us/library/cc700810.aspx 

Check if there are other programs/services running that monitor processes and potentially stop them (Symantec Endpoint or McAfee). In this case, disable them and try again and see if they cause the exception. You may see in their specific logs entries that would indicate if a Symantec DLP process has been stopped.