These blue screens were from a couple of days ago. The sandbox64.sys is new.
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:Windows\Minidump
Crash dumps are enabled on your computer.
On Thu 8/8/2013 12:39:13 AM GMT your computer crashed
crash dump file: C\Windows\Minidump\081013-42900-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C00)
Bugcheck code: 0xC1 (0xFFFFF98028654F00, 0xFFFFF98028654BD1, 0x634108, 0x23)
Error: SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION
file path: C:Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that the driver wrote to an invalid section of the special pool.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Thu 8/8/2013 12:39:13 AM GMT your computer crashed
crash dump file: C\Windows\memory.dmp
This was probably caused by the following module: sandbox64.sys (SandBox64+0x3C1EC)
Bugcheck code: 0xC1 (0xFFFFF98028654F00, 0xFFFFF98028654BD1, 0x634108, 0x23)
Error: SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION
file path: C:\Windows\system32\drivers\sandbox64.sys
product: Agnitum Ltd. Host Protection Component
company: Agnitum Ltd.
description: Host Protection Component
Bug check description: This indicates that the driver wrote to an invalid section of the special pool.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: sandbox64.sys (Host Protection Component, Agnitum Ltd.).
Google query: Agnitum Ltd. SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION
On Wed 8/7/2013 9:13:16 PM GMT your computer crashed
crash dump file: C\Windows\Minidump\080713-66643-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C00)
Bugcheck code: 0xE6 (0xF, 0x3, 0xFFFFF88003350FC0, 0x0)
Error: DRIVER_VERIFIER_DMA_VIOLATION
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This is the bug check code for all Driver Verifier
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Wed 8/7/2013 7:27:28 PM GMT your computer crashed
crash dump file: C\Windows\Minidump\080713-24804-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C00)
Bugcheck code: 0xA (0xFFFFF980251C3000, 0x2, 0x1, 0xFFFFF80002CBC655)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Wed 8/7/2013 7:11:37 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\080713-59779-01.dmp
This was probably caused by the following module: vsdatant.sys (vsdatant+0x46466)
Bugcheck code: 0xC4 (0xF6, 0x2F4, 0xFFFFFA80052D2060, 0xFFFFF88004144466)
Error: DRIVER_VERIFIER_DETECTED_VIOLATION
Bug check description: This is the general bug check code for fatal errors found by Driver Verifier.
A driver references a user-mode handle as kernel mode. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: vsdatant.sys .
Google query: vsdatant.sys DRIVER_VERIFIER_DETECTED_VIOLATION
On Wed 8/7/2013 5:40:12 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\080713-45240-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C00)
Bugcheck code: 0x19 (0x3, 0xFFFFF80002E20B00, 0xFFFFF80002E20B00, 0xFFFFF80002E20700)
Error: BAD_POOL_HEADER
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a pool header is corrupt.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Sun 7/28/2013 2:27:58 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\072713-52868-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C00)
Bugcheck code: 0xC5 (0x8, 0x2, 0x0, 0xFFFFF80002DAEB05)
Error: DRIVER_CORRUPTED_EXPOOL
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that the system attempted to access invalid memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Fri 7/26/2013 12:20:48 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\072513-52197-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C00)
Bugcheck code: 0x19 (0x3, 0xFFFFF80002E0C760, 0xFFFFF80002E0CA60, 0xFFFFF80002E0C760)
Error: BAD_POOL_HEADER
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a pool header is corrupt.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
8 crash dumps have been found and analyzed. 2 third party drivers have been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers:
sandbox64.sys (Host Protection Component, Agnitum Ltd.)
vsdatant.sys
If no updates for these drivers are available, try searching with Google on the names of these drivers in combination the errors that have been reported for these drivers and include the brand and model name of your computer as well in the query. This often yields interesting results from discussions from users who have been experiencing similar problems.
Read the topic general suggestions for troubleshooting system crashes for more information.
Note that it's not always possible to state with certainty whether a reported driver is actually responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.