Several different BSODs the past week, completely random.

The restart configures the new driver.

If you want to verify the new driver, you can do it. In Device manager, right click on the device name, that is "Intel(R) 8 Series/C220 Series SATA AHCI Controller - 8C02" and click on "properties" on the context menu. It will open the properties dialog with the "General" tag selected. Click on the "Driver" tab, and the "Driver details" button. It should show msahci.sys now.

Not right now. First let us see how it works with msahci. If the necessity arises, we will opt for verifier again.

Mate the dumps are coming up as hardware ones for me and I am wondering if it is a peripheral that is causing an issue.

Now specifically ( and I have had problems myself with it) have you got a Microsoft keyboard and mouse and if so do they use the Microsoft Intelli Media software - for which there are a few see this listing https://www.microsoft.com/hardware/en-us/downloads

Personally I have had to can the keyboards and mice at times and use another brand.

Yep well I was going on the failure bucket for that search and now am looking at the audiodg.exe and it is part of the Windows system so if you haven't already run these - I have not gone back through the thread yet

https://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html

https://www.sevenforums.com/tutorials/433-disk-check.html< if necessary include the /f and /r in the command line as per Option2
Do those in safe mode

There are other things to look through though as for example what is in the pic for msinfo.

PS on searching it is something hooked up via USB but what??

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
BAD_POOL_HEADER (19)
The pool is already corrupt at the time of the current request.
This may or may not be due to the caller.
The internal pool links must be walked to figure out a possible cause of
the problem, and then special pool applied to the suspect tags or the driver
verifier to a suspect driver.
Arguments:
Arg1: 0000000000000021, the data following the pool block being freed is corrupt.  Typically this means the consumer (call stack ) has overrun the block.
Arg2: fffffa800e43b000, The pool pointer being freed.
Arg3: 0000000000001c10, The number of bytes allocated for the pool block.
Arg4: 0012001500121c25, The corrupted value found following the pool block.
Debugging Details:
------------------
Unknown module 'Unknown_Module_fffff880_06a04000' found on stack, using vad to reload module.
!vad_reload -1 0xfffff88006a04000
Unable to get LeftChild of nt!_MMVAD_SHORT at fffffa8012003010
BUGCHECK_STR:  0x19_21
POOL_ADDRESS: GetPointerFromAddress: unable to read from fffff800030c2100
GetUlongFromAddress: unable to read from fffff800030c21c0
 fffffa800e43b000 Nonpaged pool
CUSTOMER_CRASH_COUNT:  1
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME:  audiodg.exe
CURRENT_IRQL:  2
ANALYSIS_VERSION: 6.3.9600.17298 (debuggers(dbg).141024-1500) amd64fre
LAST_CONTROL_TRANSFER:  from fffff80002fbb9c2 to fffff80002e858c0
STACK_TEXT:  
fffff880`0da5d588 fffff800`02fbb9c2 : 00000000`00000019 00000000`00000021 fffffa80`0e43b000 00000000`00001c10 : nt!KeBugCheckEx
fffff880`0da5d590 fffff880`06a24198 : 00000000`00000000 00000000`00000000 fffffa80`42434541 fffffa80`00000000 : nt!ExAllocatePoolWithTag+0x16fa
fffff880`0da5d640 00000000`00000000 : 00000000`00000000 fffffa80`42434541 fffffa80`00000000 fffff6fc`40032518 : Unknown_Module_fffff880_06a04000+0x20198
 
STACK_COMMAND:  kb
FOLLOWUP_IP: 
Unknown_Module_fffff880_06a04000+20198
fffff880`06a24198 ??              ???
SYMBOL_STACK_INDEX:  2
SYMBOL_NAME:  Unknown_Module_fffff880_06a04000+20198
FOLLOWUP_NAME:  MachineOwner
MODULE_NAME: Unknown_Module_fffff880_06a04000
IMAGE_NAME:  Unknown_Module_fffff880_06a04000
DEBUG_FLR_IMAGE_TIMESTAMP:  5252be31
FAILURE_BUCKET_ID:  X64_0x19_21_Unknown_Module_fffff880_06a04000+20198
BUCKET_ID:  X64_0x19_21_Unknown_Module_fffff880_06a04000+20198
ANALYSIS_SOURCE:  KM
FAILURE_ID_HASH_STRING:  km:x64_0x19_21_unknown_module_fffff880_06a04000+20198
FAILURE_ID_HASH:  {af464161-e09a-dda0-3dec-45d5ef50427d}
Followup: MachineOwner

This did come up at length USB\VID_0000&PID_0000\5&CC7037B&0&8 - Microsoft Community