0x0000007F BSOD

[gimp]

Anybody having any large reports of this BSOD recently?

we have numerous computers that have started having this issue since at least Monday.
We have not released or pushed any patches to any of these machines recently.

Also, the machines continually reboot, without displaying the BSOD even though they are set to Not Automatically Reboot.

The only way to see the actual BSOD is to start Windows in Debugging mode.

So far we've had probably at least 2 dozen computers have this happen, and we haven't had any luck finding a cause.

 

[Tawnos]

Do you have zone alarm installed?

 

[gimp]

nope.. corporate environment. We are using Cisco Security Agent 6.02 for HIPS, Symantec Endpoint Protection for AV, and we are running Credant Mobile Guardian Shield for encryption.

I did manage to find this:

Often 0x7F or 0x1000007F stop codes trap code 8 are due to overflowing a fixed size kernel stack space resource.

We have heard numerous reports of systems experiencing a BSOD after applying this update, and we have been able to confirm this issue results from kernel stack exhaustion. KB 2393802 leaves less stack space available in the Windows kernel for other kernel modules to use.

on a Technet Blog
http://blogs.technet.com/b/asiasupp...007f-after-installing-ms11-011-kb2393802.aspx

on one machine, removing the patch made no difference. Another machine apparently didn't even have it installed, or it at least wasn't showing up in add/remove programs.

We think we may be getting there, though.

On my laptop, I uninstalled Credant and the machine started booting normally.

Another laptop, uninstalling Credant made no difference. Uninstalled CSA and then it started booting normally.

Increasing IRPStackSize made no difference.

There really doesn't seem to be any common denominator.

 

[Tawnos]

Common denominator seems to be filter drivers. Check for KB2478960 as well, as it too has been implicated as a possible cause.