Results -9 to 0 of 3

Threaded View

  1. #3
    Player
    Raist's Avatar
    Join Date
    Aug 2013
    Posts
    2,457
    Character
    Raist Soulforge
    World
    Midgardsormr
    Main Class
    Thaumaturge Lv 60
    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).
    (1)
    Last edited by Raist; 04-26-2014 at 06:06 AM.