In my nuc 8i I’ve observed the USB when start copying data after a short period the perfomance drops and stops.
Under windows, copying 2GB of data after 30 Secs gets halted and on esxi deployment from both usb fat32 and usb dvd has same behaviour
Fw is on the latest version.
Any idea of what can be?
Thanks a lot!
So the Intel support engineers can have more information about your system, Download, run, and save the results of this utility as a text file:
Then ATTACH the text file using the instructions under the reply window ( Drag and drop here or browse files to attach ).
thanks a lot for the help.
I had a look and i'm not sure what to download as all versions seem to be OS booted related. Currently the nuc now has nothing in the drives as the failure happened while deploying the Esxi installer, so it's not bootable.
On the other hand since the USB are almost dead - they stop after a short while - any idea how can i run the diagnose?
I will point out that this isn't isolated to NUC platforms. I have Desktop PCs that exhibit the same issue. I believe that this is a systemic chipset/driver problem.
I also *hate* when this happens and the message explaining why the transfer is paused is hidden behind some other window.
The USB controllers are part of the chipset (the PCH component), which is either permanently soldered to the motherboard or, in the case of SOC processors, is embedded within the processor package. Bottom line, it is not something you can replace. Microsoft ships the drivers for the USB controllers as part of the Windows O/Ss. Intel's Chipset Device Software (a.k.a. INF Update) package optimally configures these drivers for the hardware that is present.
So, is the issue in the PCH hardware? Is the issue in the drivers? Is the issue in the configuration for these drivers? Or is the issue in the design of how Windows uses these drivers? I don't know the answer. Since these controllers and their drivers have been around for a very, very long time, I am inclined to believe that they are ok.
I believe that it is more likely that this is a fundamental issue in the Windows design, but have no proof or basis for this belief; it's just a gut feel. Because I do not use systems with AMD processors and chipsets, I do not know if the issue happens there. Perhaps you know someone you can ask?