Question New PC Fortnite Constantly Crashing

Aug 29, 2020
5
0
10
Hello,

Just the other day i built my self a brand new PC, and everything works perfectly, I can run every game perfect besides fortnite. Every time I play fortnite I can play for about 10 minutes then my game will crash. I have seen another post on this issue about 3 months ago but nothing was brought up about a fix. I really don't know what to do and if anyone has fix please help.


here is the link to the other users REDDIT post:


I get the same error message in the game logs that the other user did as well.
[2020.08.28-20.22.45:833][607]LogCore: Error: Hitch detected on gamethread (frame hasn't finished for 327.22ms):
[2020.08.28-20.22.45:833][607]LogCore: Error: Leaving hitch detector (+ 327.24ms)
[2020.08.28-20.22.45:833][607]LogCore: Error: Leaving stat scope on hitch (+ 327.26ms) [RTHeartBeat 1] STAT_Sleep
[2020.08.28-20.22.45:833][607]LogCore: Error: Leaving stat scope on hitch (+ 327.67ms) [GameThread] STAT_EventWait
[2020.08.28-20.22.45:843][607]LogWindows: FPlatformMisc::RequestExit(0)
[2020.08.28-20.22.45:843][607]LogCore: Engine exit requested (reason: Win RequestExit)
[2020.08.28-20.22.45:843][607]LogWindows: Windows GetLastError: The operation completed successfully. (0)
[2020.08.28-20.22.45:843][607]LogWindows: FPlatformMisc::RequestExit(0)
[2020.08.28-20.22.45:843][607]LogCore: Engine exit requested (reason: Win RequestExit; note: exit was already requested)
[2020.08.28-20.22.45:844][607]LogOnlineCloud: Verbose: MCP: Starting compression for file 'ClientSettings.Sav'
[2020.08.28-20.22.45:844][607]LogCore: Error: Leaving stat scope on hitch (+ 337.92ms) [RHIThread] STAT_D3D11PresentTime
[2020.08.28-20.22.45:844][607]LogCore: Error: Leaving stat scope on hitch (+ 337.94ms) [RHIThread] STAT_RHIThreadExecute
[2020.08.28-20.22.45:844][607]LogWindows: Windows GetLastError: The operation completed successfully. (0)

Specs
i9 10900k
GeForce RTX 2080 Super
64 GB Ram
z490-e gaming mobo
 
Last edited by a moderator:

Ralston18

Titan
Moderator
Look in Reliability History and Event Viewer.

Determine what error codes and warnings (if any) that Windows may be capturing with respect to the Fortnite crashes.

Update your post to include PSU: Make, model, wattage, age, condition.

Likewise - disk drives: make, model, capacity, how full?
 
Aug 29, 2020
5
0
10
Look in Reliability History and Event Viewer.

Determine what error codes and warnings (if any) that Windows may be capturing with respect to the Fortnite crashes.

Update your post to include PSU: Make, model, wattage, age, condition.

Likewise - disk drives: make, model, capacity, how full?
How do I update my post to include the PSU info and I have a 2TB m.2 Samsung and its its barley used i just built my pc i have 1.6 tb left and i have an additional 2 tb HDD that has nothing on it yet
 
Aug 29, 2020
5
0
10
Ok, I have a Brand New EVGA 210-GQ-100-v1. 1000 GQ, 80+ GOLD 1000W, Semi Modular PSU

In Reliability History when my game crashes it appears to come up with a critical event of a windows hardware error and the Problem event name is LiveKernelEvent
 
Aug 29, 2020
5
0
10
Ok, I have a Brand New EVGA 210-GQ-100-v1. 1000 GQ, 80+ GOLD 1000W, Semi Modular PSU

In Reliability History when my game crashes it appears to come up with a critical event of a windows hardware error and the Problem event name is LiveKernelEvent
Also I found in the Event Viewer when my game crashed 5 minutes before i got a Kernel-Event Tracing Error which said this Session "dfa2c640-651d-488d-a479-2fd7a7ca6e29" failed to start with the following error: 0xC0000022.

and then right when my game crashed i got a Warning for my display saying this Display driver nvlddmkm stopped responding and has successfully recovered.
 
Aug 29, 2020
5
0
10
Also I found in the Event Viewer when my game crashed 5 minutes before i got a Kernel-Event Tracing Error which said this Session "dfa2c640-651d-488d-a479-2fd7a7ca6e29" failed to start with the following error: 0xC0000022.

and then right when my game crashed i got a Warning for my display saying this Display driver nvlddmkm stopped responding and has successfully recovered.
One more Warning i found in Event Viewer under Administrative Events was Event ID 4109, Display: Application FortniteClient has been blocked from accessing Graphics hardware.
 
Dec 26, 2021
50
0
30
One more Warning i found in Event Viewer under Administrative Events was Event ID 4109, Display: Application FortniteClient has been blocked from accessing Graphics hardware.

Hello mate,

I dont suppose you found a solution to this, my game has been doing the same thing, with the same error code

Application FortniteClient has been blocked from accessing Graphics hardware.
 
Jul 31, 2022
1
0
10
Hello mate,

I dont suppose you found a solution to this, my game has been doing the same thing, with the same error code

Application FortniteClient has been blocked from accessing Graphics hardware.

Hey, don't supposed you managed to solve it? My games crashing too. Where did you find the thing that says that Fortnite was blocked from accessing Graphics hardware? I've looked in Event Viewer and couldn't find it. Just something like "Display driver nvlddmkm stopped responding"