Jump to content

Application error at logoff - real headache


Recommended Posts

Posted

Ever since we set up two new suites of PCs in september, we've been getting random application error messages at log off. These are occuring on every PC since we ghosted an image to the lot. This is what I've pulled from the application event log:

 

Application popup: Explorer.EXE - Application Error : The instruction at "0x019d1da0" referenced memory at "0x019d1da0". The memory could not be "read".

 

Click on OK to terminate the program

Click on CANCEL to debug the program

 

I've also had this which may be related:

 

Windows saved user NCTC\user registry while an application or service was still using the registry during log off. The memory used by the user's registry has not been freed. The registry will be unloaded when it is no longer in use.

 

This is often caused by services running as a user account, try configuring the services to run in either the LocalService or NetworkService account.

 

Any ideas how to solve this?

  • 2 weeks later...
Posted

We are seeing something similar. It can happen at logon or logoff and doesn't always appear. It can occur though on any station for any user. I will try to remember to capture a screenshot the next time it happens and post it to this thread.

 

Ghosting software version: 7.5.

Station OS: Windows XP Pro SP2.

Server OS: Windows 2003 SP1.

Posted

First one I would say bad memory, run memtest86 on a couple of test machines. As its every workstation it would lead me to think its a bad image. Run the same test on your image machine, scan disk etc.

 

If everything checks out look at a repair install on the image machine and reimage.

 

Thats the obvoiuse out the way, let us know what the outcome is :)

Posted

>> These are occuring on every PC since we ghosted an image to the lot.

 

So why not try and re install one of them using a normal xp disc or RIS'ing one and seeing if it still happens ?

 

If so then yes I agree with memtest86, just seems odd that all of them are doing it and all of them were ghosted using the same ghost image.

 

Who knows, maybe im wrong :)

  • 2 weeks later...
Posted
Did you ghost these all at the same time? If so I suspect there was a minor network error that corrupted the image in transit. If not, recreate your ghost image. It's broken.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...