PC Troubleshooting

From Pavlov VR Wiki
Jump to: navigation, search


I have an 11th gen Intel processor and Pavlov does not start for me. When I launch it Anti-cheat shows up then the game closes.

Does Pavlov Start then immediately end on Steam? Try this fix: Intel Gen 11 fix

(This issue and the 12th gen one below may be fixed as of the update on 22/12/2021. Need to see if others to confirm if they ever get the issue again on either CPU.)

I have a 12th gen Intel processor and Pavlov does not start for me. When I launch it Anti-cheat shows up then the game closes.

First you need to do the 11th gen Intel processor fix, then do the following:

Power-up system and enter system BIOS setup.
Enable switch Legacy Game Compatibility Mode to ON (one-time only) in BIOS.
Save BIOS setup changes and exit.
Boot to OS.
Toggle Keyboard Scroll Lock key ON.
Launch Pavlov.
Toggle Keyboard Scroll Lock key OFF after ending game title.

Note: Not all motherboard BIOS have this feature. If yours doesn't look for a bios update from manufacturer.

Verify integrity of game files (Can fix tons of random crash issues)

Got to your Steam Library. Right click Pavlov. Click Properties. Click Local Files. Click "Verify integrity of game files".

Update 26 Broke for me I crash at start with the Pavlov Crash reporter/I'm having strange game behavior/I'm getting strange game performance/game hangs on dark screen (not 11gen Intel processor)

First Delete your Pavlov folder in: %LocalAppdata%

Locate your local appdata folder on your windows installation: %localappdata%/Pavlov/

1. Press start 2. Type "%localappdata%" without quotes and press enter 3. Locate Pavlov folder and delete it.

If this doesn't help, try clearing the Steam cache: Steam>settings>downloads>clear download cache

I'm getting an error saying the procedure entry point could not be located in the Dynamic Link Libary (v8_libplatform.dll)

Find your Pavlov game installation folder and locate this directory, typically: C:\Program Files (x86)\Steam\steamapps\common\PavlovVR\Pavlov\Plugins

Note: If you have Steam installed at another directory, find wherever you installed Steam and browse to: SteamLibrary\steamapps\common\PavlovVR\Pavlov\Plugins

Find the Runtime folder, create a backup of it and move it somewhere else (Optional), and and delete it. Restart Pavlov.'

I can't play community maps| unable to move and see players crouched with everything frozen for about 30 seconds and then get disconnected with an "authentication timeout"

Change your startup map to the main menu, not shooting range.

Steam is stuck in an update loop

Please make sure you have a lot of free space on your installation drive to let steam unpack and verify the update. You can also try restarting your computer. If you have to free up space, a restart is required because Steam is having trouble recognizing freed up space.

Unable to play online, offline works fine.

Check the windows firewall to make sure Pavlov VR is allowed. Check any other 3rd party antivirus software or firewalls that may be blocking Pavlov from connection to the internet.

Vibrations on controllers are causes tracking lag (Rift/Rift S)

Try unplugging and plugging in the USB cable for the headset into a different port.

With the exception of your mouse and keyboard, disable or unplug any USB devices that may be active such as a webcam or microphone.

Tip: The Oculus Rift uses a lot of USB bandwidth and can cause issues with tracking when haptics are triggered. Some USB ports on select motherboards are not up to the proper USB 3 spec.

Error message saying need to install 2015 or 2019 runtime version

Try running vrmonitor.exe directly.

two files may be missing: msvcp140.dll & vcruntime140.dll

This may have something to do with a Microsoft update of its "Microsoft Visual C++ Redistributable for Visual Studio 2019" package

download the version of VC_redist.x64.exe from this page: https://support.microsoft.com/en-us/help/2977003/the-latest-supported-visual-c-downloads

if you have this issue in a 32-bit system, you'd want to try the 32-bit version.

LowLevelFatalError crash message on launch

Does your error contain a UGC number? It may look something like this:


This is a workshop map that is broken and you will need to unsubscribe from it. You can find out the map that is causing this by going to the link on the workshop with the UGC number. Paste the url into your browser https://steamcommunity.com/sharedfiles/filedetails/?id=

After ?id= in the link add the UGC number in your error without the UGC like so https://steamcommunity.com/sharedfiles/filedetails/?id=1234567890

  • This is not a valid UGC number and only used as an example

Please notify and report this map to developers so they can mark the map as incompatible.

Error: 0x887A0006 - 'HUNG' Unreal Engine is exiting due to D3D device being lost.

Update your graphics card drivers.

Pavlov VR in Steam is stuck on verifying

Clear Steam Download Cache. From your Steam Client, open the Settings panel by selecting “Steam > Settings” from the top left client menu. Go to the downloads section.

If the problem persists make sure your hard drive is not full, you also may need to cull or clean up your workshop downloads.

Black screen and crash on game launch

Does the application hang or crash? Is this the first time launching Pavlov VR on your system? If it hangs, leave the application open until it finally loads, it may take a long time on first load. If it completely crashes you may need to clean your unreal and Pavlov VR installation.

Many crashes are related to Steam Phonon audio. Please make sure your audio drivers for your motherboard chipset are up to date, try disabling any software that may be affecting audio in any way.

If you have a very old steam profile picture try changing it to current steam dimensions and standards without transparency. This has caused issues for some players.

Known software that can cause conflicts: Nahimic 3, 3rd party firewalls/antivirus such as Avast. Anything that tampers with hardware on your computer like CPU or GPU management software.

Make sure you are on stable, non-beta branches of your respective software. If you are on Oculus or have Oculus software installed for Revive, make sure you opt-out of any beta programs such as the Public Test Channel. If you are on SteamVR hardware make sure you are not using a SteamVR beta branch.

