How could I have missed this 
In multiple crash dumps of yours, it mentions the process crashing is ekrn.exe. Normally, this would mean absolutely nothing as in most cases a process crashing is at the fault of another 3rd party driver, or that's just the process that happened to crash with the system crash. However, ekrn.exe is ESET's NOD32 anti virus, and it may VERY well be NOD32 causing the crash. This would make the MOST sense as you mention you crash very soon after startup, and NOD32 is an anti virus that I can only assume is set to startup.
So, with this being said, let's use the official NOD32 uninstaller to safely and correctly remove the anti virus. Don't worry, you can install this later again if this doesn't end up being the culprit (I find this being very unlikely that it won't be considering this is looking very promising and is connecting with all of the bugchecks and culprits we've seen so far).
Dump for reference:
In multiple crash dumps of yours, it mentions the process crashing is ekrn.exe. Normally, this would mean absolutely nothing as in most cases a process crashing is at the fault of another 3rd party driver, or that's just the process that happened to crash with the system crash. However, ekrn.exe is ESET's NOD32 anti virus, and it may VERY well be NOD32 causing the crash. This would make the MOST sense as you mention you crash very soon after startup, and NOD32 is an anti virus that I can only assume is set to startup.
So, with this being said, let's use the official NOD32 uninstaller to safely and correctly remove the anti virus. Don't worry, you can install this later again if this doesn't end up being the culprit (I find this being very unlikely that it won't be considering this is looking very promising and is connecting with all of the bugchecks and culprits we've seen so far).
Dump for reference:
Code:
Loading Dump File [C:\Users\Cardbox\Downloads\050712-18392-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17790.amd64fre.win7sp1_gdr.120305-1505
Machine Name:
Kernel base = 0xfffff800`02e5a000 PsLoadedModuleList = 0xfffff800`0309e650
Debug session time: Mon May 7 18:59:48.728 2012 (UTC - 4:00)
System Uptime: 0 days 0:01:50.523
Loading Kernel Symbols
...............................................................
................................................................
.................................................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck C4, {e3, fffffa8008c10531, 6d0ef50, 0}
Probably caused by : ntkrnlmp.exe ( nt!VerifierBugCheckIfAppropriate+3c )
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
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: 00000000000000e3, Kernel Zw API called with user-mode address as parameter.
Arg2: fffffa8008c10531, Address inside the driver making the incorrect API call.
Arg3: 0000000006d0ef50, User-mode address used as API parameter.
Arg4: 0000000000000000
Debugging Details:
------------------
BUGCHECK_STR: 0xc4_e3
FAULTING_IP:
+6637643263363463
fffffa80`08c10531 85c0 test eax,eax
FOLLOWUP_IP:
nt!VerifierBugCheckIfAppropriate+3c
fffff800`0335f3dc cc int 3
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VERIFIER_ENABLED_VISTA_MINIDUMP
PROCESS_NAME: [B]ekrn.exe[/B]
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from fffff8000335f3dc to fffff80002ed6c80
STACK_TEXT:
fffff880`08501458 fffff800`0335f3dc : 00000000`000000c4 00000000`000000e3 fffffa80`08c10531 00000000`06d0ef50 : nt!KeBugCheckEx
fffff880`08501460 fffff800`0335fec5 : fffffa80`071e7980 fffff800`0336e09a fffff880`084fc000 fffff880`08502000 : nt!VerifierBugCheckIfAppropriate+0x3c
fffff880`085014a0 fffff800`0336139e : 00000000`00000000 00000000`00000028 fffffa80`08c103b9 fffff800`0000051e : nt!ViZwCheckAddress+0x35
fffff880`085014e0 fffff800`03361426 : fffff880`08501628 fffff880`08501628 00000000`00000000 00000000`00000000 : nt!ViZwCheckUnicodeString+0x2e
fffff880`08501520 fffff800`03364d99 : fffffa80`08c10531 00000000`00000000 00000000`70616745 00000000`00000000 : nt!ViZwCheckObjectAttributes+0x26
fffff880`08501550 fffffa80`08c10531 : 00000000`06d0ef50 00000000`00000000 00000000`06d0ef80 00000000`06d0efdc : nt!VfZwOpenFile+0x49
fffff880`08501590 00000000`06d0ef50 : 00000000`00000000 00000000`06d0ef80 00000000`06d0efdc 00000000`00000007 : 0xfffffa80`08c10531
fffff880`08501598 00000000`00000000 : 00000000`06d0ef80 00000000`06d0efdc 00000000`00000007 00000000`00000021 : 0x6d0ef50
STACK_COMMAND: kb
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: nt!VerifierBugCheckIfAppropriate+3c
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 4f558b55
FAILURE_BUCKET_ID: X64_0xc4_e3_VRF_nt!VerifierBugCheckIfAppropriate+3c
BUCKET_ID: X64_0xc4_e3_VRF_nt!VerifierBugCheckIfAppropriate+3c
Followup: MachineOwner
---------
