Many thanks to you and the Intel team for investigating.
Here is a screen shot of my registry setting that I navigated to using the hardware IDs I found in Windows device manager: You can always go back and change to '1' again if you run into any new issues. HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\PCI\\3&33fd14ca&0&C8\Device Parameters\InterruptManagement\MessageSignaledInterruptPropertiesĬhange "MSISupported" value to '0'.
Changing or deleting registry keys can have unintended consequences. The above information is what you will need from your network connection in order to locate the right place in the Windows registry.Ĭaution: Make sure you back up your registry before proceeding. The numbers are different because I have a different network connection, but this does show where to find the hardware IDs. Here is an example for my network connection. Hardware IDs can be found in the device's "Details" tab. You can use Windows Device Manager to find the hardware device ID information that will be part of the path to the registry setting shown in brackets and highlighted below. After disabling MSI on a test machine here, the hang was no longer happening. I do not anticipate any driver update for this issue, but you should be able to make a registry change to the interrupt type from MSI to legacy to work around the issue.
For some reason the driver is not getting called by the OS in battery mode resulting in transmit hangs. When the system is in battery mode to save power, Windows 8 is doing something different compared to Windows 7 and earlier versions of Windows. Some Intel engineers did investigate this issue and this is what they found.
0 kommentar(er)
