Home > Blue Screen > Symantec Causing Blue Screen

Symantec Causing Blue Screen

Contents

I have been following those articles. The issue was occoured after minor upgrade from 22.7.0.75 to 22.7.0.76 version. To use System Restore (Windows XP, Vista, 7, 8, and 10): Click the Start button. close {{{ form.header }}} {{{ form.title }}} {{{error}}} {{error}} {{ option.label }} Get Free Newsletters: {{ field.label }} {{ form.postButtonLabel }} By registering you agree with our Terms And Conditions | Source

Follow the on-screen directions to complete the uninstallation of your IDSviA64.sys-associated program. In fact, one misplaced comma can prevent your PC from booting entirely! A black box will open with a blinking cursor. We have more than 200 PCs with Norton! 1 2 3 4 5 Login or register to participate. https://www.symantec.com/connect/forums/bsod-caused-symantec-endpoint-protection-1215

Symefasi.sys Bsod

This is wonderful. Please see "Causes of IDSviA64.sys Errors" below for more information. Norton 360 - All-In-One Security) under the Name column.

IS it a case of just update to 22.7 or is it because of 22.7? Logs seems clean now. The tech worked with me in making a policy and I am going to give that a shot now. Symefasi.sys Windows 10 You can see here for some full system dumps if you need any specific info: http://www.tenforums.com/bsod-crashes-debugging/54582-frequent-bsod-whil...

Teefer2, needs a reboot after install, and then reconfiguration of the service to start 0, so install on master target before image capture: http://support.citrix.com/article/CTX137505 SEP options (regardless of version) in below Symefa.sys Blue Screen Windows 7 What Are SYS Files? I had run a live update at approximately 11 AM EST 6/28 this morning and still got a blue screen around noon. If you are able to help us with this issue.

If this action resolves your BSOD, this will be the source of your problem, and therefore your new memory is either incompatible or bad. Symantec Extended File Attributes Once I load SEP 12.1.6 (12.1 RU6 MP1) build 6318, it installs, and says it needs to reboot. System File Checker will begin scanning for IDSviA64.sys and other system file problems (be patient - the system scan may take a while). COULD YOU PLEASE REVOKE 22.7.0.76 FROM LIVE UPDATE UNTIL YOU HAVE A FIX FOR THIS ???    Maybe with 22.7.0.75 at least after a fresh install Norton won't crash any more...

Symefa.sys Blue Screen Windows 7

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 https://www.symantec.com/connect/forums/bsod-and-symefasisys DO NOT hit ENTER yet! Symefasi.sys Bsod Please reach out to us anytime on social media for more help: Recommendation: Scan your PC for IDSviA64.sys registry corruption About The Author: Jay Geater is the President and CEO of Symefa64.sys Symantec Corporation Efa This can potentially help you avoid hours of troubleshooting headaches associated with SYS errors.

If updates are available, click the Install Updates button. this contact form As a Gold Certified Independent Software Vendor (ISV), Solvusoft is able to provide the highest level of customer satisfaction through delivering top-level software and service solutions, which have been subject to Recommendation: Scan your PC for IDSviA64.sys registry corruption How To Fix IDSviA64.sys Errors Caution: We do not recommend downloading IDSviA64.sys from "SYS download" sites. enono Visitor2 Reg: 28-Jun-2016 Posts: 3 Solutions: 0 Kudos: 0 Kudos0 Re: Norton causing BSOD Posted: 28-Jun-2016 | 7:49PM • Permalink I also have the same issues. Symefa64.sys Windows 10

These malicious intruders can damage, corrupt, or even delete SYS-related files. Incorrectly editing your registry can stop your PC from functioning and create irreversible damage to your operating system. Mohanakrishnan G | Norton Forums Administrator | Symantec Corporation cccrkfg Newbie1 Reg: 29-Jun-2016 Posts: 1 Solutions: 0 Kudos: 0 Kudos0 Re: Norton causing BSOD Posted: 29-Jun-2016 | 12:18PM • Permalink Have have a peek here Restart your PC with the USB drive installed.

I'm going to disable those to see if it makes a difference. Symefa64.sys Bsod If that is the case, then it is likely you will need to replace the associated hardware causing the IDSviA64.sys error. Recommendation: Scan your PC for IDSviA64.sys registry corruption PVS 7.7.

Why Do I Have SYS Errors?

If you require a copy of IDSviA64.sys, it is recommended that you obtain it directly from Symantec. Keeping track of when and where your STOP error occurs is a critical piece of information in troubleshooting the problem. To check for Windows Updates (Windows XP, Vista, 7, 8, and 10): Click the Start button. Srtsp Type "command" in the search box...

The benefit is that it allows you to test ALL of your memory for IDSviA64.sys errors, while other programs cannot test the section of memory occupied by the software itself, the Uhlenbrock-EDV Newbie1 Reg: 30-Jun-2016 Posts: 3 Solutions: 0 Kudos: 0 Kudos0 Re: Norton causing BSOD Posted: 30-Jun-2016 | 8:00AM • Permalink I deinstalled and reinstalled Norton Security on two PCs with Tip: If you do not already have a malware protection program installed, we highly recommend using Emsisoft Anti-Malware (download here). http://digitalsurgeon.net/blue-screen/symantec-endpoint-protection-causing-blue-screen-windows-7.html Thanks.

I might have to reach out to Symantec and see if they are any help. I've stopped Norton Security on 5 computers to avoid the crashes and keep on working. your Desktop). 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

Customers are getting corrupt data from the shutdowns. These troubleshooting steps get progressively more difficult and time consuming, so we strongly recommend attempting them in ascending order to avoid unnecessary time and effort.