Jump to content
Armastadt

Crashing After Credit Screen and Re-entering Lobby After Game End

Recommended Posts

Still crashing, on both normal and experimental.

Going on 3 months, and 4 updates, BH and STILL CRASHING.

Three months. Four updates.

?

  • Like 1

Share this post


Link to post
Share on other sites

And.....Update #19 still has no fix for crashing during credits. Whatever you did on Update #17 fixed it--so go back and figure it out.

 

Oh, great, and you've added a lobby hang bug too.  Fan-freaking-tastic.

 

5 Months, 9 updates, no (permanent) fix, with more bugs added as a cherry on top.

Edited by Armastadt
Added things about lobby hang bug.

Share this post


Link to post
Share on other sites

Update #20 and still no fix for crashing during loading credits and after game when re-entering the lobby.

 

5 1/2 months, 10 updates, no permanent fix.

 

Share this post


Link to post
Share on other sites
28 minutes ago, Armastadt said:

Update #20 and still no fix for crashing during loading credits and after game when re-entering the lobby.

 

5 1/2 months, 10 updates, no permanent fix.

 

 

Hello Armastaft, thank you for the updated bug report,

Just to get a better understanding of your issue, can I please get you to fill out the bug report template below with the troubleshooting techniques you have tried / attempted, thank you.

 

Share this post


Link to post
Share on other sites
23 hours ago, PUBG_Sheepy said:

Hello Armastaft, thank you for the updated bug report,

Just to get a better understanding of your issue, can I please get you to fill out the bug report template below with the troubleshooting techniques you have tried / attempted, thank you.

 

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:

 

<ErrorMessage>

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.

</ErrorMessage>
 

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

Seriously? Yes.

 

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

Done that.

 

5.    Update Windows

Of course.

 

6.    Update your graphics card drivers

Yes, of course. Including using different video cards.

 

7.    Run Steam as Admin

Yes.

 

8.    Launch the game from Steam

Always.

 

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


Your IGN:
Armastadt

 

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.
BIOS: F8
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
Manufacturer: NVIDIA
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.

 

UE4CC-Windows-56E2500E453B4A9BCE244CB0FECD7C86_0000.zip

Share this post


Link to post
Share on other sites

So here we are at patch #22, going on 6 1/2 months and 12 updates, and still have crashing issues with this game that remain unaddressed, unfixed, and unlisted in known issues.

 

Same old, same old (except, the line number has changed):

<ErrorMessage>

LowLevelFatalError [File:D:\wk\tsl-client-dev3-branch\build\UnrealEngine\Engine\Source\Runtime\CoreUObject\Private\Serialization\AsyncLoading.cpp] [Line: 1383];

No outstanding IO, no nodes in the queue, yet we still have 'PackagesWithNodes' in the graph.;

</ErrorMessage>

Edited by Armastadt

Share this post


Link to post
Share on other sites

Hello @Armastadt

 

Thank you for the update.

 

After looking around for the specific error that you are receiving, I had found this thread back In march which players reported having the similar issue.

 

In that thread was offered possible troubleshooting techniques.

 

https://forums.playbattlegrounds.com/topic/197033-lowlevelfatalerror-crash-on-copyright-screen-work-around-reducing-cores/

 

This was offered for windows 10, but I am not sure if it would work for 8.

 

- Launch Task Manager

- Click on the Details Tab

-Sort by name and Ascending Order

-Launch PUBG

-In Task Manager will the game is loading - find the TslGame.exe process

-Right click TslGame.exe and select affinity

-Unclick all cores

-Click 1 Core

 

-

 

Share this post


Link to post
Share on other sites

@PUBG_Sheepy Hey, thanks for the response, but if you read a few postings back, where I go into great detail, I already mentioned that very same article. So I'm guessing you've got nothing new.

 

Also, I've done all the troubleshooting steps, again as I written above. Just need a fix. Been waiting for a while now.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×