I performed a crash dump analysis on those BSOD dumps you provided and it actually crashes in win32k.sys and I don't see any trace of HWiNFO involved there.
I don't know the exact reason of the crash, but it's somehow related to font processing in the win32k driver.
Here are some more details about it:
PROCESS_NAME: csrss.exe
FOLLOWUP_IP: win32k!EngFreeMem+21
IMAGE_NAME: win32k.sys
stack:
nt!KeBugCheckEx
nt!ExDeferredFreePool+0x12da
win32k!EngFreeMem+0x21
win32k!bLoadGlyphSet+0x104
win32k!bReloadGlyphSet+0x24b
win32k!ttfdQueryFontTree+0x66
win32k!ttfdSemQueryFontTree+0x5a
win32k!PDEVOBJ::QueryFontTree+0x63
win32k!PFEOBJ:
fdg+0xa3
win32k!RFONTOBJ::bRealizeFont+0x46
win32k!RFONTOBJ::bInit+0x548
win32k!ulGetFontData2+0x31
win32k!ulGetFontData+0x7f
win32k!NtGdiGetFontData+0x4d
nt!KiSystemServiceCopyEnd+0x13
I don't know the exact reason of the crash, but it's somehow related to font processing in the win32k driver.
Here are some more details about it:
PROCESS_NAME: csrss.exe
FOLLOWUP_IP: win32k!EngFreeMem+21
IMAGE_NAME: win32k.sys
stack:
nt!KeBugCheckEx
nt!ExDeferredFreePool+0x12da
win32k!EngFreeMem+0x21
win32k!bLoadGlyphSet+0x104
win32k!bReloadGlyphSet+0x24b
win32k!ttfdQueryFontTree+0x66
win32k!ttfdSemQueryFontTree+0x5a
win32k!PDEVOBJ::QueryFontTree+0x63
win32k!PFEOBJ:

win32k!RFONTOBJ::bRealizeFont+0x46
win32k!RFONTOBJ::bInit+0x548
win32k!ulGetFontData2+0x31
win32k!ulGetFontData+0x7f
win32k!NtGdiGetFontData+0x4d
nt!KiSystemServiceCopyEnd+0x13