Spherical Chicken
n00b
- Joined
- Aug 1, 2004
- Messages
- 8
I just recently received a used Audigy sound card that I won on eBay, to replace the previous, exact same model, Audigy card that I thought had gotten damaged when my motherboard went flaky from a malfunctioning power supply. I had already bought a brand new motherboard of the same brand and model as the old one, a Soyo SY-K7V Dragon Plus, and a replacement Antec ( I think) power supply with the same wattage output as the old one, an Enermax 350W.
Anyway, I pop this "new" used Audigy card into my computer (after making a backup hard drive image, just to be sure), WinXP boots up, I start the driver installer I downloaded from Creative. The install is going along fine, "Updating windows drivers", I'm thinking this is finally going to work, then... nothing. The ******* computer locked the **** up AGAIN, right near the end of the ******* install!!!! ARRRRRRRRRRRRRRRRRRRRRRRGGGGGGGGGGHHHHHHHHHHHHHHHHHHHH!
The old Audigy card did this near the end of the life of the old motherboard, and again when I got the new motherboard installed; if the drivers were installed, the system would lock up at the point where I assume the sound card is "started" by the system. If I reboot, then it would lock up about a minute after I log into WinXP. I've tried it with the drivers on the CD-ROM and from the Creative web site, as well as both driver sets on a "fresh" install of WinXP with nothing else installed and no updates. I pulled the old Audigy card before and tried it in two other WinXP machines, and it worked in both.
I've racked my brain, trying to figure out what in the world could make the old and new Audigy cards misbehave in exactly the same manner... It couldn't be software problems related to the failed installations, since I made backup drive images before each install and fell back to those when the install failed... I made sure that the on-motherboard audio was turned off, so that it wouldn't interfere with the Audigy install... The power supply and motherboard are brand new, never used in another system...
Maybe it's a CMOS configuration setting that is interfering with the proper function of the card? That's one of the few things that were in common across all the different installation attempts. And what would the driver installer be doing near the end of the installation that would make the system hang so badly? Maybe someone could tell me what a WinXP hardware driver installer does towards the end of the install, it might narrow down what is going on here.
Anyway, I pop this "new" used Audigy card into my computer (after making a backup hard drive image, just to be sure), WinXP boots up, I start the driver installer I downloaded from Creative. The install is going along fine, "Updating windows drivers", I'm thinking this is finally going to work, then... nothing. The ******* computer locked the **** up AGAIN, right near the end of the ******* install!!!! ARRRRRRRRRRRRRRRRRRRRRRRGGGGGGGGGGHHHHHHHHHHHHHHHHHHHH!
The old Audigy card did this near the end of the life of the old motherboard, and again when I got the new motherboard installed; if the drivers were installed, the system would lock up at the point where I assume the sound card is "started" by the system. If I reboot, then it would lock up about a minute after I log into WinXP. I've tried it with the drivers on the CD-ROM and from the Creative web site, as well as both driver sets on a "fresh" install of WinXP with nothing else installed and no updates. I pulled the old Audigy card before and tried it in two other WinXP machines, and it worked in both.
I've racked my brain, trying to figure out what in the world could make the old and new Audigy cards misbehave in exactly the same manner... It couldn't be software problems related to the failed installations, since I made backup drive images before each install and fell back to those when the install failed... I made sure that the on-motherboard audio was turned off, so that it wouldn't interfere with the Audigy install... The power supply and motherboard are brand new, never used in another system...
Maybe it's a CMOS configuration setting that is interfering with the proper function of the card? That's one of the few things that were in common across all the different installation attempts. And what would the driver installer be doing near the end of the installation that would make the system hang so badly? Maybe someone could tell me what a WinXP hardware driver installer does towards the end of the install, it might narrow down what is going on here.