"Could not create java virtual machine"

[zenongreat]

Can't launch 3DMark because it says this. I already have the _JAVA_OPTIONS and a maximum and minimum allocated memory size to the heap along with both 64-bit java and 32-bit java installed...

What can I do to fix this? I might have to refund if I can't get it started :(

[UL_Jarnis]

Can you just try getting rid of your JAVA_OPTIONS env variable. 3DMark does not require such a thing. It has its own virtual machine included. Normal windows install + any normal install of standalone Java has no effect on 3DMark, so whatever your system has beyond that is the culprit.

[FNARGUNNER]

Originally posted by UL_Jarnis:

Can you just try getting rid of your JAVA_OPTIONS env variable. 3DMark does not require such a thing. It has its own virtual machine included. Normal windows install + any normal install of standalone Java has no effect on 3DMark, so whatever your system has beyond that is the culprit.

I am having this issue as well. I have a fresh installation of Windows 10 and am receiving the same Could not create java virtual machine. error. I attempted to use the --trace launch parameter, but it will not create any files inside of the Documents folder. Any ideas?

[UL_Jarnis]

Couple of potential reasons...

1. your installation somehow did not properly do the latest update, so there are extra files in the jre folder under 3DMark folder. You could try deleting the jre folder under 3DMark and then re-verifying the files from Steam to ensure they are correct.

2. Your system has a version of Asus Sonic Radar 3 installed that breaks 3DMark. If this is the case, try removing it.

3. Your system somehow blocks 3DMark from writing to Documents/3DMark/ folder. One way might be that Windows Defender "anti tamper" is set to block apps from writing there.

