forth bugcheck was a corruption in the file system right after returning from a 3rd party filter driver. start cmd.exe as an admin, then run
fltmg.exe to see what filters are running. most likely a bug in a 3rd party filter.
-----------
third bugcheck was a memory corruption in a internal routine.
you might want to run memtest86 to confirm your memory settings and RAM are ok.
took 3 days to bugcheck, I would expect a driver corrupted the memory but it can not hurt to run the memtest86
----------
second bugcheck was memory corruption, most likely from a driver freeing memory twice.
verifier should b e able to catch the driver. You have lots of old drivers for such a new machine.
-----------
looked at the most current bugcheck, something corrupted something inside of the filesystem.
I would suspect your winmagic data security software. You also have a very old raid driver but you would have been getting lots of bugchecks before now.
look for a update to you encryption software.
or turn on verifier.exe and see if it can name the actual bad driver.
- make a recovery point
-start cmd.exe as an admin, then run
sfc.exe /scannow
verifier.exe /standard /all
reboot your machine and wait for the next bugcheck.
put the next bugcheck on a server and post a link.
Note: use verifier.exe /reset to turn off verifier functions when done testing.
you can also use whocrashed.exe or bluescreenview.exe to try to figure out what driver crashed.
Facebook
Twitter
Instagram