You have a permissions issue, the Workgroup isn't set up correctly and the SQL Server has conflicts! Some of the Errors overlap in that fixing one SQL error may also fix another. This is not my forte but I did a lot of searching:
If I understand correctly, QUEST2 is an add-on module for the SQL Server and interestingly enough, the searches has to be for MSSQUL or SQL, not for MSSQL$QUEST2. If this id correct, I would first suggest disabling the QUEST2 add-on. Check the system. See if it makes any difference. If not:
Resolve these:
17204:
SQL Server was unable to open the specified file due to the specified error.
This problem occurs because the user account that you use to log on to Microsoft Dynamics CRM 3.0 does not have the Microsoft Dynamics CRM System Administrator role.
See FIX here:
http://support.microsoft.com/default.aspx?scid=kb;en-us;946542
User Action
Diagnose and correct the operating system, then retry the operation.
17049:
A process outside of SQL Server may be preventing SQL Server from reading the files. As a result, errorlog entries may be lost and it may not be possible to view some SQL Server errorlogs. Make sure no other processes have locked the file with write-only access."
NOTE: possible print server conflict
7024.
The SQL error log may contain additional information about this problem
The 3417 message is an error recovering the master database so the instance can not start.
3409:
TO FIX: (should also handle Error 8313.)
1. Reinstall sqlctr.ini for this instance and ensure that the instance login account has correct registry permissions.
7034 Date: 6/11/2009 Time: 9:20:21 AM
Description: The MSSQL$QUEST service terminated unexpectedly.
FIX: A stack overflow exception may occur, and SQL Server 2000 may unexpectedly close when you submit a query that uses the UNION ALL operator more than 255 times
Hotfix download is available> http://support.microsoft.com/default.aspx?scid=kb;en-us;892141
7031
The Print Spooler service terminated unexpectedly
TO FIX:
Method 1: Remove the registry entry for the Xerox language monitor in Registry Editor
OR
Method 2: Disable the language monitor entry in the Printer.inf file of the printer
HERE: http://support.microsoft.com/default.aspx?scid=kb;en-us;888206
1003
Description:Error code 00000093
0x00000093 is "Invalid Kernel Handle" This is a relatively rare error condition. Most documentation points to a driver problem - so check all hardware drivers starting with the most obvious, the video driver.
Start> Run type "sigverif.exe" without quotes and hit OK. What
drivers are listed as unsigned? Disregard those which are not checked.
http://aumha.org/a/stop.htm
Credits to EventID.net, Microsoft, Ahuma
Get started on this. I have a bit more but need to take a break. Your problem doesn't appear to be malware related, but rather permissions and configurations. You can also view the SQL Error log itself and possibly have more information.