New virus? Uncommon effect of old virus?

  • Thread starter Thread starter Annetten7
  • Start date Start date
A

Annetten7

On 3 of my Win2K prof machines I have had the following errors. They all
started, on all the machines, on 8/14. Perhaps 1 harddrive going bad
inexplicably is possible... but 4 machines - all at once on the same day?

I did not appear to have the mblast. virus. I installed the updates, and
already had CA's InoculateIT 6.0 running on them. To be safe, I ran
Norton's Fixblast AND CA's blaster solution. Niether detected virus.

Does anyone have any clue as to what might be causing this? Any
suggestions? Oh.. I have them all on signal conditioning UPS.

The driver detected a controller error on \Device\Harddisk0\DR0.

The device, \Device\Ide\IdeDeviceP0T0L0, did not respond within the timeout
period.

An error was detected on device \Device\Harddisk0\DR0 during a paging
operation.

The following boot-start or system-start driver(s) failed to load:
MRxSmb
NetBIOS
NetBT
RasAcd
Rdbss
Tcpip

The Messenger service depends on the NetBIOS Interface service which failed
to start because of the following error:
A device attached to the system is not functioning.

The DNS Client service depends on the TCP/IP Protocol Driver service which
failed to start because of the following error:
A device attached to the system is not functioning.

Application popup: msimn.exe - Application Error : The instruction at
"0x7004e747" referenced memory at "0x03043ca0". The memory could not be
"read".

Then I had another popup telling me the instruction at (some location (was
too fast to write down)) could not be written.


On my Win2K server I have the errors :

The driver disabled the write cache on device \Device\Harddisk0\DR0

The device, \Device\Harddisk0\DR0, has a bad block
 
I also had the HD errors on two different machines in the same time frame.
Very rare. One machine had it when I copied a large image file and the
other on a defrag. Didn't happen before or since. I'm wondering if MS may
need to patch the patch.
 
Annetten7 said:
On 3 of my Win2K prof machines I have had the following errors. They all
started, on all the machines, on 8/14. Perhaps 1 harddrive going bad
inexplicably is possible... but 4 machines - all at once on the same day?

I did not appear to have the mblast. virus. I installed the updates, and
already had CA's InoculateIT 6.0 running on them. To be safe, I ran
Norton's Fixblast AND CA's blaster solution. Niether detected virus.

Does anyone have any clue as to what might be causing this? Any
suggestions? Oh.. I have them all on signal conditioning UPS.

The driver detected a controller error on \Device\Harddisk0\DR0.

The device, \Device\Ide\IdeDeviceP0T0L0, did not respond within the timeout
period.

An error was detected on device \Device\Harddisk0\DR0 during a paging
operation.

The following boot-start or system-start driver(s) failed to load:
MRxSmb
NetBIOS
NetBT
RasAcd
Rdbss
Tcpip

The Messenger service depends on the NetBIOS Interface service which failed
to start because of the following error:
A device attached to the system is not functioning.

The DNS Client service depends on the TCP/IP Protocol Driver service which
failed to start because of the following error:
A device attached to the system is not functioning.

Application popup: msimn.exe - Application Error : The instruction at
"0x7004e747" referenced memory at "0x03043ca0". The memory could not be
"read".

Then I had another popup telling me the instruction at (some location (was
too fast to write down)) could not be written.


On my Win2K server I have the errors :

The driver disabled the write cache on device \Device\Harddisk0\DR0

The device, \Device\Harddisk0\DR0, has a bad block


I've had the similar problems with the errors in the event log
starting in the same time frame as you mention:
The driver detected a controller error on \Device\Scsi\adpu160m1.
and
An error was detected on device \Device\Harddisk0\DR0 during a paging
operation.


I'm running W2k adv server - quantum scsii drives. For me, on
2003.08.14 (4:15PM) there was a huge power outage - I attributed the
problems to something basically getting fried when the power went out
....and the ups drained. After a HUGE headache trying to problem solve
this I was able to fix the issue yesterday by flashing (updating) the
bios on my adaptec scsi controller card. Everything works perfect now
- no event log errors (before I was getting literally hundreds a day
before the computer would just give up and crash). Before doing this
I made sure with disk utilities (quantum & windows) that the drives
were not broken.

Good luck
 
Back
Top