• Welcome to TechPowerUp Forums, Guest! Please check out our forum guidelines for info related to our community.

Windows 7 USBHUB.SYS causes memory corruption: system crashing, extremely difficult to diagnose

Joined
Oct 3, 2015
Messages
478 (0.13/day)
System Name Specs Last Update: 8/April/2024
Processor Intel Core i5 9400f 2.9GHz/4.0 Turbo (NoOC)
Motherboard Gigabyte Z370M D3H rev. 1.0
Cooling be quite! Dark Rock Slim 180W TDP (The Silent Wings 3 120mm Fan)
Memory Corsair Red Line 8x2 16GB 3000MHz (NoOC) DDR4-3000 15-17-17-35 (CMK16GX4M2B3000C15R) V1.35 ver 4.24
Video Card(s) NVIDIA GeForce MSI 980 Ti Golden Edition (NoOC)| Spare: GTX 650 Ti 1 GB
Storage Samsung 870 EVO 4 TB | Samsung 860 EVO 1 TB | Cold Backup: WDC Black 930 GiB WD1003FZEX
Display(s) Asus VG248QZ 1920x1080 144hz 24" (Current: 60hz)
Case Corsair Air 540
Audio Device(s) Realtek ALC892
Power Supply Corsair 850W RMi
Mouse Logitech M187 wireless (First day of use 30-9-2021)
Keyboard Logitech K270 wireless
Software Windows 10 21H2 LTSC 2021 / Linux: Candidates: Bazzite - Linux MX - Tuxedo - Kubuntu
2017-10 Security Monthly Quality Rollup for Windows 7 (KB4041681)
October 10, 2017—KB4041681 (Monthly Rollup)
Microsoft released a "security" update includes improvements and fixes that were a part of update KB4038803 (released September 19, 2017) and resolves the following issues:
  • Addressed issue with docking and undocking Internet Explorer windows.
  • Addressed issue with form submissions in Internet Explorer.
  • Addressed issue with URL encoding in Internet Explorer.
  • Addressed issue that prevents an element from receiving focus in Internet Explorer.
  • Addressed issue with the rendering of a graphics element in Internet Explorer.
  • Addressed issue where USBHUB.SYS randomly causes memory corruption that results in random system crashes that are extremely difficult to diagnose.
  • Security updates to Microsoft Windows Search Component, Windows kernel-mode drivers, Microsoft Graphics Component, Internet Explorer, Windows kernel, Windows Wireless Networking, Microsoft JET Database Engine, and the Windows SMB Server.

Source: https://support.microsoft.com/en-us/help/4041681/windows-7-update-kb4041681
 
2017-10 Security Monthly Quality Rollup for Windows 7 (KB4041681)
October 10, 2017—KB4041681 (Monthly Rollup)
Microsoft released a "security" update includes improvements and fixes that were a part of update KB4038803 (released September 19, 2017) and resolves the following issues:
  • Addressed issue with docking and undocking Internet Explorer windows.
  • Addressed issue with form submissions in Internet Explorer.
  • Addressed issue with URL encoding in Internet Explorer.
  • Addressed issue that prevents an element from receiving focus in Internet Explorer.
  • Addressed issue with the rendering of a graphics element in Internet Explorer.
  • Addressed issue where USBHUB.SYS randomly causes memory corruption that results in random system crashes that are extremely difficult to diagnose.
  • Security updates to Microsoft Windows Search Component, Windows kernel-mode drivers, Microsoft Graphics Component, Internet Explorer, Windows kernel, Windows Wireless Networking, Microsoft JET Database Engine, and the Windows SMB Server.

Source: https://support.microsoft.com/en-us/help/4041681/windows-7-update-kb4041681

That specific and serious stability bug is ridicoulus to exist in such an old OS. And far more tragic to fix it now that 2 more OS have been released after that. At least they didn't leave 7 without that fix.
 
That specific and serious stability bug is ridicoulus to exist in such an old OS. And far more tragic to fix it now that 2 more OS have been released after that. At least they didn't leave 7 without that fix.
Thing is... I posted this because I usually see people having strange unidentified "hardware" issues, however, this could be a possible cause? even when someone change his motherboard and find out it solves the problem, it could simply mean the issue isn't triggered anymore?
 
For better reference of OS updates that screw windows up, use askwoody.com
 
Pretty sure the BSOD would explicitly say usbhub.sys if it were related. They likely added "extremely difficult to diagnose" because logic dictates it would be caused by any USB device. Microsoft apparently discovered it was an error in the operating system, not the devices.
 
Back
Top