BSoD - memory_corruption on memory cleanup of a terminating process

I have no idea why you're trying to use the !errrec command on a pool header corruption, this is typically caused by bad drivers.
That command is used on 0x124 bugchecks to find the reason why the system crashed.

Kernel Memory Dumps should give us a better understanding.

Follow these instructions on how to change to Kernel Memory Dumps.

Dump Files - Configure Windows to Create on BSOD

Once changed wait for another BSOD, then upload the new dump file to a file sharing website like OneDrive.
The new dump file will be located in C:/Windows/memory.dmp.

Don't zip it up as it corrupts the dump file by compressing it.

Then enable Driver Verifier.

Enable driver verifier but only enable the options: Standard settings and IRP logging step 3.
Don't enable Force Pending I/O Requests

Enable Driver Verifier to monitor the drivers.
Driver Verifier -Enable and Disable
Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.

   Information

We use Driver Verifier as it puts a stress on the drivers, and so it makes the unstable drivers crash. This should flag the driver responsible in the dump file.
It

Driver Verifier will make the system laggy, this is normal so don't worry.

Before enabling DV, make sure that you have earlier System restore points made in your computer.

If there are no points, make a System Restore Point Manually

Post back the results.

I removed the dump from first post, since it was a wrong one.
I had actually no dump for the BSoD I reported then.

----------

Rebooting with the Driver Verifier several times (I removed presumably faulty drivers coming from softwares I identified), I end up with this one I do not know:

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

DRIVER_VERIFIER_IOMANAGER_VIOLATION (c9)
The IO manager has caught a misbehaving driver.
Arguments:
Arg1: 0000000000000006, IRP passed to IoCompleteRequest contains invalid status
Arg2: 0000000000000103, the status
Arg3: fffff98007c0ee10, the IRP
Arg4: 0000000000000000

Debugging Details:
------------------

*** WARNING: Unable to verify timestamp for nvoclk64.sys
*** ERROR: Module load completed but symbols could not be loaded for nvoclk64.sys

BUGCHECK_STR:  0xc9_6

DRIVER_VERIFIER_IO_VIOLATION_TYPE:  6

IRP_ADDRESS:  fffff98007c0ee10

DEVICE_OBJECT: fffffa8006a72860

DRIVER_OBJECT: fffffa8006a72e70

IMAGE_NAME:  nvoclk64.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4ab00e3d

MODULE_NAME: nvoclk64

FAULTING_MODULE: fffff880052f7000 nvoclk64

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP

PROCESS_NAME:  System

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff800039361d2 to fffff80003493bc0

STACK_TEXT:  
fffff880`0355b528 fffff800`039361d2 : 00000000`000000c9 00000000`00000006 00000000`00000103 fffff980`07c0ee10 : nt!KeBugCheckEx
fffff880`0355b530 fffff880`05302264 : fffff880`0355b640 00000000`00000000 00000000`00000103 fffff980`07c0ee10 : nt!IovCompleteRequest+0xc2
fffff880`0355b600 fffff880`0355b640 : 00000000`00000000 00000000`00000103 fffff980`07c0ee10 00000000`00000000 : nvoclk64+0xb264
fffff880`0355b608 00000000`00000000 : 00000000`00000103 fffff980`07c0ee10 00000000`00000000 00000000`00000002 : 0xfffff880`0355b640


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nvoclk64+b264
fffff880`05302264 ??              ???

SYMBOL_STACK_INDEX:  2

SYMBOL_NAME:  nvoclk64+b264

FOLLOWUP_NAME:  MachineOwner

FAILURE_BUCKET_ID:  X64_0xc9_6_VRF_nvoclk64+b264

BUCKET_ID:  X64_0xc9_6_VRF_nvoclk64+b264

Followup: MachineOwner
---------

Upload the dump files.

Done

[EDIT 1610Z]
After removing both nVidia drivers from the verifier list, now there is no more BSoD after the Win7 starting logo animation and before the logon screen...

I will now try to reintegrate some drivers I left aside first hand (ATK drivers for keyboard special functions and webcam ones) to see what happens

I am struggling to find any other leads, then again it is a minidump.

Why do have the Nvidia System utility installed?

As far as I know it isn't necessary.

I would remove it.

That's good news :)