- Jun 30, 2004
- 16,053
- 1,681
- 126
I've been posting a lot on these forums lately, and I've been spending a lot of time tweaking and improving my Z68 Sandy Bridge system. Those who may have seen some of my posts may know I was troubleshooting a seemingly infrequent instability problem that occurred on average about once every ten days.
Some kept telling me the problem was my overclock settings, but I'm pretty sure that's not it. I set the system back to default for a while, tweaked the OC settings, ran more stress tests.
Instead, I've been uncovering "other" hardware and driver problems; the instability seems to have disappeared. I cleaned up my Event Viewer logs. One "Distributed COM" error in particular may have caused periodic malfunction of my network interface, which had been inputting Media Center Live TV from my SiliconDust triple-tuner and then outputting it to my AVR and TV. I suspect that this may have been the problem -- or possibly one of the problems. But like I said, that behavior seems to have disappeared.
When I first built the system, I might have purchased the "Deluxe" motherboard which came with USB front-panel port device to use with the Asmedia USB 3.0 motherboard controller. But I bought the "Pro" version, and picked up a front-panel USB 3.0 Hub running off the Asmedia mobo port. This had been working fine when I first built the machine.
However, I never enabled the BIOS feature for using the Asmedia controller to "charge batteries" and devices. And I now remember one time when I plugged in my "Nicotene Vaping" device for a recharge -- to the USB 3.0 front-panel device.
The Asmedia controller worked with my USB 2.0 devices up to that point -- at least. But now, I find that a Windows Device Manager "!" with one of the two Asmedia XHCI USB controller nodes. I discovered this today when trying to upload pics from my camera for posting on another forum here. It wouldn't recognize the camera; it wouldn't recognize a USB hard disk; it wouldn't recognize a perfectly good 16GB USB thumb drive.
At first, I thought it was the front-panel hub device. And I was checking at the Egg and found reviews of that device posted after I bought it: people had experienced voltage surges with it. And certainly -- trying to charge a battery-driven item from it when the charging feature was disabled in BIOS didn't help! I removed the (SYBA or SIIG) f-panel hub, and found that direct-connect to the Asmedia mobo port still didn't recognize any of my USB devices.
So I disabled the Asmedia USB 3.0 controller on the mobo.
Well -- that wasn't the end of it. There are two USB 3.0 ports on my mobo I/O panel. I tried plugging in my USB hard disk and my flash drive. Nothing!
The mobo had a BIOS feature labeled "overvoltage or surge protection," which had been enabled.
So I'm reviewing all the Z68 schematics to see how it would be possible that my rear USB 3.0 ports aren't working. I THOUGHT those were Intel controller ports. Maybe they were Asmedia. The mobo manual doesn't specify anything other than a single USB 3.0 controller for IRQ sharing. I'm beginning to suspect that ALL the USB 3.0 ports -- the 20-pin motherboard port as well as the two rear I/O external ports -- work off the Asmedia controller.
Can anyone confirm this one way or the other? All the other USB 2.0 ports work "tip-top." I cannot find any other type of damage to the motherboard and its onboard devices. And I suppose I can simply buy a $20 PCI-E USB 3.0 controller, put it in my third PCIE x-16/x-4 slot, and I'm back in business.
I'm pretty sure the USB 3.0 controllers are backwards compatible with USB 2.0 devices, and I know I'd tested and used those front-panel hub ports several times.
Over-clocking as an addiction doesn't seem to be the major problem. When I trace it all back -- it is NICOTENE ADDICTION which may have been my downfall here!!
Some kept telling me the problem was my overclock settings, but I'm pretty sure that's not it. I set the system back to default for a while, tweaked the OC settings, ran more stress tests.
Instead, I've been uncovering "other" hardware and driver problems; the instability seems to have disappeared. I cleaned up my Event Viewer logs. One "Distributed COM" error in particular may have caused periodic malfunction of my network interface, which had been inputting Media Center Live TV from my SiliconDust triple-tuner and then outputting it to my AVR and TV. I suspect that this may have been the problem -- or possibly one of the problems. But like I said, that behavior seems to have disappeared.
When I first built the system, I might have purchased the "Deluxe" motherboard which came with USB front-panel port device to use with the Asmedia USB 3.0 motherboard controller. But I bought the "Pro" version, and picked up a front-panel USB 3.0 Hub running off the Asmedia mobo port. This had been working fine when I first built the machine.
However, I never enabled the BIOS feature for using the Asmedia controller to "charge batteries" and devices. And I now remember one time when I plugged in my "Nicotene Vaping" device for a recharge -- to the USB 3.0 front-panel device.
The Asmedia controller worked with my USB 2.0 devices up to that point -- at least. But now, I find that a Windows Device Manager "!" with one of the two Asmedia XHCI USB controller nodes. I discovered this today when trying to upload pics from my camera for posting on another forum here. It wouldn't recognize the camera; it wouldn't recognize a USB hard disk; it wouldn't recognize a perfectly good 16GB USB thumb drive.
At first, I thought it was the front-panel hub device. And I was checking at the Egg and found reviews of that device posted after I bought it: people had experienced voltage surges with it. And certainly -- trying to charge a battery-driven item from it when the charging feature was disabled in BIOS didn't help! I removed the (SYBA or SIIG) f-panel hub, and found that direct-connect to the Asmedia mobo port still didn't recognize any of my USB devices.
So I disabled the Asmedia USB 3.0 controller on the mobo.
Well -- that wasn't the end of it. There are two USB 3.0 ports on my mobo I/O panel. I tried plugging in my USB hard disk and my flash drive. Nothing!
The mobo had a BIOS feature labeled "overvoltage or surge protection," which had been enabled.
So I'm reviewing all the Z68 schematics to see how it would be possible that my rear USB 3.0 ports aren't working. I THOUGHT those were Intel controller ports. Maybe they were Asmedia. The mobo manual doesn't specify anything other than a single USB 3.0 controller for IRQ sharing. I'm beginning to suspect that ALL the USB 3.0 ports -- the 20-pin motherboard port as well as the two rear I/O external ports -- work off the Asmedia controller.
Can anyone confirm this one way or the other? All the other USB 2.0 ports work "tip-top." I cannot find any other type of damage to the motherboard and its onboard devices. And I suppose I can simply buy a $20 PCI-E USB 3.0 controller, put it in my third PCIE x-16/x-4 slot, and I'm back in business.
I'm pretty sure the USB 3.0 controllers are backwards compatible with USB 2.0 devices, and I know I'd tested and used those front-panel hub ports several times.
Over-clocking as an addiction doesn't seem to be the major problem. When I trace it all back -- it is NICOTENE ADDICTION which may have been my downfall here!!