F5F Stay Refreshed Hardware Desktop Are the games closing to the desktop without any modifications?

Are the games closing to the desktop without any modifications?

Are the games closing to the desktop without any modifications?

M
MMASTER7
Member
Find
227
04-16-2023, 03:02 AM
#1
Hi, long time lurker here, couldn't find a specific forum to post this, so here goes:
TL: DR - Borderlands 4 and Dying Light: The beast started crashing to desktop today, yet yesterday everything worked fine.
In more detail: I've been playing and enjoying both games (which run on 2 different game engines) for a few days now, without any problems. Today, I find out that they crash to desktop within 0-5 minutes, sometimes at launch even.
When checking the event viewer, I see the following errors at time of crash:
Borderlands 4
Code:
Faulting application name: Borderlands4.exe, version: 5.5.4.1, time stamp: 0x68c8ad5c
Faulting module name: ntdll.dll, version: 10.0.26100.5074, time stamp: 0x0e967e89
Exception code: 0xc0000374
Fault offset: 0x000000000011a3b5
Faulting process id: 0x516C
Faulting application start time: 0x1DC2A63A46E2AFA
Faulting application path: C:\Program Files (x86)\Steam\steamapps\common\Borderlands 4\OakGame\Binaries\Win64\Borderlands4.exe
Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll
Report Id: d62746bd-4fe5-455d-aa24-324c3acb324c
Faulting package full name:
Faulting package-relative application ID:
Dying Light The Beast:
Code:
The description for Event ID 153 from source nvlddmkm cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.
If the event originated on another computer, the display information had to be saved with the event.
The following information was included with the event:
\Device\00000100
Error occurred on GPUID: 100
The message resource is present but the message was not found in the message table
Also saw this one, not sure if related
Code:
Faulting application name: Aac3572MbHal_x86.exe, version: 1.6.1.2, time stamp: 0x67d25d1e
Faulting module name: combase.dll, version: 10.0.26100.5074, time stamp: 0x3a6aab16
Exception code: 0xc0000005
Fault offset: 0x000ae254
Faulting process id: 0x75A0
Faulting application start time: 0x1DC2A592E4DA128
Faulting application path: C:\Program Files\ASUS\AacMB\Aac3572MbHal_x86.exe
Faulting module path: C:\WINDOWS\System32\combase.dll
Report Id: 0d3247fb-628f-4350-b384-a8b2dc4de5f0
Faulting package full name:
Faulting package-relative application ID:
I've tried undervolting, resetting to factory settings of GPU and CPU, DOCP was already set to default, Windows Memory Test returned no issues, I reinstalled the drivers and updated everything including chipset and audio (etc..), verified game files on steam.
I also run FurMark on native resolution (2k) with MSAA8 with and without VSYNC, all good, for solid 20 minutes or so (thought maybe the PSU was at fault, but no issues).
I now recall that when I run Heaven Benchmark, it did crash after a while, for some reason.
I'd attach the GPU-Z logs of crashes but I can't seem to upload them here?
Specs:
Ryzen 7 7800X3D
TUF GAMING X670E-PLUS WIFI
2 X 16GB DDR5-6000 (3000 MHz) Corsair
NVIDIA GeForce RTX 3090 FE (already thermal pasted [a year ago] with max hotspot at ~93 - was 110-> crash before repasting)
I am really at wits end here with these, any thoughts perhaps? I know Borderlands 4 is a heavy, and unoptimized game, but everything worked fine until today, and nothing new was installed between yesterday and today.
Reply
Reply
M
MMASTER7
04-16-2023, 03:02 AM #1

Hi, long time lurker here, couldn't find a specific forum to post this, so here goes:
TL: DR - Borderlands 4 and Dying Light: The beast started crashing to desktop today, yet yesterday everything worked fine.
In more detail: I've been playing and enjoying both games (which run on 2 different game engines) for a few days now, without any problems. Today, I find out that they crash to desktop within 0-5 minutes, sometimes at launch even.
When checking the event viewer, I see the following errors at time of crash:
Borderlands 4
Code:
Faulting application name: Borderlands4.exe, version: 5.5.4.1, time stamp: 0x68c8ad5c
Faulting module name: ntdll.dll, version: 10.0.26100.5074, time stamp: 0x0e967e89
Exception code: 0xc0000374
Fault offset: 0x000000000011a3b5
Faulting process id: 0x516C
Faulting application start time: 0x1DC2A63A46E2AFA
Faulting application path: C:\Program Files (x86)\Steam\steamapps\common\Borderlands 4\OakGame\Binaries\Win64\Borderlands4.exe
Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll
Report Id: d62746bd-4fe5-455d-aa24-324c3acb324c
Faulting package full name:
Faulting package-relative application ID:
Dying Light The Beast:
Code:
The description for Event ID 153 from source nvlddmkm cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.
If the event originated on another computer, the display information had to be saved with the event.
The following information was included with the event:
\Device\00000100
Error occurred on GPUID: 100
The message resource is present but the message was not found in the message table
Also saw this one, not sure if related
Code:
Faulting application name: Aac3572MbHal_x86.exe, version: 1.6.1.2, time stamp: 0x67d25d1e
Faulting module name: combase.dll, version: 10.0.26100.5074, time stamp: 0x3a6aab16
Exception code: 0xc0000005
Fault offset: 0x000ae254
Faulting process id: 0x75A0
Faulting application start time: 0x1DC2A592E4DA128
Faulting application path: C:\Program Files\ASUS\AacMB\Aac3572MbHal_x86.exe
Faulting module path: C:\WINDOWS\System32\combase.dll
Report Id: 0d3247fb-628f-4350-b384-a8b2dc4de5f0
Faulting package full name:
Faulting package-relative application ID:
I've tried undervolting, resetting to factory settings of GPU and CPU, DOCP was already set to default, Windows Memory Test returned no issues, I reinstalled the drivers and updated everything including chipset and audio (etc..), verified game files on steam.
I also run FurMark on native resolution (2k) with MSAA8 with and without VSYNC, all good, for solid 20 minutes or so (thought maybe the PSU was at fault, but no issues).
I now recall that when I run Heaven Benchmark, it did crash after a while, for some reason.
I'd attach the GPU-Z logs of crashes but I can't seem to upload them here?
Specs:
Ryzen 7 7800X3D
TUF GAMING X670E-PLUS WIFI
2 X 16GB DDR5-6000 (3000 MHz) Corsair
NVIDIA GeForce RTX 3090 FE (already thermal pasted [a year ago] with max hotspot at ~93 - was 110-> crash before repasting)
I am really at wits end here with these, any thoughts perhaps? I know Borderlands 4 is a heavy, and unoptimized game, but everything worked fine until today, and nothing new was installed between yesterday and today.

Reply
Reply
M
mkelton19
Junior Member
Find
37
04-16-2023, 06:39 AM
#2
PSU details requested: make, model, wattage, age, condition. Disk drives information needed: make, model, capacity, fill level. Error codes, warnings, and events from Reliability History/Monitor should be identified. Analyze the timeline for recurring patterns.
Reply
Reply
M
mkelton19
04-16-2023, 06:39 AM #2

PSU details requested: make, model, wattage, age, condition. Disk drives information needed: make, model, capacity, fill level. Error codes, warnings, and events from Reliability History/Monitor should be identified. Analyze the timeline for recurring patterns.

Reply
Reply
J
Jorski
Member
Find
219
04-16-2023, 09:06 AM
#3
I carried out a thorough cleanup using revo uninstaller, deleting all remaining files, but it didn’t work. I also attempted to restore the system to September 15th, since everything functioned properly then, yet it still failed.

Hardware details:
- Disk drives: Sabrent Rocket 4 Plus Gaming 2TB (free 1.04 TB)
- Power supply: Corsair RM1000e 1000W Gold Modular ATX, brand new, installed in August 2023
- Reliability history: When the dying light crashes, it displays this message—only the game crash code appears.

Problem signature:
- Event: LiveKernelEvent
- Code: 141
- Parameters: ffffa68f06fa2010, fffff805b65176e0, 0, ffffa68eff7d4080
- OS version: 10_0_26100
- Service Pack: 0_0
- Product: 256_1
- OS Version: 10.0.26100.2.0.0.256.48
- Locale ID: 1033

Files associated with the issue:
WATCHDOG-20250921-1752.dmp, sysdata.xml, WERInternalMetadata.xml, memory.csv, sysinfo.txt, WERInternalRequest.xml
Reply
Reply
J
Jorski
04-16-2023, 09:06 AM #3

I carried out a thorough cleanup using revo uninstaller, deleting all remaining files, but it didn’t work. I also attempted to restore the system to September 15th, since everything functioned properly then, yet it still failed.

Hardware details:
- Disk drives: Sabrent Rocket 4 Plus Gaming 2TB (free 1.04 TB)
- Power supply: Corsair RM1000e 1000W Gold Modular ATX, brand new, installed in August 2023
- Reliability history: When the dying light crashes, it displays this message—only the game crash code appears.

Problem signature:
- Event: LiveKernelEvent
- Code: 141
- Parameters: ffffa68f06fa2010, fffff805b65176e0, 0, ffffa68eff7d4080
- OS version: 10_0_26100
- Service Pack: 0_0
- Product: 256_1
- OS Version: 10.0.26100.2.0.0.256.48
- Locale ID: 1033

Files associated with the issue:
WATCHDOG-20250921-1752.dmp, sysdata.xml, WERInternalMetadata.xml, memory.csv, sysinfo.txt, WERInternalRequest.xml

Reply
Reply
W
whatarethose1
Junior Member
Find
22
04-16-2023, 09:24 PM
#4
Running with DOCP Profile 1 resolved the problem. It seems the memory sticks are likely malfunctioning now.
Reply
Reply
W
whatarethose1
04-16-2023, 09:24 PM #4

Running with DOCP Profile 1 resolved the problem. It seems the memory sticks are likely malfunctioning now.

Reply
Reply