Results 1 to 4 of 4
  1. #1
    Player
    Natakeu's Avatar
    Join Date
    Aug 2013
    Posts
    15
    Character
    Kalerea Valewind
    World
    Balmung
    Main Class
    Arcanist Lv 70

    Intermittant Crashing

    I have followed all the steps from Microsoft windows 8.1 to troubleshoot the issue from their side. The issue at hand is that while running the game I consistently get windows to crash with the error Critical_Process_Died. In my last encounter with it happening the game responded with a sub prompt before windows forced a complete shutdown and reboot. I was not able to read what the prompt said because windows reacted so swiftly. Furthermore the issue seems to happen primarily when I am in a dungeon instance. The when of the error remains a mystery to me since it can happen at any time. The only thing I wish to add is that this problem only started to happen after the update to 2.4.
    (0)
    Last edited by Natakeu; 11-03-2014 at 09:19 PM.

  2. #2
    Player
    Squa11_Leonhart's Avatar
    Join Date
    Aug 2013
    Location
    Gridania
    Posts
    1,123
    Character
    Kaya Yuuna
    World
    Cerberus
    Main Class
    Archer Lv 70
    This is either driver fault, hardware instability or failure, user mode software such as games cannot just reboot or crash a system.
    (0)

  3. #3
    Player
    ErnestoGiovanni's Avatar
    Join Date
    Mar 2011
    Location
    Gridania
    Posts
    159
    Character
    Ceropio Malvae
    World
    Mateus
    Main Class
    Conjurer Lv 59
    I am having the same issue since patch 2.4, I had it previously with patch 2.2x and it happened regularly until the next patch it was fixed. It says it is an interrupted stop clock function on a secondary processor, if that helps.
    (0)

  4. #4
    Player
    Squa11_Leonhart's Avatar
    Join Date
    Aug 2013
    Location
    Gridania
    Posts
    1,123
    Character
    Kaya Yuuna
    World
    Cerberus
    Main Class
    Archer Lv 70
    "A clock interrupt was not received on a secondary processor within the allocated time interval" is caused by a faulty cpu, unstable overclock, or failing voltage regulation on the systems motherboard.
    (0)