Home > Blue Screen > Symantec Blue Screen Xp

Symantec Blue Screen Xp


After the installation, the computer unexpectedly restarts or encounters a blue screen with a STOP message similar to the following: STOP 0x0000007f (0x00000008, 0x00000000, 0x00000000, 0x00000000) UNEXPECTED_KERNEL_MODE_TRAP A common configuration for Create a free website or blog at WordPress.com. Run LiveUpdate to update the Proactive Threat Protection definitions to 13 September 2013 r14 or above. Provide feedback on this article Request Assistance Print Article Products Subscribe to this Article Manage your Subscriptions Search Again Situation You install Symantec Endpoint Protection. Source

Soon afterwards, Symantec posted updated — and less crash-prone — 'r12' signatures to the public LiveUpdate production servers. "Once the signature was rolled back, no new issues were reported from the If there is not enough stack space for processing the exception, then a stack overflow occurs and the system double-faults, resulting in a blue screen with a STOP message. Required minimum available kernel memory Hex value 5.0 KB 0x1400 5.5 KB 0x1600 6.0 KB 0x1800 6.5 KB 0x1a00 7.0 KB 0x1c00 7.5 KB 0x1e00 8.0 KB 0x2000 8.5 KB (recommended) If the problem persists, restart the computer. https://www.symantec.com/connect/forums/symtdisys-causing-blue-screen-win-xp-pro

Symefasi.sys Bsod

If it does not work, then one of simple solutions is to uninstall the buggy/incompatible Symantec Endpoint Protection program.   Restart Windows in Safe Mode and go to Control Panel and Privacy Policy | Cookies | Ad Choice | Advertise | Terms of Use | Mobile User Agreement Visit other CBS Interactive sites: Select SiteCBS CaresCBS FilmsCBS RadioCBS.comCBSInteractiveCBSNews.comCBSSports.comChowhoundCNETCollege NetworksGameSpotLast.fmMaxPrepsMetacritic.comMoneywatchmySimonRadio.comSearch.comShopper.comShowtimeTechRepublicThe InsiderTV.comUrbanBaby.comZDNet Topics All Right-click theKStackMinFreevalue, and then clickModify. ACCEPT & CLOSE Newsletters You have been successfully signed up.

To sign up for more newsletters or to manage your account, visit the Newsletter Subscription Center. Other possible values are defined in the following chart. After you restart the computer, confirm that the changes that you made to the KStackMinFree value are still present. Symefa64.sys Windows 10 To find out more and change your cookie settings, please view our cookie policy.

The BSOD was displaying following texts and codes:    SRTSPL64.sys is the file that's causing the problem. Edition: Asia Australia Europe India United Kingdom United States ZDNet around the globe: ZDNet Belgium ZDNet China ZDNet France ZDNet Germany ZDNet Korea ZDNet Japan Go Central Europe Middle East Scandinavia Create a SymAccount now!' Blue screen with "STOP 0x0000007f" and first parameter 0x00000008 error TECH99708 October 18th, 2016 http://www.symantec.com/docs/TECH99708 Support / Blue screen with "STOP 0x0000007f" and first parameter 0x00000008 error https://support.symantec.com/en_US/article.TECH210621.html Please log in using one of these methods to post your comment: Email (Address never made public) Name Website You are commenting using your WordPress.com account. (LogOut/Change) You are commenting using

TypeKStackMinFreefor the name of the new value. Symefasi.sys Windows 10 Submit a Threat Submit a suspected infected fileto Symantec. Recommended size for the KStackMinFree value Symantec recommends a range between 8.0 KB and 8.5 KB (Hex 2000-2200), though each environment is different and it may take some experimenting to find I understand I will receive a complimentary subscription to TechRepublic's News and Special Offers newsletter, and the Daily Digest newsletter (you can opt out at any time).

Symefa64.sys Symantec Corporation Efa

Submit a False Positive Report a suspected erroneous detection (false positive).

Information for: Enterprise Small Business Consumer (Norton) Partners Our Offerings: Products Products A-Z Services Solutions Connect with us: Support https://www.symantec.com/connect/forums/symefasys-causing-blue-screens Don't have a SymAccount? Symefasi.sys Bsod Every time a user tries to log-in, Windows gives a BSOD error message. Symefa.sys Blue Screen Windows 7 To prevent Auto-Protect from using additional kernel stack in a low stack situation, an internal configuration value named KStackMinFree was added and is configurable through the Windows registry.

Thank you for your feedback! http://brucelrussell.com/blue-screen/symantec-causing-blue-screen.html c)     Select Services tab, uncheck Services belonging to Manufacturer Symantec such as Liveupdate, Symantec Endpoint Protection,  Symantec Event Manager, Symantec Settings Manager, Symantec Management Client, Symantec Network Access Control etc. For Vista or Windows 7: type Services at Search programs and files box of Start menu, and press Enter. WARNING: We strongly recommend that you back up the registry before making any changes. 0x0000007f Windows Xp

Create a SymAccount now!' Blue screen error in SONAR Driver on Windows XP or Windows 2003 after September 16, 2013 update TECH210621 October 15th, 2013 http://www.symantec.com/docs/TECH210621 Support / Blue screen error Please see the document About Endpoint Protection staged content rollouts for details on this type of rollout. Symantec recommends that you update your virus definitions to this version or later. http://brucelrussell.com/blue-screen/symantec-blue-screen-2012.html No Yes Products Products Home Threat Protection Advanced Threat Protection Endpoint Protection Endpoint Protection Cloud IT Management Suite Email Security.cloud Data Center Security Blue Coat Products Information Protection Data Loss Prevention

d)    Press OK and restart the computer. Stop 0x0000007f (0x00000000, 0x00000000, 0x00000000, 0x00000000) Note: Auto-Protect only skips files that are accessed by trusted kernel components (Ring 0). Symantec Endpoint Protection Auto-Protect When Symantec Endpoint Protection Auto-Protect examines a file for viruses, it requests file access from the corresponding file system.

The limit is 0x2400 This scenario provides slightly less protection because Auto-Protect loads later during the startup process.

Incidents have been reported  where incompatible/buggy Symantec Endpoint Protection updates caused Blue Screen of Death on Windows Operating System: Buggy Symantec Endpoint Protection Update Blue Screens WinXP PCs: http://securitywatch.pcmag.com/none/300302-buggy-symantec-endpoint-protection-update-blue-screens-winxp-pcs Symantec explains Translated Content This is machine translated content Login to Subscribe Please login to set up your subscription. Restart the computer Changes to the KStackMinFree value take should effect after the service is restarted. 0x0000007f Windows 7 Windows Server 2003 kernel stack size The limit is 12 KB for kernel drivers.

Type msconfig and press enter. Bookmark the permalink. After the problem manifested itself on 11 July, Symantec rolled back the rev11 signature set — it was only being pushed out by the company's LiveUpdate servers for just over eight http://brucelrussell.com/blue-screen/symantec-blue-screen-windows-7.html Windows Server 2003 running NTFS Windows 2003 running NTFS examines the available kernel stack before processing an I/O request.

Set the Base to Hexadecimal, and then type2200in the Value field. It is available here: http://www.symantec.com/business/support/index?page=content&id=TECH206118 After updating a Symantec Endpoint Protection (SEP)client to these SONARdefinitions, dated September 16, 2013, a blue screen error occurs. If the registry value is set to 0, or greater than 0x2400, then File System Realtime Protection or Auto-Protect behaves normally. The problem should get solved!!!

Stop and then restart the Symantec Endpoint Protection service for changes to take effect.