Blue screen with "STOP 0x0000007f" error on Windows 2003/XP/2000/NT
Updated: 26 Oct 2011 | 3 comments
I would like a comfirmation if this article applies to Symantec Endpoint Protection version 11. Can the article be updated if that is the case ?
http://www.symantec.com/business/support/index?page=content&id=TECH99708
The document only refers to the following products but I was able to use the solution on SEP 11
3.0
AntiVirus Corporate Edition
8.0
Discussion Filed Under:
Group Ownership:
Comments
Hello, what part of the
Hello, what part of the solution were you able to use on SEP 11 and what exact build do you have? I don't think KStackMinFree in the registry is anything that SEP 11.x supports but I will have to confirm. The other solutions with OS hotfixes and driver updates could help though.
Thank you for marking as a solution if you felt this response met your needs!
I do not see this issue in SEP 11.x
We had the exact issue described in the article at the time we were using SAV 9 couple of years ago. we updated kstackmimnfree value on all our server to prevent the issue.
We deployed SEP 11 RU6 about two years ago, I have not seen any servers experienced the issues, I think you can safely start your SEP deployment.
We have few servers with SEP
We have few servers with SEP 11.0.5002.333 version with a similar issue. We installed a whitelisting application(Bouncer) which uses a kernel drivers. The server crash when we move the server to unsecured mode. This action triggers the crash event, appears to cause SEP to request additional stack memory. Ther Bug Check error is not the same as described in the article but the solution did work for me.
I found if I add the registry to SEP 11 then the server wont t crash.
This Registry key is for a 2003/2008 R2 x64 server.
[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Symantec\Symantec Endpoint Protection\AV\Storages\Filesystem\RealTimeScan]
"KStackMinFree"=dword:00002200
Would you like to reply?
Login or Register to post your comment.