Erratic [Non Fatal] Crash

I am occasionally getting an error message which says something about a memory address that could not be read. I am sure that there is another thread somewhere covering something like this but I can't find it. Also I could not capture a screenshot of the error message todayt, but it says something like:

Application Error : The instruction at "0x7c911f52" referenced memory at "Some Hex Memory Address Here". The memory could not be "read".

The two values quoted are not always the same. It happens on all my stations: Viglen, RM, Dell and unbadged AND desktopas and laptops. Clicking the 'OK' button usually allows the user to proceed to logon or logoff [These are the times this error most often happens, but it can happen at other times too: Starting a program can do it too] Anyone out there cured this because it is annoying the hell out of me!

Server OS: Windows 2003: SP1
Workstation OS: XP SP2: All the latest patches applied.

when the blue screen pops up with the error, it usually includes the effected driver; something.sys

if you can find out this it should point you in the right direction.

If the message pops up to fast, if you can get access into windows, get the System menu up from the control panel, select the advanced tab - start up and recovery - then un tick the box that says 'Automatically Restart"

The blue screen with remain on until you physically reboot the machine giving you loads of time to get the driver information down.

when the blue screen pops up with the error, it usually includes the effected driver; something.sys

if you can find out this it should point you in the right direction.

If the message pops up to fast, if you can get access into windows, get the System menu up from the control panel, select the advanced tab - start up and recovery - then un tick the box that says 'Automatically Restart"

The blue screen with remain on until you physically reboot the machine giving you loads of time to get the driver information down.

Have you tried repairing your windows install or rebuilding the station.

We get that occasionally, is usually something to with windows virtual machine.

Chris

Here is another station (newly imaged and updated Dell laptop) producing the error with another 'instruction number" included. See the attached picture.

how are you imaging them? rm station rebuild, ghost etc?

Chris

It sounds like the image is corrupted to me.

We had this issue before and we decided to recreate the image for the set of computers we were having the error on. Needless to say it sorted the problem.