My Oracle Support Banner

SQL Developer crashes after startup with Fatal Exception log generated (Doc ID 1963960.1)

Last updated on AUGUST 04, 2018

Applies to:

Oracle SQL Developer - Version 4.0 and later
All Platforms


After a particular PC system was recovered due to video/monitor issues, SQL Developer consistently crashes and generates a hs_err_pidXXXX.log.  No Oracle Client is installed. 

"Problematic Frame" in hs_err_pidXXXX.log:

  # A fatal error has been detected by the Java Runtime Environment:
  # EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x00000000695703ee, pid=6904, tid=6172
  # JRE version: Java(TM) SE Runtime Environment (7.0_71-b14) (build 1.7.0_71-b14)
  # Java VM: Java HotSpot(TM) 64-Bit Server VM (24.71-b01 mixed mode windows-amd64 compressed oops)
  # Problematic frame:
  # C [atio6axx.dll+0xac03ee]
  # Failed to write core dump. Minidumps are not enabled by default on client versions of Windows
  # If you would like to submit a bug report, please visit:
  # The crash happened outside the Java Virtual Machine in native code.
  # See problematic frame for where to report the bug.

Note the DLL file referenced in the Problematic Frame line is "atio6axx.dll."  This is a non-Oracle DLL.



Monitor/video card replacement on the system and load of drivers required for the new device(s). 


To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document

This document is being delivered to you via Oracle Support's Rapid Visibility (RaV) process and therefore has not been subject to an independent technical review.
My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.