A system I'm working on will run the benchmark and game just fine, and ran the beta through open beta with no issues, however it intermittently crashes and throws one of the two following crash errors. After it crashes it has no problem restarting and running again.
This is a new computer running windows 7 64 bit. I'm using a gtx 460 1 gig card, an amd phenom II x6 @2.8ghz, 4 gigs of ram, and a 1.5 TB hard drive.
I've run a memory diagnostic and run checkdisk but neither gave any indication of a problem. I uninstalled and reinstalled FFXIV but it is still crashing. I've tried both the regular nvidia drivers and their new beta drivers. The system has had no other issues, however the only game it's run is FFXIV. Below are the two errors it gives:
Problem signature:
牋Problem Event Name: BEX
牋Application Name: ffxivgame.exe
牋Application Version: 1.0.0.0
牋Application Timestamp: 4c9a72c1
牋Fault Module Name: ffxivgame.exe
牋Fault Module Version: 1.0.0.0
牋Fault Module Timestamp: 4c9a72c1
牋Exception Offset: 0053ec98
牋Exception Code: c000000d
牋Exception Data: 00000000
牋OS Version: 6.1.7600.2.0.0.256.1
牋Locale ID: 1033
牋Additional Information 1: 0da8
牋Additional Information 2: 0da8196e001301c5dcf9a28c736909a0
牋Additional Information 3: e1d4
牋Additional Information 4: e1d4fcf483dd8d1fce95aec021f8970c
and
Problem signature:
牋Problem Event Name: APPCRASH
牋Application Name: ffxivgame.exe
牋Application Version: 1.0.0.0
牋Application Timestamp: 4c9a72c1
牋Fault Module Name: StackHash_0a9e
牋Fault Module Version: 0.0.0.0
牋Fault Module Timestamp: 00000000
牋Exception Code: c0000005
牋Exception Offset: a0e40000
牋OS Version: 6.1.7600.2.0.0.256.1
牋Locale ID: 1033
牋Additional Information 1: 0a9e
牋Additional Information 2: 0a9e372d3b4ad19135b953a78882e789
牋Additional Information 3: 0a9e
牋Additional Information 4: 0a9e372d3b4ad19135b953a78882e789stackhash
·English·Theme
- Forums
- Cross Site
- Computer Hardware & Troubleshooting
- Stackhash crash?
Stackhash crash?Follow
While this has been showing up more for nVidia cards, it isn't exclusive--started showing up for some ATI 5770's as well. It may be a memory leak of sorts. While it could be driver related, it's been showing up for games that work fine in XP, but tank in Win7. While that doesn't rule out it being a drivger issue, it could be more OS specific--or perhaps even DirectX related.
If you haven't tried it yet, might be worth checking for a DirectX update. There was a minor revision to some of the DX9c components in June, you might need them:
http://www.microsoft.com/downloads/en/details.aspx?FamilyID=2da43d38-db71-4c1b-bc6a-9b6652cd92a3
That's the webupdate tool which should only grab updated files. If it still is flaky, you could try grabbing the full redistributable or even the beastly SDK to be doubly sure (will install older components that might not really be needed for FFXIV, but could solve missing DLL problems with older games if you are getting them).
Raist
If you haven't tried it yet, might be worth checking for a DirectX update. There was a minor revision to some of the DX9c components in June, you might need them:
http://www.microsoft.com/downloads/en/details.aspx?FamilyID=2da43d38-db71-4c1b-bc6a-9b6652cd92a3
That's the webupdate tool which should only grab updated files. If it still is flaky, you could try grabbing the full redistributable or even the beastly SDK to be doubly sure (will install older components that might not really be needed for FFXIV, but could solve missing DLL problems with older games if you are getting them).
Raist
7 posts
Good to know about the directX update, I'll try that tonight.
So as a follow up to this, it turns out this crash only happens when playing fullscreen at 1280x1024 (which was the native resolution of the monitor being used). Playing in windowed mode or connecting a different monitor (running at 1440x900) allowed for stable play. The question now becomes why would it behave this way?
So as a follow up to this, it turns out this crash only happens when playing fullscreen at 1280x1024 (which was the native resolution of the monitor being used). Playing in windowed mode or connecting a different monitor (running at 1440x900) allowed for stable play. The question now becomes why would it behave this way?
Sounds like a software/firmware glitch. Could possibly even be some sort of memory/GPU problem (design flaw perhaps). There are a lot of bug reports being filed out there. Hopefully someone will pin it down soon.
Raist
Raist
could be a bad video card ram register. That wouldn't be likely though.
Arch Duke Kaolian Drachensborn, lvl 95 Ranger, Unrest Server
Tech support forum | FAQ (Support) | Mobile Zam: http://m.zam.com (Premium only)
Forum Rules
Tech support forum | FAQ (Support) | Mobile Zam: http://m.zam.com (Premium only)
Forum Rules
4 posts
When an application crashes, a Problem Report is sent to Microsoft. The developer of the application can log on to the Microsoft WinQual site and download problem report information associated with the applications they have developed. This information is used to help identify the cause of the error hopefully resulting in a fix. If the error is identified and fixed, the developer will post a "response" on the Microsoft web site. This response may be that a new version or patch to the application is available to fix the issue, or it might be a description of a workaround. Either way, your PC will periodically check for fixes to previous problems on the Microsoft site and alert you if solutions are available,A virus checker, virtual drive S/W, security systems (or other application) has injected a piece of code into the address space of the application that crashes for some reason. In this case there is no identifiable module so a StackHash_XXXX will be created.
Recent Visitors: 19
All times are in CST
Anonymous Guests (19)
- Forums
- Cross Site
- Computer Hardware & Troubleshooting
- Stackhash crash?
© 2025 Fanbyte LLC