Hi weeeck and welcome to the forum. Two of your three dumps are error code 124. This is a fatal hardware error. Usual causes are Hardware, Incompatibility, May be
driver corruption. Your most recent dump is error code 3B:
Quote:
3B, SYSTEM_SERVICE_EXCEPTION. Usual causes: System service, Device driver, graphics driver, ?memory
Code:
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02e10000 PsLoadedModuleList = 0xfffff800`0304de50
Debug session time: Sat Nov 27 10:36:04.894 2010 (GMT-5)
System Uptime: 0 days 0:17:44.314
Loading Kernel Symbols
...............................................................
................................................................
......................
Loading User Symbols
Loading unloaded module list
.......
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 3B, {c000001d, fffff80002e7fa00, fffff88006279250, 0}
Probably caused by : memory_corruption
Followup: memory_corruption
---------
2: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c000001d, Exception code that caused the bugcheck
Arg2: fffff80002e7fa00, Address of the exception record for the exception that caused the bugcheck
Arg3: fffff88006279250, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.
Debugging Details:
------------------
EXCEPTION_CODE: (NTSTATUS) 0xc000001d - {EXCEPTION} Illegal Instruction An attempt was made to execute an illegal instruction.
FAULTING_IP:
nt!KiSystemServiceExit+65
fffff800`02e7fa00 37 ???
CONTEXT: fffff88006279250 -- (.cxr 0xfffff88006279250)
rax=0000000000000000 rbx=0000000000000000 rcx=fffffa8005655660
rdx=0000000000000000 rsi=0000000005e8fb60 rdi=0000000000000000
rip=fffff80002e7fa00 rsp=fffff88006279c20 rbp=fffff88006279ca0
r8=fffff80002e10000 r9=0000000000000000 r10=fffffffffffffffb
r11=fffffa8005655660 r12=000000007ef92000 r13=0000000005d2fd20
r14=0000000005d2ed90 r15=0000000072362450
iopl=0 nv up di pl zr na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010046
nt!KiSystemServiceExit+0x65:
fffff800`02e7fa00 37 ???
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: CODE_CORRUPTION
BUGCHECK_STR: 0x3B
PROCESS_NAME: IAStorIcon.exe
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from 0000000072362dd9 to fffff80002e7fa00
STACK_TEXT:
fffff880`06279c20 00000000`72362dd9 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceExit+0x65
00000000`05d2ed18 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x72362dd9
CHKIMG_EXTENSION: !chkimg -lo 50 -d !nt
fffff80002e7fa00-fffff80002e7fa3f 64 bytes - nt!KiSystemServiceExit+65
[ 48 89 45 d0 48 89 45 d8:37 39 34 45 36 42 41 31 ]
64 errors : !nt (fffff80002e7fa00-fffff80002e7fa3f)
MODULE_NAME: memory_corruption
IMAGE_NAME: memory_corruption
FOLLOWUP_NAME: memory_corruption
DEBUG_FLR_IMAGE_TIMESTAMP: 0
MEMORY_CORRUPTOR: LARGE_64
STACK_COMMAND: .cxr 0xfffff88006279250 ; kb
FAILURE_BUCKET_ID: X64_MEMORY_CORRUPTION_LARGE_64
BUCKET_ID: X64_MEMORY_CORRUPTION_LARGE_64
Followup: memory_corruption
---------
Debug session time: Sat Nov 27 10:17:46.828 2010 (GMT-5)
System Uptime: 2 days 23:13:33.638
Loading Kernel Symbols
...............................................................
................................................................
..........................
Loading User Symbols
Loading unloaded module list
...............................
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 124, {0, fffffa80065bc028, b2000000, 80000106}
Probably caused by : hardware
Followup: MachineOwner
---------
3: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
WHEA_UNCORRECTABLE_ERROR (124)
A fatal hardware error has occurred. Parameter 1 identifies the type of error
source that reported the error. Parameter 2 holds the address of the
WHEA_ERROR_RECORD structure that describes the error conditon.
Arguments:
Arg1: 0000000000000000, Machine Check Exception
Arg2: fffffa80065bc028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000b2000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000080000106, Low order 32-bits of the MCi_STATUS value.
Debugging Details:
------------------
BUGCHECK_STR: 0x124_GenuineIntel
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: System
CURRENT_IRQL: f
STACK_TEXT:
fffff880`031dda58 fffff800`02e23903 : 00000000`00000124 00000000`00000000 fffffa80`065bc028 00000000`b2000000 : nt!KeBugCheckEx
fffff880`031dda60 fffff800`02fe0593 : 00000000`00000001 fffffa80`063e3a60 00000000`00000000 fffffa80`063e3ab0 : hal!HalBugCheckSystem+0x1e3
fffff880`031ddaa0 fffff800`02e235c8 : 00000000`00000728 fffffa80`063e3a60 fffff880`031dde30 fffff880`031dde00 : nt!WheaReportHwError+0x263
fffff880`031ddb00 fffff800`02e22f1a : fffffa80`063e3a60 fffff880`031dde30 fffffa80`063e3a60 00000000`00000000 : hal!HalpMcaReportError+0x4c
fffff880`031ddc50 fffff800`02e22dd5 : 00000000`00000004 00000000`00000001 fffff880`031ddeb0 00000000`00000000 : hal!HalpMceHandler+0x9e
fffff880`031ddc90 fffff800`02e16e88 : fffffa80`084ff5d0 fffffa80`084ffaa8 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0x55
fffff880`031ddcc0 fffff800`02ec8fec : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40
fffff880`031ddcf0 fffff800`02ec8e53 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x6c
fffff880`031dde30 fffff800`02ec9c93 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x153
fffff880`031fd800 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x53
STACK_COMMAND: kb
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: hardware
IMAGE_NAME: hardware
DEBUG_FLR_IMAGE_TIMESTAMP: 0
FAILURE_BUCKET_ID: X64_0x124_GenuineIntel_PROCESSOR_CACHE
BUCKET_ID: X64_0x124_GenuineIntel_PROCESSOR_CACHE
Followup: MachineOwner
--------- I see one driver that could be cause of your problem; it certainly is not contributing to the stability of your system. It is an XP driver.
Quote:
MarvinBus64.sys Fri Sep 23 17:17:03 2005 - likely a part of Pinnacle Studio's Marvin Bus.
Pinnacle Systems - Product Support. Uninstall this software; it is not compatible with Win 7.
Try your system once you have uninstalled Marvin Bus. If you get another BSOD upload it to us and we will go from there. You should also read this article on your error code 124:
[2-Int] Stop 0x124 - what it means and what to try