To opt-out of Oculus PTC: Oculus Software > Settings > Beta-Version > Public Test Channel > Disable

Make sure your Oculus software is up to date with the correct version on main branch.

To opt-out of SteamVR Beta: Find SteamVR in your library under the “Tools” section. Go into Properties > Betas > None - Opt out of all beta programs

If the above does not work please proceed try cleaning your Pavlov VR installation if you have been able to get Pavlov VR to launch in the past.

Rift/Rift S Audio not working

Check all your audio settings, even if you think it’s not the problem. Things can change when SteamVR or Pavlov VR launches.

Check all these when in and out of the game:

Windows audio settings input/output Steam audio settings SteamVR audio settings Oculus Home audio settings Ingame audio settings with the microphone drop down to see if your mic is working, start a lobby and start talking, check the icon next to your name, if it changes, it’s working.

My hands are stuck on the floor

Reset your bindings for SteamVR bindings if running in SteamVR mode (Vive/WMR/Index) Reset your playspace and re-set up room (Oculus)

I'm teleporting to below/above the mappoint to point 0,0,0

Buggy control scheme for SteamVR, unsubscribe from bindings, and reset steamvr.

VAC Check Timed Out error

Follow some of the tips on this Steam support page: Vac Check timed out

Scopes cause the game to massively lag out

Make sure that supersampling is turned off (Look up how to do this for either SteamVR or Oculus software, depending on your headset). Then go into your graphics options and reduce the scaling from 100% down to 99%.

Voice chat is laggy/cutting out a lot

This usually happens when a server doesn't have powerful enough hardware for the number of players on it. Disconnect from the server and try to join a lower player server instead, this usually fixes the issue.

For reference, the absolute maximum number of players a server can hold as of 25/12/2021 is 28 players, anything higher than that and even the most powerful servers lag out, so avoid any servers with max playercounts above 28.

Cleaning your Pavlov VR installation

If you are launching Pavlov VR for the first time and are unable to, you likely do not need to clean your installation and should investigate hardware/firmware/driver related issues as well as software conflicts. This should be used by people who were able to get Pavlov working previously in the past, but are currently unable to.

Clear Steam Download Cache. From your Steam Client, open the Settings panel by selecting “Steam > Settings” from the top left client menu. Go to the downloads section. Menu.

Completely uninstall Pavlov VR from Steam

Delete the Appdata folder(s) for Pavlov

Type %localappdata% in your windows search

You made need to Select View > Show > Hidden items to get some of the folders below to show up at all.


C:/Users/[YOURUSERNAME]/AppData/Roaming/Unreal Engine


Find the folder called Pavlov and delete it. Try deleting UnrealEngine app data if you’re still having issues.

Locate main Pavlov VR folder installation in file explorer and delete leftover files located where your steam library is on your hard drive: SteamLibrary/SteamApps/Common

Find the folder labeled PavlovVR and delete it. Restart your computer.

Reinstall Pavlov and try to launch again. Proceed to the next step if this does not work.

Deleting all your downloaded workshop content

located in: steamapps/workshop/content/555160

Ram Troubleshooting

If you are having random or strange crashes, it may be a good idea to run a RAM diagnostic tool as part of your troubleshooting steps:

How to test Ram

I have an index and the grip sensitivity is not how I like it, Grenades seems to sticky

Check out this helpful guide on how to edit your bindings for SteamVR devices and adjust your grip sensitivity.

How to edit SteamVR bindings

Pavlov's easy anti cheat (EAC) is giving me an Error Code

Reinstall Easy anti-cheat:

Browse to your Pavlov install directory and fine the Easy anti cheat folder, usually located at C:\Program Files (x86)\Steam\steamapps\common\PavlovVR\EasyAntiCheat

Then run "EasyAntiCheat_EOS_Setup.exe"

"Side-by-side configuration is incorrect" error

Reinstall Microsoft Visual C++ here: https://docs.microsoft.com/en-us/cpp/windows/latest-supported-vc-redist?view=msvc-170

If that doesn't work, try all of the other steps listed here: https://www.drivereasy.com/knowledge/side-by-side-configuration-is-incorrect-in-windows-10-fixed/

Crashing with SteamVR, none of the other fixes have helped.

This is an unusual edge-case fix, but may be worth a shot if nothing else works.

Open SteamVR with your headset turned on. When SteamVR has fully launched, turn your headset off with SteamVR still running (If possible). Launch Pavlov. If Pavlov loads successfully, turn your headset back on.

None of this is working, how do I find the crash logs?

Locate your local appdata folder on your windows installation: %localappdata%/Pavlov/Saved/Crashes/

1. Press start

2. Type "%localappdata%" without quotes and press enter

3. Locate Pavlov folder.

Locate the files named: UE4Minidump.dmp and CrashContext.Runtime-xml in a folder with the date of the crash in the name and give to devs or person helping you troubleshoot. Opening this second file up with a text editor can often give some clues.

My game launches as normal, but older headset stays black. Game runs in background on SteamVR still

If this happens, it can be one of two issues. The primary one tends to be USB overload related to the rift s. Unplug all USBs and try switching to different ports until the headset works.

If that does not work then the issue is steam not noticing the older headset., This tends to be a combination of beta programs, USB overload, and 3rd party software. Disable anything unneeded to run VR, switch around USB ports, and make sure you are on a stable branch of the VR software you are running. Beta's have been known to help, but disabling 3rd party software unintentionally. Repeat older debugging steps after trying this if the issue persists.