So I finally unpacked and booted up my new desktop yesterday. It looks like this◊
and contains an AMD FX-6300, 8GB of 1600MHz DDR3 RAM, a 2GB Sapphire Radeon HD 7790 factory-OCed to 1050MHz and a 1TB 7200RPM Seagate hard drive, running off a 500W PSU. It's running 64-bit Windows 7 Home Premium. The idea now is to switch to it as my main machine (I've been using this 2008 laptop as my main for several years), but so far I've just run into a mountain of problems, so I'm wondering if I can get any advice here.
First, the machine occasionally makes a sort of metallic 'click' noise. It kinda sounds like the hard drive head resetting (and is associated with a brief flash of the hard drive light), and will tend to happen once every minute or so for spans of several minutes. Also, sometimes right after the clicking noise there's a slight buzz that abruptly stops several seconds later, and when the hard drive spins down I can clearly hear a similar sort of buzz. Is the hard drive bad? If not, is there at least some way of making the clicking noise stop? Because it's kinda loud (the machine itself is already louder than my laptop, but the clicking noise is more distracting).
Second, the two times I've tried to shut the machine down (once to restart it during the setup for my Tenda USB wireless adapter, then again later with the normal shutdown command), it has gone back to the BIOS startup screen and stopped with the message 'verifying DMI pool data'. Both times, hitting the power button (not holding it down, just pressing it once) shut it down completely. The first time I turned it back on, it also said that 'Windows was not shut down properly' and prompted me for startup options (I selected 'start Windows normally'). I suspect this may have something to do with the wireless adapter being plugged in during startup (the machine may mistake the wireless adapter for a boot drive, this seems consistent with what I've read online about this particular error message), and the next time I start it up I'll do so with the adapter unplugged, but I'd rather not have to unplug and plug in the adapter each time the machine goes off and on, and having to reset it with the power button during startup is no good for either the hardware or the software. Does anyone know of other things I could try to fix this?
Third, the new machine and my laptop (the latter running 32-bit Windows Vista Home Premium) can't see each other on the network or share their Public folders with each other. I'd especially like the laptop to be able to see the desktop's Public folder, the reverse is not so important. I've set all the settings the way they're supposed to be according to every online guide (both machines have the same workgroup name and can both access the Internet through the same router just fine), and even tried turning off the new machine's firewall temporarily, but nothing worked. I guess the other alternative is to transfer everything using my external USB hard drive (it's big enough, but the reading and writing would take a long time). Any ideas? I've noticed an option in Windows 7 that says something like 'create an ad-hoc network', so I may try that and see if I can get anywhere with it, but still, it pisses me off that the one method that's supposed
to work doesn't.
Fourth, Process Explorer reports that the xhcdrv.sys thread in the System process is constantly sucking up about 16.67% CPU usage (i.e. all of one core). Due to having 5 other cores the machine is actually pretty usable even with this happening (and it runs really cool so far, the case barely feels warmer than the room around it), but I'd still like to fix this problem sooner rather than later. The Internet suggests that Gigabyte's motherboard USB3.0 drivers are responsible, but I checked them in the Device Manager and it said the drivers were up to date. Also, even when I unplugged the wireless adapter (which is the only thing plugged into a blue USB port, the mouse and keyboard are in black ones), CPU usage stayed up. Any ideas?
EDIT: The fourth problem (System drawing excess CPU time) has been solved by installing a driver patch.
edited 19th Mar '14 11:06:22 AM by Meklar