Video Screencast Help
Search Video Help Close Back
to help
New in the Rewards Catalog: Vouchers for "Symantec Technical Specialist" and "Symantec Certified Specialist" exams.

SEMP causes BSOD 0x0000007F (0x00000008,0x806d3130,0x00000000,0x00000000) ?

Updated: 30 Jun 2011 | 10 comments
acatsyscon's picture
0 0 Votes
Login to vote
This issue has been solved. See solution.

I am new to this forum, so let me know if i didn't post this discussion at the right place.

Issue:
One of my client is experiencing the bsod 0x0000007F (0x00000008,0x806d3130,0x00000000,0x00000000) that causes the computer to restart repeatedly. I did a bit research on this error message, and found articles on both Microsoft and Symantec about this error. It says that this errors usually occurs because there is limitation in kernel space from kernel drivers, and so related to Symantec Anti-virus auto-protection feature in version 9.x. My client has SEMP version 11.0.5002.333 however.

The solution suggested from the site is to prevent Auto-protect from using additional kernel stack. In order to do that, user needs to add the KStackMinFree registry value to "specifies a minimum amount of kernel stack that must be free for File System Realtime Protection or Auto-Protect to request file IO from the file system"

My question is will this KStackMinFree apply to SEMP version 11.0.5002.333? Are there any other resolution for this error?

Any help will be appreciated. :)

I have attached the screenshots of the error as well as the memory dump files

discussion Filed Under:

Comments

Vikram Kumar-SAV to SEP's picture
18
Mar
2010
0 Votes 0
Login to vote

On this XP box..first update

On this XP box..first update it will all Micsofot update patches.

Try this First Un-install SEP.

Delete the folders
C:\Documents and Settings\All Users\Application Data\Symantec
C:\Program Files\Common Files\Symantec Shared
C:\Program Files\Symantec

Restart the computer try installing again.

acatsyscon's picture
18
Mar
2010
0 Votes 0
Login to vote

Thanks will try and let you

Thanks will try and let you know.

acatsyscon's picture
18
Mar
2010
0 Votes 0
Login to vote

...

Thanks for the suggestion Vickram. That's exactly what i am planning to do. I will let you know the outcome later.

postechgeek's picture
22
Mar
2010
0 Votes 0
Login to vote

Are you running any

Are you running any app/device control policies? I have had issues with SysPlant.sys causing BSODs. I think I have seen around the forum that the SysPlant.sys issue is going to be fixed  in RU6. I'm not 100% sure though.

Mike

acatsyscon's picture
22
Mar
2010
0 Votes 0
Login to vote

No i don't recall we apply

No i don't recall we apply the device control policies in SEPM...

pete_4u2002's picture
22
Mar
2010
0 Votes 0
Login to vote

install only Antivirus

install only Antivirus component and if it is stable test all the components of SEP on test machine, before installing on production.

acatsyscon's picture
22
Mar
2010
0 Votes 0
Login to vote

That's what we applied for

That's what we applied for this latest version 11.0.5002.3333. It had been through thorough testing before it was pushed out to clients. However, there is this one specific client that is experiencing with the bsod error (he is running window Vista x32) while the rest is using window XP or win2k3. Do you think there maybe platform compatibility issue here?

acatsyscon's picture
22
Mar
2010
0 Votes 0
Login to vote

The computer seems to be

The computer seems to be stable after uninstalling the SEPM. Question is what causes it to act like that. I now have the client to install other antivirus as a temp resolution while figuring out why the SEPM is causing him so much trouble.

Thanks Vikram for the suggestion. It does help... but still don't know the root causes.... Any thought?

tenaheff's picture
23
Mar
2010
0 Votes 0
Login to vote

I saw this at a client

I saw this at a client yesterday on a 2008 server. The solution was to install the latest version of SEMP.

Vikram Kumar-SAV to SEP's picture
23
Mar
2010
0 Votes 0
Login to vote

May be some left overs by

May be some left overs by previous version ..