0x0000007E stop error

[BarryG]

Have you tried post 18? Is the hard drive brand new?

Yes and yes. That's the reason I took out Zone Alarm and AVG Free so I could install Outpost. A file associated with ZA was causing some of the BSODs.
I got a brand new HDD because it failed several tests.
Sadly, it's still doing it.
I'm going to have to install the chipset driver mentioned in the other post by Bubbaleone to see what that does.
Barry

 

[BarryG]

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.

 

[BarryG]

I have just changed out the chipset drivers for the 15.5 set.

 

[BarryG]

The Sandbox64.sys file is apparently part of Outpost. Ugh.

 

[Ketchup]

These blue screens were from a couple of days ago. The sandbox64.sys is new.
...
--------------------------------------------------------------------------------
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

Did you say this is from before or after you uninstalled Zone Alarm? Because that is exactly what this is pointing to.

 

[BarryG]

I've downloaded LiveUpdate 5 and it says there is a chipset version 15.56 online. Anywho...

 

[Bubbaleone]

I've downloaded LiveUpdate 5 and it says there is a chipset version 15.56 online. Anywho...

If you never downloaded and installed Nvidia chipset driver version 15.5 then nothing about your Windows 7 installation, or any software that you install can work correctly. If you don't know how to download and install version 15.5 from the link I posted, then by all means use MSI's LiveUpdate 5, but whatever you do just get it installed first. After that your system will have the correct chipset drivers to function correctly, and then you'll be able to accurately determine whether or not you actually have other problems.

.

 

[BarryG]

Bubbaleone, I installed 15.50 before LiveUpdate 5 and chipset 15.56. I think I had installed it before. I can't remember right now.
I posted all of the WhoCrashed messages, from both before and after the Zone Alarm un-installation. Since I didn't delete the earlier dumps it still reads them and concludes vsdatant.sys is one of the problems.
She is installing her tablet driver now so we'll see how things go. Earlier it crashed when she started Skype, but didn't make a dump.

 

[Bubbaleone]

OK..Use CCleaner to delete all the junk files on the computer including the dump files. CCleaner leaves the dump files unchecked by default so be sure to put a check in that box. This will let you start fresh so you can see what (if any) new memory error dumps occur since installing driver version 15.56.

.

 

[BarryG]

Latest thing is for it to blue screen very briefly before going black and dead as a door knob. No dump file. It did this just a half hour ago or less.

 

[BarryG]

I've also gone back to the latest driver for video from the MSI site, not the nVidia site and re-installed Direct X using their web installer.

 

[Bubbaleone]

Be sure whenever you install any driver (or any software for that matter) that you immediately restart your computer, whether it prompts you to restart or not. There's often data that doesn't get written into the registry until a reboot occurs. If you immediately begin using the computer without rebooting, errors can occur that wouldn't otherwise have happened had you rebooted.

.

 

[denis280]

Just recently fixed a desktop with the same issue.the integrated gpu (NVIDIA) was the problem.I did try everything.new drivers old and beta.no luck.then put in a gt-430.and Voila. But as I mention in another post.Nvidia drivers are not stable lately for some cards.

 

[styrafoam]

Laptop is what, 4 -5 years old? If it was used for gaming regularly then I'm gonna go out on a limb and say its dead. The GPU/chipset is starting to go, its one thing the nvidia 8K series were really good at.

Just recently fixed a desktop with the same issue.the integrated gpu (NVIDIA) was the problem.I did try everything.new drivers old and beta.no luck.then put in a gt-430.and Voila. But as I mention in another post.Nvidia drivers are not stable lately for some cards.

Computer will be back in a few months with a dead motherboard.

 

[BarryG]

Sorry I haven't been back by lately. I bought her a nice Toshiba to replace it and this one has been running quite well. She is very happy with it. A505-S6020.
I hope styrafoam isn't right, but fear that he could be. One thought has been that the cpu I installed (from the list of approved components!) runs too hot for the shared heat sink.

I'm trying to recover the Recovery partition from the original hard drive. The original driver will be on there. All I have to do now is copy it to the new hard drive.

 

[BarryG]

Sorry I haven't been back by lately. I bought her a nice Toshiba to replace it and this one has been running quite well. She is very happy with it. A505-S6020.
I hope styrafoam isn't right, but fear that he could be. One thought has been that the cpu I installed (from the list of approved components!) runs too hot for the shared heat sink.

I'm trying to recover the Recovery partition from the original hard drive. The original driver will be on there. All I have to do now is copy it to the new hard drive.

Well, here it is just a few months later and she is back to using the MSI. The very nice and very capable Toshiba got STOLEN from our home along my son's and some other stuff. It's funny they didn't take mine which was sitting right out on the couch.
To calm nerves we've installed an alarm system.
I found an exact replacement for my son's and ....



.... replaced the motherboard in the MSI. Yes, after sitting aside for a few months the problems worsened and it had to be taken all the way down. I figure the processor was a bit much for the heat sink to handle since it also has to handle the GPU. It came with a Celeron but the white paper on the machine said it would handle a P4 with a 1066 FSB. This time I'm going with the top P4 in the list with an 800 MHz FSB. Less than 10 bucks. The celery seems a little slow when playing World of Warcraft.

Whomever said the motherboard was going was right.