I think it's probably one of these two things causing the problem but I have no idea what to do.
This shows no deadlocks at the times of the problems, and long running queries all coincide with our timeout errors, but look to be a side effect, and not the cause.Mc Afee's Script Scan Module has classified the Update Agent's activity as malicious and has stopped the service.Unregister the file found in C:\Program Files\Network Associates\Virus Scan.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.Manually editing the Windows registry to remove invalid APC_INDEX_MISMATCH keys is not recommended unless you are PC service professional. I'm really just looking for suggestions on what other troubleshooting I can do to try and track this down. There's a handful of different servers that connect to it, ranging from Windows server 2003 to 2008 of different varieties. For us the solution was not to fiddle with the SQL Server. The timeout period elapsed prior to completion of the operation or the server is not responding.) We have over 100 different applications on our network, both web and desktop apps. Our DBA says nothing is wrong with the SQL server, and IT says there's nothing wrong with the web servers or network, so of course I'm left in the middle trying to troubleshoot this.It looks like some queries/transaction lock your database till they are done.Every time I restart my computer I get the blue screen of death (the title of this post is the error code from the latest failed restart. The crashes started happening in February right after a Windows Update (not sure which one).Queries that are very basic that typically return instantly end up taking 30, 60 or 120 seconds to run at times.This happens for a few minutes then everything picks up and works fine after that.