Sure. But before I go to all that trouble, let me just recap that this issue wasn't present up until update #10 then has been constantly present until update #17 which seemed to address it as a known issue, then immediately regressed in update #18.
The error that gets thrown in the crash files is the following:
LowLevelFatalError [File:D:\wk\tsl-client-branch\build\UnrealEngine\Engine\Source\Runtime\CoreUObject\Private\Serialization\AsyncLoading.cpp] [Line: 1375]
No outstanding IO, no nodes in the queue, yet we still have 'PackagesWithNodes' in the graph.
This error has been present since at least 3/27/18, as that is the earliest crash file I've kept around just to document the occurrence of this issue. Judging by forum search results, it looks like it probably started round 3/17/18:
There's basically a 14 pages dedicated to this issue in this thread:
It happens on Intel and AMD.
It may happen more with over clocked AMD chips, but the AMD overclocking crash seems to be a separate issue based on other forum threads.
It happens on all all versions of Windows.
It happens whether you uninstall and reinstall the game.
It happens whether you turn HPET (High Performance Event Timer) on or off, though some report success with turning off.
It happens whether or not you update graphics drivers, or change graphics cards.
It happens regardless of Windows updates.
It happens when you have the latest BIOS updates.
It happens whether you start Steam as an admin or not.
It happens whether you've verified the program files in Steam or not.
BattleEye starts correctly, the service is running.
You can see the extent that some people have gone to try and troubleshoot this issue:
Now for what I've tried with respect to your basic troubleshooting guide:
1. Try turning it off and back on again
2. Remove all launch options
There are no launch options to remove, I launch it from Steam. However Steam launches the game is how it starts from the day in purchased and installed the game until now.
3. Verify the integrity of the game files
Done that, multiple times. Both as administrator and not.
4. Manually remove configuration settings
5. Update Windows
6. Update your graphics card drivers
Yes, of course. Including using different video cards.
7. Run Steam as Admin
8. Launch the game from Steam
9. Check that BattlEye is running correctly
Yes. Service is there, and starts correctly.
10. Add exception rules to your anti-virus and firewalls
Exceptions are already present, for Production, Test and Experimental.
11. Connect directly to your router/modem
No. Impractical and not related to firewall or modem, since clearly reducing the number of active CPUs to one solves the problem. It's a threading issue.
12. Enable Port Forwarding for PUBG
No. Not necessary as it's not related to a port issue. Since clearly reducing the number of active CPUs to one solves the problem. It's a threading issue.
13. Attempt tethering to a mobile device
No. Impractical and not related to the way I connect to the Internet or my ISP, since clearly reducing the number of active CPUs to one solves the problem. It's a threading issue.
14. Uninstall/reinstall PUBG
Yes. Multiple times.
Which of the three crashing issues you are experiencing:
1. When launching the game
3. When leaving a match
Operating System: Windows 8.1 Enterprise 64-bit (6.3, Build 9600) (9600.winblue_ltsb_escrow.180718-1800)
Language: English (Regional Setting: English)
System Manufacturer: Gigabyte Technology Co., Ltd.
System Model: To be filled by O.E.M.
Processor: AMD A10-7870K Radeon R7, 12 Compute Cores 4C+8G (4 CPUs), ~3.9GHz
Memory: 8192MB RAM
Available OS Memory: 8136MB RAM
Page File: 4844MB used, 6491MB available
DirectX Version: DirectX 11
Card name: NVIDIA GeForce GTX 1080 Ti
Chip type: GeForce GTX 1080 Ti
DAC type: Integrated RAMDAC
Device Type: Full Device
Device Key: Enum\PCI\VEN_10DE&DEV_1B06&SUBSYS_374C1458&REV_A1
Display Memory: 15188 MB
Dedicated Memory: 11120 MB
Shared Memory: 4067 MB
Current Mode: 1920 x 1080 (32 bit) (60Hz)
Monitor Name: Generic PnP Monitor
Attached is a crash on startup, just after the credits/copyright screen.