Gigabyte BIOS update won't stick; thoughts?

[Ketchup]

I could see a hub doing something like that, esp. if it's a Belkin.

 

[UsandThem]

So I looked at the memory mappings in the Windows System Information viewer, and the space 0xFF000000 - 0xFFFFFFFF belongs to a device called "Legacy device." Right away I'm thinking "south bridge / chipset."

So I go into Device Manager, set it to "Show Resources by Type" and expand the Memory tree. I find the device called "Legacy device" and righlt-click->Properties. I check and see that the Parent Device is "PCI."

Well, I don't have any legacy PCI devices (just the 3.0 x16 card for the GPU which is not on the SB/chipset bus on Skylake, anyway).

I have the exact same thing listed in my device manager, and I'm not having those issues. It's got to be something else. I also don't have any PCI devices.

 

[FlippedBit]

I could see a hub doing something like that, esp. if it's a Belkin.

It's a Rosewill. Actually I've got two hubs. I forgot the one built into my Dell monitor.

I have the exact same thing listed in my device manager, and I'm not having those issues. It's got to be something else. I also don't have any PCI devices.

I think those memory addresses would be the same. The theory right now is that one of my USB devices (or hubs) is acting up, or there's a bad interaction with the driver.

Everything's still plugged in but what I did last night is I went to Device Manager clicked on a couple things under System Devices to search for an updated driver online. The "Legacy device" did not have any updates available, but the "LPC controller" did. So I installed it over the existing driver and so far today there hasn't been a blue screen... but it's still too early. Fingers crossed.

 

[UsandThem]

It's a Rosewill. Actually I've got two hubs. I forgot the one built into my Dell monitor.



I think those memory addresses would be the same. The theory right now is that one of my USB devices (or hubs) is acting up, or there's a bad interaction with the driver.

Everything's still plugged in but what I did last night is I went to Device Manager clicked on a couple things under System Devices to search for an updated driver online. The "Legacy device" did not have any updates available, but the "LPC controller" did. So I installed it over the existing driver and so far today there hasn't been a blue screen... but it's still too early. Fingers crossed.

Good luck. You have more patience than I do. I would have yanked out everything besides the CPU, memory, and one hard drive and reset Windows 10.

If I didn't get any more crashes, I would add back the other hardware one item at a time until I had an issue.

Hopefully in the end it is just a driver issue instead of flaky hardware.

 

[FlippedBit]

Good luck. You have more patience than I do. I would have yanked out everything besides the CPU, memory, and one hard drive and reset Windows 10.

If I didn't get any more crashes, I would add back the other hardware one item at a time until I had an issue.

Hopefully in the end it is just a driver issue instead of flaky hardware.

That'll be my Plan B. Haven't taken that approach yet because it's too much of a hassle to disassemble my PC at this point.

 

[FlippedBit]

At the risk of jinxing myself or speaking too soon, I think I might be stable.

It's been about a week now since I updated the driver for the LPC controller in Device Manager, and I haven't seen any blue screens. I never unplugged my USB gear so everything is as it was (including the GPU) except for that one driver.

In case anyone's interested to know more about LPC: https://en.wikipedia.org/wiki/Low_Pin_Count

Not only does it manage legacy devices (PS/2, serial, etc.) but it shares a bus with BIOS and a controller with other I/O devices such as SATA and USB.

 

[UsandThem]

Hopefully that was the source of your issue. Maybe you have something installed or connected to your PC that the LPC controller had issues with.

Good work (knock on wood)!

 

[FlippedBit]

Thanks for the help!

If it comes back I'll start a new topic, as technically my BIOS issue is solved.