If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
|
Thread Tools | Display Modes |
#1
|
|||
|
|||
USB Controller list in Device Manager
Hello all....
I have an older (2003) custom built computer with XP Home SP3 that's been having problems with the six USB ports and Windows not finding drivers for plugged in devices. Under USB controllers in the Device Manager, with nothing plugged into the ports, there are multiple listings for the USB controllers. Is this normal? The list is as follows: SiS 7001 PCI to USB Open Host Controller (this is on PCI bus 0, device 3, function 0) SiS 7001 PCI to USB Open Host Controller (this is on PCI bus 0, device 3, function 1) SiS 7001 PCI to USB Enhanced Host Controller (this is on PCI bus 0, device 3, function 3) USB Root Hub (Location 0, 3 ports available) USB Root Hub (Location 0, 3 ports available) USB Root Hub (Location 0, 6 ports available) I ask because I have another machine that shows only one PCI to USB Universal Host Controller and one Root Hub for its two ports. If this isn't a problem, then I'll have to post all the specifics. Thanks in advance. |
Ads |
#2
|
|||
|
|||
USB Controller list in Device Manager
Big E wrote:
Hello all.... I have an older (2003) custom built computer with XP Home SP3 that's been having problems with the six USB ports and Windows not finding drivers for plugged in devices. Under USB controllers in the Device Manager, with nothing plugged into the ports, there are multiple listings for the USB controllers. Is this normal? The list is as follows: SiS 7001 PCI to USB Open Host Controller (this is on PCI bus 0, device 3, function 0) SiS 7001 PCI to USB Open Host Controller (this is on PCI bus 0, device 3, function 1) SiS 7001 PCI to USB Enhanced Host Controller (this is on PCI bus 0, device 3, function 3) USB Root Hub (Location 0, 3 ports available) USB Root Hub (Location 0, 3 ports available) USB Root Hub (Location 0, 6 ports available) I ask because I have another machine that shows only one PCI to USB Universal Host Controller and one Root Hub for its two ports. I don't see that the above is a problem. I suspect that your older machine's motherboard is failing. While 5 years isn't long to adult humans, it is elderly in computer years. If you want to keep the machine longer, consider installing a PCI USB controller as a workaround. They are very inexpensive. Malke -- MS-MVP Elephant Boy Computers - Don't Panic! FAQ - http://www.elephantboycomputers.com/#FAQ |
#3
|
|||
|
|||
USB Controller list in Device Manager
Big E wrote:
Hello all.... I have an older (2003) custom built computer with XP Home SP3 that's been having problems with the six USB ports and Windows not finding drivers for plugged in devices. Under USB controllers in the Device Manager, with nothing plugged into the ports, there are multiple listings for the USB controllers. Is this normal? The list is as follows: SiS 7001 PCI to USB Open Host Controller (this is on PCI bus 0, device 3, function 0) SiS 7001 PCI to USB Open Host Controller (this is on PCI bus 0, device 3, function 1) SiS 7001 PCI to USB Enhanced Host Controller (this is on PCI bus 0, device 3, function 3) USB Root Hub (Location 0, 3 ports available) USB Root Hub (Location 0, 3 ports available) USB Root Hub (Location 0, 6 ports available) I ask because I have another machine that shows only one PCI to USB Universal Host Controller and one Root Hub for its two ports. If this isn't a problem, then I'll have to post all the specifics. Thanks in advance. When I run into "wonky" behavior, I boot an alternate OS, and compare the operation of the hardware. For example, when my old 440BX motherboard exhibited freezing when I had more than 512MB of memory installed, I booted Linux and noticed exactly the same symptoms. That pointed to a design flaw of some sort in the hardware. The hardware was extremely stable (ran Prime95 for 16 hours no problem), once the memory total was at or below 512MB. (So it turned out to not be a Win98 issue, which was the OS in the box.) It didn't matter what slots the memory was in, it just didn't like too much memory. The freezing happened on accesses to the AGP slot. I have a Ubuntu and a Knoppix Linux Live CD here, and those don't need to be installed to a hard drive to work. I prefer the Knoppix slightly, because of the text messages output to the screen during the initial boot. You can find Ubuntu at ubuntu.com and Knoppix at knopper.net . The latest distro of Knoppix takes a whole DVD, while if you go back a release or two, there is a release that fits a CD. The CD versions would be a 700MB download, only viable with something other than dialup networking. Since I only have one DVD drive, the DVD version is pretty well useless to me as a daily test mechanism. (I have a workaround, but it isn't worth writing about...) Of course, actually testing the hardware in Linux, means that a driver has to be available. If the function of the peripheral is obscure or is complicated, there might not be a driver for it, and perhaps no way to exercise the functions and prove it works. So it's far from being an ideal test environment. But it is free, and adds to your ability to collect additional symptoms. Linux tools of interest dmesg (shows hardware detection saved to a file, at boot) lspci (lists detected hardware such as PCI or PCI Express cards) lsusb (lists stuff sitting on USB ports) As a hardware designer, I have a slightly different perspective on hardware and why it "wears out". The silicon part of it is robust, and not usually given to wearout mechanisms. But the motherboard does have power regulation circuitry, and sometimes that fails or degrades, causing the hardware to become weak. Popped MOSFETs, leaking or bulging capacitors, are typical items seen failing on the board. There aren't too many chipsets with known failure mechanisms - the ICH5 USB static discharge problem is one, and the Nvidia's tendency to lose PCI Express slots is another (again, could be static related failures). There have been many other chipsets that were faultless, in terms of outright dead ports or functions. There have been chip failures in the past, some due to chemical contamination. I've read some IBM documents describing their detective efforts, to figure some of them out. But if the manufacturing wasn't botched, there is no inherent reason for silicon to fail. For example, I've had the same digital watch strapped to my wrist, for longer than I can remember. It still works. It's got to be more than 20 years old. The things shown in Device Manager, are the logic blocks that control more than one port. A lot of chipsets have one USB 1.1 logic block per two physical connectors. There may be one USB 2.0 logic block to share over all the physical connectors. So the entries in Device Manager don't correspond to the physical port. The protocol during setup of the USB device, results in either the USB 1.1 or the USB 2.0 block being connected to the port. A Windows application such as UVCView (older version(s) had names like USBView), can be used to display the config info coming from a USB device. That doesn't guarantee its function, but gives some evidence that a connection can be made. UVCView used to be available for download from microsoft.com, but is no longer hosted there. There are a couple private web sites, that still offer a copy for download (at least, a couple I was able to find). One feature of UVCView, is it isn't as stupid as USBView was, about handling a large number of USB ports. ******* ftp://ftp.efo.ru/pub/ftdichip/Utilities/UVCView.x86.exe http://www.users.on.net/~fzabkar/USB...VCView.x86.exe File size is 167,232 bytes. MD5sum is 93244d84d79314898e62d21cecc4ca5e This is a picture of what the UVCView info looks like. http://www.die.de/blog/content/binary/usbview.png Some information on the parameters seen in UVCView. http://www.beyondlogic.org/usbnutshell/usb5.htm ******* HTH, Paul |
#4
|
|||
|
|||
USB Controller list in Device Manager
Good suggestions. I hadn't thought of booting to an alternate OS. I am vaguely familiar with Linux as I occasionally run some programs within Cygwin. I may give that a shot at least out of curiosity. New controller card may be the way to go because I'm certainly no USB guru but I'd like to rule out any software glitches before I spend even a little dough on this geezer. The motherboard is extremely stable. The regulator caps for the CPU have been replaced - victim of the rash of bad caps made at the time. This is probably the most stable machine I have ever seen. I work it hard and it never crashes so I'd like to hang on to it a little while longer before I rplace the whole thing. The main problem is that it is selective about what it will recognize plugged into the USB ports. This wasn't noticed before as I only ever plugged in two USB devices and they work OK. It recognizes: a) MOTU Micro Lite MIDI interface with software drivers b) Epson 1650 scanner with Windows default drivers. Both operate without glitches in any port. What it doesn't like: 1) Logitech reciever for wireless LX-8 mouse 2) Microsoft receiver for wireless Microsoft Mouse 3000 3) Sony 4GB Microvault USM4GL(B) 4) Sony Walkman NWZ-B105F These all work in our other XP and Vista machines so it's not the devices. It doesn't matter into which of six ports any of them are plugged. The Walkman didn't work with SP2. The Microvault and mice are new purchases since SP3. Windows can not find the drivers. All show up in Device Manager ONLY under Other Devices - the mouse receivers as "USB Receiver"; the Microvault as "Storage Media"; and the Walkman as "WALKMAN" and the drivers are missing. So Windows knows what they are but not what to do with them assuming the drivers are part of the firmware. Here's what I've tried so far as picked up from other threads: Cleared the SoftwareDistribution folder. Reinstalled usb.inf Installed Windows Installer 4.5 Installed Kelly's tweak #400 Made sure .NET was the latest. Nothing has worked. The machine has a Foxconn 661M03-G-6L motherboard with the last bios update available (2007), 3.4GHz Pentium (chip actually runs at 2.8GHz), 1GB RAM, 75 GB HD, 160 GB HD, CD-ROM, DVD/CD burner, floppy (yup, some people still have a use for 'em), nVidea G-Force FX-5200 graphics card with updated drivers, Echo Mia audio card with updated drivers (onboard sound is disabled), onboard ethernet. I've seen similar problems in a lot of threads both here and at other sites but not a lot of definitive solutions posted. I'm willing to try most any suggestions short of a sledge hammer (tempting, though it is and probably fun, too) and at the same time, come up with a good list of potential fixes so others can benefit. And... I'll report back. Thanks again |
#5
|
|||
|
|||
USB Controller list in Device Manager
"Big E" wrote in message ... Hello all.... I have an older (2003) custom built computer with XP Home SP3 that's been having problems with the six USB ports and Windows not finding drivers for plugged in devices. Under USB controllers in the Device Manager, with nothing plugged into the ports, there are multiple listings for the USB controllers. Is this normal? The list is as follows: SiS 7001 PCI to USB Open Host Controller (this is on PCI bus 0, device 3, function 0) SiS 7001 PCI to USB Open Host Controller (this is on PCI bus 0, device 3, function 1) SiS 7001 PCI to USB Enhanced Host Controller (this is on PCI bus 0, device 3, function 3) USB Root Hub (Location 0, 3 ports available) USB Root Hub (Location 0, 3 ports available) USB Root Hub (Location 0, 6 ports available) The above is typical of a PC that has 6 USB2 ports, though slightly unusual because generally there would be 3 OHCI controllers with 2 ports available each but don't let that worry you. The ports are always duplicated for the high speed mode for very good technical reasons. I ask because I have another machine that shows only one PCI to USB Universal Host Controller and one Root Hub for its two ports. That is typical of a machine that has 2 USB1 only ports. If this isn't a problem, then I'll have to post all the specifics. Post away. |
#6
|
|||
|
|||
USB Controller list in Device Manager
"Big E" wrote: Good suggestions. I hadn't thought of booting to an alternate OS. I am vaguely familiar with Linux as I occasionally run some programs within Cygwin. I may give that a shot at least out of curiosity. New controller card may be the way to go because I'm certainly no USB guru but I'd like to rule out any software glitches before I spend even a little dough on this geezer. The motherboard is extremely stable. The regulator caps for the CPU have been replaced - victim of the rash of bad caps made at the time. This is probably the most stable machine I have ever seen. I work it hard and it never crashes so I'd like to hang on to it a little while longer before I rplace the whole thing. The main problem is that it is selective about what it will recognize plugged into the USB ports. This wasn't noticed before as I only ever plugged in two USB devices and they work OK. It recognizes: a) MOTU Micro Lite MIDI interface with software drivers b) Epson 1650 scanner with Windows default drivers. Both operate without glitches in any port. What it doesn't like: 1) Logitech reciever for wireless LX-8 mouse 2) Microsoft receiver for wireless Microsoft Mouse 3000 3) Sony 4GB Microvault USM4GL(B) 4) Sony Walkman NWZ-B105F These all work in our other XP and Vista machines so it's not the devices. It doesn't matter into which of six ports any of them are plugged. The Walkman didn't work with SP2. The Microvault and mice are new purchases since SP3. Windows can not find the drivers. All show up in Device Manager ONLY under Other Devices - the mouse receivers as "USB Receiver"; the Microvault as "Storage Media"; and the Walkman as "WALKMAN" and the drivers are missing. So Windows knows what they are but not what to do with them assuming the drivers are part of the firmware. Here's what I've tried so far as picked up from other threads: Cleared the SoftwareDistribution folder. Reinstalled usb.inf Installed Windows Installer 4.5 Installed Kelly's tweak #400 Made sure .NET was the latest. Nothing has worked. The machine has a Foxconn 661M03-G-6L motherboard with the last bios update available (2007), 3.4GHz Pentium (chip actually runs at 2.8GHz), 1GB RAM, 75 GB HD, 160 GB HD, CD-ROM, DVD/CD burner, floppy (yup, some people still have a use for 'em), nVidea G-Force FX-5200 graphics card with updated drivers, Echo Mia audio card with updated drivers (onboard sound is disabled), onboard ethernet. I've seen similar problems in a lot of threads both here and at other sites but not a lot of definitive solutions posted. I'm willing to try most any suggestions short of a sledge hammer (tempting, though it is and probably fun, too) and at the same time, come up with a good list of potential fixes so others can benefit. And... I'll report back. Thanks again |
#7
|
|||
|
|||
USB Controller list in Device Manager
I graduated from Texas A&M so I'm not bright enough to keep up with you
gentlemen, but I have an aging Sony Vaio with the same symptoms. I recently used the recovery disc to restore my c drive only and it will only recognize my logitech mouse. Anything else it usually identifies and sticks in other hardware without loading the driver which is out there in most cases. Windows just won't recognize and load them. "Big E" wrote: Good suggestions. I hadn't thought of booting to an alternate OS. I am vaguely familiar with Linux as I occasionally run some programs within Cygwin. I may give that a shot at least out of curiosity. New controller card may be the way to go because I'm certainly no USB guru but I'd like to rule out any software glitches before I spend even a little dough on this geezer. The motherboard is extremely stable. The regulator caps for the CPU have been replaced - victim of the rash of bad caps made at the time. This is probably the most stable machine I have ever seen. I work it hard and it never crashes so I'd like to hang on to it a little while longer before I rplace the whole thing. The main problem is that it is selective about what it will recognize plugged into the USB ports. This wasn't noticed before as I only ever plugged in two USB devices and they work OK. It recognizes: a) MOTU Micro Lite MIDI interface with software drivers b) Epson 1650 scanner with Windows default drivers. Both operate without glitches in any port. What it doesn't like: 1) Logitech reciever for wireless LX-8 mouse 2) Microsoft receiver for wireless Microsoft Mouse 3000 3) Sony 4GB Microvault USM4GL(B) 4) Sony Walkman NWZ-B105F These all work in our other XP and Vista machines so it's not the devices. It doesn't matter into which of six ports any of them are plugged. The Walkman didn't work with SP2. The Microvault and mice are new purchases since SP3. Windows can not find the drivers. All show up in Device Manager ONLY under Other Devices - the mouse receivers as "USB Receiver"; the Microvault as "Storage Media"; and the Walkman as "WALKMAN" and the drivers are missing. So Windows knows what they are but not what to do with them assuming the drivers are part of the firmware. Here's what I've tried so far as picked up from other threads: Cleared the SoftwareDistribution folder. Reinstalled usb.inf Installed Windows Installer 4.5 Installed Kelly's tweak #400 Made sure .NET was the latest. Nothing has worked. The machine has a Foxconn 661M03-G-6L motherboard with the last bios update available (2007), 3.4GHz Pentium (chip actually runs at 2.8GHz), 1GB RAM, 75 GB HD, 160 GB HD, CD-ROM, DVD/CD burner, floppy (yup, some people still have a use for 'em), nVidea G-Force FX-5200 graphics card with updated drivers, Echo Mia audio card with updated drivers (onboard sound is disabled), onboard ethernet. I've seen similar problems in a lot of threads both here and at other sites but not a lot of definitive solutions posted. I'm willing to try most any suggestions short of a sledge hammer (tempting, though it is and probably fun, too) and at the same time, come up with a good list of potential fixes so others can benefit. And... I'll report back. Thanks again |
#8
|
|||
|
|||
USB Controller list in Device Manager
I've been fiddling around and I'm still not sure that it's a hardware problem
with the motherboard. On a lark, I did a driver update for the MIDI interface and now the interface does not work. It shows up under USB controllers as "MOTU USB MIDI (WDM)". It shows the device is working correctly. However, there is another entry under Other Devices - Unknown Device. If I remove the unknown device, nothing changes. I can see the .sys driver files under Windows\System32\drivers but Windows won't let me pick them to install. Any thoughts/comments appreciated. Thanks |
#9
|
|||
|
|||
USB Controller list in Device Manager
More info...
I deleted all the host controllers and root hubs and restarted so they would be reinstalled. Windows found no drivers for them and now all the USB controllers are listed under Other Devices with that dreaded yellow question mark. If it makes any difference, the chipset is SiS 661 FX for the North Bridge and 963/963L for the South Bridge. SiS website lists no USB drivers as they are provided by the operating system. This sounds like software to me but I'm thinking of trying a PCI USB card and seeing what happens. |
#10
|
|||
|
|||
USB Controller list in Device Manager
Big E wrote:
SiS 7001 PCI to USB Open Host Controller (this is on PCI bus 0, device 3, Googling "Sis 7001" comes up with this page http://www.usbman.com/Guides/SiS%20USB%20Tips%20and%20Tricks.htm PCI add-in card I think. -- Adrian C |
#11
|
|||
|
|||
USB Controller list in Device Manager
I wonder if the PCI bus is going out or if XP has gotten stupid.
1. The onboard SiS USB has been disabled. 2. Installed PCI USB card (supposedly PnP campatible). 3. XP knew a USB controller was plugged in but would not recognize drivers on the CD. 4. Downloaded and ran a setup file from the mfgr's website to install drivers. That helped a little bit. Device manager now shows (2) PCI Class USB 2.0 Enhanced Host Controllers and (2) USB 2.0 Root Hub Devices. There is no Open Host Controller or Root Hub. USB still not functional. Here's the kicker - Had to move the audio card to a different slot to make anything happen. Now XP can't "find" the audio card drivers even though I can see them in the drivers folder and point XP to look in System32 (it won't let me burrow down farther than that). Point is I can see all the drivers for both devices but XP can't. Could the PCI bus be getting wonky? |
#12
|
|||
|
|||
USB Controller list in Device Manager
Big E wrote:
I wonder if the PCI bus is going out or if XP has gotten stupid. 1. The onboard SiS USB has been disabled. 2. Installed PCI USB card (supposedly PnP campatible). 3. XP knew a USB controller was plugged in but would not recognize drivers on the CD. 4. Downloaded and ran a setup file from the mfgr's website to install drivers. That helped a little bit. Device manager now shows (2) PCI Class USB 2.0 Enhanced Host Controllers and (2) USB 2.0 Root Hub Devices. There is no Open Host Controller or Root Hub. USB still not functional. Here's the kicker - Had to move the audio card to a different slot to make anything happen. Now XP can't "find" the audio card drivers even though I can see them in the drivers folder and point XP to look in System32 (it won't let me burrow down farther than that). Point is I can see all the drivers for both devices but XP can't. Could the PCI bus be getting wonky? I have a situation like that. My sound card has one bit on the PCI bus that seems to make bad connections. If the connection is open, I see a "Hardware" wizard, asking for drivers. If I power off and reseat the card, the drivers that are already installed, work fine. I can use Everest or the Device Manager, to check the current VEN/DEV info, and see the one bit difference. The USB drivers should already be in WinXP, and if you were to check the USB card CDROM, it might show either of two things 1) Ancient USB2 driver, from before WinXP SP1. 2) If intended for SP1 or later, the driver folder for WinXP may be empty. Licensing restrictions prevent distributing a USB driver, for stuff after SP1. If you look for usbport.inf in your inf folder, that file covers common USB host devices. [Manufacturer] %AMD.Mfg%=AMD.Section %ACER.Mfg%=ACER.Section %Compaq.Mfg%=Compaq.Section %CMD.Mfg%=CMD.Section %Cypress.Mfg%=Cypress.Section %Generic.Mfg%=Generic.Section %Intel.Mfg%=Intel.Section %Lucent.Mfg%=Lucent.Section %NEC.Mfg%=NEC.Section %Microsoft.Mfg%=Microsoft.Section %OPTi.Mfg%=OPTi.Section %Philips.Mfg%=Philips.Section %Reliance.Mfg%=Reliance.Section %SIS.Mfg%=SIS.Section %SMSC.Mfg%=SMSC.Section %Symbios.Mfg%=Symbios.Section %VIA.Mfg%=VIA.Section [SIS.Section] %PCI\VEN_1039&DEV_7001&CC_0C0310.DeviceDesc%=OHCI_ HYDRA.Dev,PCI\VEN_1039&DEV_7001&CC_0C0310 %PCI\VEN_1039&DEV_7002.DeviceDesc%=EHCI.Dev,PCI\VE N_1039&DEV_7002 On newer chipsets, the manufacturers try to reuse their existing VEN/DEV info, so that the default driver works automatically. (7001 and 7002 would have been used on a lot of different SIS chipsets.) The logic blocks should have the standard interface, so the Microsoft driver will feel right at home. You can get a copy of Everest here, and use Devices:PCI to view your hardware. The list of hardware makes it a bit quicker (fewer mouse clicks) to see DeviceID info. http://majorgeeks.com/download4181.html HTH, Paul |
#13
|
|||
|
|||
USB Controller list in Device Manager
Thanks Paul. Tried moving the PCI cards all around to different slots to no avail. The USB card has an NEC chipset and reports the proper IDs that compare to the .inf files. The OS just won't recognize the drivers or something in the ID tranlation which takes me back to my previous post... If the onboard USB is assigned as PCI slot 0 and now neither of my other two PCI cards are recognized in any slot 1 - 3, could the PCI bus have gone bad? Seems unlikely but sometimes you never know. I'll probably have to shell out for one of those new-fangled kick-butt boxes and relagate this one to lowly file server status. Seems a shame since it's been a fantastic runner. |
#14
|
|||
|
|||
USB Controller list in Device Manager
Big E wrote:
Thanks Paul. Tried moving the PCI cards all around to different slots to no avail. The USB card has an NEC chipset and reports the proper IDs that compare to the .inf files. The OS just won't recognize the drivers or something in the ID tranlation which takes me back to my previous post... If the onboard USB is assigned as PCI slot 0 and now neither of my other two PCI cards are recognized in any slot 1 - 3, could the PCI bus have gone bad? Seems unlikely but sometimes you never know. I'll probably have to shell out for one of those new-fangled kick-butt boxes and relagate this one to lowly file server status. Seems a shame since it's been a fantastic runner. When you say the cards aren't recognized, have you tried running Everest and looked in Devices:PCI, to see if something is detected ? Everest http://majorgeeks.com/download4181.html You also mentioned in one of your posts, that a 3.4GHz P4 was running at 2.8GHz. What is the FSB running at ? Can you check with CPUZ ? You might also want to check the memory section, and see if the memory is running at or below its stated limit. Looking back at the rest of this thread, it occurs to me that something doesn't smell right there. http://www.cpuid.com/cpuz.php What I'm specifically looking for, is the CPU Input clock setting. The BIOS "SuperSpeed" option, allows setting the CPU input clock manually. On older motherboards, the PCI and AGP clocks are derived from the CPU input clock setting. On newer boards, there is a feature called clock locking, where, no matter what the CPU input clock, the PCI and AGP run at sane 33Mhz and 66MHz values respectively. If the motherboard is an older one, that feature is not present. If you select, say "165MHz" in the BIOS, the PCI could be 165/4 = 41.25MHz. That is too high, and will cause some or all PCI devices to fail in one way or another. For example, if a PCI IDE controller card, derives a ribbon cable clock from the PCI bus clock, that will overclock the disk interface, resulting in data corruption. So this is why I'm asking for details about any manual settings to the clock (SuperSpeed etc). It is a BIOS designer tradition, to *NOT* warn the user of impending bad choices for PCI or AGP. The prospective values to be used for those things, may not even be shown on the screen. We have to guess at what might happen. Mobo http://www.foxconnchannel.com/EN-US/...D=en-gb0000191 Manual http://www.foxconnchannel.com/EN-US/...D=en-us0002117 Other than that, I'd be researching the health of my hardware, with an alternative OS boot disk. See if the hardware is visible in Ubuntu or Knoppix (700MB download and burn bootable CD), while running dmesg, lspci, lsusb, from a terminal window. Also, I like Adrians's suggestion of a web page to try. The only part of the suggestions there, that make me nervous, are applying hot fixes. I don't understand Microsoft's idea of version control, and how all of their software remains "sane" after being tweaked. This is why, you'll notice in the answers I give, I tend to shy away from hotfix type solutions, and would prefer if a fix was delivered in a Service Pack or Windows Update, because I basically don't trust Microsoft's ability for a hotfix not to bugger something up. Paul |
#15
|
|||
|
|||
USB Controller list in Device Manager
We’re getting into an area where I don’t know the nuts and bolts, but with
logic and your help, I’m learning. If it has screws, plugs and knobs, I’m all over it otherwise. I’m not a big fan of hot fixes either for similar reasons. I looked at the USBMan website info but I didn’t try anything there yet as none of the PCI slots seem to be working correctly at this point so the problem seems bigger than the SiS 7001. Everest recognizes both the onboard SiS USB and the NEC USB card for what they are as far as I can tell though I’m far from being an expert. The video card (Gigabyte GeForce FX 5200) shows up correctly as well. The audio card (Echo Mia) is another story altogether as Microsoft would have no data for that one. It shows up as Multimedia Controller [NoDB]. I’ll try a reinstall on that one later. As far as the CPU chip goes, I’m guessing that the folks who assembled the mobo only had 3.4GHz chips on hand. The board is designed to run at 2.8GHz, 800MHz FSB with a Prescott chip, hence the discrepancy. Clock info from CPU-Z and Everest as follows: Per CPU-Z CPU core speed 2806.5 Mhz Multiplier 14.0 Bus Speed 200.5 MHz Rated FSB 801.8 MHz Per Everest: CPU Clock: floats around 2804.65 to 2808.13 MHz Multiplier: 14.0 FSB: 200.33 to 200.58 MHz Memory bus same as FSB Seems to me not too far off the mark. The Award BIOS date is 12/28/04 and the version number matches the last one released by Foxconn though their website says it was released in 2007. Go figure. I’m reluctant to use a third party update - I’ve seen those royally hose up a machine. BIOS SuperSpeed set at 200 MHz (allowable range 200 – 232). On the Frequency/Voltage Control page, items listed are as follows: Auto Detect DIMM/PCI Clk: Enabled Spread Spectrum: Disabled CPU DRAM Frequency: SPD I haven’t found anything that specifically states at what speed the PCI bus is running. AGP must be OK, otherwise I probably wouldn’t be able to see what I’m typing. The installed memory is currently now 2GB PC-3200 400 MHz; was 1GB 400 MHz when I started this thread. What’s next? Thanks. |
|
Thread Tools | |
Display Modes | |
|
|