Don't even bother contacting support if you have a crash issue.

[Raist]

the 0xc0000005 errors are some of the worst to diagnose. Without seeing the additional parameters given with the blue screen or (hopefully) saved with the event log, it is hard to narrow down where the culprit may be. It is basically reporting an access violation error--often bound to a problem with a driver. Something has locked a memory address and then something else tried to use the same space (or it was otherwise unresponsive--so it could actually be a physical problem).

It could be a driver for any device on your system--even something not bound to hardware like antivirus or a firewall. Could even be malware for that matter. Could be a corrupted swap file or bad sector within the swap file. Could be a bad cell in the memory. It could even be tied into a bad Windows Update (it has happened before).

Basically--something tried to access a memory location that was in use, locked, or otherwise could not access it. Anyone trying to help you track it down is going to need more information on your system--may be better to find someone locally that is computer savvy if you can. There is a LOOOOONG laundry list to go through. It may require you to strip every nonessential hardware/device from running while you try to play the game to try to narrow it down...and even then you may still come up empty-handed.

[MrBinary]

the 0xc0000005 errors are some of the worst to diagnose. Without seeing the additional parameters given with the blue screen or (hopefully) saved with the event log, it is hard to narrow down where the culprit may be. It is basically reporting an access violation error--often bound to a problem with a driver. Something has locked a memory address and then something else tried to use the same space (or it was otherwise unresponsive--so it could actually be a physical problem).

It could be a driver for any device on your system--even something not bound to hardware like antivirus or a firewall. Could even be malware for that matter. Could be a corrupted swap file or bad sector within the swap file. Could be a bad cell in the memory. It could even be tied into a bad Windows Update (it has happened before).

Basically--something tried to access a memory location that was in use, locked, or otherwise could not access it. Anyone trying to help you track it down is going to need more information on your system--may be better to find someone locally that is computer savvy if you can. There is a LOOOOONG laundry list to go through. It may require you to strip every nonessential hardware/device from running while you try to play the game to try to narrow it down...and even then you may still come up empty-handed.

Thank you for the reply, I am well aware of the difficulty of trying to diagnose this and how many things could be the cause. The issue I am bringing up is not the error as there is a whole separate forum dedicated to it, but more the way SE handled the ticket and the pure absurdity of the reply I received.

This was to draw attention to the pure lack of quality of SE's support.

[sucht]

the 0xc0000005 errors are some of the worst to diagnose. Without seeing the additional parameters given with the blue screen or (hopefully) saved with the event log, it is hard to narrow down where the culprit may be. It is basically reporting an access violation error--often bound to a problem with a driver. Something has locked a memory address and then something else tried to use the same space (or it was otherwise unresponsive--so it could actually be a physical problem).

It could be a driver for any device on your system--even something not bound to hardware like antivirus or a firewall. Could even be malware for that matter. Could be a corrupted swap file or bad sector within the swap file. Could be a bad cell in the memory. It could even be tied into a bad Windows Update (it has happened before).

Basically--something tried to access a memory location that was in use, locked, or otherwise could not access it. Anyone trying to help you track it down is going to need more information on your system--may be better to find someone locally that is computer savvy if you can. There is a LOOOOONG laundry list to go through. It may require you to strip every nonessential hardware/device from running while you try to play the game to try to narrow it down...and even then you may still come up empty-handed.

if the problem was on my PC(or on somebody else's pc for that matter), be it hardware, software or what ever, then this error is bound to come up with other applications/games that use directx11 and x64, but i have this problem just with Final Fantasy XIV and i bet that this is true for most if not all People complaining here on this forum.

[Raist]

if the problem was on my PC(or on somebody else's pc for that matter), be it hardware, software or what ever, then this error is bound to come up with other applications/games that use directx11 and x64, but i have this problem just with Final Fantasy XIV and i bet that this is true for most if not all People complaining here on this forum.

not necessarily...not with the way Windows runs on Virtual Memory, amongst a host of other variables at play.

[sucht]

not necessarily...not with the way Windows runs on Virtual Memory, amongst a host of other variables at play.

you are right of course, i always forget that we are talking about Windows and the things it does
but i think it would have been better to not make the game x64 directx11, they should have just polished the directx9 stuff like AO, bad Shadows and so on.

and sorry MrBinary for hijacking your thread, and talking about the same stuff discussed in other threads about the damn directx11 crashes.