Jump to content


  • Content Count

  • Joined

  • Last visited

Everything posted by Cazlone

  1. I resolved my SATA problems. Turns out the MB was faulty, as the drive wasn't even spinning up. RMA'd it and the new board works fine. In your case you might have a problem specifically related to the Maxtor DM drive - there are a lot of posts in here about Maxtor specific issues on these boards. You should do a search for Maxtor Diamondmax problems......
  2. All, I think the answer is probably so obvious I shouldn't be asking but I haven't been able to find it written odwn anywhere so figured I'd check in with the experienced members of this forum. My Hitachi T7K250 HD is an SATA2 drive, buts ships in SATA1 mode. I need to run the manufacturers FTool programme to enable SATA2 (and NCQ I believe). It comes with dire warnings that this will make the drive unusable on any SATA controller that is not SATA2 compliant. I believe that the NF2 SLi-DR chipset SATA ports (1-4) ARE already SATA2, but do I need to do anything in the BIOS to enable this (I can find a Command Queueing option but no SATA2/1 option)? Do I need to change anything in a Windows driver? My guess is that all I need to do is enable Command Queueing in the BIOS, run the FTool programme and enable NCQ and SATA2 on the HD and it should all work fine. But given the Warnings i'd like to be sure Can anyone advise? Thanks
  3. Just a quick question regarding the 12V rails on my PSU. It has 2 rails, combined its rated at 34A, split each rail is up to 20A. If I have all 4 power connectors connected on my NF4 SLi-DR, would I be better off using the split rails or running in combined mode? When using split rails, does the PSU run one rail into the the ATX 24 pin connector and everything else off the second rail? Is this therefore more stable as the CPU gets its own power supply effectively? I'd appreciate the education....
  4. I have a similar problem with my Hitachi T7k250. Detection on the NV SATA ports 1-4 became increasingly infrequent until eventual nothing I would do got it detected by the BIOS. My first thought was that it was the HD, but I noticed that the drive wasn't spinning up on power up. This on a fully stable system, with variable HD startup delays set in Bios. Confusingly it got "gradually" worse, until no detection at all. Port 1 was first to go then port 3 worked for a while, then that stopped too. Tried swapping cables etc no change. However, when I put the HD onto the Si3114 ports it immediately span up on power up, and was detected by the Si3114 BIOS (though wouldn't boot to WinXP). The DFI engineer suggested on this basis that the MOBO was faulty and so its been RMA'd. Not saying its completely clear cut since it could be to do with BIOS settings (though the 23 passes of memtest and lack of HD power up when on ports 1-4 made me suspicious).
  5. Had the same problem only with the Nvidia SATA ports 1-4. Became gradually unable to recognise HD on any of these ports, and the HD wasn't spinning up on boot up. When I plugged it into the Si3114 ports the HDD was recognised and span up immediately on power up. Confirmed with DFI engineer that this was likely a board problem and had to RMA the board. Sounds like you have similar problem only on the SI ports. Try swapping HDD to the ports 1-4 and if detected you've a problem on the SI ports. Try it with your case open and your hand on the HDD to detect the vibration (with usual safety precautions....).
  6. Thanks - I know I don't need to install any drivers, but was under the impression that the BIOS comes with some NVidia drivers built in to allow it to know how the chipset works etc (when you look at the DFI bios site it refers to NVxx 4.xx included in the BIOS file for example). I was asking therefore whether the nvidia sata stuff embedded in the BIOS might be the problem. Clearly my problem is not a WinXP problem. Incidentally, I could not install WinXP without using the F6 option and installing dirvers from the floppy no matter what I did. the install would stall quoting something about missing hardware (namely the HDD). When I used the F6 option and only installed the drivers for IDE not RAID it worked fine. In any case since I can't get the HDD to be recognised, any solution involving Windows isn't going to help me!!!
  7. OK, if that fixed it it implies the problem is with the NVidia drivers embedded in the BIOS? and that the NVRaid drivers are ok? Would a BIOS upgrade therefore help if it had different drivers in it? Also, if I change my set up now to a JBOD array will I lose the data on the disk?
  8. I'm having serious trouble getting the MB to detect my SATA HDD with any regularity at all. I've searched and read most of the posts relating to this issue and I think it might have to be an RMA job, but before I do that I thought I'd try one last check. System set up as below. Followed the WinXP install guide on this forum to get it stable, and flashed to the official 623-3 BIOS to solve instability problems relating to not supporting SD chips. Finally got memory stable at stock speeds, Memtest passing overnight 23 passes no errors at 2-2-2-5 and 2-2-3-6. Windows installed and stable (WinXP Pro SP2). Throughout whole process always had intermittent problems with the BIOS detecting the Htachi T7k250 HDD in single disk mode, all RAID functions disabled, all SATA ports enabled. Usually on cold boot it wouldn't find the HDD on SATA1 without going into the BIOS to manually detect it. SATA1 eventually stopped working at all. Moved it to SATA3 after reading threads here suggesting that might help, and sure enough it worked fine for 5-7 days, but y-day it didn't detect first time but did when done so manually in the BIOS, and finally this morning it would detect at all on any SATA port either through BIOS or direct. HDD LED coming on fine so think its getting power. Have varied the detection delay in the BIOS but makes no difference. Put it onto SiL controller ports, and it is detected by the SiL bios (in SATA only mode in BIOS). WinXP however won't boot, it offers Safe mode options but immediately gives BSOD reboots once past that stage. Can't read the error code cos its too fast. Given that the HDD has worked fine once detected in the past I'm not convinced its an HDD problem. Haven't yet tried changing the cable but will do so tonight. If that doesn't help am I looking at a Mobo chipset problem? Can't remember chipset voltage, though NB temp showing 52C no matter what I do (fairly hot room). Would increasing chipset voltage help? Supplier have sent me an RMA code for both the Mobo and HDD, as they weren't sure which was at fault. Any advice before I send t back? Many thanks......
  9. OK thanks, so that would be a recommendation to bypass the 310 bios and go to 510, as some of my problems may be related to lack of support for my particular chip? 510-3 or 510-1 for OCZ PC 4800 (TCCD i think)?
  10. All, just recently built a new system with specs as below in signature. I finally got windows to install by following RGOne's winXP install guide. Its still not entirely stable but I think this is BIOS/Ram related. My board came with the 1-25 bios presintalled, which I gather isn't exactly optimal..... I haven't flashed to a new version yet. BIOS Settings as per RGOne guide below I'm having a few stability problems and have a few questions that hopefully you'll be able to help me out on: 1. Sometimes my pc boots and sometimes it doesnt - most common error is not finding HD and gving system boot error - please insert disc. Usually rebooting solves this. Windows locks up fairly regularly but this is probably the same problem. I'm thinking this is most likely solvable with a BIOS upgrade right? 2. The DFI manual for the MB shows that polarity for the MB FDD-style power connector as having 12V on pin one but my PSU only fits with the 5V on pin 1. I didn't cause a probelm first time i booted and someone suggested this was a known error in the manual - is this tru and should I just fit it anyway? 3. With OCZ PC4800 plat I ought ot be able to run 2-2-2-5 timings at around 2.8V at 200HT 1:1 right? Its only when I increase the freq that I might need to loosen the timings? 4. Finally - when I download the bios flash .exe files from DFI's website, my understanding is that when I run them it installs everything I need onto the floppy so I don't need to add boot-type files? Or is this incorrect? You know, I know its an enthusiasts board designed for tinkering, but there really should be a health warning before you buy. That you can't simply plug in your bits and boot first time (albeit at slow but stable settings) - is this normal? Any help appreciated. RGONe guide settings: a. Make sure Erratta94 is disabled. b. Turn off cpu throttling. c. Set Pci pay load to 256mb and not default 4096 or to what your memory on video card actually is. d. I usually set hard drive delay to 2 seconds in order to give them time to spin up before the bios tries to read them. Especially good for some PATA drives but I use on all. e. Think that covers most of the odd things outside the Genie Bios expcept I turn off any Lan, Firewire, Serial Port and any other thing I am not using except I never ever turn off any SATA drive as long as I use ANY sata product. Now to the Genie Bios and these numbers are going to be conservative because I know some of you are scared and have a hard time undestanding that if you plan to run fast you must add volts and I have run considerable more but now have settled well on to these and I really do not care to debate the issue as these work and I have spent considerable energy to get this all to work on a broad cross reference of setups to get UP and GOING. a. Genie Bios first page from the top down and remember to turn off all at bottom you are not using. a1. LTD/FSB = X4.0 a2. CPU/FSB Frequency Ratio Manual Set to what Your Default Multiplier Is. a3. PCI EX Frequency = 105 ATI video cards Nvidia 100 or 101. a4. Cpu Startup VID = 1.425 Volts. a5. CPU VID 1.425 Volts. a6. CPU VID Special Control = 110% and this is around 1.52Volts total and is far and way fine as I have run it with OEM HSF and never gotten over 46C full tilt with 3000+ Winnie. Note we are trying to throw out all variables and get running and you then tune up or down on your own. Maybe I tell you too much but this is 72 hours worth of work. a7. LTD voltage = 1.4 Volts. a8. Chipset Voltage = 1.8 Volts. a9. Dram Voltage = 2.9 Volts. 5. Genie Bios first entry at top> DRAM CONFIGURATION a1. 200 Dram Frequency 1:1 a2. Enable CPC - not an option in 1-25 bios!! 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.
  11. I've just built myself a new system based on the DFI NF4 sli-DR MB, with A64 3700+ SD. I put everything together, plugged all the power connectors in to the relevant places and booted into the BIOS. It all looked good, I was able to detect all the drives and memory, the fans were working etc. However, after coming out of the BIOs, rebooting and trying to install WinXP Pro from the disc, the machine reads from the CD, tehn posts " Setup is testing your hardware configuration....." and just sits there. For hours. Nothing happens. Clearly I've got some sort of hardware config problem. Ive checked all the cables and reseated everything. Only thing I noticed was that onthe MB floppy style power connector, the manual says the right hand pin (pin1) is +12V. My TAGAN PSU's FDD connector will only fit into the slot one way round, and it shows the pin 1 connector is +5V. Am I mistaken or is this a problem? Any help would be appreciated - I've checked the various guides on installation, and I will follow them (resetting bios, one set of DDR only, etc etc), but any other views would be appreciated.
  • Create New...