Jump to content

sudrin

Members
  • Content Count

    36
  • Joined

  • Last visited

Everything posted by sudrin

  1. Okay, i got this board back in April or so and was plagued by this problem. I put the board down until now and haven't really been keeping track of what's going on. Am I to understand that all these months later no comprehensive fix truly exists yet? Is there a FAQ somewhere to get me back up to speed? Thanks, David
  2. Can anyone give me any advice on how to cool the PWM IC then? I get temps up to 50C on it. I don't even know where it is to try and figure out how to keep it cool.
  3. I'm going to try this a little later. As Spock once said "It would explain a great many things". I'm glad someone was finally clever enough to think (way) outside the box on this one. /fingers crossed
  4. I feel kind of the same way. My first foray into "Building your own" since I was in my 20s (back when Computer Shopper was a HUGE magazine) has been kind of a bummer since I spent a lot of money to put together a really sweet rig and its been cool except for this, which is troublesome since it seems completely out of my hands to fix.
  5. The wierd 2 hour pattern mine does it in really freaks me out.. Its almost always 2 hours apart. What can cause that?!
  6. The MUX settings are inside Ventrilo configuration. I play World of Warcraft and we had a lot of people in our guild who would blast the game sounds to us (very annoying) until we figured it out. By default its set to "STEREO MIX" which combines all the sounds into one. No idea why this setting exists, but until its changed to "Mic" (I beileve it was this) it would cause everyone to hear themselves. I don't use the sound module myself so I can't verify exactly what steps you have to change to fix it, but it sounds like the problem.
  7. Are you seeing this with Teamspeak and Ventrilo by any chance? I haven't had this particular problem but i have known people using Ventrio to have this problem if thier "mux" was set to MIX (or something similar). It basically causes exactly what you are describing to happen. Its the only thing *I* can think of.
  8. Except that just makes it LESS clear, since that drive HAS TLER. So now its something with the controller then?
  9. Well, without spamming you with my entire Event Log I am noticing the same wierd 2 hour pattern between "Events" (Except for a few cases). I don't see how the drives can go into a "Deep Recovery Cycle" every two hours! But that's just me. Here is my info: 5/15/2006 10:33:03 PM m5288 Error The device, DeviceScsim52881, did not respond within the timeout period. 7:48:02 PM m5288 Error The device, DeviceScsim52881, did not respond within the timeout period. 5/14/2006 11:21:17 PM m5288 Error The device, DeviceScsim52881, did not respond within the timeout period. 9:19:22 PM m5288 Error The device, DeviceScsim52881, did not respond within the timeout period. 7:17:41 PM m5288 Error The device, DeviceScsim52881, did not respond within the timeout period. 5:16:37 PM m5288 Error The device, DeviceScsim52881, did not respond within the timeout period. 3:15:56 PM m5288 Error The device, DeviceScsim52881, did not respond within the timeout period. 1:16:11 PM m5288 Error The device, DeviceScsim52881, did not respond within the timeout period. 11:13:39 AM m5288 Error The device, DeviceScsim52881, did not respond within the timeout period. 8:53:48 AM m5288 Error The device, DeviceScsim52881, did not respond within the timeout period. 5/13/2006 6:35:58 PM m5288 Error The device, DeviceScsim52881, did not respond within the timeout period. 4:27:21 PM m5288 Error The device, DeviceScsim52881, did not respond within the timeout period. 1:56:25 PM m5288 The device, DeviceScsim52881, did not respond within the timeout period.
  10. Well, I for one am not really willing to "Settle" for that. Its a partial solution at best if I'm expected to switch over to the SIL controller. I have four 3.0g drives and I want to use them at 3 not 1.5. I'll post some more detailed info when I get home if that helps with the troubleshooting.
  11. Yes, it happens once every few hours for 10 seconds or so. Its the only problem with this motherboard I have yet to track down. I have tried the four drives in a Raid 0 and Raid 0+1 configuration. I've tried updating the drivers, various bios settings, etc.
  12. Wow.. I'll be happy if we find the problem, but sad if this is it.. I bought 4 of these to the tune of 400 bucks and Newegg will only replace them with the same make and model, so I've just thrown the money away.
  13. Well, I have 4 WD2500KS drives from Newegg which does not appear to have the TLER feature. At least not according to the officical WD site or the Newegg site.
  14. So either the problem is my Power Supply or the fact that I have Four Western Digital Drives? Boy, color me sad.
  15. Has anyone made any progress with this problem? I'm out of tricks to try.
  16. Well, I tried to upgrade the ULI driver yesterday on my machine and it hosed up my windows install so I had to rebuild it meaning I don't have my old event list, but I will try and put together a new one. I am looking forward to having this problem resolved. I've had to go back to playing World of Warcraft on my old machine. Fortunately it plays it just fine (Warcraft hasn't really benefited much from a fast machine much to my grief) so I can be patient.
  17. The persistance of this problem is making me sad. Its tarnishing my opinion of this Motherboard. I've had my system a week now and I've spent more time trying to solve this problem than enjoying the PC. Okay does anyone having this problem not have a RAID configuration of some kind?
  18. When I first got my setup (which is similar to that) I couldn't get a screen until I had plugged the Crossfire dongle in. Also, make sure both cards are in the correct slots for master and slave. The error codes seem arbitrary at best and I have never seen a reference for them.
  19. hehe.. Yeah I just have to be satisfied knowing that its the BEST POSSIBLE experience I could have with the game with this machine. That helps a little.
  20. I couldn't get crossfire to work properly until I rolled back to 6.3. Drove me crazy trying to get it to work, only to find out it makes zero difference in World of Warcraft. Still, it does look nice in games that DO support it.
  21. Does anyone having this problem NOT have some version of the Sound Blaster in thier machine? I'm about ready to remove it and try the onboard myself to see if it goes away. Thats not my number one choice, but I need a machine I can trust to run for more than an hour or two without doing this in the middle of PvP in World of Warcraft Edit: I guess I should have said "PCI Sound card of some brand" instead of Sound Blaster. In my day they were ALL Sound Blasters. ;-)
  22. Does the problem persist if you unhook the network cable? I had this problem and I think its attached to a wake-on-lan bug. It still did it even though WOL was turned off but my problem went away as soon as I unhooked it.
  23. Well I didn't have this problem so I can't speak to that, but I did notice there is a new version the bios that specifically addresses memory compatability. You might try that
  24. Speaking of the onboard sound, even if you ARE NOT using it I found I had to install the drivers to get rid of the "PCI Device", even though I am not. Then it went a way and I went on about my business.
×
×
  • Create New...