E67 Error on a XeDK

Discussion in 'Xbox 360 Development' started by dulledblade, Dec 18, 2009.

  1. dulledblade

    dulledblade Guest

    So I've got a E67 error on a XeDK, which is a system error (I read somewhere it's a hard drive issue). Any suggestions?

    Thanks!
     

    Attached Files:

    • 12.jpg
      12.jpg
      File size:
      42.4 KB
      Views:
      339
  2. LEo

    LEo Fiery Member

    Joined:
    Jan 19, 2008
    Messages:
    845
    Likes Received:
    16
    Well try removing the hdd and then booting it up. Taking off the sidecar is a pain in the butt, but really I see no other way

    Edit on a second thought, have you tried booting it up with a recovery in place?
     
    Last edited: Dec 18, 2009
  3. dulledblade

    dulledblade Guest

    Haven't yet, but I will try, thanks.
     
  4. Pikkon

    Pikkon "Moving in Stereo"

    Joined:
    Mar 4, 2005
    Messages:
    2,695
    Likes Received:
    80
    Well first just disconnect the sidecar then boot your 360 up to see if the hdd is done for.
     
  5. l_oliveira

    l_oliveira Officer at Arms

    Joined:
    Nov 24, 2007
    Messages:
    3,879
    Likes Received:
    245
    Out of curiosity, isn't HDD error "E68" ?
     
  6. Pikkon

    Pikkon "Moving in Stereo"

    Joined:
    Mar 4, 2005
    Messages:
    2,695
    Likes Received:
    80
    Error 67,68,69 and 70 are hard drive errors.
     
  7. l_oliveira

    l_oliveira Officer at Arms

    Joined:
    Nov 24, 2007
    Messages:
    3,879
    Likes Received:
    245
    Care to detail what specifically is each ? :)
     
  8. TheFallen93

    TheFallen93 Spirited Member

    Joined:
    Apr 22, 2009
    Messages:
    167
    Likes Received:
    68
    The error numbers are actuall misleading. When the console boots it runs various functions that do stuff with hardware, If one of them fails and returns a non 0 value, the console calls VdDispayFatelError, and passes the return value to it. That's the error number you see, and the LED sequence to blink. The only real way to tell what went wrong is by the secondary error code. You can get E-67 and it could be like 10 different things that are completly unrelated.
     
  9. kratosjohn

    kratosjohn Guest

    I'm getting 0110 secondary on my demo kit, any clue?
     
  10. corranga

    corranga Rapidly Rising Member

    Joined:
    Mar 13, 2013
    Messages:
    97
    Likes Received:
    3
    I have the same error on one of my XDKs, new to the scene so lots to learn, but I'm hoping this can be sorted :O

    Chris
     
    Last edited: Mar 14, 2013
  11. gumshield

    gumshield Active Member

    Joined:
    Mar 12, 2013
    Messages:
    29
    Likes Received:
    0
    One of the dev kits I picked up had the 67 error and as suggested I took of the hard drive. Problem solved, I guess 8yr old hard drives sitting in storage don't do too well.
     
  12. Bunny

    Bunny Spirited Member

    Joined:
    Jan 1, 2013
    Messages:
    156
    Likes Received:
    2
    That is a Ram error.

    Fix it by:
    1) Reflow the RAM
    2) Loosen your heatsink screws and make sure the heatsink isnt shorting out a capacitor...
    3) Look for missing and bridged components like resisitors and caps and replace them
    4) X-Clamp replacement
     
sonicdude10
Draft saved Draft deleted
Insert every image as a...
  1.  0%

Share This Page