the "2 hours" crash...

Just confirmed with the two leaguemates that they use the regular client and not the steam version.

One crashes regularly, the other usually when zoning. Specifically, Thanagar.

Since the House of Legends update, I have crashed pretty regularly after about two hours of play. My wife has as well. We will also randomly crash sooner than that from time to time. I have tried re-installing Windows 10 (I believe I was on 20H1 when it first happened). We installed clean Windows 10 21H2 and only installed the game and its Microsoft Visual C++ Redistributables.

Typically, I can tell when the crash is about to happen now and I will exit the game before trying to queue for any instances, knowing that zoning into the instance will cause a crash. The crash is preceded by choppy frame rates if I rotate my character around an environment. The crash itself appears as an application crash with a generic crash code of 0xc0000005, which feels like a memory management issue to me. Either a memory leak is occurring, or memory is being accessed after a variable has gone out of scope or been cleaned up.

Windows Error Reporting actually caught the crash most recently and points to a memory leak:

Code:

Fault bucket 2009133527114125891, type 5
Event Name: RADAR_PRE_LEAK_WOW64
Response: Not available
Cab Id: 0
 
Problem signature:
P1: DCGAME.EXE
P2: 78.0.30693.2369
P3: 10.0.19044.2.0.0
P4: 
P5: 
P6: 
P7: 
P8: 
P9: 
P10: 
 
Attached files:
\\?\C:\Users\Mik\AppData\Local\Temp\RDR2C41.tmp\empty.txt
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2C52.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2C63.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2C61.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2C81.tmp.txt
 
These files may be available here:
 
 
Analysis symbol: 
Rechecking for solution: 0
Report Id: 1a5e3150-13ad-41c1-83d1-33b244e8f5f6
Report Status: 268435456
Hashed bucket: 988931c5a8786f42dbe1e04c4df71243

Same as TC. Every day about 3-5 minutes after logging in the game minimizes itself to task bar, after about an hour it will just close/crash with no error or warning. Also, not sure if it's related, but I still don't get any loading screens when playing in fullscreen( this has been ongoing since 5 years ago ).

The minimizing for us turned out to be antivirus software that would periodically pop up a notification about an update. DCUO does not seem to play well with notifications, so you may want to investigate something similar.

I was really hoping Mepps would respond to my post laying out the error details. In any case, you should check if you have error details in your Event Viewer logs:

1. Go to your search bar in Windows Type here to search
2. Type "eventvwr.msc" and press Enter to launch Event Viewer
3. Navigate to Windows Logs
4. Navigate to Application under Windows Logs
5. Click on an item in the list (most should say Information as their log level)
6. Press CTRL + F
7. Type in DCGame.exe and press Enter
8. Use F3 to navigate to subsequent logs with DCGAME.EXE involved
9. Look for Event 1001 for Windows Error Reporting or Event 1000 for Application Error events

You should see something similar to my previous post and another entry similar to the one below:

Code:

Faulting application name: DCGAME.EXE, version: 78.0.30693.2369, time stamp: 0x61da29d9
Faulting module name: DCGAME.EXE, version: 78.0.30693.2369, time stamp: 0x61da29d9
Exception code: 0xc0000005
Fault offset: 0x007b6747
Faulting process id: 0x3e44
Faulting application start time: 0x01d80bb188fee95a
Faulting application path: C:\Program Files (x86)\Steam\steamapps\common\DC Universe Online\Unreal3\Binaries\Win32\DCGAME.EXE
Faulting module path: C:\Program Files (x86)\Steam\steamapps\common\DC Universe Online\Unreal3\Binaries\Win32\DCGAME.EXE
Report Id: faaad1ea-b806-45f0-9c0f-2c03364325d5
Faulting package full name:
Faulting package-relative application ID: 

Thanks for the instructions. Will do this next crash.

Just had my third crash overall this week. Just checked the event logs like you suggested and pretty much each one was what you said.

Crashed last night. Something I noticed before the crash was that two objects had no textures, they were simply black, no detail/maps applied to them. After relogging the two items were as normal.

Code:

Fault bucket 1970005313965347341, type 1
Event Name: APPCRASH
Response: Not available
Cab Id: 0
 
Problem signature:
P1: DCGAME.EXE
P2: 78.0.30693.2369
P3: 61da29d9
P4: DCGAME.EXE
P5: 78.0.30693.2369
P6: 61da29d9
P7: c0000005
P8: 007b6747
P9:
P10:
 
Attached files:
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER6B6D.tmp.dmp
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER6D24.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER6D35.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER6D33.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER6D53.tmp.txt
 
These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_DCGAME.EXE_f9cef9c86732a59f5b1eefebed4a9f82666a18c4_78f7d12b_c9b03c2f-2ac7-4718-82dc-8d80fe407c2e
 
Analysis symbol:
Rechecking for solution: 0
Report Id: a573bf62-467e-426f-8397-7644ef240d11
Report Status: 268435456
Hashed bucket: 21635338652fe0d76b56dd654089520d
Cab Guid: 0

Code:

Faulting application name: DCGAME.EXE, version: 78.0.30693.2369, time stamp: 0x61da29d9
Faulting module name: DCGAME.EXE, version: 78.0.30693.2369, time stamp: 0x61da29d9
Exception code: 0xc0000005
Fault offset: 0x007b6747
Faulting process id: 0x2290
Faulting application start time: 0x01d819fdeb7e145f
Faulting application path: H:\PC GAMES\dcuo\Unreal3\Binaries\Win32\DCGAME.EXE
Faulting module path: H:\PC GAMES\dcuo\Unreal3\Binaries\Win32\DCGAME.EXE
Report Id: a573bf62-467e-426f-8397-7644ef240d11
Faulting package full name:
Faulting package-relative application ID: 

Yesterday evening I had a strange problem, the game froze as if it was not responding for a short time, at first I thought I was going to suffer the famous 2 hour crash phenomenon or that I was facing a problem with my box, but no, it just froze for a moment and finally debugged...