chaoscreater
New member
- Apr 25, 2022
- 3
Hi all,
I'm new to this forum and hopefully I've posted this thread in the right section. I have a very annoying app crashing issue and I've tried pretty much everything I can think of. Hopefully someone here will be able to help me identity what the issue is!
Basically, a while ago I've done an in-place upgrade from Win10 to Win11. Everything works fine, except that I have an app (TOW.exe) that seems to crash after running for about 20 mins ~ 2 hours. Sometimes it would work for 20 minutes and crash, sometimes it would work for hours and crash. The crash is always the same. This was never an issue running on Windows 10.
Below is a screenshot of the crash shown in Nirsoft's AppCrashView:
The exception code is always the same - "0xc0000005". I Googled this a bit and apparently, apps that are made using Unity don't seem to like RAM running at 3200MHz (which is what I'm using). The problem is, I'm running this on a laptop. I can't change the RAM timing in the BIOS and again, I never had this problem in Windows 10.
I've also tried installing Unity 2017.4.40 and then replacing the UnityPlayer.dll file in the path (D:\tow\app\UnityPlayer.dll) with the UnityPlayer.dll from the (Program Files\Unity) folder. The end result is the same.
I'm using the latest Win11 stable build as of this writing (22000.613) and my system is fully patched with Windows Update. I've also installed the latest AMD chipset driver and AMD display driver. Dependencies such as C++ are fully up to date. I've used the one from here - Visual C++ Redistributable Runtimes All-in-One (Feb 2022) Download.
I'm not using any 3rd party antivirus either, it's just using Windows Defender and I've added D:\ to the Folder Exclusion list.
I've tried to use Sysinternal's Process Monitor (ProcMon) to debug the app, but whenever I run ProcMon, the app (TOW.exe) wouldn't start. I've also tried using WinDBG (Preview) to launch the app and hook into it, but again the app wouldn't start if it is launched from WinDBG.
Possibly related, I also noticed that another app (Line.exe) always shows up in the AppCrashView logs. The weird thing is, this app doesn't crash and still works fine, but it always registers an entry in AppCrashView. The crash error is always the same and it is generated whenever the app process is launched.
However, on Windows 10, this error never shows up. It's only on Windows 11.
To completely rule out the fact that it's a Windows 11 issue, I did a fresh Win11 install on a test machine and then ran the 2 apps (Tow.exe and Line.exe). No crash errors generated and TOW.exe runs fine for hours and hours. So at this point, I believe the issue is specific to my machine with the Win11 that was installed via the in-place upgrade.
I also used Process Explorer to look at the "Threads" column for both Line.exe and Tow.exe. I noticed that they're both referencing ntdll.dll:
So then I used Nirsoft's LoadedDllsView to look at what apps are loading/using the ntdll.dll. I then closed all the apps found in the list. Here's an example:
However, the crash error for Line still registers in AppCrashView, whenever the process is launched. Also, TOW.exe still crashes after running for a while.
Below are links to the .WER and .DMP files, which I found from here - C:\Users\All Users\Microsoft\Windows\WER\ReportArchive and %localappdata%\CrashDumps
https://easyupload.io/zuiien
https://easyupload.io/1xxls9
I'm new to this forum and hopefully I've posted this thread in the right section. I have a very annoying app crashing issue and I've tried pretty much everything I can think of. Hopefully someone here will be able to help me identity what the issue is!
Basically, a while ago I've done an in-place upgrade from Win10 to Win11. Everything works fine, except that I have an app (TOW.exe) that seems to crash after running for about 20 mins ~ 2 hours. Sometimes it would work for 20 minutes and crash, sometimes it would work for hours and crash. The crash is always the same. This was never an issue running on Windows 10.
Below is a screenshot of the crash shown in Nirsoft's AppCrashView:
The exception code is always the same - "0xc0000005". I Googled this a bit and apparently, apps that are made using Unity don't seem to like RAM running at 3200MHz (which is what I'm using). The problem is, I'm running this on a laptop. I can't change the RAM timing in the BIOS and again, I never had this problem in Windows 10.
I've also tried installing Unity 2017.4.40 and then replacing the UnityPlayer.dll file in the path (D:\tow\app\UnityPlayer.dll) with the UnityPlayer.dll from the (Program Files\Unity) folder. The end result is the same.
I'm using the latest Win11 stable build as of this writing (22000.613) and my system is fully patched with Windows Update. I've also installed the latest AMD chipset driver and AMD display driver. Dependencies such as C++ are fully up to date. I've used the one from here - Visual C++ Redistributable Runtimes All-in-One (Feb 2022) Download.
I'm not using any 3rd party antivirus either, it's just using Windows Defender and I've added D:\ to the Folder Exclusion list.
I've tried to use Sysinternal's Process Monitor (ProcMon) to debug the app, but whenever I run ProcMon, the app (TOW.exe) wouldn't start. I've also tried using WinDBG (Preview) to launch the app and hook into it, but again the app wouldn't start if it is launched from WinDBG.
Possibly related, I also noticed that another app (Line.exe) always shows up in the AppCrashView logs. The weird thing is, this app doesn't crash and still works fine, but it always registers an entry in AppCrashView. The crash error is always the same and it is generated whenever the app process is launched.
However, on Windows 10, this error never shows up. It's only on Windows 11.
To completely rule out the fact that it's a Windows 11 issue, I did a fresh Win11 install on a test machine and then ran the 2 apps (Tow.exe and Line.exe). No crash errors generated and TOW.exe runs fine for hours and hours. So at this point, I believe the issue is specific to my machine with the Win11 that was installed via the in-place upgrade.
I also used Process Explorer to look at the "Threads" column for both Line.exe and Tow.exe. I noticed that they're both referencing ntdll.dll:
So then I used Nirsoft's LoadedDllsView to look at what apps are loading/using the ntdll.dll. I then closed all the apps found in the list. Here's an example:
However, the crash error for Line still registers in AppCrashView, whenever the process is launched. Also, TOW.exe still crashes after running for a while.
Below are links to the .WER and .DMP files, which I found from here - C:\Users\All Users\Microsoft\Windows\WER\ReportArchive and %localappdata%\CrashDumps
https://easyupload.io/zuiien
https://easyupload.io/1xxls9
Last edited: