Thanks for a useful summary of your problem - most of us users don’t provide enough info.
Your info has given me some ideas which might be helpful.
How recently was this? Were you also using the same version of Windows (build 17134 which is version 1803)? It is possible that a Windows update could make a difference because there were changes in drivers and driver processing in 1803 and the previous version.
It is also worth checking that there is not some other underlying problem with your system:
-
Other drivers impacting the GlassWire driver
If this were a GlassWire bug then I’d expect more reports from other users as has happened in the past. But this might be because you have a unique configuration and a driver for another device is the culprit. This has happened before, e.g., with Nahimic audio drivers.
It may also be worthwhile checking if PFN_LIST_CORRUPT errors are happening on HP notebook models similar to yours. I would have checked myself but I couldn’t actually identify your model based on the info in your post. -
Other drivers which are out of date.
These three items (2-4) are discussed in this article:
https://www.drivereasy.com/knowledge/fix-pfn-list-corrupt-error-on-windows-solved/ -
Faulty memory is a common cause but I’d expect this to affect more processes.
-
Corrupted data on your storage drive(s) again is unlikely but still possible.