Kharma, You had 2 dump files for 5/26
Code:
[COLOR=red]MEMORY_MANAGEMENT (1a)[/COLOR]
# Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000000411, The subtype of the bugcheck.
Arg2: fffff6fb831fd218
Arg3: 000000000000fa00
Arg4: fffff68000000003
Code:
BAD_POOL_HEADER (19)
The pool is already corrupt at the time of the current request.
This may or may not be due to the caller.
The internal pool links must be walked to figure out a possible cause of
the problem, and then special pool applied to the suspect tags or the driver
verifier to a suspect driver.
Arguments:
Arg1: 0000000000000003, the pool freelist is corrupt.
Arg2: fffff8a0030e5840, the pool entry being checked.
Arg3: fffff8a0030e5840, the read back flink freelist value (should be the same as 2).
Arg4: fffff8a010cb63d0, the read back blink freelist value (should be the same as 2).
You don't list what SSD you have, but please make sure you have the latest Firmware.
That is the second dump naming memory. With 32Gb of ram, it will take about 40 hours to run Memtest86+. From my perspective, a memory error is the worst error to have. When memory throws an error, the debugger will name almost any driver. So, that makes any dump file not reliable. I would like to try one other thing before you run memtest86+, however there is a possibility you will end up with a clean install of the OS. I have never had it happen to me, but it is still possible. I would suggest you back up all personal files to an external source.
The first thing is to make sure your SSD has the latest Firmware. I would also like you to run Seatools for DOS on your non SSD drive, both the long and the short test.
http://www.sevenforums.com/tutorials/313457-seatools-dos-windows-how-use.html#Part3 Also please run check disk on it
http://www.sevenforums.com/tutorials/433-disk-check.html
Next I would like you to create a restore point before going any further. The link for how to do that is below. When you are setting this up. Please sort the drivers by Provider and select all drivers NOT provided by Microsoft. Please run it for 24 hours of actual use. There are no restrictions. Do anything you want to. The test puts extra strain on the drivers in hopes that the bad driver will make the computer BSOD and the bad driver will be caught.
Driver Verifier - Enable and Disable
Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.
Information
What is Driver Verifier:
It puts stress on the drivers, and tries to make the faulty driver crash the computer. It is designed this way, to attempt to trap the offending driver.
What you will notice:
It will tend to make the computer rather slow and sluggish because the drivers are being stressed.
Let us know the results, with the subsequent crash dumps, if any
.
