M
m
I built a new rig with an E6400/ECS P965-A/1GB RAM/SATA(3GB) WD Caviar
Drive. Dual boot with Windows 2000 and XP on it. When I installed XP I
noticed that the hard drive was continuously running, this is even before I
installed the drivers for the network card, so unless there's a virus on the
XP install(please no MS comments) I cannot believe this is virus related(I
also did a virus scan and nothing was found). Did some digging with
filemon, processmon, etc. Looks like excessive read/writes to the registry,
specifically around the applications Winlogon, lsass and crsass. I've seen
quite a few posts on the net about this type of issue, doesn't appear anyone
has found a solution so I am poking and hoping by posting here. Now note my
CPU is sitting at <1% utlilization so it's not like this is slowing down the
machine. But I am very concerned that the hard drive being accessed
continuously will degrade the life of the drive.
I logged in to XP under safe mode and the hard drive activity is still
there, so it doesn't appear to be a driver issue. Also when I login under
2000 there is no hard drive activity, once she boots up she's done hashing
away on the hard drive.
I've done some things like shutdown the indexing on the drives and also
shutting down the auto restore point in XP. No help.
I looked at my other computers here and they also show access to the hard
drive continuously from Winlogon, lsass and crsass, although I do not see
the drive light on with these machines nor do I hear the hard drive hashing
away.
I also installed XP again to attempt to see if it was something I installed
post install of XP, no dice, same hard drive activity.
I hope this is not normal XP behavior otherwise this is an MS conspiracy
with the HD manufacturers to sell more drives.
Any thoughts? This newsgroup is a knowledgable group so this is why I
thought I would throw it up against the wall here and see if anyone had any
insight.
I have a thread going with MS to see if they can help solve the problem(yes
someone from MS actually responded to my question surprisingly).
Thanks! If I find the solution I'll post it here.
Drive. Dual boot with Windows 2000 and XP on it. When I installed XP I
noticed that the hard drive was continuously running, this is even before I
installed the drivers for the network card, so unless there's a virus on the
XP install(please no MS comments) I cannot believe this is virus related(I
also did a virus scan and nothing was found). Did some digging with
filemon, processmon, etc. Looks like excessive read/writes to the registry,
specifically around the applications Winlogon, lsass and crsass. I've seen
quite a few posts on the net about this type of issue, doesn't appear anyone
has found a solution so I am poking and hoping by posting here. Now note my
CPU is sitting at <1% utlilization so it's not like this is slowing down the
machine. But I am very concerned that the hard drive being accessed
continuously will degrade the life of the drive.
I logged in to XP under safe mode and the hard drive activity is still
there, so it doesn't appear to be a driver issue. Also when I login under
2000 there is no hard drive activity, once she boots up she's done hashing
away on the hard drive.
I've done some things like shutdown the indexing on the drives and also
shutting down the auto restore point in XP. No help.
I looked at my other computers here and they also show access to the hard
drive continuously from Winlogon, lsass and crsass, although I do not see
the drive light on with these machines nor do I hear the hard drive hashing
away.
I also installed XP again to attempt to see if it was something I installed
post install of XP, no dice, same hard drive activity.
I hope this is not normal XP behavior otherwise this is an MS conspiracy
with the HD manufacturers to sell more drives.
Any thoughts? This newsgroup is a knowledgable group so this is why I
thought I would throw it up against the wall here and see if anyone had any
insight.
I have a thread going with MS to see if they can help solve the problem(yes
someone from MS actually responded to my question surprisingly).
Thanks! If I find the solution I'll post it here.