Did you run that executable? Hopefully not as it could have installed malicious software.
As to your crashes...
Code:
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [D:\Kingston\BSODDmpFiles\mark1981\mark1981\022912-18408-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`03010000 PsLoadedModuleList = 0xfffff800`03255670
Debug session time: Wed Feb 29 06:42:34.003 2012 (UTC - 7:00)
System Uptime: 0 days 7:04:00.727
Loading Kernel Symbols
...............................................................
................................................................
................................................................
...
Loading User Symbols
Loading unloaded module list
..........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 7A, {fffff6fb400007a0, ffffffffc00000c0, 11b7f0884, fffff680000f4000}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+37bba )
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
KERNEL_DATA_INPAGE_ERROR (7a)
The requested page of kernel data could not be read in. Typically caused by
a bad block in the paging file or disk controller error. Also see
KERNEL_STACK_INPAGE_ERROR.
If the error status is 0xC000000E, 0xC000009C, 0xC000009D or 0xC0000185,
it means the disk subsystem has experienced a failure.
If the error status is 0xC000009A, then it means the request failed because
a filesystem failed to make forward progress.
Arguments:
Arg1: fffff6fb400007a0, lock type that was held (value 1,2,3, or PTE address)
Arg2: ffffffffc00000c0, error status (normally i/o status code)
Arg3: 000000011b7f0884, current process (virtual address for lock type 3, or PTE)
Arg4: fffff680000f4000, virtual address that could not be in-paged (or PTE contents if arg1 is a PTE address)
Debugging Details:
------------------
ERROR_CODE: (NTSTATUS) 0xc00000c0 - This device does not exist.
BUGCHECK_STR: 0x7a_c00000c0
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: ERIS.exe
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from fffff800030fdb52 to fffff8000308cc40
STACK_TEXT:
fffff880`09241338 fffff800`030fdb52 : 00000000`0000007a fffff6fb`400007a0 ffffffff`c00000c0 00000001`1b7f0884 : nt!KeBugCheckEx
fffff880`09241340 fffff800`030b46cf : fffffa80`03cf20a0 fffff880`092414b0 fffffa80`078e1ec8 fffffa80`03cf20a0 : nt! ?? ::FNODOBFM::`string'+0x37bba
fffff880`09241420 fffff800`0309b02a : 00000000`00000000 00000000`00000008 ffffffff`ffffffff fffff680`000f8000 : nt!MiIssueHardFault+0x28b
fffff880`092414f0 fffff800`0306f90a : 00000000`00000000 fffff680`000f4000 00000000`00000000 fffffa80`0787b180 : nt!MmAccessFault+0x146a
fffff880`09241650 fffff800`030bf1ca : 00000000`1e990000 fffff6fb`7da00000 fffff680`000f4000 000007fe`00000001 : nt!MiMakeSystemAddressValid+0xea
fffff880`092416b0 fffff800`0305eb79 : ffffffff`00000000 00000000`1ea8ffff fffffa80`00000000 fffffa80`0787b180 : nt!MiDeleteVirtualAddresses+0xa39
fffff880`09241870 fffff800`03362b1a : fffff8a0`02640780 fffff880`09241c20 00000000`00000000 fffffa80`0787b180 : nt!MmCleanProcessAddressSpace+0x679
fffff880`092418c0 fffff800`0334609d : 00000000`c0000006 fffffa80`078e1e01 000007ff`fffd7000 00000000`00000000 : nt!PspExitThread+0x56a
fffff880`092419c0 fffff800`030803fa : 00000000`00000001 00000000`00000000 fffffa80`01698a20 fffff880`00961000 : nt!PsExitSpecialApc+0x1d
fffff880`092419f0 fffff800`03080740 : 00000000`19cdeb90 fffff880`09241a70 fffff800`03346010 00000000`00000001 : nt!KiDeliverApc+0x2ca
fffff880`09241a70 fffff800`0308bf77 : fffffa80`0787b180 00000000`19cdea78 fffff880`09241bc8 00000980`00000000 : nt!KiInitiateUserApc+0x70
fffff880`09241bb0 00000000`774f18ca : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceExit+0x9c
00000000`19cdea58 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x774f18ca
STACK_COMMAND: kb
FOLLOWUP_IP:
nt! ?? ::FNODOBFM::`string'+37bba
fffff800`030fdb52 cc int 3
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: nt! ?? ::FNODOBFM::`string'+37bba
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 4e02aaa3
FAILURE_BUCKET_ID: X64_0x7a_c00000c0_nt!_??_::FNODOBFM::_string_+37bba
BUCKET_ID: X64_0x7a_c00000c0_nt!_??_::FNODOBFM::_string_+37bba
Followup: MachineOwner
---------
Eris.exe is a possible malware threat. Remove the offending program if you are not familiar with it. Check in Start Menu -> Control Panel -> Uninstall a Program for any unrecognized items. Also check your task manager processes (show processes for all users) and look for any out of place processes.
Also, you may want to start a thread in https://www.sevenforums.com/system-security/ regarding these malicious items.
Quote