CONTRIBUTE TO OUR LEGAL DEFENSE

If you accept cookies from this site, you will only be shown this dialog once!You can press escape or click on the X to close this box.

Register a free account to unlock additional features at BleepingComputer.com

Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.

While AustrAlien checks your dump files,please uninstall Norton antivirus.If there are still crashes upload the new dump file

Spot on! Thank you narenxp.

It is quite possible that ultimate responsibility for the current problem lies with the Windows XP system being outdated, running Service Pack 2 only. However, the chief cause of the BSODs is that memory is being corrupted by one or more drivers. Examination of the WinDbg output reveals that drivers belonging to the Norton/Symantec security software are directly implicated as likely causes in 5 of the 13 crashes. If you can remove Norton/Symantec from the system, that is likely to stop the current BSOD problem.

Please confirm what I think we already know, whether or not you are able to load Windows normally and then proceed to uninstall the Norton/Symantec software. Meantime, I will consult with colleagues as to the best way to disable Norton/Symantec on startup and thereby allow you to start Windows normally. If we can do that successfully, then we can work out the best way to go about removing Norton/Symantec from the system and then deal with any other matters necessary.

I did wonder about the memory and considered the value of testing after reading a post that I found during my research (the following taken from my notes):

Glen BodieIn my case, I had this error on a Windows XP Pro SP3 system, new load, crash/blue screen several times a day, no pattern in terms of which application. Error codes included 00000019, 000000FC, 1000000A, 10000050, 1000007E, 1000007F, 1000008E, 100000BE, 100000D1 ... total of 40 codes all within 3 days! System was scanned for virus and trojans. All Windows patches applied. All drivers were updated. Unnecessary hardware removed. All boards / pins / cables were carefully reseated to make good contact. No improvement. Ran the Windows Memory Diagnostic (see EV100088) and found that one of the 2 DIMMs was marginal. Replaced the DIMM and no more crashes. Source: http://www.eventid.net/display-eventid-1003-source-System-eventno-1274-phase-1.htm>>>>> CHECK MEMORY <<<< ****

You would be well advised to run the Norton removal tool if applicable to your Norton version: