Hello
I recently purchased 4 @ MSI USB Digivox TV tuners.
The application is in the USA, with an antenna to capture ATSC broadcasts. I am using Windows Media Center.
I attached 2 of them to 2 each of 2 different computers both running Windows-7 64 bit. One computer is a Gateway, the other a ZOTAC.
In each case the results were the same. If attached to the USB 3.0 ports, works well at first, then problems later.
Specifically, some hours or days after I start using the Digivox, the system starts running slowly, with perhaps 20% of the CPU being used by "NT Kernel and System" process. At this point the system is too slow to make a high-quality video recording from the TV broadcast. Recorded broadcast is spotty at best, often with the bottom half of the screen grayed out. I can restart WMC or reboot to temporarily resolve the issue, but sooner or later it returns.
I have done the obvious and moved the Digivox devices to the USB 2.0 ports, and moved other (apparently) less sensitive equipment to the USB 3.0 ports, and for now all seems well.
Is this a problem with the Digivox, with the computer, with the driver???
Not a crisis, since I have a viable workaround, but it would seem like someone else must have also seen this issue.
I recently purchased 4 @ MSI USB Digivox TV tuners.
The application is in the USA, with an antenna to capture ATSC broadcasts. I am using Windows Media Center.
I attached 2 of them to 2 each of 2 different computers both running Windows-7 64 bit. One computer is a Gateway, the other a ZOTAC.
In each case the results were the same. If attached to the USB 3.0 ports, works well at first, then problems later.
Specifically, some hours or days after I start using the Digivox, the system starts running slowly, with perhaps 20% of the CPU being used by "NT Kernel and System" process. At this point the system is too slow to make a high-quality video recording from the TV broadcast. Recorded broadcast is spotty at best, often with the bottom half of the screen grayed out. I can restart WMC or reboot to temporarily resolve the issue, but sooner or later it returns.
I have done the obvious and moved the Digivox devices to the USB 2.0 ports, and moved other (apparently) less sensitive equipment to the USB 3.0 ports, and for now all seems well.
Is this a problem with the Digivox, with the computer, with the driver???
Not a crisis, since I have a viable workaround, but it would seem like someone else must have also seen this issue.
