You have one error code that I have never seen before and it is 0x000000A7: BAD_EXHANDLE and it means that the kernel-mode handle table detected an inconsistent handle table entry state. There is virtually zero on the internet concerning this error and even Microsoft gives no more than what I wrote here. However, I did find this additional information: "is caused by a corrupt registry entry that should be repaired immediately to prevent further corruption in other applications and/or hardware. Risks include hardware failure, blue screen errors and fatal crashes." That is a tad melodramatic and read further for a suggested next step.
Two errors are 0xD1 and these are predominantly caused by faulty drivers though faulty or mismatched RAM can also be a cause. One did not give anything dfinitive, but the other specifically cited the Symantec/Norton driver Symtdi.sys as the probable cause. We've seen many problems here concerning this driver and Symantec as a whole.
However, the last two dumps are what is most telling at this point. Both are 0x8E errors and these are almost always caused by hardware and are a strong indicator of corrupted memory. One dump was not specific but one cited hardware as the cause.
My first besty advice for you is to run Memtest on your RAM. See this link:
https://www.techspot.com/vb/topic62524.html
Let it run for a LONG time. The rule is a minimum of 7 Passes. There are 8 individual tests per Pass. Many people will start this test before going to bed and check it the next day.
If you have errors you have corrupted memory and it needs to be replaced.
Also, with errors you need to run this test per stick of RAM. Take out one and run the test. Then take that one out and put the other in and run the test. If you start getting errors before 7 Passes you know that stick is corrupted and you don’t need to run the test any further on that stick.
* Get back to us with the results.
