MMM
Page 1 of 3 123 LastLast
Results 1 to 25 of 55

Thread: DFI + Hitachi = error code 10DE 0057

  1. #1
    Xtreme Enthusiast
    Join Date
    Nov 2002
    Location
    SoCal, USA
    Posts
    562

    DFI + Hitachi = error code 10DE 0057

    Anybody else getting this error trying to use RAID?

    TIA

  2. #2
    Registered User
    Join Date
    Nov 2004
    Posts
    632
    UPDATE YOUR BIOS TO 2/19 it fixes all issues.
    I have the same HDD
    Tba

  3. #3
    Xtreme Enthusiast
    Join Date
    Nov 2002
    Location
    SoCal, USA
    Posts
    562
    Ok thanks! do you have a link?

  4. #4
    Xtreme Enthusiast
    Join Date
    Nov 2002
    Location
    SoCal, USA
    Posts
    562
    So where is this bios 2/19 that everybody is talking about but nobody knows where to find it?

  5. #5
    Banned
    Join Date
    Jan 2004
    Location
    Land of Buckeye
    Posts
    2,881
    Quote Originally Posted by Unrealcpu
    UPDATE YOUR BIOS TO 2/19 it fixes all issues.
    I have the same HDD

    219? never heard about this version

  6. #6
    Xtreme Enthusiast
    Join Date
    Nov 2002
    Location
    SoCal, USA
    Posts
    562
    OPB,

    Do you know or heard anything about this error I'm getting?

  7. #7
    XS D2OL & RAM News
    Join Date
    Aug 2004
    Location
    Somewhere, USA
    Posts
    3,589
    Which DFI board do you have?

    jjcom

  8. #8
    Banned
    Join Date
    Jan 2004
    Location
    Land of Buckeye
    Posts
    2,881
    Quote Originally Posted by EQuito
    OPB,

    Do you know or heard anything about this error I'm getting?

    I only know 10DE is Nvidia (manufacture code) but I never heard about 2.19 bios..

  9. #9
    Xtreme Enthusiast
    Join Date
    Nov 2002
    Location
    SoCal, USA
    Posts
    562
    nF4 LP UD

  10. #10
    Xtreme Enthusiast
    Join Date
    Nov 2002
    Location
    SoCal, USA
    Posts
    562
    Quote Originally Posted by Onepagebook
    I only know 10DE is Nvidia (manufacture code) but I never heard about 2.19 bios..
    Do you get the code?
    the error code shows right after the "press F10" message. I cannot install XP to these drives. Single or RAID mode XP won't boot from them.
    Hitachi says they're not aware of such error code so it must be an NVRAID bios error.

    Any help is greatly appreciated.

  11. #11
    Banned
    Join Date
    Jan 2004
    Location
    Land of Buckeye
    Posts
    2,881
    Quote Originally Posted by EQuito
    Do you get the code?
    the error code shows right after the "press F10" message. I cannot install XP to these drives. Single or RAID mode XP won't boot from them.
    Hitachi says they're not aware of such error code so it must be an NVRAID bios error.

    Any help is greatly appreciated.

    Well, I installed xp or any OS without any problem, but I do see the code when NV raid rom detect my raid array.
    I will pass this thread to Oskar see if he got any idea.

  12. #12
    XS D2OL & RAM News
    Join Date
    Aug 2004
    Location
    Somewhere, USA
    Posts
    3,589
    http://www.dfi.com.tw/Support/Downlo...&STATUS_FLAG=B

    thats the latest I could find on there website.

  13. #13
    Xtreme Enthusiast
    Join Date
    Nov 2002
    Location
    SoCal, USA
    Posts
    562
    ok thanks!

    Q: do you see 10DE 0057 or just 10DE?

  14. #14
    Xtreme 3DTeam Member
    Join Date
    Dec 2004
    Location
    UK
    Posts
    865
    Quote Originally Posted by Onepagebook
    219? never heard about this version
    exactly, who's using the 219 and could someone plz post a link?, i know of the 209, 217 and 218 but havnt seen a link to the 219

    Opty 144 0546FPMW @ 2.8ghz
    MSI K8N Neo 2
    2 x 512mb OCZ Platinum Rev. 2 TCCD
    ATI X800 Pro @ 570/1200
    Plus some other metal fings...
    Will do me till Conroe
    Heat

  15. #15
    Xtreme Enthusiast
    Join Date
    Nov 2002
    Location
    SoCal, USA
    Posts
    562
    ok I give up, no RAId for me I guess...

  16. #16
    Xtreme Enthusiast
    Join Date
    Jun 2004
    Location
    lake forest, CA
    Posts
    787
    Hey guys I get this same error code using WD 36GB Raptor hard drives, it only pops up if I try to use the RAID function BUT I can't install winXP either (always gets to the part when the actual installation starts after it finishes partitioning/formatting the drive and reboots...).

    I have the 2/1/2005 BIOS installed BTW...

    Anybody got links to any of the later BIOS's that Jamo mentioned (217 and 218 BIOS?) as I'm willing to give it one more shot before I RMA.

    Thanks.

  17. #17
    Xtreme Enthusiast
    Join Date
    Nov 2002
    Location
    SoCal, USA
    Posts
    562
    http://www.xtremesystems.org/forums/...ad.php?t=53553

    Bios 218 bios didn't help me. In fact, I get the same error or message (whatever you wanna call it) every time I hook a SATA drive with any bios, beta or not. I've been trying to install XP to the array for 2 days to no avail.

    I'm don't know what's going on but I don't like it and I'm almost ready to give up on this board.

  18. #18
    Xtreme Enthusiast
    Join Date
    Nov 2002
    Location
    SoCal, USA
    Posts
    562
    btw: another problem I'm having is the board absolutely refuses to boot up after a bios change if I use my HyperX PC3500 BH5...

  19. #19
    Xtreme Mentor
    Join Date
    Jul 2004
    Location
    Ontario
    Posts
    2,780
    does a cmos clearing allow it to boot afterwards?

    I hear a lot of these quirks with this board.
    Silverstone Temjin TJ-09BW w/ Silverstone DA750
    Asus P8P67
    2600K w/ Thermalright Venomous X Black w/ Sanyo Denki San Ace 109R1212H1011
    8GB G.Skill DDR-1600 7-8-7-24
    Gigabyte GTX 460 1G
    Modded Creative X-Fi Fatal1ty w/ Klipsch Promedia 2.1
    1 X 120GB OCZ Vertex
    1 X 300GB WD Velociraptor HLFS
    1 X Hitachi 7K1000 1TB
    Pioneer DVR-216L DVD-RW
    Windows 7 Ultimate 64


    Quote Originally Posted by alexio View Post
    From the hip and aim at the kitchen if she doesn't approve your purchases. She'll know better next time.

  20. #20
    Evil Kitty
    Join Date
    Jun 2002
    Location
    Detroit, MI
    Posts
    3,305
    Sorry to hear about the troubles with the board.

    Keep in mind, the board was originally "tuned" for TCCD memory then things were changed around at the last minute (the delay) to accomodate BH5 better. What resulted was a board that was tuned for niether perfectly. Later BIOSes have improved things a bit.

    Beware of the Optimised Defaults when running BH5. Set everything to AUTO on the DRAM page when running BH5 and tweak slowly. Push the voltahe hard on the memory.

    If you have Gskill tccd, that's what would work best.

    As for the hitachi error, I'll see what I can dig up....
    9900k @ 5.1Ghz
    Asus Maximus Hero XI
    32GB (8 x 4) Gskill @4000
    Strix 2080 Ti OC
    OS & Apps: Samsung 970 Pro 512GB
    Games: Samsung 970 Pro 1TB
    Storage: Crucial M500 2TB
    Seasonic Platinum 1000W
    Phanteks Evolv X

  21. #21
    Evil Kitty
    Join Date
    Jun 2002
    Location
    Detroit, MI
    Posts
    3,305
    Okay, after looking around, I'm seeing other running the new Hitachi SATAII drives successfully on the DFI, so I don't think its a inherent incompatability.

    Going from there, are you loading BOTH drivers on the floppy when you press F6? Are you running BIOS defaults (except the memory which you should set everything to auto). The IDE/SATA BIOS settings should be left at default.
    9900k @ 5.1Ghz
    Asus Maximus Hero XI
    32GB (8 x 4) Gskill @4000
    Strix 2080 Ti OC
    OS & Apps: Samsung 970 Pro 512GB
    Games: Samsung 970 Pro 1TB
    Storage: Crucial M500 2TB
    Seasonic Platinum 1000W
    Phanteks Evolv X

  22. #22
    Xtreme Enthusiast
    Join Date
    Jun 2004
    Location
    lake forest, CA
    Posts
    787
    I leave all memory settings at default except to turn on 2T command rate (or at least I try to, it always says that memory is set to 1T whenever it boots up) and I turn off bank interleave.

    I've pushed the memory all the way up to 3.2v and at default voltages but still its a no go...

    My memory is GeiL PC4400 BTW.

    Also, something else that is strange, I was able to flash the BIOS to the 218 BIOS and when I run MemTest I get all sorts of errors. Now I know this RAM is good as I've had it for almost 6 months now and its been running OC'd in my socket 754 motherboard just fine (EpoX 8KDA3J+) without any errors, but if I plug it into the DFI board even at default settings I get errors...

    I think this board is just f**ked up, so I'll RMA it, unless someone knows for sure that my RAM is incompatible with this motherboard (which makes no damn sense at all since the memory controller is on the CPU die, the motherboard shouldn't effect RAM compatibility at all because of that unless DFI screwed up...).

  23. #23
    Evil Kitty
    Join Date
    Jun 2002
    Location
    Detroit, MI
    Posts
    3,305
    Have you tried this from DFI Streets forum:

    5. Genie Bios first entry at top> DRAM CONFIGURATION
    a1. 200 Dram Frequency 1:1
    a2. Enable CPC
    a3. 2.5
    a4. 04
    a5. 07
    a6. 04
    a7. 07
    a8. 14
    a9. 05
    a10. 03
    a11. 02
    a12. 05
    a13. 3120
    a14. 05
    a15. Bank Interleave= DISABLED You want mediocre memory to run don't you? Then disable it and see how much better the thing will clock and do business right now.

    a16. DQS Skew Control = INCREASE
    a17. DQS Skew Value = 0 (zero)
    a18. Dram Drive Strength= Level 6
    a19. Dram Data Drive Strength= Level 4
    a20. MAX ASYNCH LATENCY = 7X
    a21. READ PREAMBLE= 5X
    a22. IDLE CYLCE= 256 cycles
    a23. DYNAMIC Counter= Disabled
    a24. R/W Que Bypass = 16x
    a25. ByPass Max 7X
    a26. 32 Byte Granularity = Disable 8 Bursts.

    Now in most cases this will take the boards that hate two sticks and problematic with TCCD and some other classes of memory and make them starters and runners and moved me from starting with a starter stick and hardly stable at 225 to 240FSB to now prime95 stable and memtest86 Rev 1.51, test #8 stable for hours @275x9 with my 3000+ Winchester. For many of you it might be worth a try for sure and for some just to see some bigger numbers.

    Key for the present time is to turn off bank interleave so the memory volts can drop and to set MaxAsysnch Latency to 7X and to set Read Preamble to 5x. I have tried this on a couple of weaker TCCD memories and with Crucial Ballistix pC3200 and all the settings will just about work for any marginal or troublesome memory.

    Try it you might be pleasantly surprised at the benches that finish and the stability of your system.
    9900k @ 5.1Ghz
    Asus Maximus Hero XI
    32GB (8 x 4) Gskill @4000
    Strix 2080 Ti OC
    OS & Apps: Samsung 970 Pro 512GB
    Games: Samsung 970 Pro 1TB
    Storage: Crucial M500 2TB
    Seasonic Platinum 1000W
    Phanteks Evolv X

  24. #24
    Xtreme Enthusiast
    Join Date
    Jun 2004
    Location
    lake forest, CA
    Posts
    787
    Just tried that, still fails test #5 on que...

    Anyone know if there is a link that lists incompatible RAM for the DFI nF4 Ultra-D?

  25. #25
    Fused
    Join Date
    Dec 2003
    Location
    Malaysia
    Posts
    2,769
    check the sticky DFI bug and fix thread

Page 1 of 3 123 LastLast

Bookmarks

Bookmarks

Posting Permissions

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