Does the BIOS for your Mobo come with a built-in flash utility? If you're using UEFI, it should be able to access files on your drives, in which case you can direct it to the .ROM file of your BIOS update and have it install through there. Otherwise, yeah, you may have to use their bloatware, just make sure to uninstall it afterwards.
When I get home this evening from work, I will use my work Laptop using the same ethernet/router port to download the same files - Only difference is this laptop is Win 7 x64 Professional instead of Ultimate, but that should make zero difference.
I'll download xperf & wireshark some time during the day and run it when I get home
The in OS executable method is not the best way to update your BIOS.
With the below method, it will ensure nothing will interfere during the update process.
Disclaimer: A failed BIOS update can cause severe issues with your computer. Only update BIOS if you have an issue that requires it.
How to update Gigabyte BIOS
Qflash method
Gigabyte "How To ~ Qflash Guide"
Use the Qflash method with a USB flash drive formatted to FAT32.
Apologies in the delay.
Hectic work week and personal issues.
I am now loading xperx and wireshark onto my work laptop and will run the same download file as before. Same Ethernet cable / router Port.
Please standby
Note, I was able to update BIOS to FD, but it made no difference.
Update:
So I installed Wireshark and xperf on the laptop.
Started xperf & Wireshark
Started the download of Windows6.1-KB947821-v22-x64.msu
Since it never stalled I let it run the full time of the download
I ended the xperf and it gave me a warning:
xperf: warning: Session "NT Kernel Logger" lost 341 events.
To avoid losing events, for in-file tracing try increasing buffer size or the minimum/maximum number of buffers. It is also recommended that a separate secondary storage device is used for in-file tracing, especially when analyzing secondary storage activity. Another way to avoid losing events is to trace in memory (-buffering mode). This guarantees that events will not be lost, but the time range of events captured can be significantly shorter than with in-file tracing.
Also, Wireshark refused to stop recording... Tried clicking the stop button, used the menu command, keyed command (ctrl-E) had to force quit it to stop recording subsequently losing the report.
I will try to run the full test again hoping for different results.
Same result as the first time, this time though it says 84329 events were lost.
Can't get Wireshark to stop recording for some reason
let me know if you want these xperf logs uploaded or if you think there's a workaround to avoid the event loss.
Just a quick update from more testing this weekend.
Went out and got a PCI 10/100 NIC card.
Popped it in, started to download the normal file listed previously.
It seemed to be OK at the start then it would stall out every min or so. Stopped at 27%, 35%, 53%, 66% & 91% It would hang for a min, then resume downloading, stall, resume without manual intervention.
Tested it on a few different download
Trillian 23mb download stalled at 33% and around 70%
Wireshark - 21MB download - stalled at 73% then finished up a few min later.
So I guess this might be good news that it's not hardware related???
In few occasions Wireshark will refuse to disconnect like that because there ends up being an issue with the LibPCap filter doesn't wanna discontinue. You'll need to restart the computer to get it to start working properly.
Can you provide another xperf/wireshark log combo with the new NIC so I can compare it with your previous logs?
Quote