1. #1

    This application has encountered a critical error: ERROR #134 Fatal Condition

    I was on a blimp from Tirisfal Glades to Ogrimmar when I got this error message:

    This application has encountered a critical error:
    ERROR #134 (0x85100086) Fatal Condition
    Program: C:\Users\Public\Games\World of Warcraft\WoW.exe
    Failed to read file World\Maps\Kalimdor\Kalimdor_40_26_tex0.adt.
    Press OK to terminate the application

    Then I got this "Wowerror" window:

    The following data will be sent to Blizzard when you click Send
    Though you can opt not to send this information, doing so will help us to improve the game.
    Describe what you were doing when the crash occured

    ==============================================================================
    World of WarCraft: Retail Build (build 13329)

    Exe: C:\Users\Public\Games\World of Warcraft\WoW.exe
    Time: Dec 11, 2010 9:55:54.980 AM
    User: *********
    Computer: *********
    ------------------------------------------------------------------------------

    This application has encountered a critical error:

    ERROR #134 (0x85100086) Fatal Condition
    Program: C:\Users\Public\Games\World of Warcraft\WoW.exe

    Failed to read file World\Maps\Kalimdor\Kalimdor_40_26_tex0.adt.

    Debug Details:

    [15] err=0 text=SFileReadFile - World\Maps\Kalimdor\Kalimdor_40_26_tex0.adt - Data/Cache/patch-base-13164.MPQ
    [14] err=87 text=System_Mopaq::mopaq_read - fail to repair offset 0 amount 1895996
    [13] err=87 text=System_Mopaq::SectorReadHandler::InitializeAndRead - fail to repair offset 0 amount 1895996
    [12] err=87 text=System_Mopaq::SectorReadHandler::ReadData - fail to repair non-streamed file offset 0 amount 1895996
    [11] err=1006 text=RepairCacheFile - Error in deleting World\Maps\Kalimdor\Kalimdor_40_26_tex0.adt
    [10] err=104 text=System_Mopaq::SectorReadHandler::ReadAndDecompressData - PerformRead error 0 472 1553373 1895996 entry: 1243161494 1553845 1895996 2214593024 0
    [9] err=1006 text=System_Mopaq::MD5VerifyData::ValidateRead - InitializeMD5Buffer fail 2 472
    [8] err=1006 text=System_Mopaq::MD5VerifyData::ValidateBlock - ValidateBlock fail 20 16384 3 0
    [7] err=1006 text=Blizzard::Mopaq::MpqRepairOnDemandErrorHandler::HandleMD5BlockError - MarkOffsetRemote error (block #20, amount = 16384)
    [6] err=1006 text=MarkOffsetRemote - Failed to mark data (offset = 1243489174, length = 16384) remote
    [5] err=1006 text=System_Mopaq::MD5VerifyData::ValidateBlock - ValidateBlock fail 20 16384 2 0
    [4] err=1006 text=Blizzard::Mopaq::MpqRepairOnDemandErrorHandler::HandleMD5BlockError - MarkOffsetRemote error (block #20, amount = 16384)
    [3] err=1006 text=MarkOffsetRemote - Failed to mark data (offset = 1243489174, length = 16384) remote
    [2] err=1006 text=System_Mopaq::MD5VerifyData::ValidateBlock - ValidateBlock fail 20 16384 1 0
    [1] err=1006 text=Blizzard::Mopaq::MpqRepairOnDemandErrorHandler::HandleMD5BlockError - MarkOffsetRemote error (block #20, amount = 16384)
    [0] err=1006 text=MarkOffsetRemote - Failed to mark data (offset = 1243489174, length = 16384) remote

    ========================

    So I closed all 3 open windows, and restarted WoW.
    Restarted my PC, then tried playing WoW, same thing.
    Restarted WoW, tried to log on as my lowbie Orc mage, worked fine. Once I started walking towards Ogrimar from Razor Hill, same thing.
    Restarted WoW, tried to log in my Level 80 DK who is in Orgrimmar, got the same thing.
    Tried running WoW on my laptop (13in Macbook Pro, using the character that was causing WoW to crash), it works OK
    Tried logging in to WoW on my desktop, logged in as my lowbie Tauren Paladin, who is in Mulgore, and it works OK.
    Have NOT tried reinstalling WoW (Unless a blue poster specifies to try that.)

    I am very very very frustrated that I cannot log in my main character. Am I the only who is having this issue? Please help.

  2. #2
    Mechagnome Minifig's Avatar
    Join Date
    Oct 2010
    Location
    Legoland.
    Posts
    534
    Run the repair tool.

  3. #3
    High Overlord Battlecry's Avatar
    Join Date
    Oct 2008
    Location
    England
    Posts
    115
    Hi carlitos ,
    My Brother recently had this error or something very similar . He tried many things to fix it , including Running the repair tool but with no luck . He had a blue post yesterday asking him to go into ur warcraft files . It was Warcraft/Data and then delete his cache file and then to run the repair tool in that order and this worked , hope this works for you .

  4. #4
    Tried using the Wow Repair tool, didnt work either.

    ---------- Post added 2010-12-11 at 10:32 AM ----------

    Quote Originally Posted by Battlecry View Post
    Hi carlitos ,
    My Brother recently had this error or something very similar . He tried many things to fix it , including Running the repair tool but with no luck . He had a blue post yesterday asking him to go into ur warcraft files . It was Warcraft/Data and then delete his cache file and then to run the repair tool in that order and this worked , hope this works for you .
    Thank you!!! It worked!!!

    ---------- Post added 2010-12-11 at 10:32 AM ----------

    Thank you everyone. This issue may now be closed.

  5. #5
    Google "ERROR #134 (0x85100086) Fatal Condition" and start reading.
    One of the good things about having a huge player base is that this error will happen to load of folks.

    Edit- hmmm never start a post and go do something else before finishing it or else you get this.
    And answer was figured out in the time between.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •