Jones Jun 2, 2023 @ 5:18am
Games crashing but not finding a crash log
I recently got a new to me PC that has some older hardware (2018-2019) but it seems to run great. I loaded Steam onto it yesterday and downloaded my games. I started to play My Garage and after about 1 minute of gameplay it crashes. I ran Whocrashed and it cannot find a crash log. I tried to play Gas Station Simulator and it to crashed. It seems that all my Steam games are going to do the same. Any idea why there would not be a crash log or could it be that Whocrashed is just missing them? Any help would be appreciated.

Something went wrong while displaying this content. Refresh

Error Reference: Community_9708323_
Loading CSS chunk 7561 failed.
(error: https://community.fastly.steamstatic.com/public/css/applications/community/communityawardsapp.css?contenthash=789dd1fbdb6c6b5c773d)
< 1 2 >
Showing 1-15 of 19 comments
Linus Javelson Jun 2, 2023 @ 1:35pm 
Crash logs are usually located inside Steam's "common" folder, i.e:
C:\Program Files (x86)\Steam\steamapps\common\[game-specific folder here]
Have you manually checked this directory for these logs and found nothing?

Alternatively, you could try running a game that you know will have a readily available crash report. (Considering the fact that every single game seems to crash on you here.)
Jones Jun 2, 2023 @ 1:47pm 
I believe I did and found nothing but will check again when I get home
Jones Jun 2, 2023 @ 1:48pm 
Just thinking… could a poor internet connection cause this issue?
Linus Javelson Jun 2, 2023 @ 1:57pm 
Originally posted by bjones2.0:
Just thinking… could a poor internet connection cause this issue?
No, it seems highly unlikely. These games do not really connect to the internet to work. I guess it'd be worth a shot to try them out in offline mode and see if they start at all.
Iceira Jun 2, 2023 @ 2:10pm 
Are you aware of windows own event viewer log.

google how to event viewer and why app crash, and i bet you know why i did not link it.
Jones Jun 2, 2023 @ 3:01pm 
Originally posted by Iceira W10:
Are you aware of windows own event viewer log.

google how to event viewer and why app crash, and i bet you know why i did not link it.

I checked it and it just states that it is an "unknown hang type."
Jones Jun 2, 2023 @ 3:02pm 
Originally posted by Linus Javelson:
Crash logs are usually located inside Steam's "common" folder, i.e:
C:\Program Files (x86)\Steam\steamapps\common\[game-specific folder here]
Have you manually checked this directory for these logs and found nothing?

Alternatively, you could try running a game that you know will have a readily available crash report. (Considering the fact that every single game seems to crash on you here.)


I did go to the path you stated and no logs at all. I'm going to uninstall and reinstall and see if that helps.
Jones Jun 2, 2023 @ 4:25pm 
Anybody see anything odd in this Windows Event Log? Very new to Windows so I'm an old guy trying to learn.

Log Name: Application
Source: Application Error
Date: 6/2/2023 6:10:48 PM
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer: DESKTOP
Description:
Faulting application name: My Garage.exe, version: 2020.3.2.55559, time stamp: 0x605f8b9f
Faulting module name: atidxx64.dll, version: 31.0.12027.9001, time stamp: 0x6425ffc3
Exception code: 0xc0000005
Fault offset: 0x000000000099c796
Faulting process id: 0xdc0
Faulting application start time: 0x01d995a4b66bbccd
Faulting application path: C:\Program Files (x86)\Steam\steamapps\common\My Garage\My Garage.exe
Faulting module path: C:\Windows\System32\DriverStore\FileRepository\u0390451.inf_amd64_39377efdd62734d1\B390182\atidxx64.dll
Report Id: 9d591434-9d39-48c4-8baf-c547cf5613ab
Faulting package full name:
Faulting package-relative application ID:
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Application Error" />
<EventID Qualifiers="0">1000</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>100</Task>
<Opcode>0</Opcode>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2023-06-02T23:10:48.2553891Z" />
<EventRecordID>567</EventRecordID>
<Correlation />
<Execution ProcessID="0" ThreadID="0" />
<Channel>Application</Channel>
<Computer>DESKTOP-B8AQ2U1</Computer>
<Security />
</System>
<EventData>
<Data>My Garage.exe</Data>
<Data>2020.3.2.55559</Data>
<Data>605f8b9f</Data>
<Data>atidxx64.dll</Data>
<Data>31.0.12027.9001</Data>
<Data>6425ffc3</Data>
<Data>c0000005</Data>
<Data>000000000099c796</Data>
<Data>dc0</Data>
<Data>01d995a4b66bbccd</Data>
<Data>C:\Program Files (x86)\Steam\steamapps\common\My Garage\My Garage.exe</Data>
<Data>C:\Windows\System32\DriverStore\FileRepository\u0390451.inf_amd64_39377efdd62734d1\B390182\atidxx64.dll</Data>
<Data>9d591434-9d39-48c4-8baf-c547cf5613ab</Data>
<Data>
</Data>
<Data>
</Data>
</EventData>
</Event>
Linus Javelson Jun 3, 2023 @ 2:22am 
Assuming you've made sure Windows is fully updated, I think you should try updating the graphics drivers since the game seems to have a problem with the atidxx64.dll module. If you go here, you should be able to find the latest drivers for your hardware: http://www.amd.com/en/support.

From what I gathered, you could also have a problem with the .NET Framework. In case updating and/or reinstalling the graphics drivers does not solve your problems, you can try using the Microsoft .NET Framework Repair Tool located here: http://www.microsoft.com/en-us/download/details.aspx?id=30135
Iceira Jun 3, 2023 @ 3:21am 
above user alredy is on top of this, if you still have issue, dont forget AMD is the support there on ATI driver issue.
Last edited by Iceira; Jun 3, 2023 @ 3:22am
Jones Jun 3, 2023 @ 5:12am 
Originally posted by Linus Javelson:
Assuming you've made sure Windows is fully updated, I think you should try updating the graphics drivers since the game seems to have a problem with the atidxx64.dll module. If you go here, you should be able to find the latest drivers for your hardware: http://www.amd.com/en/support.

From what I gathered, you could also have a problem with the .NET Framework. In case updating and/or reinstalling the graphics drivers does not solve your problems, you can try using the Microsoft .NET Framework Repair Tool located here: http://www.microsoft.com/en-us/download/details.aspx?id=30135
I did what you suggested and those issues went away but now I am getting a UnityPlayer.dll crash. From searching that seems like a common issue. Its funny though... I can play this same game at work on a junk computer and no issues at all other than 5FPS lol
Linus Javelson Jun 3, 2023 @ 6:03am 
Originally posted by bjones2.0:
Originally posted by Linus Javelson:
Assuming you've made sure Windows is fully updated, I think you should try updating the graphics drivers since the game seems to have a problem with the atidxx64.dll module. If you go here, you should be able to find the latest drivers for your hardware: http://www.amd.com/en/support.

From what I gathered, you could also have a problem with the .NET Framework. In case updating and/or reinstalling the graphics drivers does not solve your problems, you can try using the Microsoft .NET Framework Repair Tool located here: http://www.microsoft.com/en-us/download/details.aspx?id=30135
I did what you suggested and those issues went away but now I am getting a UnityPlayer.dll crash. From searching that seems like a common issue. Its funny though... I can play this same game at work on a junk computer and no issues at all other than 5FPS lol
I think you're going to need to provide more information here. Are the error reports telling you there's a general problem with UnityPlayer.dll, or is it just missing? Have you tried using "Verify integrity of game files..."? You do that by right-clicking on the game in the Steam Library, choosing "Properties...", then clicking on "Local Files" in the window that opens; finally, you click "Verify integrity of game files...".
Jones Jun 3, 2023 @ 6:25am 
Originally posted by Linus Javelson:
Originally posted by bjones2.0:
I did what you suggested and those issues went away but now I am getting a UnityPlayer.dll crash. From searching that seems like a common issue. Its funny though... I can play this same game at work on a junk computer and no issues at all other than 5FPS lol
I think you're going to need to provide more information here. Are the error reports telling you there's a general problem with UnityPlayer.dll, or is it just missing? Have you tried using "Verify integrity of game files..."? You do that by right-clicking on the game in the Steam Library, choosing "Properties...", then clicking on "Local Files" in the window that opens; finally, you click "Verify integrity of game files...".

This time I was able to play the game about 20 minutes and now I get this crash log. The crash before was saying that the Faulting module path: C:\Program Files (x86)\Steam\steamapps\common\My Garage\UnityPlayer.dll

UnityPlayer.dll is there. On Monday I am going to see what the difference between these files are on my work computer and this one.


Log Name: Application
Source: Application Error
Date: 6/3/2023 8:15:38 AM
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer: DESKTOP
Description:
Faulting application name: My Garage.exe, version: 2020.3.2.55559, time stamp: 0x605f8b9f
Faulting module name: atidxx64.dll, version: 31.0.14037.17019, time stamp: 0x644698b3
Exception code: 0xc0000005
Fault offset: 0x0000000000ae2406
Faulting process id: 0x42c
Faulting application start time: 0x01d9961abc2b59f1
Faulting application path: C:\Program Files (x86)\Steam\steamapps\common\My Garage\My Garage.exe
Faulting module path: C:\Windows\System32\DriverStore\FileRepository\u0391195.inf_amd64_09ef84849323988b\B391209\atidxx64.dll
Report Id: b496ad20-69ff-44d5-b12c-f59e0cc9bc0b
Faulting package full name:
Faulting package-relative application ID:
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Application Error" />
<EventID Qualifiers="0">1000</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>100</Task>
<Opcode>0</Opcode>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2023-06-03T13:15:38.7537145Z" />
<EventRecordID>754</EventRecordID>
<Correlation />
<Execution ProcessID="0" ThreadID="0" />
<Channel>Application</Channel>
<Computer>DESKTOP-B8AQ2U1</Computer>
<Security />
</System>
<EventData>
<Data>My Garage.exe</Data>
<Data>2020.3.2.55559</Data>
<Data>605f8b9f</Data>
<Data>atidxx64.dll</Data>
<Data>31.0.14037.17019</Data>
<Data>644698b3</Data>
<Data>c0000005</Data>
<Data>0000000000ae2406</Data>
<Data>42c</Data>
<Data>01d9961abc2b59f1</Data>
<Data>C:\Program Files (x86)\Steam\steamapps\common\My Garage\My Garage.exe</Data>
<Data>C:\Windows\System32\DriverStore\FileRepository\u0391195.inf_amd64_09ef84849323988b\B391209\atidxx64.dll</Data>
<Data>b496ad20-69ff-44d5-b12c-f59e0cc9bc0b</Data>
<Data>
</Data>
<Data>
</Data>
</EventData>
</Event>
Just run the SFC Scan Tool and see if that fixes anything. Just remember to reboot the PC if it finds corruptions.
Linus Javelson Jun 3, 2023 @ 6:45am 
Originally posted by bjones2.0:
Originally posted by Linus Javelson:
I think you're going to need to provide more information here. Are the error reports telling you there's a general problem with UnityPlayer.dll, or is it just missing? Have you tried using "Verify integrity of game files..."? You do that by right-clicking on the game in the Steam Library, choosing "Properties...", then clicking on "Local Files" in the window that opens; finally, you click "Verify integrity of game files...".

This time I was able to play the game about 20 minutes and now I get this crash log. The crash before was saying that the Faulting module path: C:\Program Files (x86)\Steam\steamapps\common\My Garage\UnityPlayer.dll

UnityPlayer.dll is there. On Monday I am going to see what the difference between these files are on my work computer and this one.


Log Name: Application
Source: Application Error
Date: 6/3/2023 8:15:38 AM
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer: DESKTOP
Description:
Faulting application name: My Garage.exe, version: 2020.3.2.55559, time stamp: 0x605f8b9f
Faulting module name: atidxx64.dll, version: 31.0.14037.17019, time stamp: 0x644698b3
Exception code: 0xc0000005
Fault offset: 0x0000000000ae2406
Faulting process id: 0x42c
Faulting application start time: 0x01d9961abc2b59f1
Faulting application path: C:\Program Files (x86)\Steam\steamapps\common\My Garage\My Garage.exe
Faulting module path: C:\Windows\System32\DriverStore\FileRepository\u0391195.inf_amd64_09ef84849323988b\B391209\atidxx64.dll
Report Id: b496ad20-69ff-44d5-b12c-f59e0cc9bc0b
Faulting package full name:
Faulting package-relative application ID:
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Application Error" />
<EventID Qualifiers="0">1000</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>100</Task>
<Opcode>0</Opcode>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2023-06-03T13:15:38.7537145Z" />
<EventRecordID>754</EventRecordID>
<Correlation />
<Execution ProcessID="0" ThreadID="0" />
<Channel>Application</Channel>
<Computer>DESKTOP-B8AQ2U1</Computer>
<Security />
</System>
<EventData>
<Data>My Garage.exe</Data>
<Data>2020.3.2.55559</Data>
<Data>605f8b9f</Data>
<Data>atidxx64.dll</Data>
<Data>31.0.14037.17019</Data>
<Data>644698b3</Data>
<Data>c0000005</Data>
<Data>0000000000ae2406</Data>
<Data>42c</Data>
<Data>01d9961abc2b59f1</Data>
<Data>C:\Program Files (x86)\Steam\steamapps\common\My Garage\My Garage.exe</Data>
<Data>C:\Windows\System32\DriverStore\FileRepository\u0391195.inf_amd64_09ef84849323988b\B391209\atidxx64.dll</Data>
<Data>b496ad20-69ff-44d5-b12c-f59e0cc9bc0b</Data>
<Data>
</Data>
<Data>
</Data>
</EventData>
</Event>
So, is it still having a problem with atidxx64.dll? I thought you said those issues were resolved. In any case, your best bet is probably to just run the System File Checker tool [support.microsoft.com] now. Comparing the same .dll files on two different computers and replacing one with the other will most likely not solve your problem because of different hardware configurations.
Last edited by Linus Javelson; Jun 3, 2023 @ 6:52am
< 1 2 >
Showing 1-15 of 19 comments
Per page: 1530 50

Date Posted: Jun 2, 2023 @ 5:18am
Posts: 19