BSOD - 1000007e lots of crashes

[cbjfan2009]

OK, so I've had very few problems until lately. Now, I see this BSOD.
[FONT=&quot]Problem signature:[/FONT]
[FONT=&quot] Problem Event Name: BlueScreen[/FONT]
[FONT=&quot] OS Version: 6.1.7601.2.1.0.768.3[/FONT]
[FONT=&quot] Locale ID: 1033[/FONT]
[FONT=&quot] [/FONT]
[FONT=&quot]Additional information about the problem:[/FONT]
[FONT=&quot] BCCode: 1000007e[/FONT]
[FONT=&quot] BCP1: FFFFFFFFC000001D[/FONT]
[FONT=&quot] BCP2: FFFFF80002C93F90[/FONT]
[FONT=&quot] BCP3: FFFFF88003910738[/FONT]
[FONT=&quot] BCP4: FFFFF8800390FF90[/FONT]
[FONT=&quot] OS Version: 6_1_7601[/FONT]
[FONT=&quot] Service Pack: 1_0[/FONT]
[FONT=&quot] Product: 768_1[/FONT]

I've added 3 minidumps. I hope you guys/gals know what's going on here.
THANK YOU

 

[Maguscreed]

Not sure exactly how to read this, but it almost looks like a failing harddrive.
The intel storage device driver is crashing even though you appear to have the proper and up to date version.
you can check that here though.
Intel® Driver Update Utility

Probably caused by : hardware ( iaStor+49e95 )

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

1: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003.  This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG.  This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG.  This will let us see why this breakpoint is
happening.
Arguments:
Arg1: ffffffffc000001d, The exception code that was not handled
Arg2: fffff80002c93f90, The address that the exception occurred at
Arg3: fffff88003910738, Exception Record Address
Arg4: fffff8800390ff90, Context Record Address

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


EXCEPTION_CODE: (NTSTATUS) 0xc000001d - {EXCEPTION}  Illegal Instruction  An attempt was made to execute an illegal instruction.

FAULTING_IP: 
nt!KiCommitThreadWait+1d0
fffff800`02c93f90 ff              ???

EXCEPTION_RECORD:  fffff88003910738 -- (.exr 0xfffff88003910738)
ExceptionAddress: fffff80002c93f90 (nt!KiCommitThreadWait+0x00000000000001d0)
   ExceptionCode: c000001d (Illegal instruction)
  ExceptionFlags: 00000000
NumberParameters: 0

CONTEXT:  fffff8800390ff90 -- (.cxr 0xfffff8800390ff90)
rax=0000000000000000 rbx=fffffa8004778b60 rcx=fffff88003910930
rdx=000000ec00000000 rsi=fffffa8004778c20 rdi=fffff880033d3180
rip=fffff80002c93f90 rsp=fffff88003910970 rbp=fffffa8004778b60
 r8=0000000000000000  r9=000000000027bc76 r10=000000000000d485
r11=fffff880009ed180 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na pe nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010282
nt!KiCommitThreadWait+0x1d0:
fffff800`02c93f90 ff              ???
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x7E

PROCESS_NAME:  System

CURRENT_IRQL:  2

ERROR_CODE: (NTSTATUS) 0xc000001d - {EXCEPTION}  Illegal Instruction  An attempt was made to execute an illegal instruction.

MISALIGNED_IP: 
nt!KiCommitThreadWait+1d0
fffff800`02c93f90 ff              ???

LAST_CONTROL_TRANSFER:  from fffff80002c934aa to fffff80002c93f90

FAILED_INSTRUCTION_ADDRESS: 
nt!KiCommitThreadWait+1d0
fffff800`02c93f90 ff              ???

STACK_TEXT:  
fffff880`03910970 fffff800`02c934aa : 00000000`00000000 fffffa80`048d0b08 00000000`00000000 00000000`00000000 : nt!KiCommitThreadWait+0x1d0
fffff880`03910a00 fffff880`014c6e95 : fffffa80`00000002 fffff880`03910d00 fffffa80`00000000 fffffa80`00000000 : nt!KeWaitForMultipleObjects+0x272
fffff880`03910cc0 fffffa80`00000002 : fffff880`03910d00 fffffa80`00000000 fffffa80`00000000 fffff880`0336df00 : iaStor+0x49e95
fffff880`03910cc8 fffff880`03910d00 : fffffa80`00000000 fffffa80`00000000 fffff880`0336df00 fffffa80`04778b00 : 0xfffffa80`00000002
fffff880`03910cd0 fffffa80`00000000 : fffffa80`00000000 fffff880`0336df00 fffffa80`04778b00 00000000`00000000 : 0xfffff880`03910d00
fffff880`03910cd8 fffffa80`00000000 : fffff880`0336df00 fffffa80`04778b00 00000000`00000000 fffffa80`04778c68 : 0xfffffa80`00000000
fffff880`03910ce0 fffff880`0336df00 : fffffa80`04778b00 00000000`00000000 fffffa80`04778c68 fffffa80`048d0ad8 : 0xfffffa80`00000000
fffff880`03910ce8 fffffa80`04778b00 : 00000000`00000000 fffffa80`04778c68 fffffa80`048d0ad8 fffffa80`048d0b08 : 0xfffff880`0336df00
fffff880`03910cf0 00000000`00000000 : fffffa80`04778c68 fffffa80`048d0ad8 fffffa80`048d0b08 fffff880`03367f40 : 0xfffffa80`04778b00


FOLLOWUP_IP: 
iaStor+49e95
fffff880`014c6e95 ??              ???

SYMBOL_STACK_INDEX:  2

SYMBOL_NAME:  iaStor+49e95

FOLLOWUP_NAME:  MachineOwner

IMAGE_NAME:  hardware

DEBUG_FLR_IMAGE_TIMESTAMP:  0

STACK_COMMAND:  .cxr 0xfffff8800390ff90 ; kb

MODULE_NAME: hardware

FAILURE_BUCKET_ID:  X64_IP_MISALIGNED

BUCKET_ID:  X64_IP_MISALIGNED

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