System Extremely Unstable

Question

Windows 7 Ultimate x64 with all patches
Office 2007 Ultimate with all patches
One of my systems has begun to crash a lot lately.  The information below is from bluescreenview. 
The associated mini-dumps are at: http://1drv.ms/1kgMrIW
The latest two crashes (first two below) occurred with verifier turned on for all drivers.  Any suggestion on where to look further would be appreaciated.
==================================================
Dump File         : 060114-7875-01.dmp
Crash Time        : 6/1/2014 10:54:13 PM
Bug Check String  : UNEXPECTED_KERNEL_MODE_TRAP
Bug Check Code    : 0x0000007f
Parameter 1       : 00000000`00000008
Parameter 2       : 00000000`80050031
Parameter 3       : 00000000`000006f8
Parameter 4       : fffff800`028cfbf2
Caused By Driver  : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+75bc0
File Description  : NT Kernel & System
Product Name      : Microsoft® Windows® Operating System
Company           : Microsoft Corporation
File Version      : 6.1.7601.18409 (win7sp1_gdr.140303-2144)
Processor         : x64
Crash Address     : ntoskrnl.exe+75bc0
Stack Address 1   :
Stack Address 2   :
Stack Address 3   :
Computer Name     :
Full Path         : C:\Windows\Minidump\060114-7875-01.dmp
Processors Count  : 1
Major Version     : 15
Minor Version     : 7601
Dump File Size    : 268,984
==================================================
==================================================
Dump File         : 060114-17343-01.dmp
Crash Time        : 6/1/2014 10:42:32 PM
Bug Check String  : UNEXPECTED_KERNEL_MODE_TRAP
Bug Check Code    : 0x0000007f
Parameter 1       : 00000000`00000008
Parameter 2       : 00000000`80050031
Parameter 3       : 00000000`000006f8
Parameter 4       : fffff800`0286f87e
Caused By Driver  : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+75bc0
File Description  : NT Kernel & System
Product Name      : Microsoft® Windows® Operating System
Company           : Microsoft Corporation
File Version      : 6.1.7601.18409 (win7sp1_gdr.140303-2144)
Processor         : x64
Crash Address     : ntoskrnl.exe+75bc0
Stack Address 1   :
Stack Address 2   :
Stack Address 3   :
Computer Name     :
Full Path         : C:\Windows\Minidump\060114-17343-01.dmp
Processors Count  : 1
Major Version     : 15
Minor Version     : 7601
Dump File Size    : 268,984
==================================================
==================================================
Dump File         : 060114-8218-01.dmp
Crash Time        : 6/1/2014 10:16:17 PM
Bug Check String  : UNEXPECTED_KERNEL_MODE_TRAP
Bug Check Code    : 0x0000007f
Parameter 1       : 00000000`00000008
Parameter 2       : 00000000`80050031
Parameter 3       : 00000000`000006f8
Parameter 4       : fffff800`028c7b90
Caused By Driver  : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+75bc0
File Description  : NT Kernel & System
Product Name      : Microsoft® Windows® Operating System
Company           : Microsoft Corporation
File Version      : 6.1.7601.18409 (win7sp1_gdr.140303-2144)
Processor         : x64
Crash Address     : ntoskrnl.exe+75bc0
Stack Address 1   :
Stack Address 2   :
Stack Address 3   :
Computer Name     :
Full Path         : C:\Windows\Minidump\060114-8218-01.dmp
Processors Count  : 1
Major Version     : 15
Minor Version     : 7601
Dump File Size    : 268,984
==================================================
==================================================
Dump File         : 060114-8343-01.dmp
Crash Time        : 6/1/2014 10:04:50 PM
Bug Check String  : UNEXPECTED_KERNEL_MODE_TRAP
Bug Check Code    : 0x0000007f
Parameter 1       : 00000000`00000008
Parameter 2       : 00000000`80050031
Parameter 3       : 00000000`000006f8
Parameter 4       : fffff800`028d1b90
Caused By Driver  : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+75bc0
File Description  : NT Kernel & System
Product Name      : Microsoft® Windows® Operating System
Company           : Microsoft Corporation
File Version      : 6.1.7601.18409 (win7sp1_gdr.140303-2144)
Processor         : x64
Crash Address     : ntoskrnl.exe+75bc0
Stack Address 1   :
Stack Address 2   :
Stack Address 3   :
Computer Name     :
Full Path         : C:\Windows\Minidump\060114-8343-01.dmp
Processors Count  : 1
Major Version     : 15
Minor Version     : 7601
Dump File Size    : 268,984
==================================================
http://www.saberman.com

