BSOD on start up, locale 2057, after virus removal.

Symantec Endpoint Driver itself is your problem, as it is seen very often.

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {fffff80003421080, 0, fffff880098cfd83, 2}

*** WARNING: Unable to verify timestamp for SRTSPL64.SYS
*** ERROR: Module load completed but symbols could not be loaded for SRTSPL64.SYS

Could not read faulting driver name
Probably caused by : SRTSPL64.SYS ( SRTSPL64+27d83 )

Followup: MachineOwner
---------

Description here: Driver Reference Table - SRTSPL64.SYS

And, all the three crash dumps show the same result here.

Uninstall Norton and all Symentec products using Norton Removal tool. Use Microsoft Security Essentials as your antivirus with windows inbuilt firewall, and free MBAM as the on demand scanner.
Download, install and update those, and then run full system scans with both of them, one by one.

Let us know the results.

You are welcome mate :)
For any further issues, let us know.

Hi,

Replacing Antivirus can not be a solution.

There is a fix note related to SRTSPL64.SYS in SEP 11.x platform

SRTSPL64.SYS crashes on Windows 2008 Server
Fix ID: 1949035
Symptom: BugCheck 50, PAGE_FAULT_IN_NONPAGED_AREA, in SRTSPL64.SYS
Solution: Fixed resource cleanup issues

Reference: http://www.symantec.com/docs/TECH103087

SEP latest version should not cause any issue. Latest version details can be found here: https://www-secure.symantec.com/connect/articles/what-are-symantec-endpoint-protection-sep-versions-released-officially

To handle virus related issue always follow the best practice:
Best Practices for Troubleshooting Viruses on a Network
http://www.symantec.com/docs/TECH122466

You can always involve Symantec support team if threat could not detect. Be aware that third-party antivirus products are often designed with a different purpose in mind, and therefore employ a different scope of detection. Symantec security products such as SAV and Symantec Endpoint Protection (SEP) are intended to balance detection of legitimate threats with a level of false positive detection acceptable to enterprise-class computing environments with thousands or even hundreds of thousands of seats.

However to get it assured submit the suspicious files to Symantec security response team for further analysis.
Using Symantec Help (SymHelp) Tool, how do we Collect the Suspicious Files in SEP 12.1 and Submit the same to Symantec Security Response Team.
https://www-secure.symantec.com/connect/articles/u...
Symantec Help (SymHelp)
http://www.symantec.com/docs/TECH170752
You can scan the machine using Symantec power eraser tool also.
Use Power Eraser to detect threat and remove them
http://www.symantec.com/theme.jsp?themeid=spe-user...

Regards,
Chetan Savade

Chetan, here we are independent debuggers. Our responsibility is to the issue only, not to anything else. If anybody comes to us seeking help, and we know that his problem is caused by the antivirus that is a wide problem, we definitely will suggest to remove that costly but crash prone antivirus and to install the free but more efficient one.

And, replacing the antivirus is the solution, that is already proved in post #3.

Well said Arc!! Excellent!!

How many hundreds of instances have we seen Symantec cause these BSOD's? Way too many!!

Golden said:

Well said Arc!!

How many hundreds of instances have we seen Symantec cause these BSOD's? Way too many!!

Hundreds is not the appropriate unit to measure the mess .... as we dont measure time in nanoseconds

Giga is better, maybe Peta?