Welcome aboard.
Checked both your dumps. The latest one says ....
Code:
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck BE, {fffff880019d3b20, 80000000047cf121, fffff80000ba0580, a}
Probably caused by : tcpip.sys ( tcpip!WfpAlepReauthorizeInboundConnection+39c )
Followup: MachineOwner
---------
It indicates network blockage. A network blockage may be caused either by an outdated network driver, or by an antivirus program.
Searching for the network driver, we got it:
Code:
Name [00000012] Realtek PCIe FE Family Controller
Driver c:\windows\system32\drivers\rt64win7.sys (7.46.610.2011, 526.60 KB (539,240 bytes), 6/10/2011 7:34 AM)
Apparently it is old. Did a further check.
Code:
lmvm rt64win7
start end module name
fffff880`04854000 fffff880`048d9000 Rt64win7 (deferred)
Image path: \SystemRoot\system32\DRIVERS\Rt64win7.sys
Image name: Rt64win7.sys
Timestamp: Fri Jun 10 12:03:15 2011 (4DF1BAAB)
CheckSum: 0008B67F
ImageSize: 00085000
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
It is really old. Update it from Realtek
Then, checked the another dump.
Code:
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000007E, {ffffffffc000001d, fffff800034bf6ad, fffff880037167b8, fffff88003716010}
Probably caused by : memory_corruption ( nt!MiAdjustCachedStacks+2d )
Followup: MachineOwner
---------
2: 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: fffff800034bf6ad, The address that the exception occurred at
Arg3: fffff880037167b8, Exception Record Address
Arg4: fffff88003716010, Context Record Address
Debugging Details:
------------------
EXCEPTION_CODE: (NTSTATUS) 0xc000001d - {EXCEPTION} Illegal Instruction An attempt was made to execute an illegal instruction.
FAULTING_IP:
nt!MiAdjustCachedStacks+2d
fffff800`034bf6ad 418d4e05 lea ecx,[r14+5]
EXCEPTION_RECORD: fffff880037167b8 -- (.exr 0xfffff880037167b8)
ExceptionAddress: fffff800034bf6ad (nt!MiAdjustCachedStacks+0x000000000000002d)
ExceptionCode: c000001d (Illegal instruction)
ExceptionFlags: 00000000
NumberParameters: 0
CONTEXT: fffff88003716010 -- (.cxr 0xfffff88003716010)
rax=0000000000000000 rbx=0000000000000008 rcx=00000000000000ff
rdx=0000000000002000 rsi=fffffa8004ee2400 rdi=0000000000000003
rip=fffff800034bf6ad rsp=fffff880037169f0 rbp=0000000000000001
r8=fffff88000002000 r9=0000000000000100 r10=000000000000203f
r11=0000000000000007 r12=0000000000000001 r13=fffff80003705a40
r14=0000000000000000 r15=fffff880009eef40
iopl=0 nv up ei pl zr na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010246
nt!MiAdjustCachedStacks+0x2d:
fffff800`034bf6ad 418d4e05 lea ecx,[r14+5]
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
BUGCHECK_STR: 0x7E
PROCESS_NAME: System
CURRENT_IRQL: 0
ERROR_CODE: (NTSTATUS) 0xc000001d - {EXCEPTION} Illegal Instruction An attempt was made to execute an illegal instruction.
LAST_CONTROL_TRANSFER: from fffff800034bff1d to fffff800034bf6ad
FAILED_INSTRUCTION_ADDRESS:
nt!MiAdjustCachedStacks+2d
fffff800`034bf6ad 418d4e05 lea ecx,[r14+5]
STACK_TEXT:
fffff880`037169f0 fffff800`034bff1d : 00000000`00000008 00000000`00000001 fffffa80`04ee2400 fffff800`034bfe8b : nt!MiAdjustCachedStacks+0x2d
fffff880`03716a40 fffff800`034c03eb : 00000000`00000008 fffff880`03716ad0 00000000`00000001 fffffa80`00000000 : nt!MmWorkingSetManager+0x45
fffff880`03716a90 fffff800`0376ce5a : fffffa80`04f04040 00000000`00000080 fffffa80`04ee2400 00000000`00000001 : nt!KeBalanceSetManager+0x1c3
fffff880`03716c00 fffff800`034c6d26 : fffff880`009ea180 fffffa80`04f04040 fffff880`009f4fc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`03716c40 00000000`00000000 : fffff880`03717000 fffff880`03711000 fffff880`037165c0 00000000`00000000 : nt!KiStartSystemThread+0x16
FOLLOWUP_IP:
nt!MiAdjustCachedStacks+2d
fffff800`034bf6ad 418d4e05 lea ecx,[r14+5]
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: nt!MiAdjustCachedStacks+2d
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
DEBUG_FLR_IMAGE_TIMESTAMP: 503f82be
STACK_COMMAND: .cxr 0xfffff88003716010 ; kb
IMAGE_NAME: memory_corruption
FAILURE_BUCKET_ID: X64_0x7E_BAD_IP_nt!MiAdjustCachedStacks+2d
BUCKET_ID: X64_0x7E_BAD_IP_nt!MiAdjustCachedStacks+2d
Followup: MachineOwner
---------
So, it gives us an idea that something makes memory failure. And it must be the antivirus.
Having a common suspect from both the dumps, I searched for your install AV, and found it.
Code:
Start Menu\Programs\McAfee
Frankly speaking, we have solved a real lot of memory leakage and network blockage issue by uninstalling McAfee only. It is strictly recommended to uninstall McAfee Using McAfee Removal Tool.
Use Microsoft Security Essentials as your antivirus with windows inbuilt firewall, and free MBAM as the on demand scanner.
Download and install those, and then run full system scans with both of them, one by one. Just for a safety reason, which McAfee cannot assure, too.
If you think, you may test your RAM modules for possible errors.
How to Test and Diagnose RAM Issues with Memtest86+
Run memtest for at least 8 passes, preferably overnight, per RAM module per slot.
Though I am not recommending memtest right now. ATM you do the aforesaid two. Update network driver and uninstall McAfee.
Free up the startup.
- Click on the Start button
- Type “msconfig (without quotes), click the resulting link. It will open the System Configuration window.
- Select the “Startup” tab.
- Deselect all items other than the antivirus.
- Apply > OK
- Accept the restart.
Let us know the results.
Quote