[BUG] Scheduled scan hangs PC

  • Thread starter Thread starter Jorabi
  • Start date Start date
J

Jorabi

The PC hangs hard when MSAS tries to do a scheduled scan. Cold
reboot required.

I shut off the scheduled scan and the crash went away. A manual
scan does not crash, so it is not a particular file being scanned
that is causing it.

After the reboot MS Crash Analysis tells me that the Intel Storage
Driver caused the crash. I have installed the latest Intel Storage
Driver a month ago and and was not having any other problems with
it until this.

Microsoft AntiSpyware version 1.0.501
Windows OS: XP
Windows OS Version Info: 148
Windows OS Major Version: 5
Windows OS Minor Version: 1
Windows OS Build: 2600
Current Path: C:\Program Files\Microsoft AntiSpyware
Install Path: C:\Program Files\Microsoft AntiSpyware\
Session.RunMode: 5
Session.TimeBombDaysRemaining: 181
Session.TimeBombExpirationDate: 7/31/2005
Real-time protection running: True
Real-time protection enabled: True
Security Agents Application Enabled: True
Security Agents Internet Enabled: True
Security Agents System Enabled: True
Security Agents Checkpoints: 59
Definitions Update Date: 1/29/2005 11:34:29 AM
AutoUpdater Enabled: 1
AutoUpdater AutoApply Enabled:
Definitions Increment Version: 38/38
Definitions ThreatAuditThreatData: 1215017
Definitions ThreatAuditScanData: 2103732
Definitions DeterminationData: 113316
Software Update Check Date: 1/26/2005 11:00:25 PM
AutoUpdater Software Enabled:
TotalThreatsDetected: 8
TotalScansRun: 3
LastScanDate: 1/29/2005 11:36:16 AM
Is US Locale: True
Locale Language: English (United States):English (0409)
Locale Country: United States:United States (1)
Processor Identifier: x86 Family 15 Model 0 Stepping 10
Processor Name: Intel(R) Pentium(R) 4 CPU 1500MHz
IE Version: 6.0.2900.2180
msvbvm60.dll: 6.0.96.90
vbscript.dll: 5.6.0.8820
gcUnCompress.dll: 1.1.0.0
gcmd5query.dll: 1.0.0.1
openports.dll:
SDelete.dll:
gcASSoapLib.dll: 1.0.0.501
gcPorttoProcess.dll:
gcTCPObjLib.dll: 1.0.0.501
gcasDtServ.exe: 1.0.0.501
gcAntiSpywareLibrary.dll: 1.0.0.501
gcIPtoHostQueue.exe: 1.0.0.501
gcasServ.exe: 1.0.0.501
gcasServAlert.exe: 1.0.0.501
gcasServHook.dll:
gcASHashLibrary.dll:
gcASThreatAudit.dll: 1.0.0.501
gcASCleaner.exe: 1.0.0.501
GIANTAntiSpywareUpdater.exe: 1.0.0.501
gcASPrivacyLib.dll: 1.0.0.501
gcASShredCtxShell.dll:
gcasSWUpdater.exe: 1.0.0.501
gcSoftwareUpdateLib.dll: 1.0.0.501
GIANTSpywareScan.exe:
gcasDtServ Status: Loaded
gcasDtServ IsAuthorized: True
gcAntiSpywareLibrary Status: Loaded
gcAntiSpywareLibrary IsAuthorized: True
gcASThreatAudit Status: Loaded
gcASThreatAudit IsAuthorized: True
Now: 1/31/2005 1:26:09 PM
 
Thanks Jorabi. I think you've posted this before? I don't have any
suggestions as workarounds except disabling scheduled scans, or removing the
Intel storage driver.

It'd be interesting to know whether removing the Intel storage driver in
facts alleviates the problem, but I know that you would 1) rather not run
that way forever, and 2) probably don't want to try the experiment of
removing the driver, testing, replacing it, and testing again to see if you
get the same crash.

Can you post the version information for the Intel Storage driver?
 
Back
Top