Memory could not be read

[Tony]

I look after several XP Prof PCs in the office and
generally the PC crashes when a user logs onto a PC for
the first time or after several months of not being
logged into the PC. It will boot up fine to ctrl alt
delete. The user then logs in and the PC will try an
load that persons profile. 5 times out of 10 an error
message will come up
"instructions @ 0x75a7b3lf referenced memory @
0x00760061. The memory could not be read" or "written to"
It will then restart the PC and the user needs to logon
again.
People here can log into any PC on the network but they
don't download a roaming profile. A local profile is
created on each PC they use.

 

[Malke]

I look after several XP Prof PCs in the office and
generally the PC crashes when a user logs onto a PC for
the first time or after several months of not being
logged into the PC. It will boot up fine to ctrl alt
delete. The user then logs in and the PC will try an
load that persons profile. 5 times out of 10 an error
message will come up
"instructions @ 0x75a7b3lf referenced memory @
0x00760061. The memory could not be read" or "written to"
It will then restart the PC and the user needs to logon
again.
People here can log into any PC on the network but they
don't download a roaming profile. A local profile is
created on each PC they use.

These computers are infected by the Swen or Gibe virus. Go to
www.sarc.com and read all about it. Get those boxen off the network and
the Internet. You will need to completely disinfect all computers on
the network. If you are looking after these pc's, then you need to put
proper antivirus software in place.

Malke