BSOD with either Visual Studio .Net 2005 or Sql Server 2005

Yes, I have exactly:

Microsoft Visual Studio 2005
Version 8.0.50727.762  (SP.050727-7600)
Microsoft .NET Framework
Version 2.0.50727 SP1

Installed Edition: Professional

Microsoft Visual Basic 2005   77626-009-0000007-41973
Microsoft Visual Basic 2005

Microsoft Visual C# 2005   77626-009-0000007-41973
Microsoft Visual C# 2005

Microsoft Visual C++ 2005   77626-009-0000007-41973
Microsoft Visual C++ 2005

Microsoft Visual J# 2005   77626-009-0000007-41973
Microsoft Visual J# 2005

Microsoft Visual Web Developer 2005   77626-009-0000007-41973
Microsoft Visual Web Developer 2005

Core Lab MySQLDirect .NET   4.0.12.0
Core Lab MySQLDirect .NET Data Provider
Copyright  2002 - 2007 Core Lab. All rights reserved.
Web: www.crlab.com/mysqlnet
Support: mysqlnet@crlab.com

Crystal Reports    AAC60-G0CSA4B-V7000AY
Crystal Reports for Visual Studio 2005


Microsoft Visual Studio 2005 Premier Partner Edition - ENU Service Pack 1 (KB926601)  
This service pack is for Microsoft Visual Studio 2005 Premier Partner Edition - ENU.
If you later install a more recent service pack, this service pack will be uninstalled automatically.
For more information, visit http://support.microsoft.com/kb/926601

SQL Server Analysis Services  
Microsoft SQL Server Analysis Services Designer
Version 9.00.1399.00

SQL Server Integration Services  
Microsoft SQL Server Integration Services Designer
Version 9.00.1399.00

SQL Server Reporting Services  
Microsoft SQL Server Reporting Services Designers
Version 9.00.1399.00

First, make sure that SymEvent.sys has really been uninstalled, as it's been known to hang around after a Symantec product uninstall.  The following link describes how to manually remove it from your system...  Word of caution, though....  DO NOT remove it if you have any other Symantec product still installed on your PC, as most of them use this file!
http://service1.symantec.com/support/ent-security.nsf/854fa02b4f5013678825731a007d06af/cd511bce1bd0fc838825721a007c21e3?OpenDocument

Assuming the SymEvent.sys file is no longer an issue, then this KB article might help as it describes your last minidump perfectly:
http://support.microsoft.com/kb/897574/en-us

Zip 5 to 6 minidumps to a zip file and attach it to "EE Expert Area". I will study the dump and find out the culprit. If you can't provide the minidumps, run memtest to stress test the ram. Make sure that your windows is not infected with spyware, adware adn chkdsk /r.
http://www.memtest86.com/. The minidump is at the folder /windows/minidumps


Upload Minidumps to EE "Expert Area"
. Login http://www.ee-stuff.com using your Experts-Exchange username and password.
. Click on "Expert Area" tab
. Type url link of your Question
. "Browse" your pc to the location of your Minidumps click "Upload"
. Copy the resulting "url" and post it back here.

I uploaded the last five minidumps in a zip file in the Expert Area.
They are here:
http://www.ee-stuff.com/Expert/Upload/viewFilesQuestion.php?qid=23103517

BTW, I can sort of repro the problem.
When Windows XP starts, and the login screen appears, I login immediatly while windows is still loading.
Then while I still hear the HD making noises while loading and starting whatever it starts, I open Vs.Net 2003. Then I open Sql Server 2005 Mgmt Studio. Then I open my project. Then I login into my local copy of Sql Server 2005.
Well, sometimes, just during the load of either Vs.Net or Sql Server it crashes. Sometimes it crashes when I click on my first project. Sometimes it crashes when I login into Sql Server.
I've notice, that if instead of opening this applications in the very begining, I let Windows to load completely until I don't hear HD noises. Then I login, and don't open anything again until I no longer hear windows loading, then, I can open Vs.net and Sql Server and works for a couple hours without problems. Of course I could do this all the time, but sooner or later, during that working session, it will crash.

During this day, I was able to pass the test I was soing (opening everything quickly in the begining), several times.
Just for fun, I reinstalled zone alarm, and now it is causing the BSOD again at vsdatant.sys.
Somehow, I don't think the problem is specific to neither Symantec Antivirus, nor Zone Alarm. I think it just happens that these products put my system in certain point or stress the recurses in some way, that it causes the crash.

BTW, in the BSOD screens, some parts of the text are corrupt. Sometimes it is like a 4, 6 or 8 squares that are turned on red with little dots of blue or green, really weird.
I wonder if this could mean there's something wrong in the video card.

From the minidumps, Norton AV are installed and active at 5 minidumps. I don't think it is uninstalled. BTW your version of Norton AV has known software problem ,Your version of ZA is very current and it maybe unstable. 3 of the crashes are related to Norton AV. I also find footprint ot ZA at stack trace of the 4 crashes.  Uninstall Norton AV requires special procedure. Search google using "uninstall Norton AV' and it will guide you how to uninstall Norton AV.

Mini012008-01.dmp BugCheck 10000050, {e77f9000, 0, 89de03de, 1}
Owning Process            88056020       Image:         devenv.exe
Probably caused by : SYMEVENT.SYS ( SYMEVENT+12285 )

Mini012008-02.dmp BugCheck 10000050, {e64b8000, 0, 89ddf3de, 1}
Owning Process            88a97858       Image:         SqlWb.exe
Probably caused by : SYMEVENT.SYS ( SYMEVENT+12285 )

Mini012008-03.dmp BugCheck 10000050, {e6935000, 0, 89de13de, 1}
Owning Process            892336a0       Image:         devenv.exe
Probably caused by : SYMEVENT.SYS ( SYMEVENT+12285 )

Mini012108-01.dmp BugCheck 10000050, {e661e000, 0, 89de03de, 1}
Owning Process            8980bc10       Image:         devenv.exe
Probably caused by : vsdatant.sys ( vsdatant+3d409 )

Mini012208-01.dmp BugCheck 10000050, {e63e5000, 0, 89de23de, 1}
Owning Process            884ff020       Image:         devenv.exe
Mini012208-01.dmp Probably caused by : ntkrpamp.exe ( nt!PsCallImageNotifyRoutines+36 )

vsdatant.sys Thu Nov 15 06:43:05 2007 (473B79F9)
SYMEVENT.SYS Tue Sep 19 08:52:19 2006 (450F3F43)

You are right about those dump files were from when Sysmantec was install installed, and ZoneAlarm was still installed.
But after completely remove the AV, and totally removing ZoneAlarm, I still getting the BSOD, but now instead of crashing with either an AV file or a ZA file, it is crashing with a windows file ntkrpamp.exe.

Here are 3 dumps file that have no trace of neither AV nor ZA in the stack (I guess)
http://www.ee-stuff.com/Expert/Upload/getFile.php?fid=6718

Please take a look at this files.

Do you have any update?

If I uninstall BOTH Zone Alarm and the Antivirus, then I get no BSODs.
That how I have my computer right now, but I feel kind of naked :(