Programmers learn & share
0 votes
141 views

Problem :

I am getting following java error

failed to write core dump. minidumps are not enabled by default on client versions of windows 10

by (6.9k points)   | 141 views

2 Answers

0 votes

Solution :

I can give you two solutions as following

1: Using jvmargs

One of the jvmargs was giving the error to me while starting the jetty ant task with jrebel args. So i removed the jvmargs arguments and just ran the  mvn jetty:run command with -javaagent keeping pointed to jrebel.jar and it simply worked for me.

2: Using .metadat

  1. One can close Eclipse.
  2. Delete the .metadata folder from your workspace directory.
  3. Now open Eclipse and import the projects from the workspace please do not copy these because they are already in it.
  4. It will also solve the issue
by (36.1k points)  
0 votes

Solution:

Create a Dump File

  1. Open the Minecraft startup device.

  2. Open Task Manager and go to Process for Windows 8/8.1 or Applications for 7.

  3. Right-click on Java(TM) Platform SE Binary or simply on your MC Launcher.

  4. find “Create Dump File” and click on it

  5. wait until the end and play Minecraft without screwing up

Updating Java to latest version.

You have a problem in native code. Updating Java will unlikely help in that situation.

Update Windows

This will only help if the native code that you use is updated through Windows Updates

Enable Mini-dumps through Advanced System Settings -- > Startup & Recovery -- > Settings -- > Choosing 'small memory dump'.

This setting is for kernel mode crashes (Blue Screen), not for application crashes (user mode). There is also a setting for application crashes (a Registry setting called LocalDumps) but it won't work for Java, since Java does its own exception handling.

To get crash dumps from Java 9 and above, use the following command line switch:

-XX:+CreateCoredumpOnCrash
On Java 8 and before, use the Windows specific command line
-XX:+CreateMinidumpOnCrash

This will give you more details on what happens at the time of the crash. It will still be an AccessViolation but you'll get the callstack etc. - if you have the knowledge of debugging it with WinDbg or similar.

Update Graphic Driver to latest from official producer's (Nvidia) website.

 

ago by (8k points)  
2,204 questions
2,608 answers
59 comments
241 users