Still getting BSOD with this game

[Elysium]

I can't believe after so much time I still get this horrible BSODs.

My temps and drivers are fine.. no virus and my setup is less than a year old

I play many other games and no problems.. but FF XIV ARR crash my computer at random times.. I can play sometimes for hours and hours.. even weeks with no problems but suddendly the game crashes my computer with error BC Code 124 hall.dll

My computer crashes only with this game.. I'm Playing Batman Arkham Origins right now finished the entire game and playing the dlc now.. not one BSOD. I play many other games and no BSODs also

I've had this problem since months ago and was never fixed.. any tips or workaround to avoid this horrible BSODs?

[RaphaelDDL]

BSOD? Really? That just happens on Win7 when your RAM is damaged (and trying to allocate on damaged part causes fatal error), never seen happening otherwise.

My laptop is 5y old, with I3 1st gen, 4GB RAM and 512mb RAM Radeon.
Therefore is not the game, is your computer which the other games might not use all your ram. FF14 DO use.

The easiest way to test your RAM:
Press Start Menu;
Type memory on the search and press enter;
Pick your choice: restart now to test or test on next boot;

More info on
http://www.pcadvisor.co.uk/how-to/pc-upgrades/3432631/how-check-for-bad-ram-modules-in-your-pc/ and http://www.computerhope.com/issues/ch000708.htm

Both tell about the memory option (windows own tool) and also MemTest86 which is a 3rd party program that can help you too.

[Raist]

Those stop errors can be caused by any number of things... faulty ram, overstressed cache on the CPU (more common if overclocking), overheating, screwy drivers that try to access locked memory, corrupted page file, even something as simple as a corrupted/failing sector on the hard drive....and those are just a handful of the more common ones.

This game thrashes the heck out of your CPU, Memory, and at times your hard drive as well. More so than some of those other games likely do, simply because of how they are coded (a good bit of XIV's DirectX is emulated and relies heavily on your CPU, simply because it is using shoddy DX9 implementation and not a more proper DX10/11 environment).

If you can note the actual stop error and hex-code (like "IRQL_NOT_LESS_OR_EQUAL" with a checksum of 0x0000000A, or PAGE_FAULT_IN_NONPAGED_AREA with a checksum of 0x00000050) it may shed more light on just where your problem lies. It may be logged in your Event Logs (eventvwr.msc from the run or search line) with more details listed (some of the argument codes can give further clarification).