All of the attached DMP files are of the DRIVER_PAGE_FAULT_BEYOND_END_OF_ALLOCATION (d6)
This indicates the driver accessed memory beyond the end of its pool allocation.
Essentially, what happened here was there was a driver that allocated N bytes of memory (random #) and then went ahead and referenced way more than that original #. This bug check occurs when you have the Special Pool option enabled with Driver Verifier, which we can confirm:
2: kd> !verifier
Verify Level 1aaedbf ... enabled options are:
Inject random low-resource API failures
All pool allocations checked on unload
Io subsystem checking enabled
Deadlock detection enabled
DMA checking enabled
Security checks enabled
Miscellaneous checks enabled
Also with -- DEFAULT_BUCKET_ID: VERIFIER_ENABLED_VISTA_MINIDUMP
...and - FAILURE_BUCKET_ID: X64_0xD6_VRF
We can also see from the FBID string that nvlddmkm.sys (nVidia video driver) was the driver that caused the bug check. Aside from the beta and the latest, have you tried a few versions behind? If so, there's likely a conflict going on here which we'll need a bit of detective work to find.
HWiNFO64A.SYS - Fri Nov 22 10:45:10 2013
^^ HWiNFO32 Kernel Driver. I am very curious as to if HWiNFO is causing conflicts with its diagnostics, so let's go ahead and remove it for temporary troubleshooting purposes.