A
abhijeet gautam
this is my system's error log
Advanced System Information - Error Log
Please wait while information is being collected...
100% (collecting Error Log information)
Refresh screen
Error Log
Date - Time Source Description
Tuesday, April 13, 2004 Service Control Manager The
Background Intelligent Transfer Service service hung on
starting.
Wednesday, April 14, 2004 Service Control Manager The
Background Intelligent Transfer Service service hung on
starting.
Wednesday, April 14, 2004 Service Control Manager The
Background Intelligent Transfer Service service hung on
starting.
Thursday, April 15, 2004 Service Control Manager The
Background Intelligent Transfer Service service hung on
starting.
Friday, April 16, 2004 Service Control Manager The
Background Intelligent Transfer Service service hung on
starting.
Friday, April 16, 2004 Service Control Manager The
Background Intelligent Transfer Service service hung on
starting.
Friday, April 16, 2004 Service Control Manager Timeout
(30000 milliseconds) waiting for a transaction response
from the BITS service.
Saturday, April 17, 2004 Service Control Manager The
Background Intelligent Transfer Service service hung on
starting.
Saturday, April 17, 2004 Service Control Manager Timeout
(30000 milliseconds) waiting for a transaction response
from the NVSvc service.
Saturday, April 17, 2004 DCOM The server {F3A614DC-ABE0-
11D2-A441-00C04 F795683} did not register with DCOM
within the required timeout.
Monday, April 19, 2004 Service Control Manager The
Background Intelligent Transfer Service service hung on
starting.
Monday, April 19, 2004 Service Control Manager Timeout
(30000 milliseconds) waiting for a transaction response
from the NVSvc service.
Monday, April 19, 2004 Service Control Manager The
Background Intelligent Transfer Service service hung on
starting.
Monday, April 19, 2004 Service Control Manager The
Background Intelligent Transfer Service service hung on
starting.
Monday, April 19, 2004 Service Control Manager The
Background Intelligent Transfer Service service hung on
starting.
Monday, April 19, 2004 Service Control Manager The
Background Intelligent Transfer Service service hung on
starting.
Monday, April 19, 2004 Service Control Manager Timeout
(30000 milliseconds) waiting for a transaction response
from the NVSvc service.
Monday, April 19, 2004 Service Control Manager The
Background Intelligent Transfer Service service hung on
starting.
Monday, April 19, 2004 Service Control Manager The
Background Intelligent Transfer Service service hung on
starting.
Tuesday, April 20, 2004 Service Control Manager The
Background Intelligent Transfer Service service hung on
starting.
Tuesday, April 20, 2004 Service Control Manager The
Background Intelligent Transfer Service service hung on
starting.
Tuesday, April 20, 2004 Service Control Manager The
Background Intelligent Transfer Service service hung on
starting.
Tuesday, April 20, 2004 Service Control Manager The
Background Intelligent Transfer Service service hung on
starting.
Tuesday, April 20, 2004 Service Control Manager The
Background Intelligent Transfer Service service hung on
starting.
Tuesday, April 20, 2004 Service Control Manager The
Background Intelligent Transfer Service service hung on
starting.
Tuesday, April 20, 2004 Service Control Manager Timeout
(30000 milliseconds) waiting for a transaction response
from the NVSvc service.
Wednesday, April 21, 2004 Service Control Manager The
Background Intelligent Transfer Service service hung on
starting.
Wednesday, April 21, 2004 Service Control Manager The
Background Intelligent Transfer Service service hung on
starting.
Thursday, April 22, 2004 Service Control Manager The
Background Intelligent Transfer Service service hung on
starting.
Thursday, April 22, 2004 Service Control Manager The
Background Intelligent Transfer Service service hung on
starting.
Thursday, April 22, 2004 Service Control Manager The
Background Intelligent Transfer Service service hung on
starting.
Friday, April 23, 2004 Service Control Manager The
Background Intelligent Transfer Service service hung on
starting.
Friday, April 23, 2004 Service Control Manager Timeout
(30000 milliseconds) waiting for a transaction response
from the NVSvc service.
Saturday, April 24, 2004 Service Control Manager The
Background Intelligent Transfer Service service hung on
starting.
Tuesday, April 27, 2004 Service Control Manager The
Background Intelligent Transfer Service service hung on
starting.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Friday, April 30, 2004 Service Control Manager The
Background Intelligent Transfer Service service hung on
starting.
Friday, April 30, 2004 Service Control Manager Timeout
(30000 milliseconds) waiting for a transaction response
from the NVSvc service.
Friday, April 30, 2004 Service Control Manager The
Background Intelligent Transfer Service service hung on
starting.
Friday, April 30, 2004 Service Control Manager The
Background Intelligent Transfer Service service hung on
starting.
Friday, April 30, 2004 Service Control Manager Timeout
(30000 milliseconds) waiting for a transaction response
from the NVSvc service.
Saturday, May 01, 2004 Service Control Manager The
Background Intelligent Transfer Service service hung on
starting.
Sunday, May 02, 2004 Service Control Manager The
Background Intelligent Transfer Service service hung on
starting.
Sunday, May 02, 2004 Service Control Manager The
Background Intelligent Transfer Service service hung on
starting.
Sunday, May 02, 2004 Service Control Manager The
Background Intelligent Transfer Service service hung on
starting.
Sunday, May 02, 2004 Service Control Manager Timeout
(30000 milliseconds) waiting for a transaction response
from the NVSvc service.
Monday, May 03, 2004 Service Control Manager The
Background Intelligent Transfer Service service hung on
starting.
Monday, May 03, 2004 Service Control Manager Timeout
(30000 milliseconds) waiting for a transaction response
from the NVSvc service.
Monday, May 03, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Monday, May 03, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Monday, May 03, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Monday, May 03, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Monday, May 03, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Monday, May 03, 2004 PlugPlayMa nager The device 'SAMSUNG
CD-ROM SC-152C' (IDE\CdRomSAMSUNG_CD-ROM_SC-15
2C__________________CS05____\5 &19766646&0&0.1.0)
disappeared from the system without first being prepared
for removal.
Monday, May 03, 2004 Service Control Manager The
Background Intelligent Transfer Service service hung on
starting.
Monday, May 03, 2004 Service Control Manager The
Background Intelligent Transfer Service service hung on
starting.
Monday, May 03, 2004 Service Control Manager Timeout
(30000 milliseconds) waiting for a transaction response
from the NVSvc service.
Friday, May 07, 2004 Service Control Manager The
Background Intelligent Transfer Service service hung on
starting.
Friday, May 07, 2004 Service Control Manager Timeout
(30000 milliseconds) waiting for a transaction response
from the NVSvc service.
Friday, May 07, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Friday, May 07, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Friday, May 07, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Friday, May 07, 2004 Service Control Manager The
Background Intelligent Transfer Service service hung on
starting.
Friday, May 07, 2004 Service Control Manager Timeout
(30000 milliseconds) waiting for a transaction response
from the NVSvc service.
Friday, May 07, 2004 Service Control Manager The
Background Intelligent Transfer Service service hung on
starting.
Saturday, May 08, 2004 Service Control Manager The
Background Intelligent Transfer Service service hung on
starting.
Saturday, May 08, 2004 Service Control Manager Timeout
(30000 milliseconds) waiting for a transaction response
from the NVSvc service.
Saturday, May 08, 2004 Service Control Manager The
Background Intelligent Transfer Service service hung on
starting.
Saturday, May 08, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Saturday, May 08, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Saturday, May 08, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Saturday, May 08, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Saturday, May 08, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Saturday, May 08, 2004 PlugPlayMa nager The
device 'SAMSUNG CD-ROM SC-152C' (IDE\CdRomSAMSUNG_CD-
ROM_SC-15 2C__________________CS05____\5
&19766646&0&0.1.0) disappeared from the system without
first being prepared for removal.
Saturday, May 08, 2004 Service Control Manager The
Background Intelligent Transfer Service service hung on
starting.
Monday, May 10, 2004 Service Control Manager The
Background Intelligent Transfer Service service hung on
starting.
Monday, May 10, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Monday, May 10, 2004 Service Control Manager The
Background Intelligent Transfer Service service hung on
starting.
Monday, May 10, 2004 Service Control Manager Timeout
(30000 milliseconds) waiting for a transaction response
from the NVSvc service.
Tuesday, May 11, 2004 Service Control Manager The
Background Intelligent Transfer Service service hung on
starting.
Wednesday, May 12, 2004 Service Control Manager The
Background Intelligent Transfer Service service hung on
starting.
Wednesday, May 12, 2004 Service Control Manager The
Background Intelligent Transfer Service service hung on
starting.
Wednesday, May 12, 2004 Service Control Manager The
Background Intelligent Transfer Service service hung on
starting.
Thursday, May 13, 2004 Service Control Manager The
Background Intelligent Transfer Service service hung on
starting.
Thursday, May 13, 2004 Service Control Manager Timeout
(30000 milliseconds) waiting for a transaction response
from the NVSvc service.
Thursday, May 13, 2004 Service Control Manager The
Background Intelligent Transfer Service service hung on
starting.
Thursday, May 13, 2004 Service Control Manager The
Background Intelligent Transfer Service service hung on
starting.
Thursday, May 13, 2004 Service Control Manager Timeout
(30000 milliseconds) waiting for a transaction response
from the NVSvc service.
Thursday, May 13, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Thursday, May 13, 2004 Service Control Manager The
Background Intelligent Transfer Service service hung on
starting.
Thursday, May 13, 2004 Service Control Manager Timeout
(30000 milliseconds) waiting for a transaction response
from the NVSvc service.
Monday, May 17, 2004 Service Control Manager The
Background Intelligent Transfer Service service hung on
starting.
Monday, May 17, 2004 Service Control Manager Timeout
(30000 milliseconds) waiting for a transaction response
from the NVSvc service.
Monday, May 17, 2004 Service Control Manager The
Background Intelligent Transfer Service service hung on
starting.
Monday, May 17, 2004 Service Control Manager Timeout
(30000 milliseconds) waiting for a transaction response
from the NVSvc service.
Monday, May 17, 2004 Service Control Manager The
Background Intelligent Transfer Service service hung on
starting.
Tuesday, May 18, 2004 Service Control Manager The
Background Intelligent Transfer Service service hung on
starting.
Wednesday, May 19, 2004 Service Control Manager The
Background Intelligent Transfer Service service hung on
starting.
Tuesday, May 25, 2004 Service Control Manager The
Background Intelligent Transfer Service service hung on
starting.
Tuesday, May 25, 2004 Service Control Manager Timeout
(30000 milliseconds) waiting for a transaction response
from the NVSvc service.
Wednesday, May 26, 2004 Service Control Manager The
Background Intelligent Transfer Service service hung on
starting.
Sunday, May 30, 2004 Service Control Manager The
Background Intelligent Transfer Service service hung on
starting.
Sunday, May 30, 2004 Service Control Manager Timeout
(30000 milliseconds) waiting for a transaction response
from the BITS service.
Sunday, June 06, 2004 Service Control Manager Timeout
(30000 milliseconds) waiting for a transaction response
from the NVSvc service.
Wednesday, June 09, 2004 DCOM The server {F3A614DC-ABE0-
11D2-A441-00C04 F795683} did not register with DCOM
within the required timeout.
Thursday, June 10, 2004 DCOM The server {F3A614DC-ABE0-
11D2-A441-00C04 F795683} did not register with DCOM
within the required timeout.
Saturday, June 12, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Monday, December 15, 2003 Applicatio n Error Faulting
application iexplore.exe, version 6.0.2600.0, faulting
module mshtml.dll, version 6.0.2800.1106, fault address
0x00091de2.
Monday, December 15, 2003 Applicatio n Error Fault bucket
22778503.
Monday, December 15, 2003 Applicatio n Hang Hanging
application IEXPLORE.EXE, version 6.0.2600.0, hang module
kernel32.dll, version 5.1.2600.0, hang address
0x000178ce.
Monday, December 15, 2003 Applicatio n Hang Hanging
application IEXPLORE.EXE, version 6.0.2600.0, hang module
kernel32.dll, version 5.1.2600.0, hang address
0x000178ce.
Monday, December 15, 2003 Applicatio n Hang Hanging
application IEXPLORE.EXE, version 6.0.2600.0, hang module
kernel32.dll, version 5.1.2600.0, hang address
0x000178ce.
Tuesday, December 16, 2003 Applicatio n Hang Hanging
application IEXPLORE.EXE, version 6.0.2600.0, hang module
hungapp, version 0.0.0.0, hang address 0x00000000.
Sunday, December 21, 2003 Applicatio n Error Faulting
application wmplayer.exe, version 9.0.0.2980, faulting
module pictureviz_ii.dll, version 1.0.0.2, fault address
0x0001c411.
Friday, December 26, 2003 Applicatio n Hang Hanging
application Skype.exe, version 0.95.0.36, hang module
hungapp, version 0.0.0.0, hang address 0x00000000.
Tuesday, December 30, 2003 Applicatio n Hang Hanging
application iexplore.exe, version 6.0.2600.0, hang module
hungapp, version 0.0.0.0, hang address 0x00000000.
Sunday, January 04, 2004 Applicatio n Error Faulting
application iexplore.exe, version 6.0.2600.0, faulting
module flash.ocx, version 7.0.14.0, fault address
0x00023664.
Thursday, January 08, 2004 Applicatio n Error Faulting
application wmplayer.exe, version 9.0.0.2980, faulting
module pictureviz_ii.dll, version 1.0.0.2, fault address
0x0001c411.
Monday, January 12, 2004 EventSyste m The COM+ Event
System detected a bad return code during its internal
processing. HRESULT was 8007043C from line 44 of
d:\nt\com\com1x\src\events\tie r1\eventsystemobj.cpp.
Please contact Microsoft Product Support Services to
report this error.
Monday, January 12, 2004 VSS Volume Shadow Copy Service
error: Unexpected error calling routine CoCreateInstance.
hr = 0x80040206.
Tuesday, January 13, 2004 Applicatio n Error Faulting
application wmplayer.exe, version 9.0.0.2980, faulting
module pictureviz_ii.dll, version 1.0.0.2, fault address
0x0001c411.
Saturday, January 17, 2004 crypt32 Failed auto update
retrieval of third-party root list sequence number from:
with error: 0x5b4
Saturday, January 17, 2004 crypt32 Failed auto update
retrieval of third-party root list sequence number from:
with error: 0x8ca
Saturday, January 17, 2004 crypt32 Failed auto update
retrieval of third-party root list sequence number from:
with error: 0x8ca
Saturday, January 17, 2004 crypt32 Failed auto update
retrieval of third-party root list sequence number from:
with error: 0x8ca
Saturday, January 17, 2004 crypt32 Failed auto update
retrieval of third-party root list sequence number from:
with error: 0x8ca
Saturday, January 17, 2004 crypt32 Failed auto update
retrieval of third-party root list sequence number from:
with error: 0x8ca
Saturday, January 17, 2004 crypt32 Failed auto update
retrieval of third-party root list sequence number from:
with error: 0x8ca
Saturday, January 17, 2004 crypt32 Failed auto update
retrieval of third-party root list sequence number from:
with error: 0x8ca
Saturday, January 17, 2004 crypt32 Failed auto update
retrieval of third-party root list sequence number from:
with error: 0x8ca
Saturday, January 17, 2004 crypt32 Failed auto update
retrieval of third-party root list sequence number from:
with error: 0x8ca
Saturday, January 17, 2004 crypt32 Failed auto update
retrieval of third-party root list sequence number from:
with error: 0x8ca
Saturday, January 17, 2004 crypt32 Failed auto update
retrieval of third-party root list sequence number from:
with error: 0x8ca
Saturday, January 17, 2004 crypt32 Failed auto update
retrieval of third-party root list sequence number from:
with error: 0x8ca
Saturday, January 17, 2004 crypt32 Failed auto update
retrieval of third-party root list sequence number from:
with error: 0x5b4
Saturday, January 17, 2004 crypt32 Failed auto update
retrieval of third-party root list sequence number from:
with error: 0x3a
Saturday, January 17, 2004 crypt32 Failed auto update
retrieval of third-party root list sequence number from:
with error: 0x3a
Saturday, January 17, 2004 crypt32 Failed auto update
retrieval of third-party root list sequence number from:
with error: 0x3a
Saturday, January 17, 2004 crypt32 Failed auto update
retrieval of third-party root list sequence number from:
with error: 0x3a
Saturday, January 17, 2004 Applicatio n Error Faulting
application p2p networking.exe, version 1.24.0.70,
faulting module p2p networking.exe, version 1.24.0.70,
fault address 0x00064043.
Saturday, January 17, 2004 Applicatio n Error Fault
bucket 70254781.
Sunday, January 18, 2004 Applicatio n Error Faulting
application wmplayer.exe, version 9.0.0.2980, faulting
module pictureviz_ii.dll, version 1.0.0.2, fault address
0x0001c411.
Monday, January 19, 2004 Applicatio n Error Faulting
application wmplayer.exe, version 9.0.0.2980, faulting
module pictureviz_ii.dll, version 1.0.0.2, fault address
0x0001c411.
Monday, January 19, 2004 Applicatio n Error Faulting
application wmplayer.exe, version 9.0.0.2980, faulting
module pictureviz_ii.dll, version 1.0.0.2, fault address
0x0001c411.
Monday, January 19, 2004 Applicatio n Error Faulting
application wmplayer.exe, version 9.0.0.2980, faulting
module pictureviz_ii.dll, version 1.0.0.2, fault address
0x0001c411.
Saturday, January 31, 2004 Microsoft Fax The Fax service
failed to receive a fax. From: . CallerId: . To: 91-612-
2284502. Pages: 0. Device Name: Motorola SM56 Voice
Modem.
Wednesday, February 04, 2004 Applicatio n Error Faulting
application wmplayer.exe, version 9.0.0.2980, faulting
module pictureviz_ii.dll, version 1.0.0.2, fault address
0x0001c411.
Wednesday, February 04, 2004 Applicatio n Error Faulting
application wmplayer.exe, version 9.0.0.2980, faulting
module pictureviz_ii.dll, version 1.0.0.2, fault address
0x0001c411.
Wednesday, February 04, 2004 Applicatio n Error Faulting
application wmplayer.exe, version 9.0.0.2980, faulting
module pictureviz_ii.dll, version 1.0.0.2, fault address
0x0001c411.
Wednesday, February 04, 2004 Applicatio n Error Faulting
application wmplayer.exe, version 9.0.0.2980, faulting
module pictureviz_ii.dll, version 1.0.0.2, fault address
0x0001c411.
Wednesday, February 04, 2004 Applicatio n Error Faulting
application wmplayer.exe, version 9.0.0.2980, faulting
module pictureviz_ii.dll, version 1.0.0.2, fault address
0x0001c411.
Wednesday, February 04, 2004 Applicatio n Error Fault
bucket 35302591.
Wednesday, February 04, 2004 Applicatio n Error Faulting
application wmplayer.exe, version 9.0.0.2980, faulting
module pictureviz_ii.dll, version 1.0.0.2, fault address
0x0001c411.
Wednesday, February 04, 2004 Applicatio n Error Fault
bucket 35302591.
Wednesday, February 04, 2004 Applicatio n Error Faulting
application wmplayer.exe, version 9.0.0.2980, faulting
module pictureviz_ii.dll, version 1.0.0.2, fault address
0x0001c411.
Wednesday, February 04, 2004 Applicatio n Error Fault
bucket 35302591.
Wednesday, February 04, 2004 Applicatio n Error Faulting
application wmplayer.exe, version 9.0.0.2980, faulting
module pictureviz_ii.dll, version 1.0.0.2, fault address
0x0001c411.
Wednesday, February 04, 2004 Applicatio n Error Fault
bucket 35302591.
Wednesday, February 04, 2004 Applicatio n Error Faulting
application wmplayer.exe, version 9.0.0.2980, faulting
module pictureviz_ii.dll, version 1.0.0.2, fault address
0x0001c411.
Wednesday, February 04, 2004 Applicatio n Error Faulting
application wmplayer.exe, version 9.0.0.2980, faulting
module pictureviz_ii.dll, version 1.0.0.2, fault address
0x0001c411.
Wednesday, February 04, 2004 Applicatio n Error Fault
bucket 35302591.
Wednesday, February 04, 2004 Applicatio n Error Faulting
application wmplayer.exe, version 9.0.0.2980, faulting
module pictureviz_ii.dll, version 1.0.0.2, fault address
0x0001c411.
Wednesday, February 04, 2004 Applicatio n Error Fault
bucket 35302591.
Wednesday, February 04, 2004 Applicatio n Error Faulting
application wmplayer.exe, version 9.0.0.2980, faulting
module pictureviz_ii.dll, version 1.0.0.2, fault address
0x0001c411.
Wednesday, February 04, 2004 Applicatio n Error Fault
bucket 35302591.
Wednesday, February 04, 2004 Applicatio n Error Faulting
application wmplayer.exe, version 9.0.0.2980, faulting
module pictureviz_ii.dll, version 1.0.0.2, fault address
0x0001c411.
Wednesday, February 04, 2004 Applicatio n Error Faulting
application wmplayer.exe, version 9.0.0.2980, faulting
module pictureviz_ii.dll, version 1.0.0.2, fault address
0x0001c411.
Wednesday, February 04, 2004 Applicatio n Error Fault
bucket 35302591.
Wednesday, February 04, 2004 Applicatio n Error Faulting
application wmplayer.exe, version 9.0.0.2980, faulting
module pictureviz_ii.dll, version 1.0.0.2, fault address
0x0001c411.
Wednesday, February 04, 2004 Applicatio n Error Faulting
application wmplayer.exe, version 9.0.0.2980, faulting
module pictureviz_ii.dll, version 1.0.0.2, fault address
0x0001c411.
Wednesday, February 04, 2004 Applicatio n Error Fault
bucket 35302591.
Wednesday, February 04, 2004 Applicatio n Error Faulting
application wmplayer.exe, version 9.0.0.2980, faulting
module pictureviz_ii.dll, version 1.0.0.2, fault address
0x0001c411.
Wednesday, February 04, 2004 Applicatio n Error Faulting
application wmplayer.exe, version 9.0.0.2980, faulting
module pictureviz_ii.dll, version 1.0.0.2, fault address
0x0001c411.
Wednesday, February 04, 2004 Applicatio n Error Fault
bucket 35302591.
Wednesday, February 04, 2004 Applicatio n Error Faulting
application wmplayer.exe, version 9.0.0.2980, faulting
module pictureviz_ii.dll, version 1.0.0.2, fault address
0x0001c411.
Wednesday, February 04, 2004 Applicatio n Error Fault
bucket 35302591.
Wednesday, February 04, 2004 Applicatio n Error Faulting
application wmplayer.exe, version 9.0.0.2980, faulting
module pictureviz_ii.dll, version 1.0.0.2, fault address
0x0001c411.
Wednesday, February 04, 2004 Applicatio n Error Fault
bucket 35302591.
Wednesday, February 04, 2004 Applicatio n Error Faulting
application wmplayer.exe, version 9.0.0.2980, faulting
module pictureviz_ii.dll, version 1.0.0.2, fault address
0x0001c411.
Wednesday, February 04, 2004 Applicatio n Error Fault
bucket 35302591.
Wednesday, February 04, 2004 Applicatio n Error Faulting
application wmplayer.exe, version 9.0.0.2980, faulting
module pictureviz_ii.dll, version 1.0.0.2, fault address
0x0001c411.
Wednesday, February 04, 2004 Applicatio n Error Fault
bucket 35302591.
Wednesday, February 04, 2004 Applicatio n Error Faulting
application wmplayer.exe, version 9.0.0.2980, faulting
module pictureviz_ii.dll, version 1.0.0.2, fault address
0x0001c411.
Wednesday, February 04, 2004 Applicatio n Error Fault
bucket 35302591.
Wednesday, February 04, 2004 Applicatio n Error Faulting
application wmplayer.exe, version 9.0.0.2980, faulting
module pictureviz_ii.dll, version 1.0.0.2, fault address
0x0001c411.
Wednesday, February 04, 2004 Applicatio n Error Faulting
application wmplayer.exe, version 9.0.0.2980, faulting
module pictureviz_ii.dll, version 1.0.0.2, fault address
0x0001c411.
Wednesday, February 04, 2004 Applicatio n Error Faulting
application wmplayer.exe, version 9.0.0.2980, faulting
module pictureviz_ii.dll, version 1.0.0.2, fault address
0x0001c411.
Wednesday, February 04, 2004 Applicatio n Error Faulting
application wmplayer.exe, version 9.0.0.2980, faulting
module pictureviz_ii.dll, version 1.0.0.2, fault address
0x0001c411.
Wednesday, February 04, 2004 Applicatio n Error Faulting
application wmplayer.exe, version 9.0.0.2980, faulting
module pictureviz_ii.dll, version 1.0.0.2, fault address
0x0001c411.
Wednesday, February 04, 2004 Applicatio n Error Faulting
application wmplayer.exe, version 9.0.0.2980, faulting
module pictureviz_ii.dll, version 1.0.0.2, fault address
0x0001c411.
Wednesday, February 04, 2004 Applicatio n Error Faulting
application wmplayer.exe, version 9.0.0.2980, faulting
module pictureviz_ii.dll, version 1.0.0.2, fault address
0x0001c411.
Wednesday, February 04, 2004 Applicatio n Error Faulting
application wmplayer.exe, version 9.0.0.2980, faulting
module pictureviz_ii.dll, version 1.0.0.2, fault address
0x0001c411.
Wednesday, February 04, 2004 Applicatio n Error Faulting
application wmplayer.exe, version 9.0.0.2980, faulting
module pictureviz_ii.dll, version 1.0.0.2, fault address
0x0001c411.
Wednesday, February 04, 2004 Applicatio n Error Faulting
application wmplayer.exe, version 9.0.0.2980, faulting
module pictureviz_ii.dll, version 1.0.0.2, fault address
0x0001c411.
Wednesday, February 04, 2004 Applicatio n Error Faulting
application wmplayer.exe, version 9.0.0.2980, faulting
module pictureviz_ii.dll, version 1.0.0.2, fault address
0x0001c411.
Wednesday, February 04, 2004 Applicatio n Error Faulting
application wmplayer.exe, version 9.0.0.2980, faulting
module pictureviz_ii.dll, version 1.0.0.2, fault address
0x0001c411.
Wednesday, February 04, 2004 Applicatio n Error Faulting
application wmplayer.exe, version 9.0.0.2980, faulting
module pictureviz_ii.dll, version 1.0.0.2, fault address
0x0001c411.
Wednesday, February 04, 2004 Applicatio n Error Faulting
application wmplayer.exe, version 9.0.0.2980, faulting
module pictureviz_ii.dll, version 1.0.0.2, fault address
0x0001c411.
Wednesday, February 04, 2004 Applicatio n Error Faulting
application wmplayer.exe, version 9.0.0.2980, faulting
module pictureviz_ii.dll, version 1.0.0.2, fault address
0x0001c411.
Wednesday, February 04, 2004 Applicatio n Error Faulting
application wmplayer.exe, version 9.0.0.2980, faulting
module pictureviz_ii.dll, version 1.0.0.2, fault address
0x0001c411.
Wednesday, February 04, 2004 Applicatio n Error Faulting
application wmplayer.exe, version 9.0.0.2980, faulting
module pictureviz_ii.dll, version 1.0.0.2, fault address
0x0001c411.
Wednesday, February 04, 2004 Applicatio n Error Faulting
application wmplayer.exe, version 9.0.0.2980, faulting
module pictureviz_ii.dll, version 1.0.0.2, fault address
0x0001c411.
Wednesday, February 04, 2004 Applicatio n Error Faulting
application wmplayer.exe, version 9.0.0.2980, faulting
module pictureviz_ii.dll, version 1.0.0.2, fault address
0x0001c411.
Wednesday, February 04, 2004 Applicatio n Error Faulting
application wmplayer.exe, version 9.0.0.2980, faulting
module pictureviz_ii.dll, version 1.0.0.2, fault address
0x0001c411.
Wednesday, February 04, 2004 Applicatio n Error Faulting
application wmplayer.exe, version 9.0.0.2980, faulting
module pictureviz_ii.dll, version 1.0.0.2, fault address
0x0001c411.
Wednesday, February 04, 2004 Applicatio n Error Faulting
application wmplayer.exe, version 9.0.0.2980, faulting
module pictureviz_ii.dll, version 1.0.0.2, fault address
0x0001c411.
Sunday, February 08, 2004 Applicatio n Error Faulting
application ypager.exe, version 5.6.0.1347, faulting
module ntdll.dll, version 5.1.2600.0, fault address
0x00057412.
Sunday, February 08, 2004 Applicatio n Error Faulting
application wmplayer.exe, version 9.0.0.2980, faulting
module pictureviz_ii.dll, version 1.0.0.2, fault address
0x0001c411.
Saturday, February 14, 2004 Applicatio n Hang Hanging
application IEXPLORE.EXE, version 6.0.2600.0, hang module
hungapp, version 0.0.0.0, hang address 0x00000000.
Saturday, February 14, 2004 Applicatio n Hang Hanging
application ypager.exe, version 5.6.0.1347, hang module
hungapp, version 0.0.0.0, hang address 0x00000000.
Sunday, February 15, 2004 Microsoft Office 10 Faulting
application winword.exe, version 10.0.2627.0, faulting
module mso.dll, version 10.0.2625.0, fault address
0x002a374e.
Sunday, February 15, 2004 Microsoft Office 10 Faulting
application frontpg.exe, version 10.0.2623.0, faulting
module fpeditax.dll, version 10.0.2623.0, fault address
0x00074001.
Sunday, February 15, 2004 Microsoft Office 10 Faulting
application frontpg.exe, version 10.0.2623.0, faulting
module fpeditax.dll, version 10.0.2623.0, fault address
0x00074001.
Sunday, February 15, 2004 Microsoft Office 10 Faulting
application frontpg.exe, version 10.0.2623.0, faulting
module fpeditax.dll, version 10.0.2623.0, fault address
0x00074001.
Sunday, February 15, 2004 Applicatio n Hang Hanging
application FRONTPG.EXE, version 10.0.2623.0, hang module
hungapp, version 0.0.0.0, hang address 0x00000000.
Sunday, February 15, 2004 Applicatio n Error Faulting
application wmplayer.exe, version 9.0.0.2980, faulting
module wmp.dll, version 9.0.0.2980, fault address
0x0021a8a5.
Wednesday, February 18, 2004 Applicatio n Hang Hanging
application wmplayer.exe, version 9.0.0.2980, hang module
hungapp, version 0.0.0.0, hang address 0x00000000.
Thursday, February 26, 2004 Applicatio n Hang Hanging
application Explorer.EXE, version 6.0.2600.0, hang module
hungapp, version 0.0.0.0, hang address 0x00000000.
Tuesday, March 02, 2004 Applicatio n Hang Hanging
application PINBALL.EXE, version 5.1.2600.0, hang module
ntdll.dll, version 5.1.2600.0, hang address 0x00003741.
Friday, March 19, 2004 Applicatio n Error Faulting
application demo32.exe, version 6.71.100.1130, faulting
module demo32.exe, version 6.71.100.1130, fault address
0x0004ba18.
Sunday, March 21, 2004 Applicatio n Error Faulting
application demo32.exe, version 6.71.100.1130, faulting
module demo32.exe, version 6.71.100.1130, fault address
0x0004ba18.
Monday, March 22, 2004 Applicatio n Hang Hanging
application Explorer.EXE, version 6.0.2600.0, hang module
hungapp, version 0.0.0.0, hang address 0x00000000.
Friday, March 26, 2004 Applicatio n Hang Hanging
application wmplayer.exe, version 9.0.0.2980, hang module
hungapp, version 0.0.0.0, hang address 0x00000000.
Monday, April 12, 2004 EventSyste m The COM+ Event System
detected an inconsistency in its internal state. The
assertion "GetLastError() == 122L" failed at line 201 of
d:\nt\com\com1x\src\events\sha red\sectools.cpp. Please
contact Microsoft Product Support Services to report this
error.
Tuesday, April 13, 2004 Applicatio n Hang Hanging
application wmplayer.exe, version 9.0.0.2980, hang module
hungapp, version 0.0.0.0, hang address 0x00000000.
Tuesday, April 13, 2004 Applicatio n Hang Hanging
application wmplayer.exe, version 9.0.0.2980, hang module
hungapp, version 0.0.0.0, hang address 0x00000000.
Tuesday, April 13, 2004 Applicatio n Hang Hanging
application wmplayer.exe, version 9.0.0.2980, hang module
hungapp, version 0.0.0.0, hang address 0x00000000.
Tuesday, April 13, 2004 Applicatio n Hang Hanging
application wmplayer.exe, version 9.0.0.2980, hang module
hungapp, version 0.0.0.0, hang address 0x00000000.
Tuesday, April 13, 2004 Applicatio n Hang Hanging
application wmplayer.exe, version 9.0.0.2980, hang module
hungapp, version 0.0.0.0, hang address 0x00000000.
Tuesday, April 13, 2004 Applicatio n Hang Hanging
application wmplayer.exe, version 9.0.0.2980, hang module
hungapp, version 0.0.0.0, hang address 0x00000000.
Tuesday, April 13, 2004 Applicatio n Hang Hanging
application wmplayer.exe, version 9.0.0.2980, hang module
hungapp, version 0.0.0.0, hang address 0x00000000.
Tuesday, April 13, 2004 Applicatio n Hang Hanging
application wmplayer.exe, version 9.0.0.2980, hang module
hungapp, version 0.0.0.0, hang address 0x00000000.
Tuesday, April 13, 2004 Applicatio n Hang Hanging
application wmplayer.exe, version 9.0.0.2980, hang module
hungapp, version 0.0.0.0, hang address 0x00000000.
Thursday, April 15, 2004 Applicatio n Hang Hanging
application WINWORD.EXE, version 10.0.2627.0, hang module
WINWORD.EXE, version 10.0.2627.0, hang address
0x0030bc23.
Thursday, April 15, 2004 Applicatio n Hang Hanging
application WINWORD.EXE, version 10.0.2627.0, hang module
WINWORD.EXE, version 10.0.2627.0, hang address
0x0030bc23.
Thursday, April 15, 2004 Applicatio n Hang Hanging
application WINWORD.EXE, version 10.0.2627.0, hang module
WINWORD.EXE, version 10.0.2627.0, hang address
0x0030bc23.
Thursday, April 15, 2004 Applicatio n Hang Fault bucket
21260544.
Thursday, April 15, 2004 Applicatio n Hang Fault bucket
21260544.
Friday, April 16, 2004 EventSyste m The COM+ Event System
detected an inconsistency in its internal state. The
assertion "GetLastError() == 122L" failed at line 201 of
d:\nt\com\com1x\src\events\sha red\sectools.cpp. Please
contact Microsoft Product Support Services to report this
error.
Tuesday, April 27, 2004 Applicatio n Error Faulting
application wmplayer.exe, version 9.0.0.2980, faulting
module ir50_32.dll, version 5.2562.15.55, fault address
0x000026f9.
Monday, May 03, 2004 Applicatio n Hang Hanging
application wmplayer.exe, version 9.0.0.2980, hang module
hungapp, version 0.0.0.0, hang address 0x00000000.
Saturday, May 08, 2004 Applicatio n Hang Hanging
application IEXPLORE.EXE, version 6.0.2600.0, hang module
hungapp, version 0.0.0.0, hang address 0x00000000.
Sunday, May 30, 2004 EventSyste m The COM+ Event System
detected an inconsistency in its internal state. The
assertion "GetLastError() == 122L" failed at line 201 of
d:\nt\com\com1x\src\events\sha red\sectools.cpp. Please
contact Microsoft Product Support Services to report this
error.
Friday, June 04, 2004 Applicatio n Error Faulting
application hbc.exe, version 0.0.0.0, faulting module ,
version 0.0.0.0, fault address 0x00000000.
Friday, June 04, 2004 Applicatio n Error Faulting
application satyamac.exe, version 1.0.0.1, faulting
module satyamac.exe, version 1.0.0.1, fault address
0x00021d0a.
Sunday, June 06, 2004 Applicatio n Hang Hanging
application IEXPLORE.EXE, version 6.0.2600.0, hang module
hungapp, version 0.0.0.0, hang address 0x00000000.
Sunday, June 06, 2004 Applicatio n Hang Fault bucket
02094221.
Monday, June 07, 2004 Applicatio n Hang Hanging
application HBC.exe, version 5.2.0.0, hang module
hungapp, version 0.0.0.0, hang address 0x00000000.
Wednesday, June 09, 2004 Applicatio n Error Faulting
application start.exe, version 1.0.0.1, faulting module
start.exe, version 1.0.0.1, fault address 0x00024578.
Wednesday, June 09, 2004 Applicatio n Error Faulting
application hbc.exe, version 0.0.0.0, faulting module
hbc.exe, version 5.2.0.0, fault address 0x000ba410.
Wednesday, June 09, 2004 Applicatio n Hang Hanging
application rundll32.exe, version 5.1.2600.0, hang module
hungapp, version 0.0.0.0, hang address 0x00000000.
Wednesday, June 09, 2004 Applicatio n Hang Hanging
application rundll32.exe, version 5.1.2600.0, hang module
hungapp, version 0.0.0.0, hang address 0x00000000.
Wednesday, June 09, 2004 Applicatio n Hang Hanging
application rundll32.exe, version 5.1.2600.0, hang module
hungapp, version 0.0.0.0, hang address 0x00000000.
Thursday, June 10, 2004 Applicatio n Hang Hanging
application rundll32.exe, version 5.1.2600.0, hang module
ntdll.dll, version 5.1.2600.0, hang address 0x0000aafb.
Thursday, June 10, 2004 Applicatio n Hang Hanging
application HBC.exe, version 5.2.0.0, hang module
hungapp, version 0.0.0.0, hang address 0x00000000.
Thursday, June 10, 2004 Applicatio n Error Faulting
application hbc.exe, version 0.0.0.0, faulting module ,
version 0.0.0.0, fault address 0x00000000.
Saturday, June 12, 2004 Applicatio n Error Faulting
application start.exe, version 1.0.0.1, faulting module
start.exe, version 1.0.0.1, fault address 0x00024315.
Saturday, June 12, 2004 Applicatio n Error Faulting
application start.exe, version 1.0.0.1, faulting module
start.exe, version 1.0.0.1, fault address 0x00024315.
Sunday, June 13, 2004 Applicatio n Hang Hanging
application IEXPLORE.EXE, version 6.0.2600.0, hang module
hungapp, version 0.0.0.0, hang address 0x00000000.
Sunday, June 13, 2004 Applicatio n Hang Fault bucket
02094221.
Monday, June 14, 2004 Applicatio n Hang Hanging
application IEXPLORE.EXE, version 6.0.2600.0, hang module
hungapp, version 0.0.0.0, hang address 0x00000000.
Monday, June 14, 2004 Applicatio n Hang Fault bucket
02094221.
my system is too slow,it virtually crawls ,what do i do
to get it sorted out?
Advanced System Information - Error Log
Please wait while information is being collected...
100% (collecting Error Log information)
Refresh screen
Error Log
Date - Time Source Description
Tuesday, April 13, 2004 Service Control Manager The
Background Intelligent Transfer Service service hung on
starting.
Wednesday, April 14, 2004 Service Control Manager The
Background Intelligent Transfer Service service hung on
starting.
Wednesday, April 14, 2004 Service Control Manager The
Background Intelligent Transfer Service service hung on
starting.
Thursday, April 15, 2004 Service Control Manager The
Background Intelligent Transfer Service service hung on
starting.
Friday, April 16, 2004 Service Control Manager The
Background Intelligent Transfer Service service hung on
starting.
Friday, April 16, 2004 Service Control Manager The
Background Intelligent Transfer Service service hung on
starting.
Friday, April 16, 2004 Service Control Manager Timeout
(30000 milliseconds) waiting for a transaction response
from the BITS service.
Saturday, April 17, 2004 Service Control Manager The
Background Intelligent Transfer Service service hung on
starting.
Saturday, April 17, 2004 Service Control Manager Timeout
(30000 milliseconds) waiting for a transaction response
from the NVSvc service.
Saturday, April 17, 2004 DCOM The server {F3A614DC-ABE0-
11D2-A441-00C04 F795683} did not register with DCOM
within the required timeout.
Monday, April 19, 2004 Service Control Manager The
Background Intelligent Transfer Service service hung on
starting.
Monday, April 19, 2004 Service Control Manager Timeout
(30000 milliseconds) waiting for a transaction response
from the NVSvc service.
Monday, April 19, 2004 Service Control Manager The
Background Intelligent Transfer Service service hung on
starting.
Monday, April 19, 2004 Service Control Manager The
Background Intelligent Transfer Service service hung on
starting.
Monday, April 19, 2004 Service Control Manager The
Background Intelligent Transfer Service service hung on
starting.
Monday, April 19, 2004 Service Control Manager The
Background Intelligent Transfer Service service hung on
starting.
Monday, April 19, 2004 Service Control Manager Timeout
(30000 milliseconds) waiting for a transaction response
from the NVSvc service.
Monday, April 19, 2004 Service Control Manager The
Background Intelligent Transfer Service service hung on
starting.
Monday, April 19, 2004 Service Control Manager The
Background Intelligent Transfer Service service hung on
starting.
Tuesday, April 20, 2004 Service Control Manager The
Background Intelligent Transfer Service service hung on
starting.
Tuesday, April 20, 2004 Service Control Manager The
Background Intelligent Transfer Service service hung on
starting.
Tuesday, April 20, 2004 Service Control Manager The
Background Intelligent Transfer Service service hung on
starting.
Tuesday, April 20, 2004 Service Control Manager The
Background Intelligent Transfer Service service hung on
starting.
Tuesday, April 20, 2004 Service Control Manager The
Background Intelligent Transfer Service service hung on
starting.
Tuesday, April 20, 2004 Service Control Manager The
Background Intelligent Transfer Service service hung on
starting.
Tuesday, April 20, 2004 Service Control Manager Timeout
(30000 milliseconds) waiting for a transaction response
from the NVSvc service.
Wednesday, April 21, 2004 Service Control Manager The
Background Intelligent Transfer Service service hung on
starting.
Wednesday, April 21, 2004 Service Control Manager The
Background Intelligent Transfer Service service hung on
starting.
Thursday, April 22, 2004 Service Control Manager The
Background Intelligent Transfer Service service hung on
starting.
Thursday, April 22, 2004 Service Control Manager The
Background Intelligent Transfer Service service hung on
starting.
Thursday, April 22, 2004 Service Control Manager The
Background Intelligent Transfer Service service hung on
starting.
Friday, April 23, 2004 Service Control Manager The
Background Intelligent Transfer Service service hung on
starting.
Friday, April 23, 2004 Service Control Manager Timeout
(30000 milliseconds) waiting for a transaction response
from the NVSvc service.
Saturday, April 24, 2004 Service Control Manager The
Background Intelligent Transfer Service service hung on
starting.
Tuesday, April 27, 2004 Service Control Manager The
Background Intelligent Transfer Service service hung on
starting.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Tuesday, April 27, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Friday, April 30, 2004 Service Control Manager The
Background Intelligent Transfer Service service hung on
starting.
Friday, April 30, 2004 Service Control Manager Timeout
(30000 milliseconds) waiting for a transaction response
from the NVSvc service.
Friday, April 30, 2004 Service Control Manager The
Background Intelligent Transfer Service service hung on
starting.
Friday, April 30, 2004 Service Control Manager The
Background Intelligent Transfer Service service hung on
starting.
Friday, April 30, 2004 Service Control Manager Timeout
(30000 milliseconds) waiting for a transaction response
from the NVSvc service.
Saturday, May 01, 2004 Service Control Manager The
Background Intelligent Transfer Service service hung on
starting.
Sunday, May 02, 2004 Service Control Manager The
Background Intelligent Transfer Service service hung on
starting.
Sunday, May 02, 2004 Service Control Manager The
Background Intelligent Transfer Service service hung on
starting.
Sunday, May 02, 2004 Service Control Manager The
Background Intelligent Transfer Service service hung on
starting.
Sunday, May 02, 2004 Service Control Manager Timeout
(30000 milliseconds) waiting for a transaction response
from the NVSvc service.
Monday, May 03, 2004 Service Control Manager The
Background Intelligent Transfer Service service hung on
starting.
Monday, May 03, 2004 Service Control Manager Timeout
(30000 milliseconds) waiting for a transaction response
from the NVSvc service.
Monday, May 03, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Monday, May 03, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Monday, May 03, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Monday, May 03, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Monday, May 03, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Monday, May 03, 2004 PlugPlayMa nager The device 'SAMSUNG
CD-ROM SC-152C' (IDE\CdRomSAMSUNG_CD-ROM_SC-15
2C__________________CS05____\5 &19766646&0&0.1.0)
disappeared from the system without first being prepared
for removal.
Monday, May 03, 2004 Service Control Manager The
Background Intelligent Transfer Service service hung on
starting.
Monday, May 03, 2004 Service Control Manager The
Background Intelligent Transfer Service service hung on
starting.
Monday, May 03, 2004 Service Control Manager Timeout
(30000 milliseconds) waiting for a transaction response
from the NVSvc service.
Friday, May 07, 2004 Service Control Manager The
Background Intelligent Transfer Service service hung on
starting.
Friday, May 07, 2004 Service Control Manager Timeout
(30000 milliseconds) waiting for a transaction response
from the NVSvc service.
Friday, May 07, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Friday, May 07, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Friday, May 07, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Friday, May 07, 2004 Service Control Manager The
Background Intelligent Transfer Service service hung on
starting.
Friday, May 07, 2004 Service Control Manager Timeout
(30000 milliseconds) waiting for a transaction response
from the NVSvc service.
Friday, May 07, 2004 Service Control Manager The
Background Intelligent Transfer Service service hung on
starting.
Saturday, May 08, 2004 Service Control Manager The
Background Intelligent Transfer Service service hung on
starting.
Saturday, May 08, 2004 Service Control Manager Timeout
(30000 milliseconds) waiting for a transaction response
from the NVSvc service.
Saturday, May 08, 2004 Service Control Manager The
Background Intelligent Transfer Service service hung on
starting.
Saturday, May 08, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Saturday, May 08, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Saturday, May 08, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Saturday, May 08, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Saturday, May 08, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Saturday, May 08, 2004 PlugPlayMa nager The
device 'SAMSUNG CD-ROM SC-152C' (IDE\CdRomSAMSUNG_CD-
ROM_SC-15 2C__________________CS05____\5
&19766646&0&0.1.0) disappeared from the system without
first being prepared for removal.
Saturday, May 08, 2004 Service Control Manager The
Background Intelligent Transfer Service service hung on
starting.
Monday, May 10, 2004 Service Control Manager The
Background Intelligent Transfer Service service hung on
starting.
Monday, May 10, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Monday, May 10, 2004 Service Control Manager The
Background Intelligent Transfer Service service hung on
starting.
Monday, May 10, 2004 Service Control Manager Timeout
(30000 milliseconds) waiting for a transaction response
from the NVSvc service.
Tuesday, May 11, 2004 Service Control Manager The
Background Intelligent Transfer Service service hung on
starting.
Wednesday, May 12, 2004 Service Control Manager The
Background Intelligent Transfer Service service hung on
starting.
Wednesday, May 12, 2004 Service Control Manager The
Background Intelligent Transfer Service service hung on
starting.
Wednesday, May 12, 2004 Service Control Manager The
Background Intelligent Transfer Service service hung on
starting.
Thursday, May 13, 2004 Service Control Manager The
Background Intelligent Transfer Service service hung on
starting.
Thursday, May 13, 2004 Service Control Manager Timeout
(30000 milliseconds) waiting for a transaction response
from the NVSvc service.
Thursday, May 13, 2004 Service Control Manager The
Background Intelligent Transfer Service service hung on
starting.
Thursday, May 13, 2004 Service Control Manager The
Background Intelligent Transfer Service service hung on
starting.
Thursday, May 13, 2004 Service Control Manager Timeout
(30000 milliseconds) waiting for a transaction response
from the NVSvc service.
Thursday, May 13, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Thursday, May 13, 2004 Service Control Manager The
Background Intelligent Transfer Service service hung on
starting.
Thursday, May 13, 2004 Service Control Manager Timeout
(30000 milliseconds) waiting for a transaction response
from the NVSvc service.
Monday, May 17, 2004 Service Control Manager The
Background Intelligent Transfer Service service hung on
starting.
Monday, May 17, 2004 Service Control Manager Timeout
(30000 milliseconds) waiting for a transaction response
from the NVSvc service.
Monday, May 17, 2004 Service Control Manager The
Background Intelligent Transfer Service service hung on
starting.
Monday, May 17, 2004 Service Control Manager Timeout
(30000 milliseconds) waiting for a transaction response
from the NVSvc service.
Monday, May 17, 2004 Service Control Manager The
Background Intelligent Transfer Service service hung on
starting.
Tuesday, May 18, 2004 Service Control Manager The
Background Intelligent Transfer Service service hung on
starting.
Wednesday, May 19, 2004 Service Control Manager The
Background Intelligent Transfer Service service hung on
starting.
Tuesday, May 25, 2004 Service Control Manager The
Background Intelligent Transfer Service service hung on
starting.
Tuesday, May 25, 2004 Service Control Manager Timeout
(30000 milliseconds) waiting for a transaction response
from the NVSvc service.
Wednesday, May 26, 2004 Service Control Manager The
Background Intelligent Transfer Service service hung on
starting.
Sunday, May 30, 2004 Service Control Manager The
Background Intelligent Transfer Service service hung on
starting.
Sunday, May 30, 2004 Service Control Manager Timeout
(30000 milliseconds) waiting for a transaction response
from the BITS service.
Sunday, June 06, 2004 Service Control Manager Timeout
(30000 milliseconds) waiting for a transaction response
from the NVSvc service.
Wednesday, June 09, 2004 DCOM The server {F3A614DC-ABE0-
11D2-A441-00C04 F795683} did not register with DCOM
within the required timeout.
Thursday, June 10, 2004 DCOM The server {F3A614DC-ABE0-
11D2-A441-00C04 F795683} did not register with DCOM
within the required timeout.
Saturday, June 12, 2004 atapi The device,
\Device\Ide\IdePort1, did not respond within the timeout
period.
Monday, December 15, 2003 Applicatio n Error Faulting
application iexplore.exe, version 6.0.2600.0, faulting
module mshtml.dll, version 6.0.2800.1106, fault address
0x00091de2.
Monday, December 15, 2003 Applicatio n Error Fault bucket
22778503.
Monday, December 15, 2003 Applicatio n Hang Hanging
application IEXPLORE.EXE, version 6.0.2600.0, hang module
kernel32.dll, version 5.1.2600.0, hang address
0x000178ce.
Monday, December 15, 2003 Applicatio n Hang Hanging
application IEXPLORE.EXE, version 6.0.2600.0, hang module
kernel32.dll, version 5.1.2600.0, hang address
0x000178ce.
Monday, December 15, 2003 Applicatio n Hang Hanging
application IEXPLORE.EXE, version 6.0.2600.0, hang module
kernel32.dll, version 5.1.2600.0, hang address
0x000178ce.
Tuesday, December 16, 2003 Applicatio n Hang Hanging
application IEXPLORE.EXE, version 6.0.2600.0, hang module
hungapp, version 0.0.0.0, hang address 0x00000000.
Sunday, December 21, 2003 Applicatio n Error Faulting
application wmplayer.exe, version 9.0.0.2980, faulting
module pictureviz_ii.dll, version 1.0.0.2, fault address
0x0001c411.
Friday, December 26, 2003 Applicatio n Hang Hanging
application Skype.exe, version 0.95.0.36, hang module
hungapp, version 0.0.0.0, hang address 0x00000000.
Tuesday, December 30, 2003 Applicatio n Hang Hanging
application iexplore.exe, version 6.0.2600.0, hang module
hungapp, version 0.0.0.0, hang address 0x00000000.
Sunday, January 04, 2004 Applicatio n Error Faulting
application iexplore.exe, version 6.0.2600.0, faulting
module flash.ocx, version 7.0.14.0, fault address
0x00023664.
Thursday, January 08, 2004 Applicatio n Error Faulting
application wmplayer.exe, version 9.0.0.2980, faulting
module pictureviz_ii.dll, version 1.0.0.2, fault address
0x0001c411.
Monday, January 12, 2004 EventSyste m The COM+ Event
System detected a bad return code during its internal
processing. HRESULT was 8007043C from line 44 of
d:\nt\com\com1x\src\events\tie r1\eventsystemobj.cpp.
Please contact Microsoft Product Support Services to
report this error.
Monday, January 12, 2004 VSS Volume Shadow Copy Service
error: Unexpected error calling routine CoCreateInstance.
hr = 0x80040206.
Tuesday, January 13, 2004 Applicatio n Error Faulting
application wmplayer.exe, version 9.0.0.2980, faulting
module pictureviz_ii.dll, version 1.0.0.2, fault address
0x0001c411.
Saturday, January 17, 2004 crypt32 Failed auto update
retrieval of third-party root list sequence number from:
with error: 0x5b4
Saturday, January 17, 2004 crypt32 Failed auto update
retrieval of third-party root list sequence number from:
with error: 0x8ca
Saturday, January 17, 2004 crypt32 Failed auto update
retrieval of third-party root list sequence number from:
with error: 0x8ca
Saturday, January 17, 2004 crypt32 Failed auto update
retrieval of third-party root list sequence number from:
with error: 0x8ca
Saturday, January 17, 2004 crypt32 Failed auto update
retrieval of third-party root list sequence number from:
with error: 0x8ca
Saturday, January 17, 2004 crypt32 Failed auto update
retrieval of third-party root list sequence number from:
with error: 0x8ca
Saturday, January 17, 2004 crypt32 Failed auto update
retrieval of third-party root list sequence number from:
with error: 0x8ca
Saturday, January 17, 2004 crypt32 Failed auto update
retrieval of third-party root list sequence number from:
with error: 0x8ca
Saturday, January 17, 2004 crypt32 Failed auto update
retrieval of third-party root list sequence number from:
with error: 0x8ca
Saturday, January 17, 2004 crypt32 Failed auto update
retrieval of third-party root list sequence number from:
with error: 0x8ca
Saturday, January 17, 2004 crypt32 Failed auto update
retrieval of third-party root list sequence number from:
with error: 0x8ca
Saturday, January 17, 2004 crypt32 Failed auto update
retrieval of third-party root list sequence number from:
with error: 0x8ca
Saturday, January 17, 2004 crypt32 Failed auto update
retrieval of third-party root list sequence number from:
with error: 0x8ca
Saturday, January 17, 2004 crypt32 Failed auto update
retrieval of third-party root list sequence number from:
with error: 0x5b4
Saturday, January 17, 2004 crypt32 Failed auto update
retrieval of third-party root list sequence number from:
with error: 0x3a
Saturday, January 17, 2004 crypt32 Failed auto update
retrieval of third-party root list sequence number from:
with error: 0x3a
Saturday, January 17, 2004 crypt32 Failed auto update
retrieval of third-party root list sequence number from:
with error: 0x3a
Saturday, January 17, 2004 crypt32 Failed auto update
retrieval of third-party root list sequence number from:
with error: 0x3a
Saturday, January 17, 2004 Applicatio n Error Faulting
application p2p networking.exe, version 1.24.0.70,
faulting module p2p networking.exe, version 1.24.0.70,
fault address 0x00064043.
Saturday, January 17, 2004 Applicatio n Error Fault
bucket 70254781.
Sunday, January 18, 2004 Applicatio n Error Faulting
application wmplayer.exe, version 9.0.0.2980, faulting
module pictureviz_ii.dll, version 1.0.0.2, fault address
0x0001c411.
Monday, January 19, 2004 Applicatio n Error Faulting
application wmplayer.exe, version 9.0.0.2980, faulting
module pictureviz_ii.dll, version 1.0.0.2, fault address
0x0001c411.
Monday, January 19, 2004 Applicatio n Error Faulting
application wmplayer.exe, version 9.0.0.2980, faulting
module pictureviz_ii.dll, version 1.0.0.2, fault address
0x0001c411.
Monday, January 19, 2004 Applicatio n Error Faulting
application wmplayer.exe, version 9.0.0.2980, faulting
module pictureviz_ii.dll, version 1.0.0.2, fault address
0x0001c411.
Saturday, January 31, 2004 Microsoft Fax The Fax service
failed to receive a fax. From: . CallerId: . To: 91-612-
2284502. Pages: 0. Device Name: Motorola SM56 Voice
Modem.
Wednesday, February 04, 2004 Applicatio n Error Faulting
application wmplayer.exe, version 9.0.0.2980, faulting
module pictureviz_ii.dll, version 1.0.0.2, fault address
0x0001c411.
Wednesday, February 04, 2004 Applicatio n Error Faulting
application wmplayer.exe, version 9.0.0.2980, faulting
module pictureviz_ii.dll, version 1.0.0.2, fault address
0x0001c411.
Wednesday, February 04, 2004 Applicatio n Error Faulting
application wmplayer.exe, version 9.0.0.2980, faulting
module pictureviz_ii.dll, version 1.0.0.2, fault address
0x0001c411.
Wednesday, February 04, 2004 Applicatio n Error Faulting
application wmplayer.exe, version 9.0.0.2980, faulting
module pictureviz_ii.dll, version 1.0.0.2, fault address
0x0001c411.
Wednesday, February 04, 2004 Applicatio n Error Faulting
application wmplayer.exe, version 9.0.0.2980, faulting
module pictureviz_ii.dll, version 1.0.0.2, fault address
0x0001c411.
Wednesday, February 04, 2004 Applicatio n Error Fault
bucket 35302591.
Wednesday, February 04, 2004 Applicatio n Error Faulting
application wmplayer.exe, version 9.0.0.2980, faulting
module pictureviz_ii.dll, version 1.0.0.2, fault address
0x0001c411.
Wednesday, February 04, 2004 Applicatio n Error Fault
bucket 35302591.
Wednesday, February 04, 2004 Applicatio n Error Faulting
application wmplayer.exe, version 9.0.0.2980, faulting
module pictureviz_ii.dll, version 1.0.0.2, fault address
0x0001c411.
Wednesday, February 04, 2004 Applicatio n Error Fault
bucket 35302591.
Wednesday, February 04, 2004 Applicatio n Error Faulting
application wmplayer.exe, version 9.0.0.2980, faulting
module pictureviz_ii.dll, version 1.0.0.2, fault address
0x0001c411.
Wednesday, February 04, 2004 Applicatio n Error Fault
bucket 35302591.
Wednesday, February 04, 2004 Applicatio n Error Faulting
application wmplayer.exe, version 9.0.0.2980, faulting
module pictureviz_ii.dll, version 1.0.0.2, fault address
0x0001c411.
Wednesday, February 04, 2004 Applicatio n Error Faulting
application wmplayer.exe, version 9.0.0.2980, faulting
module pictureviz_ii.dll, version 1.0.0.2, fault address
0x0001c411.
Wednesday, February 04, 2004 Applicatio n Error Fault
bucket 35302591.
Wednesday, February 04, 2004 Applicatio n Error Faulting
application wmplayer.exe, version 9.0.0.2980, faulting
module pictureviz_ii.dll, version 1.0.0.2, fault address
0x0001c411.
Wednesday, February 04, 2004 Applicatio n Error Fault
bucket 35302591.
Wednesday, February 04, 2004 Applicatio n Error Faulting
application wmplayer.exe, version 9.0.0.2980, faulting
module pictureviz_ii.dll, version 1.0.0.2, fault address
0x0001c411.
Wednesday, February 04, 2004 Applicatio n Error Fault
bucket 35302591.
Wednesday, February 04, 2004 Applicatio n Error Faulting
application wmplayer.exe, version 9.0.0.2980, faulting
module pictureviz_ii.dll, version 1.0.0.2, fault address
0x0001c411.
Wednesday, February 04, 2004 Applicatio n Error Faulting
application wmplayer.exe, version 9.0.0.2980, faulting
module pictureviz_ii.dll, version 1.0.0.2, fault address
0x0001c411.
Wednesday, February 04, 2004 Applicatio n Error Fault
bucket 35302591.
Wednesday, February 04, 2004 Applicatio n Error Faulting
application wmplayer.exe, version 9.0.0.2980, faulting
module pictureviz_ii.dll, version 1.0.0.2, fault address
0x0001c411.
Wednesday, February 04, 2004 Applicatio n Error Faulting
application wmplayer.exe, version 9.0.0.2980, faulting
module pictureviz_ii.dll, version 1.0.0.2, fault address
0x0001c411.
Wednesday, February 04, 2004 Applicatio n Error Fault
bucket 35302591.
Wednesday, February 04, 2004 Applicatio n Error Faulting
application wmplayer.exe, version 9.0.0.2980, faulting
module pictureviz_ii.dll, version 1.0.0.2, fault address
0x0001c411.
Wednesday, February 04, 2004 Applicatio n Error Faulting
application wmplayer.exe, version 9.0.0.2980, faulting
module pictureviz_ii.dll, version 1.0.0.2, fault address
0x0001c411.
Wednesday, February 04, 2004 Applicatio n Error Fault
bucket 35302591.
Wednesday, February 04, 2004 Applicatio n Error Faulting
application wmplayer.exe, version 9.0.0.2980, faulting
module pictureviz_ii.dll, version 1.0.0.2, fault address
0x0001c411.
Wednesday, February 04, 2004 Applicatio n Error Fault
bucket 35302591.
Wednesday, February 04, 2004 Applicatio n Error Faulting
application wmplayer.exe, version 9.0.0.2980, faulting
module pictureviz_ii.dll, version 1.0.0.2, fault address
0x0001c411.
Wednesday, February 04, 2004 Applicatio n Error Fault
bucket 35302591.
Wednesday, February 04, 2004 Applicatio n Error Faulting
application wmplayer.exe, version 9.0.0.2980, faulting
module pictureviz_ii.dll, version 1.0.0.2, fault address
0x0001c411.
Wednesday, February 04, 2004 Applicatio n Error Fault
bucket 35302591.
Wednesday, February 04, 2004 Applicatio n Error Faulting
application wmplayer.exe, version 9.0.0.2980, faulting
module pictureviz_ii.dll, version 1.0.0.2, fault address
0x0001c411.
Wednesday, February 04, 2004 Applicatio n Error Fault
bucket 35302591.
Wednesday, February 04, 2004 Applicatio n Error Faulting
application wmplayer.exe, version 9.0.0.2980, faulting
module pictureviz_ii.dll, version 1.0.0.2, fault address
0x0001c411.
Wednesday, February 04, 2004 Applicatio n Error Fault
bucket 35302591.
Wednesday, February 04, 2004 Applicatio n Error Faulting
application wmplayer.exe, version 9.0.0.2980, faulting
module pictureviz_ii.dll, version 1.0.0.2, fault address
0x0001c411.
Wednesday, February 04, 2004 Applicatio n Error Faulting
application wmplayer.exe, version 9.0.0.2980, faulting
module pictureviz_ii.dll, version 1.0.0.2, fault address
0x0001c411.
Wednesday, February 04, 2004 Applicatio n Error Faulting
application wmplayer.exe, version 9.0.0.2980, faulting
module pictureviz_ii.dll, version 1.0.0.2, fault address
0x0001c411.
Wednesday, February 04, 2004 Applicatio n Error Faulting
application wmplayer.exe, version 9.0.0.2980, faulting
module pictureviz_ii.dll, version 1.0.0.2, fault address
0x0001c411.
Wednesday, February 04, 2004 Applicatio n Error Faulting
application wmplayer.exe, version 9.0.0.2980, faulting
module pictureviz_ii.dll, version 1.0.0.2, fault address
0x0001c411.
Wednesday, February 04, 2004 Applicatio n Error Faulting
application wmplayer.exe, version 9.0.0.2980, faulting
module pictureviz_ii.dll, version 1.0.0.2, fault address
0x0001c411.
Wednesday, February 04, 2004 Applicatio n Error Faulting
application wmplayer.exe, version 9.0.0.2980, faulting
module pictureviz_ii.dll, version 1.0.0.2, fault address
0x0001c411.
Wednesday, February 04, 2004 Applicatio n Error Faulting
application wmplayer.exe, version 9.0.0.2980, faulting
module pictureviz_ii.dll, version 1.0.0.2, fault address
0x0001c411.
Wednesday, February 04, 2004 Applicatio n Error Faulting
application wmplayer.exe, version 9.0.0.2980, faulting
module pictureviz_ii.dll, version 1.0.0.2, fault address
0x0001c411.
Wednesday, February 04, 2004 Applicatio n Error Faulting
application wmplayer.exe, version 9.0.0.2980, faulting
module pictureviz_ii.dll, version 1.0.0.2, fault address
0x0001c411.
Wednesday, February 04, 2004 Applicatio n Error Faulting
application wmplayer.exe, version 9.0.0.2980, faulting
module pictureviz_ii.dll, version 1.0.0.2, fault address
0x0001c411.
Wednesday, February 04, 2004 Applicatio n Error Faulting
application wmplayer.exe, version 9.0.0.2980, faulting
module pictureviz_ii.dll, version 1.0.0.2, fault address
0x0001c411.
Wednesday, February 04, 2004 Applicatio n Error Faulting
application wmplayer.exe, version 9.0.0.2980, faulting
module pictureviz_ii.dll, version 1.0.0.2, fault address
0x0001c411.
Wednesday, February 04, 2004 Applicatio n Error Faulting
application wmplayer.exe, version 9.0.0.2980, faulting
module pictureviz_ii.dll, version 1.0.0.2, fault address
0x0001c411.
Wednesday, February 04, 2004 Applicatio n Error Faulting
application wmplayer.exe, version 9.0.0.2980, faulting
module pictureviz_ii.dll, version 1.0.0.2, fault address
0x0001c411.
Wednesday, February 04, 2004 Applicatio n Error Faulting
application wmplayer.exe, version 9.0.0.2980, faulting
module pictureviz_ii.dll, version 1.0.0.2, fault address
0x0001c411.
Wednesday, February 04, 2004 Applicatio n Error Faulting
application wmplayer.exe, version 9.0.0.2980, faulting
module pictureviz_ii.dll, version 1.0.0.2, fault address
0x0001c411.
Wednesday, February 04, 2004 Applicatio n Error Faulting
application wmplayer.exe, version 9.0.0.2980, faulting
module pictureviz_ii.dll, version 1.0.0.2, fault address
0x0001c411.
Wednesday, February 04, 2004 Applicatio n Error Faulting
application wmplayer.exe, version 9.0.0.2980, faulting
module pictureviz_ii.dll, version 1.0.0.2, fault address
0x0001c411.
Wednesday, February 04, 2004 Applicatio n Error Faulting
application wmplayer.exe, version 9.0.0.2980, faulting
module pictureviz_ii.dll, version 1.0.0.2, fault address
0x0001c411.
Wednesday, February 04, 2004 Applicatio n Error Faulting
application wmplayer.exe, version 9.0.0.2980, faulting
module pictureviz_ii.dll, version 1.0.0.2, fault address
0x0001c411.
Wednesday, February 04, 2004 Applicatio n Error Faulting
application wmplayer.exe, version 9.0.0.2980, faulting
module pictureviz_ii.dll, version 1.0.0.2, fault address
0x0001c411.
Sunday, February 08, 2004 Applicatio n Error Faulting
application ypager.exe, version 5.6.0.1347, faulting
module ntdll.dll, version 5.1.2600.0, fault address
0x00057412.
Sunday, February 08, 2004 Applicatio n Error Faulting
application wmplayer.exe, version 9.0.0.2980, faulting
module pictureviz_ii.dll, version 1.0.0.2, fault address
0x0001c411.
Saturday, February 14, 2004 Applicatio n Hang Hanging
application IEXPLORE.EXE, version 6.0.2600.0, hang module
hungapp, version 0.0.0.0, hang address 0x00000000.
Saturday, February 14, 2004 Applicatio n Hang Hanging
application ypager.exe, version 5.6.0.1347, hang module
hungapp, version 0.0.0.0, hang address 0x00000000.
Sunday, February 15, 2004 Microsoft Office 10 Faulting
application winword.exe, version 10.0.2627.0, faulting
module mso.dll, version 10.0.2625.0, fault address
0x002a374e.
Sunday, February 15, 2004 Microsoft Office 10 Faulting
application frontpg.exe, version 10.0.2623.0, faulting
module fpeditax.dll, version 10.0.2623.0, fault address
0x00074001.
Sunday, February 15, 2004 Microsoft Office 10 Faulting
application frontpg.exe, version 10.0.2623.0, faulting
module fpeditax.dll, version 10.0.2623.0, fault address
0x00074001.
Sunday, February 15, 2004 Microsoft Office 10 Faulting
application frontpg.exe, version 10.0.2623.0, faulting
module fpeditax.dll, version 10.0.2623.0, fault address
0x00074001.
Sunday, February 15, 2004 Applicatio n Hang Hanging
application FRONTPG.EXE, version 10.0.2623.0, hang module
hungapp, version 0.0.0.0, hang address 0x00000000.
Sunday, February 15, 2004 Applicatio n Error Faulting
application wmplayer.exe, version 9.0.0.2980, faulting
module wmp.dll, version 9.0.0.2980, fault address
0x0021a8a5.
Wednesday, February 18, 2004 Applicatio n Hang Hanging
application wmplayer.exe, version 9.0.0.2980, hang module
hungapp, version 0.0.0.0, hang address 0x00000000.
Thursday, February 26, 2004 Applicatio n Hang Hanging
application Explorer.EXE, version 6.0.2600.0, hang module
hungapp, version 0.0.0.0, hang address 0x00000000.
Tuesday, March 02, 2004 Applicatio n Hang Hanging
application PINBALL.EXE, version 5.1.2600.0, hang module
ntdll.dll, version 5.1.2600.0, hang address 0x00003741.
Friday, March 19, 2004 Applicatio n Error Faulting
application demo32.exe, version 6.71.100.1130, faulting
module demo32.exe, version 6.71.100.1130, fault address
0x0004ba18.
Sunday, March 21, 2004 Applicatio n Error Faulting
application demo32.exe, version 6.71.100.1130, faulting
module demo32.exe, version 6.71.100.1130, fault address
0x0004ba18.
Monday, March 22, 2004 Applicatio n Hang Hanging
application Explorer.EXE, version 6.0.2600.0, hang module
hungapp, version 0.0.0.0, hang address 0x00000000.
Friday, March 26, 2004 Applicatio n Hang Hanging
application wmplayer.exe, version 9.0.0.2980, hang module
hungapp, version 0.0.0.0, hang address 0x00000000.
Monday, April 12, 2004 EventSyste m The COM+ Event System
detected an inconsistency in its internal state. The
assertion "GetLastError() == 122L" failed at line 201 of
d:\nt\com\com1x\src\events\sha red\sectools.cpp. Please
contact Microsoft Product Support Services to report this
error.
Tuesday, April 13, 2004 Applicatio n Hang Hanging
application wmplayer.exe, version 9.0.0.2980, hang module
hungapp, version 0.0.0.0, hang address 0x00000000.
Tuesday, April 13, 2004 Applicatio n Hang Hanging
application wmplayer.exe, version 9.0.0.2980, hang module
hungapp, version 0.0.0.0, hang address 0x00000000.
Tuesday, April 13, 2004 Applicatio n Hang Hanging
application wmplayer.exe, version 9.0.0.2980, hang module
hungapp, version 0.0.0.0, hang address 0x00000000.
Tuesday, April 13, 2004 Applicatio n Hang Hanging
application wmplayer.exe, version 9.0.0.2980, hang module
hungapp, version 0.0.0.0, hang address 0x00000000.
Tuesday, April 13, 2004 Applicatio n Hang Hanging
application wmplayer.exe, version 9.0.0.2980, hang module
hungapp, version 0.0.0.0, hang address 0x00000000.
Tuesday, April 13, 2004 Applicatio n Hang Hanging
application wmplayer.exe, version 9.0.0.2980, hang module
hungapp, version 0.0.0.0, hang address 0x00000000.
Tuesday, April 13, 2004 Applicatio n Hang Hanging
application wmplayer.exe, version 9.0.0.2980, hang module
hungapp, version 0.0.0.0, hang address 0x00000000.
Tuesday, April 13, 2004 Applicatio n Hang Hanging
application wmplayer.exe, version 9.0.0.2980, hang module
hungapp, version 0.0.0.0, hang address 0x00000000.
Tuesday, April 13, 2004 Applicatio n Hang Hanging
application wmplayer.exe, version 9.0.0.2980, hang module
hungapp, version 0.0.0.0, hang address 0x00000000.
Thursday, April 15, 2004 Applicatio n Hang Hanging
application WINWORD.EXE, version 10.0.2627.0, hang module
WINWORD.EXE, version 10.0.2627.0, hang address
0x0030bc23.
Thursday, April 15, 2004 Applicatio n Hang Hanging
application WINWORD.EXE, version 10.0.2627.0, hang module
WINWORD.EXE, version 10.0.2627.0, hang address
0x0030bc23.
Thursday, April 15, 2004 Applicatio n Hang Hanging
application WINWORD.EXE, version 10.0.2627.0, hang module
WINWORD.EXE, version 10.0.2627.0, hang address
0x0030bc23.
Thursday, April 15, 2004 Applicatio n Hang Fault bucket
21260544.
Thursday, April 15, 2004 Applicatio n Hang Fault bucket
21260544.
Friday, April 16, 2004 EventSyste m The COM+ Event System
detected an inconsistency in its internal state. The
assertion "GetLastError() == 122L" failed at line 201 of
d:\nt\com\com1x\src\events\sha red\sectools.cpp. Please
contact Microsoft Product Support Services to report this
error.
Tuesday, April 27, 2004 Applicatio n Error Faulting
application wmplayer.exe, version 9.0.0.2980, faulting
module ir50_32.dll, version 5.2562.15.55, fault address
0x000026f9.
Monday, May 03, 2004 Applicatio n Hang Hanging
application wmplayer.exe, version 9.0.0.2980, hang module
hungapp, version 0.0.0.0, hang address 0x00000000.
Saturday, May 08, 2004 Applicatio n Hang Hanging
application IEXPLORE.EXE, version 6.0.2600.0, hang module
hungapp, version 0.0.0.0, hang address 0x00000000.
Sunday, May 30, 2004 EventSyste m The COM+ Event System
detected an inconsistency in its internal state. The
assertion "GetLastError() == 122L" failed at line 201 of
d:\nt\com\com1x\src\events\sha red\sectools.cpp. Please
contact Microsoft Product Support Services to report this
error.
Friday, June 04, 2004 Applicatio n Error Faulting
application hbc.exe, version 0.0.0.0, faulting module ,
version 0.0.0.0, fault address 0x00000000.
Friday, June 04, 2004 Applicatio n Error Faulting
application satyamac.exe, version 1.0.0.1, faulting
module satyamac.exe, version 1.0.0.1, fault address
0x00021d0a.
Sunday, June 06, 2004 Applicatio n Hang Hanging
application IEXPLORE.EXE, version 6.0.2600.0, hang module
hungapp, version 0.0.0.0, hang address 0x00000000.
Sunday, June 06, 2004 Applicatio n Hang Fault bucket
02094221.
Monday, June 07, 2004 Applicatio n Hang Hanging
application HBC.exe, version 5.2.0.0, hang module
hungapp, version 0.0.0.0, hang address 0x00000000.
Wednesday, June 09, 2004 Applicatio n Error Faulting
application start.exe, version 1.0.0.1, faulting module
start.exe, version 1.0.0.1, fault address 0x00024578.
Wednesday, June 09, 2004 Applicatio n Error Faulting
application hbc.exe, version 0.0.0.0, faulting module
hbc.exe, version 5.2.0.0, fault address 0x000ba410.
Wednesday, June 09, 2004 Applicatio n Hang Hanging
application rundll32.exe, version 5.1.2600.0, hang module
hungapp, version 0.0.0.0, hang address 0x00000000.
Wednesday, June 09, 2004 Applicatio n Hang Hanging
application rundll32.exe, version 5.1.2600.0, hang module
hungapp, version 0.0.0.0, hang address 0x00000000.
Wednesday, June 09, 2004 Applicatio n Hang Hanging
application rundll32.exe, version 5.1.2600.0, hang module
hungapp, version 0.0.0.0, hang address 0x00000000.
Thursday, June 10, 2004 Applicatio n Hang Hanging
application rundll32.exe, version 5.1.2600.0, hang module
ntdll.dll, version 5.1.2600.0, hang address 0x0000aafb.
Thursday, June 10, 2004 Applicatio n Hang Hanging
application HBC.exe, version 5.2.0.0, hang module
hungapp, version 0.0.0.0, hang address 0x00000000.
Thursday, June 10, 2004 Applicatio n Error Faulting
application hbc.exe, version 0.0.0.0, faulting module ,
version 0.0.0.0, fault address 0x00000000.
Saturday, June 12, 2004 Applicatio n Error Faulting
application start.exe, version 1.0.0.1, faulting module
start.exe, version 1.0.0.1, fault address 0x00024315.
Saturday, June 12, 2004 Applicatio n Error Faulting
application start.exe, version 1.0.0.1, faulting module
start.exe, version 1.0.0.1, fault address 0x00024315.
Sunday, June 13, 2004 Applicatio n Hang Hanging
application IEXPLORE.EXE, version 6.0.2600.0, hang module
hungapp, version 0.0.0.0, hang address 0x00000000.
Sunday, June 13, 2004 Applicatio n Hang Fault bucket
02094221.
Monday, June 14, 2004 Applicatio n Hang Hanging
application IEXPLORE.EXE, version 6.0.2600.0, hang module
hungapp, version 0.0.0.0, hang address 0x00000000.
Monday, June 14, 2004 Applicatio n Hang Fault bucket
02094221.
my system is too slow,it virtually crawls ,what do i do
to get it sorted out?