Discussion Locked

Kixtart 3.62

0 helpful
2 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I have one and only one workstation generating this error during Login. Any ideas what this could be?

KIX32 caused a general protection fault
in module at 0000:000016cf.

2 replies

by mckaytech

Gee, that's a useful error message. If your Kixstart script is pretty simple, probably the easiest approach to troubleshooting would be to copy your script to a different filename, point this workstation to the new filename for it's logon script and then just remove one line at a time until the problem goes away.

Then just look very closely at the problem line and try to understand what it's doing and what drivers or programs it might be calling and update those drivers or programs.

In our operation, we're fortunate enough to have a standard image and standard hardware so when we see this sort of thing, we just re-image the machine. Kind of a blunt approach but it saves a lot of time.

Hope this provides some useful ideas....

paul

by mark.tassin

Actually it was a holdover from our Novell Days. Although we had uninstalled the Novell Clients, we hadn't removed the software from the HD and it had left a trailer in the Registry that ran some thingy or other. Removing that fixed it all.

This discussion is closed to new replies.