As a result, you may experience blue screen errors associated with WpsHelper.sys. Memtest86 will now be installed on your USB and you are ready to test for the possible source of WpsHelper.sys errors. symptons: 3 different domain controlled networks with computers of various builds (windows 7 and windows 10, both pro) are all getting a worker thread impersonalization BSOD. Using Registry Editor incorrectly can cause serious problems that may require you to reinstall Windows. http://digitalsurgeon.net/blue-screen/symantec-endpoint-protection-12-1-blue-screen-windows-7.html
Follow the steps in the Wizard to choose a restore point. I already contacted norton support, but he says "I've never heard that issue". Please try the request again. thank you tons. https://www.symantec.com/connect/forums/bsod-caused-symantec-endpoint-protection-1215
Furthermore, there's a possibility that the WpsHelper.sys blue screen error you are experiencing is related to a component of the malicious program itself. For Vista or Windows 7: type msconfig at Search programs and files box of Start menu, and press Enter. Mohan_G Admin Administrator30 Reg: 18-Jan-2012 Posts: 1,279 Solutions: 45 Kudos: 1,070 Kudos0 Re: Norton causing BSOD Posted: 29-Jun-2016 | 12:42PM • Permalink Thanks @cccrkfg, I've sent you a Private Message requesting
Using a registry cleaner automates the process of finding invalid registry entries, missing file references (like the one causing your WpsHelper.sys error), and broken links within the registry. SYS files such as WpsHelper.sys are third-party (eg. If all of the above steps were unsuccessful, and Memtest86 finds memory corruption, it highly likely that your WpsHelper.sys blue screen error is due to bad memory. Symefasi.sys Windows 10 Looks like I am using 12.1.6 as well.
Manually editing the Windows registry to remove invalid WpsHelper.sys keys is not recommended unless you are PC service professional. Symefa64.sys Windows 10 Maintaining a driver backup provides you with the security of knowing that you can rollback any driver to a previous version if necessary. I didnt understand any other websites and blah blah this was so easy to followReplyDeleteAnonymous19 August 2013 at 11:04Thanks, It works fine.ReplyDeleteimjussayin!3 September 2013 at 16:28You are the freakin man. https://www.symantec.com/connect/forums/symefasys-causing-blue-screens If you are getting error The Windows Installer Service could not be accessed.
In all 3 environments i see a common after effect. http://www.technologydwell.com/2013/01/fixing-blue-screen-of-death-bsod-error.html Hugh NortonoftheSea Contributor4 Reg: 28-Jun-2016 Posts: 10 Solutions: 0 Kudos: 0 Kudos0 Re: Norton causing BSOD Posted: 29-Jun-2016 | 8:05PM • Edited: 29-Jun-2016 | 8:06PM • Permalink Our third machine applied Symefasi.sys Bsod Click Programs and Features. Symefa64.sys Symantec Corporation Efa b) In Services, select Windows Installer, right-click it and select Properties.
Also, this is happening with it still in maintenance mode, not just standard. 1358-375062-1914785 Back to top Ed Schmidt Members #12 Ed Schmidt 67 posts Posted 05 February 2016 - 02:52 this contact form Because of this risk, we highly recommend using a trusted registry cleaner such as WinThruster (Developed by Microsoft Gold Certified Partner) to scan and repair any WpsHelper.sys-related registry problems. Use Registry Editor at your own risk. In the Export Range box, be sure that "Selected branch" is selected. Symefa.sys Blue Screen Windows 7
JVO Visitor2 Reg: 29-Jun-2016 Posts: 2 Solutions: 0 Kudos: 0 Kudos0 Re: Norton causing BSOD Posted: 30-Jun-2016 | 9:52AM • Permalink Hi Snehansh, All affected machines at my customers are at Your cache administrator is webmaster. To avoid data loss, you must be sure that you have backed-up all of your important documents, pictures, software installers, and other personal data before beginning the process. http://digitalsurgeon.net/blue-screen/symantec-endpoint-protection-causing-blue-screen-windows-7.html Norton is only updated.
System Restore can return your PC's system files and programs back to a time when everything was working fine. Symantec Bluecoat Several functions may not work. You will be prompted with a permission dialog box.
your Desktop). c) Under Startup type, select Disabled, then OK. Vincent und die Grenadinen Südafrika Surinam Swasiland Tadschikistan Taiwan Tansania Thailand Togo Trinidad und Tobago Tschad Tschechien Tunesien Türkei Turkmenistan Turks- und Caicosinseln Uganda Ukraine Ungarn Uruguay USA Usbekistan Vanuatu Venezuela I have personally tried to strip my policies back and I still get the same issue. 1358-375062-1914661 Back to top Ed Schmidt Members #9 Ed Schmidt 67 posts Posted 04 February
lol. 1358-375062-1914518 Back to top Andrew Prather Members #6 Andrew Prather 4 posts Posted 04 February 2016 - 06:21 PM Ed. They are telling me "it is too complicated for me to understand and fix" (paraphrased) bjm_ Guru Norton Fighter25 Reg: 07-Sep-2008 Posts: 13,586 Solutions: 279 Kudos: 1,977 Kudos0 Re: Norton causing Please see "Causes of WpsHelper.sys Errors" below for more information. Check This Out Please Note: If WpsHelper.sys errors still persist after a clean install of Windows, your SYS problem MUST be hardware related.
If the previous troubleshooting steps did not resolve your WpsHelper.sys STOP error, running “chkdsk” may uncover and repair the cause of your BSOD. W10 enterprise x64. Urgent Customer Issues If you are experiencing an issue that needs urgent assistance please visit our customer support area: Chat with Norton Support @NortonSupport on Twitter Who's online There are currently However I have had enough today so I am out of here! 1358-375062-1914677 Back to top Ed Schmidt Members #10 Ed Schmidt 67 posts Posted 05 February 2016 - 12:10 AM
Monday the first and today second and third. NortonoftheSea Contributor4 Reg: 28-Jun-2016 Posts: 10 Solutions: 0 Kudos: 0 Kudos0 Re: Norton causing BSOD Posted: 29-Jun-2016 | 10:57PM • Permalink There is no fix yet. The only option is to presidente Visitor2 Reg: 01-Jul-2016 Posts: 3 Solutions: 0 Kudos: 0 Kudos0 Re: Norton causing BSOD Posted: 01-Jul-2016 | 3:18AM • Permalink Yesterday we did a test in 4 machine of different will be keeping an eye on this site!!ReplyDeleteBruno Pereira15 January 2014 at 13:35Congratulations!ReplyDeleteAnonymous13 February 2014 at 12:43you are a genius man!
thanks!!!ReplyDeleteAnonymous13 February 2014 at 20:24thanks alot, spend alot of time trying other fixes with no successReplyDeleteYoshi Green22 April 2014 at 18:07Thank youReplyDeleteAnonymous11 July 2014 at 22:27Awesome easy fix thanks,,!ReplyDeleteAnonymous22 June 2015 Cheers Ean NortonoftheSea Contributor4 Reg: 28-Jun-2016 Posts: 10 Solutions: 0 Kudos: 0 Kudos0 Re: Norton causing BSOD Posted: 29-Jun-2016 | 9:33AM • Edited: 29-Jun-2016 | 9:33AM • Permalink There's nothing specific Step 8: Check for Hard Drive Corruption ("chkdsk /f") While most storage-related, WpsHelper.sys blue screen errors are caused by problems with your hard disk drivers or storage controllers, in some cases Mohanakrishnan G | Norton Forums Administrator | Symantec Corporation GRPCPA Visitor2 Reg: 30-Jun-2016 Posts: 5 Solutions: 0 Kudos: 1 Kudos0 Re: Norton causing BSOD Posted: 30-Jun-2016 | 12:52PM • Permalink In
I have one Win10 and one Win7 machine affected so far. Symantec) device drivers or critical system files that come as part of the Windows operating system. These could be related to either Symantec Endpoint Protection 11.0 software or Symantec hardware, but it is not necessarily the case. Instructions for Windows XP: Open Programs and Features by clicking the Start button.
The Problem: Recently, we got a BSOD on one of our Windows 7 64-bit OS.