Jump to content

sniper007

Members
  • Posts

    46
  • Joined

  • Last visited

sniper007's Achievements

Newbie

Newbie (1/14)

  1. Fixed this by doing the following: Booted with one of the two drives in my mirror array attached to the mobo with raid enabled and instead of detecting array, got an error in array message. Was able to get into raid options by hitting F10 and deleted this disk from array. Fired up machine with other drive attached on its own and deleted that from array also. Then booted with both and was able to setup an array from scratch. So it seems as though the array got completely corrupt. Possibly due to overclocking.
  2. Sorry my signature although i updated it is currently on the 704-2bt BIOS Tony modded one. Hmm any other ideas? Im pretty stumped.
  3. But I've tried a single DIMM in there and also tried different settings - 1t and 2t and has no affect. The memory passes mem test in dual channnel mode at 1t @ 220mhz and is superpi 32m stable. I have tried running it at stock and even lower settings and settings I know that work, and there is no difference. I really get the impression, that this is NOT a memory issue. It still has the same problem with complete CMOS resets and optimised defaults loaded.
  4. I have a problem with RAID on my Ultra-D. Originally, I had a problem whereby windows would NOT restart or shutdown and would hang. I fixed this issue by using the 6.86 nvidia forceware driver package as opposed to the 5.53 ? ones on DFi site. This fixed the issue for me. One thing I did notice with the 6.86s though, is that they did not install the Nvidia MAss Storage / raid software to tell of the status of RAID arrays etc. Anyway... I have my system setup to run windows from my IDE main drive, and then a RAID 1 array off of two SATA drives. This is a new build, and as soon as I enabled RAID, everything worked fine, except that on start up intermittantly windows decided it needed to do a checkdisk to check the consistency of data on my RAID Volume. This soon started ot be everytime I started windows which ever way. After a day or so of using the system to try to solve this problem of checking disks each time windows started, I decided to enter the nvidia RAID BIOS to rebuild my array from scracth. I hit rebuild on both drives and then exited, assuming that the system would rebuild, and all I get now on boot up is the usual nvidia RAID bios message but then get a "DETECTING ARRAY" and it just hangs. I used to get a "HEALTHY ARRAY" message where my mirror'd array was detected fine. It then sits on this message infinitely and also will not allow me to enter the BIOS. If I unplug the sata drives and/or disable raid in BIOS the system boots fine and I can get into setup as well. The drives are detected fine in the BIOS and are both healthy and are found in windows when RAID is not enabled. But everytime I go to enable raid even on different sata ports, I get this same hanging problem on "DETECTING ARRAY". I dont even care if I have lost the array and need to rebuild from scratch, but I cant do anything with raid enabled at the mo, and just get that same message, like the nvidia raid BIOS is corrupt. I have also tried CMOS reset and load optimmised default. I haven't tried re-flashing to another BIOS yet as I though the nvidia RAID bios was held in its on right on a different BIOS chip? I have performed searches and have found this issue crop up a lot before, but in the past BIOS updates have fixed it on other MOBOs, and people have had th eproblem when they arent even running raid. I WANT to run raid but cant do anything with it. Also, I have everything at stock as have seen that this can sometimes be due to an overclock. EDIT: Also got this message once during the madness: ""Warning! Now system in safe mode. Please resetting CPU frequency in the cmos setup" But Im sure this was at a point when it was not overclocked. I have had this running stock most of the time occasionally running a VERY mild overclock. (i know it can do loads more) Any ideas how I can get the raid bios to start working again and not hang on detecting array? Regards
  5. Its simple, perform a search by clicking on the search button at the top of the forum page. I would recommend doing an advanced search and search the Nforce4 forum by title for terms such as "slot" "which" "difference" "lower" "upper" "bottom" and you will find a wealth of info that has all been discussed in much detail before on this subject. Then you will see and agree that the subject does not really need to be discussed any more and any further additions can be added to one of the many existing threads. Being told to search is not a rude reply as such, it is merely teaching you for the future, that you do need to have the courtest to follow forum guidelines and advise, of which is to search before posting. Regards
  6. Exroadie, What exactly do you mean by "if it was the motherboard, NO PSU would work." ? ? ? What kind of a generalised meaningless statement is that with regard to this problem? Are you implying that if the DFI Expert Motherboard is at fault, that ALL PSUs would simply stop working? I personally dont own a DFI Expert so I say this from what I hope can be taken as a serious unbiast view; ITS A CLEAR MOBO PROBLEM.
  7. Cheers but I thought that the freezer uses 1/4" tubing and have heard that its a bit of a flow killer. Im looking for 1/2" high flow block and I dont need it to be low profile as running card in lower slot.
  8. The side is off my case already as im testing at the moment. Made no real difference. I know how to apply AS5 and im sure its seated ok. What 1/2" ID waterblocks are available for NF4 chipset?
  9. Thats not a fix, and why Exroadie are you trying to get PSU manufacturers to make alterations when just ONE of DFI's products are really the clear cause?
  10. Nice. Read loads of people have done this on many forums. Whacked on my zalman passive the other day and used AS5 thermal paste. Before idled around 48 and load bout 55. But obviously the fans was unacceptably loud imo. Now with the zalman it idles at like 58 degrees C and at load goes into 60s. This is unuseable and Im amazed at how badly the Zalman cools with no active cooling. I am going for a silent case with minimal fans, and have read of others doing this with little problems. I know mine is seated fine but still poor temps! If I get a 120mm fan blowing directly onto it from a few inches away though, if will idle at mid 32-34 degrees C. This is becomming tedious now. Im all watercooled on the CPU and GFX and temps are very very cool. Just the chipset that is annoying. What can I do to cool it in silence? I dont want to add it to my watercooled loop as will add uneccesary heat to it and kill my flowrate. I dont want a seperate small loop for it because additional pump = more noise and another rad which will be tight on space. Help!?
  11. This is a forum for discussing DFI motherboards. As with all computer forums it will mainly be ISSUES and problems with such boards posting for assistance especially with the presence of real DFI support people. Your going to see problems posted basically. PLus they are very popular boards so many people use them hence more probs, plus majority of users overclock = more problems. They are the best boards out there for OCing and since I have started my DFI ownership i have not had one problem with the board at all and it has performed very well. Same board you are asking bout too.
  12. Exroadie, where are you going with this one? Either way its still a MOBO problem.
×
×
  • Create New...