Originally posted by: Chugworth
Originally posted by: jlambvo
Regarding the Audigy 2 problem, I just got mine working for a 3rd run (apparently), just for kicks I moved the card back to PCI slot 1 (hey, that's where it was working originally) and cleared the CMOS. I had to let it discharge for a lot longer than it usually takes, AND I disconnected the mainboard power connector. Left it sit like that for a good 5-10 minutes. Then it would boot. Just letting it discharge for 20 seconds or so didn't do anything. Without making any adjustments in the BIOS it has booted fine and seems to work properly.
For those that have it working, it sounds like the beta bios isn't a problem, but are you overclocking? One theory I have is a problem with the PCI lock that is apparently present in the 1003.005 beta BIOS. Is it possible this isn't working consistently and causing some problems (PCI is trying to run too fast)?
Poking around on some other tech forums, I've heard reports of people on Asus boards (not necessarily the A8N) having problems booting with the onboard sound controller disabled. I don't recall having issues with this, anyone else? Could this have anything to do with this issue? There seem to be a lot of us...
I have this problem, and I have never done any overclocking.
But I've gone about five days without the Audigy 2 (?) crash. Then today it happened again. I was defragging partitions on two hard drives at once, while downloading a lot of email into Outlook 2003. Right when Outlook finished downloading the email and its blue transparent window popped up, everything hanged. What interested me was that was about the time Outlook would play the new mail sound. I didn't have my speakers on so I didn't here whether or not it even played it though.
When this happened in the past, Windows would always get stuck in a loop in the XP loading screen. The blue bar would keep moving, but nothing would happen. But this time rather than reinstall XP, I unplugged the computer for exactly five minutes - I even timed it. When I booted back up, Windows loaded fine and is working fine. This is interesting because that is the same method I used to fix the dead nVidia network port.
But now I am more convinced that this issue of Windows hanging and getting stuck in a loop in the loading screen is related to the Audigy 2. I don't want to get rid of my Audigy 2 though. If this issue doesn't happen often, and it is recoverable, I guess I can deal with it. Maybe it will be fixed in a future bios/driver release.
I am very curious about this though. I may want to go a few days without the Audigy 2 just to see if it really is the cause...