4. 3DMark cannot create or write to C:\ProgramData\UL\ folder (under normal circumstances in Windows 10, applications can always write to ProgramData (which is by default a hidden folder)

If UI never starts, 3dmark.log would not exist anyway but --trace should add 3dmark-native.log into Documents/3DMark/ no matter what.

[FNARGUNNER]

Originally posted by UL_Jarnis:

Couple of potential reasons...

1. your installation somehow did not properly do the latest update, so there are extra files in the jre folder under 3DMark folder. You could try deleting the jre folder under 3DMark and then re-verifying the files from Steam to ensure they are correct.

2. Your system has a version of Asus Sonic Radar 3 installed that breaks 3DMark. If this is the case, try removing it.

3. Your system somehow blocks 3DMark from writing to Documents/3DMark/ folder. One way might be that Windows Defender "anti tamper" is set to block apps from writing there.

4. 3DMark cannot create or write to C:\ProgramData\UL\ folder (under normal circumstances in Windows 10, applications can always write to ProgramData (which is by default a hidden folder)

Note that using --trace requires you to start 3DMark with "force 64bit" option on the Steam version, otherwise no trace log is created. If UI never starts, 3dmark.log would not exist anyway but --trace should add 3dmark-native.log into Documents/3DMark/ no matter what.

Perfect, this solved it! Once I disable Windows Defender "anti-tamper" and deleted the jre folders, that allowed it to start with no errors. I greatly appreciate the SUPER quick reply. You've earned yourself a positive review! Thank you!

[Lasse Eindryngen]

Originally posted by UL_Jarnis:

Couple of potential reasons...

1. your installation somehow did not properly do the latest update, so there are extra files in the jre folder under 3DMark folder. You could try deleting the jre folder under 3DMark and then re-verifying the files from Steam to ensure they are correct.

I had the same issue since I replaced my Gpu and updated to the newest Nvidia Driver.
Uninstalling 3DMark and downloading/reinstalling didnt work for me,
But the first point you mentioned woprked just fine for me
Thank you very much!

[Zac Congo]

I've tried all of the steps and still the same.

I even tried to copy in a fresh jre folder from my java install. Still the same thing.

Seems to also happen with the 3DMark demo.

Running another app that uses java, ProjectZomboid, works just fine. :-/

Checking C:\ProgramData, the only folder in there is an empty 'tmp' folder in:
C:\ProgramData\UL\3DMark\tmp

Checking Documents, there is no 3DMark folder.
I do have a custom path to my Documents, going to D: drive instead of C:

[UL_Jarnis]

Don't try to replace jre contents with something else. We no longer use Oracle JVM so that can't work. Delete the folder again and revalidate files from Steam.

Try deleting UL folder under ProgramData to ensure there is no file permission issues there. Documents folder should not matter here yet since it never gets to a point where it would try to write there. You can try adding launch option in steam for 3DMark: --trace and then starting using Force 64bit. This should create 3dmark-native.log in Documents/3DMark/

If the folder still is missing and there is no log file, then it suggests 3DMark cannot write to Documents folder. Is Windows Anti-Tamper enabled?

[Zac Congo]

Thanks for getting back to me on this.

I've deleted and re-verified installation.

Deleted C:\ProgramData\UL folder. Before it dies, running again re-creates the folders:
UL
UL\3DMark
UL\3DMark\tmp

Added --trace to the launch options via RMB -> Properties -> Set Launch Options.

No 3DMark folder appears in my Documents at all.

If I open 'Tamper Protection' from the Windows Start menu, it launches the Windows Security window that shows
'Page Not Available'
'Your IT administrator has limited access to some areas of this app, and the item
you tried to access is not available. Contact IT helpdesk for more information.'

Double checked my windows account, I am the only user, and an Administrator.

Whatever the tamper protection options are, my Windows appears to either not have it, or is being coy about it.

I have Windows10 Home.


Hrmmm. Are there any launch options I can set that can give the vm some more logging options?
Currently it's just a blanket:

---------------------------
Java Virtual Machine Launcher
---------------------------
Error: Could not create the Java Virtual Machine.
Error: A fatal exception has occurred. Program will exit.
---------------------------
OK
---------------------------

[UL_Jarnis]

If no 3DMark folder appears in Documents and tamper protection feature claims its administered by IT administrator, that suggests your Windows 10 configuration is unusual.

Does anything change if you manually create a folder "3DMark" in your Documents folder?

[Zac Congo]

That did it! Manually created the folder "3DMark" in my Documents folder and it started up just fine.

[UL_Jarnis]

Very strange that 3DMark could not create that folder itself. Something odd with the folder permissions of the Documents folder, but if this sorts it out, guess that is fine.

[JohannZA]

Originally posted by UL_Jarnis:

Very strange that 3DMark could not create that folder itself. Something odd with the folder permissions of the Documents folder, but if this sorts it out, guess that is fine.

I've tested three different machines. 3DMark is now broken on all three. I've also tried EVERYTHING suggested in this thread (up to this point). Nothing has helped.

Two machines are AM4-based. One machine uses socket AM3+. All three are running completely normal Windows 64 Pro. One is a fresh Windows install.

[UL_Jarnis]

Originally posted by JohannZA:

Originally posted by UL_Jarnis:

Very strange that 3DMark could not create that folder itself. Something odd with the folder permissions of the Documents folder, but if this sorts it out, guess that is fine.

I've tested three different machines. 3DMark is now broken on all three. I've also tried EVERYTHING suggested in this thread (up to this point). Nothing has helped.

Two machines are AM4-based. One machine uses socket AM3+. All three are running completely normal Windows 64 Pro. One is a fresh Windows install.

Can you be more specific how is it failing for you and can you supply trace logs (see above for instructions)?

[JohannZA]

Originally posted by UL_Jarnis:

Originally posted by JohannZA:

I've tested three different machines. 3DMark is now broken on all three. I've also tried EVERYTHING suggested in this thread (up to this point). Nothing has helped.

Two machines are AM4-based. One machine uses socket AM3+. All three are running completely normal Windows 64 Pro. One is a fresh Windows install.

Can you be more specific how is it failing for you and can you supply trace logs (see above for instructions)?

I checked a fourth machine today (socket FM2, Win 64 Pro). Same problem. 3DMark doesn't start. Then the following error messages appear:

Error: Could not create the Java Virtual Machine.
Error: A fatal exception has occurred. Program will exit.

I believe this is the same problem everyone else in this thread is having/had.

The following log was generated on my AM4 machine a couple of minutes ago.

0.000000 looking for earlier pid 2680
0.078000 starting 3DMark with arguments "C:\Program Files (x86)\Steam\steamapps\common\3DMark\bin\x64\3DMark.exe" --trace
0.078000 launching server with splash images/splash_3DMark_100.png
3.843000 promise<pair<wstring, int>> port_promise;
3.843000 p->on_stdout
3.843000 p->on_stderr(
3.890000 process launch succeeded
3.890000 port_future.wait();
4.047000 BOM not detected
4.047000 READ MESSAGE:
4.047000 <JAVA_HOME>/lib/ext exists, extensions mechanism no longer supported; Use -classpath instead.
4.047000 (std-out) <JAVA_HOME>/lib/ext exists, extensions mechanism no longer supported; Use -classpath instead.
35.217999 (jre\bin\javaw.exe (stderr)) reading pipe ended
35.217999 port_future.get();
35.217999 server_info.second
35.217999 (jre\bin\javaw.exe (stdout)) reading pipe ended
35.217999 stream ended
35.217999 failed to start server process, ui launch cancelled
0.000000 looking for earlier pid 2680
0.078000 starting 3DMark with arguments "C:\Program Files (x86)\Steam\steamapps\common\3DMark\bin\x64\3DMark.exe" --trace
0.078000 launching server with splash images/splash_3DMark_100.png
3.562000 promise<pair<wstring, int>> port_promise;
3.562000 p->on_stdout
3.562000 p->on_stderr(
3.578000 process launch succeeded
3.578000 port_future.wait();
3.640000 BOM not detected
3.640000 READ MESSAGE:
3.640000 <JAVA_HOME>/lib/ext exists, extensions mechanism no longer supported; Use -classpath instead.
3.640000 (std-out) <JAVA_HOME>/lib/ext exists, extensions mechanism no longer supported; Use -classpath instead.
4.750000 (jre\bin\javaw.exe (stdout)) reading pipe ended
4.750000 (jre\bin\javaw.exe (stderr)) reading pipe ended
4.750000 stream ended
4.750000 port_future.get();
4.750000 server_info.second
4.750000 failed to start server process, ui launch cancelled

[UL_Jarnis]

And to be sure, you have tried deleting jre folder under 3DMark install folder and then re-validation files from steam?

Also does your system have any Java-related env variables set in Windows?

3.640000 (std-out) <JAVA_HOME>/lib/ext exists, extensions mechanism no longer supported; Use -classpath instead.

..is a curious error which makes me think something in your system is making JAVA_HOME to point to a wrong place. After the latest 2.11 update, there is no "ext" folder under "lib" folder in 3DMark/jre any more (we changed away from using Oracle Java and use OpenJDK now) and if your 3DMark/jre/lib/ folder has ext folder in it that would suggests there are leftover files or the update otherwise is messed up.