GFX Card Issue?

Hatake

Hatake

Hatake

Associate
Joined
7 Mar 2005
Posts
197
Location
Glasgow, Scotland
I built the below PC back in December 2019 and it's been running OK for the most part. Occasional GFX issues that updates from Radeon seemed to solve.

Since yesterday, games like Destiny 2 from Steam have been crashing to desktop even before it opens (loads for a second then C2D). Dauntless from Epicgames hangs on the logo screen then C2D even though it was working fine earlier that day.

I've updated all drivers, including AMD chipset and processor drivers and not really getting anywhere. Short of doing a fresh install of Windows, I'm out of ideas on how to fix this or locate the problem. Only concern is that Radeon recommend a 600W PSU although everything I've read and been told suggests that I'm unlikely to see over 500W peak load.

Any ideas?


​
 
Have you stress tested and benched everything, including the memory? I assume you restarted after the CTDs?

Do you have any monitoring software running?
 
I haven't stress tested anything, not sure where to begin with that to be honest. No monitoring software other than the native windows and AMD Radeon ones. I'll have a google and start running some tests.

Multiple restarts didn't help with games not loading. Done a complete uninstall of the GFX drivers with DDU and reinstalled fresh but still no joy

*edit

  • Furmark ran for around 15 minutes, peak temps of 73C, no glitches.
  • 4 instances of MemTest ran concurrently, testing 12GB of RAM, 150%+ coverage, no errors

Will run Unigine Heaven in a bit, got some work to finish
 
Last edited:
Is there anything in the boot logs of those games? You could try installing the DirectX runtime, just incase your PC is missing some components or they got corrupted or something?

If they have a configuration .ini file you could delete it and let the game rebuild it.

What monitor are you using?
 
just completed Unigine Heaven benchmark 3 times, last run on ultra setting. Completed without any problems, 137FPS on ultra settings. All my hardware is stock, no overclocking apart from XMP profile for the RAM. Used GPU-Z to monitor temps and power draw during the ultra benchmark. Peak 200W power draw and less than 80C temps with fan speeds of 46%.

My monitor is a Dell Ultrasharp U2311H. Not the newest monitor but I'm more than happy with it.

I'll have a google and see if I can find where the boot log may be stored for those games
 
Currently Destiny 2 doesn't even open, the mouse goes into the loading circle then stays on desktop. Dauntless opens, hangs on the logo screen, then CTD 30s later.

Windows event viewer has the following application error for the two:

Code: 
Faulting application name: destiny2.exe, version: 19305.0.0.0, time stamp: 0x5eed63ec
Faulting module name: ntdll.dll, version: 10.0.18362.815, time stamp: 0xb29ecf52
Exception code: 0xc0000374
Fault offset: 0x00000000000f9229
Faulting process ID: 0x2100
Faulting application start time: 0x01d6594de063e276
Faulting application path: C:\Program Files (x86)\Steam\steamapps\common\Destiny 2\destiny2.exe
Faulting module path: C:\Windows\SYSTEM32\ntdll.dll
Report ID: 57e17909-f238-4d4f-aa2f-2e2bc40b3f77
Faulting package full name:
Faulting package-relative application ID:

Code: 
Faulting application name: Dauntless-Win64-Shipping.exe, version: 4.24.3.0, time stamp: 0x5f050344
Faulting module name: ntdll.dll, version: 10.0.18362.815, time stamp: 0xb29ecf52
Exception code: 0xc0000374
Fault offset: 0x00000000000f9229
Faulting process ID: 0x1688
Faulting application start time: 0x01d6594e14c2dc1a
Faulting application path: C:\Program Files\Epic Games\Dauntless\Archon\Binaries\Win64\Dauntless-Win64-Shipping.exe
Faulting module path: C:\Windows\SYSTEM32\ntdll.dll
Report ID: b3e6e9ee-3235-47c8-9e5f-981fa024d3e7
Faulting package full name:
Faulting package-relative application ID:

And the windows error reporting log

Code: 
Fault bucket 1296404691600007943, type 4
Event Name: APPCRASH
Response: Not available
Cab Id: 0

Problem signature:
P1: destiny2.exe
P2: 19305.0.0.0
P3: 5eed63ec
P4: StackHash_0283
P5: 10.0.18362.815
P6: b29ecf52
P7: c0000374
P8: PCH_3C_FROM_ntdll+0x000000000009CBC4
P9:
P10:

Attached files:
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERCBA1.tmp.dmp
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERCE13.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERCE23.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERCE21.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERCE41.tmp.txt

These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_destiny2.exe_ff2478f0c43ddfbe3e24fd44f62696cc83d4f4c_c71779fc_84ffd58e-4ba9-4041-885a-a32fe23f0adb

Analysis symbol:
Rechecking for solution: 0
Report Id: 57e17909-f238-4d4f-aa2f-2e2bc40b3f77
Report Status: 268435456
Hashed bucket: 86c7a853a67db05101fdc132c7f7e307
Cab Guid: 0

Code: 
Fault bucket 2139460759403715686, type 4
Event Name: APPCRASH
Response: Not available
Cab Id: 0

Problem signature:
P1: Dauntless-Win64-Shipping.exe
P2: 4.24.3.0
P3: 5f050344
P4: StackHash_b2a2
P5: 10.0.18362.815
P6: b29ecf52
P7: c0000374
P8: PCH_3C_FROM_ntdll+0x000000000009CBC4
P9:
P10:

Attached files:
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER24D8.tmp.dmp
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER266F.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER267F.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER267F.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2690.tmp.txt

These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_Dauntless-Win64-_ef2ffc9e15d6e6edc76ebad501d357c6d2bf8_136f7592_aa439ebf-fcd8-44ca-a4ac-b6ae51305c21

Analysis symbol:
Rechecking for solution: 0
Report Id: b3e6e9ee-3235-47c8-9e5f-981fa024d3e7
Report Status: 268435456
Hashed bucket: b2af45c47e828a866db0e439af255c66
Cab Guid: 0

None of that means anything to me and not sure how to go about googling that. Whatever ntdll.dll is, is that the source of my problems since it's the faulting module in both games?
 
The description of that file on the interwebs is pretty vague, I saw a few posts relating to emulation and anti-virus software.

Do you have a 'clean' Windows install with nothing else running in the background?

Any unusual USB devices, controllers, steering wheels, wireless, KVMs?
 
It's a clean install as far as I installed it fresh when I built the PC. Not really any unusual USB devices apart from a generic xbox look-a-like controller that Steam registers as a PS3 controller for some reason but it's not plugged in.

Since the benchmark didn't have any glitches, I can only assume it's software related. Gonna have to bite the bullet and just do a fresh install of windows. May as well get a second HDD since I could do with storage space and have my current SSD as a boot drive.

Thanks for the help!
 
Remove the drivers and use the ones from April. There are a lot of people having issues with the drivers post April suggest you use them as a starting point and then at least you know its not a driver issue.
 
You must log in or register to reply here.
Back
Top Bottom