Answer 1

Hi,
All of the attached DMP files are of the
UNEXPECTED_KERNEL_MODE_TRAP (7f)
This bug check indicates that the Intel CPU generated a trap and the kernel failed to catch this trap.
BugCheck 7F, {8, 80050031, 6f8, fffff800028cfbf2}
The 1st parameter of the bug check is 0x00000008, or Double Fault, indicates that an exception occurs during a call to the handler for a prior exception. Typically, the two exceptions are handled serially. However, there are several exceptions that
cannot be handled serially, and in this situation the processor signals a double fault. There are two common causes of a double fault:
A kernel stack overflow. This overflow occurs when a guard page is hit, and the kernel tries to push a trap frame. Because there is no stack left, a stack overflow results, causing the double fault.
A hardware problem.
FAILURE_BUCKET_ID: X64_0x7f_8_VRF_nt!KiDoubleFaultAbort+b2
This dump is verifier enabled, yet failed to detect a 3rd party driver in violation, therefore this is likely a hardware problem, or you did not set up verifier properly. It's interesting to see
KiDoubleFaltAbort in the FBID, so I looked further:
kd> k
Child-SP RetAddr Call Site
fffff800`00ba4d28 fffff800`028c6169 nt!KeBugCheckEx
fffff800`00ba4d30 fffff800`028c4632 nt!KiBugCheckDispatch+0x69
fffff800`00ba4e70 fffff800`028cfbf2 nt!KiDoubleFaultAbort+0xb2
fffff880`009b9000 00000000`00000000 nt!KeAcquireInStackQueuedSpinLockAtDpcLevel+0x2
nt!KeAcquireInStackQueuedSpinLockAtDpcLevel+0x2 calls into
nt!KiDoubleFaultAbort+0xb2. KeAcquireInStackQueuedSpinLockAtDpcLevel is a routine that acquires a queued spin lock when the caller is already running at IRQL >= DISPATCH_LEVEL.
kd> !irql
Debugger saved IRQL for processor 0x0 -- 2 (DISPATCH_LEVEL)
We seem to be at DISPATCH_LEVEL at the time of the crash, so there's nothing wrong there. I suspect a hardware problem despite the problem stemming from acquiring a spinlock.
First off, please run Memtest for NO LESS than ~8 passes (several hours):
Memtest86+:
Download Memtest86+ here:
http://www.memtest.org/
Which should I download?
You can either download the pre-compiled ISO that you would burn to a CD and then boot from the CD, or you can download the auto-installer for the USB key. What this will do is format your USB drive, make it a bootable device, and then install the necessary
files. Both do the same job, it's just up to you which you choose, or which you have available (whether it's CD or USB).
Do note that some older generation motherboards do not support USB-based booting, therefore your only option is CD (or Floppy if you really wanted to).
How Memtest works:
Memtest86 writes a series of test patterns to most memory addresses, reads back the data written, and compares it for errors.
The default pass does 9 different tests, varying in access patterns and test data. A tenth test, bit fade, is selectable from the menu. It writes all memory with zeroes, then sleeps for 90 minutes before checking to see if bits have changed (perhaps because
of refresh problems). This is repeated with all ones for a total time of 3 hours per pass.
Many chipsets can report RAM speeds and timings via SPD (Serial Presence Detect) or EPP (Enhanced Performance Profiles), and some even support changing the expected memory speed. If the expected memory speed is overclocked, Memtest86 can test that memory performance
is error-free with these faster settings.
Some hardware is able to report the "PAT status" (PAT: enabled or PAT: disabled). This is a reference to Intel Performance acceleration technology; there may be BIOS settings which affect this aspect of memory timing.
This information, if available to the program, can be displayed via a menu option.
Any other questions, they can most likely be answered by reading this great guide here:
http://forum.canardpc.com/threads/28864-FAQ-please-read-before-posting
2. If the above happens to pass without errors, the only driver I see that could be causing a problem is VirtualBox (please uninstall), and your Intel network drivers are dated from 2008, so see if an update is available -
http://www.intel.com/p/en_US/support/detect
Regards,
Patrick
“Be kind whenever possible. It is always possible.” - Dalai Lama