BSOD at shutdown PFN Corrupt message

Rich thank you finding that bad setpoint driver - I have updated. Please tell zbook thank you for me. I have d/l the old DM log colector and will run per your instructions with the new flags added.

- - - Updated - - -

Set up verifier with new flags then rebooted - crashed instantly: DRIVER VERIFIER DETECTED VIOLATION. Restarted PC went into auto repair mode! Had to safe boot to get a start so I could reset verifier and get the logs.
Here is the DM log collector results.
OWNER981841-PC-Fri_07_31_2020_123314_53.zip - Google Drive

The DV induced crash is blaming a Hauppague driver.

Code:

DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
A device driver attempting to corrupt the system has been caught.  This is
because the driver was specified in the registry as being suspect (by the
administrator) and the kernel has enabled substantial checking of this driver.
If the driver attempts to corrupt the system, bugchecks 0xC4, 0xC1 and 0xA will
be among the most commonly seen crashes.
Arguments:
Arg1: 0000000000002004, Code Integrity Issue: The image contains a section that is not page aligned.
Arg2: ffffa20fbc6c4ac8, The image file name (Unicode string).
Arg3: fffff80e8b4101f8, The address of the section header.
Arg4: ffff898efb2061d0, The section name (UTF-8 encoded string).  .
. 
.
.
MODULE_NAME: hcw89
.
.
.
1: kd> lmvm hcw89
Browse full module list
start             end                 module name
fffff80e`8b410000 fffff80e`8b598080   hcw89      (no symbols)           
    Loaded symbol image file: hcw89.sys
    Image path: hcw89.sys
    Image name: hcw89.sys
    Browse all global symbols  functions  data
    Timestamp:        Tue Jul 10 07:53:40 2012 (4FFC41F4)
    CheckSum:         001960F8
    ImageSize:        00188080
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    Information from resource tables:

2012 is pretty old for Windows 10 - there's a Hauppague support page here which might have a newer driver for your device.

FIXED ! BSOD at shutdown PFN Corrupt message.
Thank you to ZTRUKER, CWSINK, MRPEPKA & ZBOOK for your professional advice and instruction. Ten Forums saves another lost soul!

Sorry I forgot to explain that. The solution was learning to use verifier and having you show me which old drivers need updates. In my case three drivers were left from before upgrading to Windows 10, that I thought were fixed with the upgrade: Nvidia - Video. Logitech - Setpoint, and Netgear - dongle.