Jump to content

SiLvABuLLetZ

Members
  • Content Count

    128
  • Joined

  • Last visited

About SiLvABuLLetZ

  • Rank
    Member
  1. looks like this http://img472.imageshack.us/img472/7950/dfifixbz8.jpg
  2. So I figured out why my comp started freezing again randomly - and better yet I figured out a fix. Basically if you click Start, Control Panel, System, Hardware tab, then click device manager, Expand the "SCSI and RAID Controller." There should only be Uli SATA/RAID Controller (M1575/M1697). If, like in my case, a second SCSI Controller device was found, and it's labeled SCSI Host Controller you need to use the Beta Raid drivers (6.2.2.1) on that device as well. DO NOT REBOOT THE COMPUTER AFTER YOU'VE LOADED THE BETA DRIVERS ONTO THIS DEVICE. IMPORTANT. After you've made sure you've loaded the beta raid drivers to both the Uli SATA/RAID Controller (M1575/M1697) and the SCSI Host controller, you need to DISABLE the SCSI Host Controller in device manager - Don't just uninstall it, or else it will come back and you'll need to do the entire process over again. DISABLE THE SCSI Host Controller which should now also be called Uli SATA/RAID Controller (M1575/M1697) after you've loaded the drivers. NOW IN THE END you should have in your SCSI and Raid controllers expanded view two SATA/RAID Controller (M1575/M1697) devices. The 1st ULI SATA/RAID Controller (M1575/M1697) should be disabled (this was labeled "SCSI Host controller" initially [right?] - i'm saying "right" here because you have to make sure you're disabling the right one. The 2nd "Uli SATA/RAID Controller" is not disabled - This one was your real ULI controller. Now you may reboot and enjoy your flawless machine. AGAIN I repeat, do not at any time uninstall any of these devices or you may not be able to get back into windows. Also, make sure you're disabling the right "device" which was the "SCSI Host Controller" initially. If you disable the wrong 1, the fix may not work and you may not be able to get back into windows so follow these steps carefully. I'm assuming that the motherboard has a glitch so windows detects 2 uli controllers. When we all loaded the beta drivers in, we didn't take the fake uli controller into account as well - so what was happening was windows was timing out due to this fact.. Just disable the fake one after you've loaded the beta drivers into it. Also - Lastly, if you have a HDD Smart option in your bios, set it to enabled. Furthermore, be sure to have 7/28 bios. Any other bios version has the freezes attached to it. Nick
  3. So I figured out why my comp started freezing again randomly - and better yet I figured out a fix. Basically if you click Start, Control Panel, System, Hardware tab, then click device manager, Expand the "SCSI and RAID Controller." There should only be Uli SATA/RAID Controller (M1575/M1697). If, like in my case, a second SCSI Controller device was found, and it's labeled SCSI Host Controller you need to use the Beta Raid drivers (6.2.2.1) on that device as well. DO NOT REBOOT THE COMPUTER AFTER YOU'VE LOADED THE BETA DRIVERS ONTO THIS DEVICE. IMPORTANT. After you've made sure you've loaded the beta raid drivers to both the Uli SATA/RAID Controller (M1575/M1697) and the SCSI Host controller, you need to DISABLE the SCSI Host Controller in device manager - Don't just uninstall it, or else it will come back and you'll need to do the entire process over again. DISABLE THE SCSI Host Controller which should now also be called Uli SATA/RAID Controller (M1575/M1697) after you've loaded the drivers. NOW IN THE END you should have in your SCSI and Raid controllers expanded view two SATA/RAID Controller (M1575/M1697) devices. The 1st ULI SATA/RAID Controller (M1575/M1697) should be disabled (this was labeled "SCSI Host controller" initially [right?] - i'm saying "right" here because you have to make sure you're disabling the right one. The 2nd "Uli SATA/RAID Controller" is not disabled - This one was your real ULI controller. Now you may reboot and enjoy your flawless machine. AGAIN I repeat, do not at any time uninstall any of these devices or you may not be able to get back into windows. Also, make sure you're disabling the right "device" which was the "SCSI Host Controller" initially. If you disable the wrong 1, the fix may not work and you may not be able to get back into windows so follow these steps carefully. I'm assuming that the motherboard has a glitch so windows detects 2 uli controllers. When we all loaded the beta drivers in, we didn't take the fake uli controller into account as well - so what was happening was windows was timing out due to this fact.. Just disable the fake one after you've loaded the beta drivers into it. Also - Lastly, if you have a HDD Smart option in your bios, set it to enabled. Furthermore, be sure to have 7/28 bios. Any other bios version has the freezes attached to it. Nick
  4. So I figured out why my comp started freezing again randomly - and better yet I figured out a fix. Basically if you click Start, Control Panel, System, Hardware tab, then click device manager, Expand the "SCSI and RAID Controller." There should only be Uli SATA/RAID Controller (M1575/M1697). If, like in my case, a second SCSI Controller device was found, and it's labeled SCSI Host Controller you need to use the Beta Raid drivers (6.2.2.1) on that device as well. DO NOT REBOOT THE COMPUTER AFTER YOU'VE LOADED THE BETA DRIVERS ONTO THIS DEVICE. IMPORTANT. After you've made sure you've loaded the beta raid drivers to both the Uli SATA/RAID Controller (M1575/M1697) and the SCSI Host controller, you need to DISABLE the SCSI Host Controller in device manager - Don't just uninstall it, or else it will come back and you'll need to do the entire process over again. DISABLE THE SCSI Host Controller which should now also be called Uli SATA/RAID Controller (1575/M1697) after you've loaded the drivers. NOW IN THE END you should have in your SCSI and Raid controllers expanded view two SATA/RAID Controller (M1575/M1697) devices. The 1st ULI SATA/RAID Controller (M1575/M1697) should be disabled (this was labeled "SCSI Host controller" initially [right?] - i'm saying "right" here because you have to make sure you're disabling the right one. The 2nd "Uli SATA/RAID Controller" is not disabled - This one was your real ULI controller. Now you may reboot and enjoy your flawless machine. AGAIN I repeat, do not at any time uninstall any of these devices or you may not be able to get back into windows. Also, make sure you're disabling the right "device" which was the "SCSI Host Controller" initially. If you disable the wrong 1, the fix may not work and you may not be able to get back into windows so follow these steps carefully. I'm assuming that the motherboard has a glitch so windows detects 2 uli controllers. When we all loaded the beta drivers in, we didn't take the fake uli controller into account as well - so what was happening was windows was timing out due to this fact.. Just disable the fake one after you've loaded the beta drivers into it. Also - Lastly, if you have a HDD Smart option in your bios, set it to enabled. Furthermore, be sure to have 7/28 bios. Any other bios version has the freezes attached to it. Nick As a side note. If this fix does not work - Try disabling the other device while enabling the fake 1 alternatively. But i'm pretty sure I had it right the first time.
  5. The best thing that worked for people were 4/25 bios and beta raid drivers from dfi's beta driver download site... I'm too lazy to get the links, but this is what worked best for people.
  6. Is it possible that they are using a different beta bios then the one uploaded on the site? I haven't tried the beta bios with my new rma'd board, but with 7/28 and the beta raid drivers I get no freezes for hours (up to 8), and it will randomly error our after hours and hours of usage.. Normal? I dunno, but I will try beta bios to see if it still freezes hours later... -BulletZ
  7. Do not try this! I almost ended up repairing windows with a complete reinstall due to trying to use this driver. Luckily, selecting the "Use last known good configuration" option when windows wouldn't boot up reinstalled the old working driver. Wheew!!!! Bulletz
  8. It would be great if you gave people a step by step guide on doing what you did. Thanks
  9. Alright. I want to get into crossfire with 1 other 512mb x1800 xt. Now, I read somewhere and heard as well, that with the cfx3200-dr, a crossfire edition graphics card is not necessary in order to cross fire. All that is needed is just another x1800 xt. Will crossfire performance be lower if I simply stuck in 2 x1800xt's rather than an x1800xt and a crossfire edition x1800 xt? Was it the motherboard that allows this, or the new catalysts? Thanks guys. I'm interested in crossfire now because even with my rig, I played splinter cell double agent and cried on the cruise ship level when I got 10 fps. Thanks again. -bulletz
  10. No.. You are incorrect. The Prob happens all the time and randomly no matter what setting, not matter which bios. Except for me, I rma'd my board, and they sent me one that only works 99% flawlessly with 4/25 bios and beta raid drivers.. I say 99% because I won't lie, after like 8 hours of use and no errors, I'll get a quick stop.. Annoying, but unacceptable.
  11. Guys, My rma'd board is so weird! On 4/25 bios and 7.2 beta raid's, I do not get any errors ever, and it runs like a dream. On 7/28 and any other raid driver besides the 7.2's the thing WILL lock up. Now I suggest all to do the 4/25 and 7.2 combo and confirm that your boards run like dreams!
×
×
  • Create New...