David_Wallis

Any ideas why we get the following message from scan32... seems to occur when the machine is locked over night... getting this from more that one pc... finally managed to get the error message..

The instruction at 0x00d5bcd2 referenced memory 0x00916000 The memory could not be "read".

I know this is a bit generic.. but people are starting to whinge...

Machines are compaq deskpro's running NT4 SP6a VirusScan 4.51 with latest sp (i believe...)

David

ChrisB

He was due to be travelling out to the Far East some time soon David, so you might need to bump a couple of times.

David_Wallis

cheers.

David

JackClark

Not flying till Sunday.

That msg usually indicates a corrupt file, try scanning smaller sections of the disk in an effort to track the culprit down.

Give that a go, let me know if you sus it.

David_Wallis

its running a scheduled scan via epo to do the whole disk..

Its happening on a fair few machines though??

David

JackClark

Best advice for now is to run scans manually on one of the troublesome machines, start with the windows directory or something to see if you can nail it down to one directory. It could be a file common to the machines that is causing the problem. We'd be interested in seeing the file if you do track it of course.