Unsolved
This post is more than 5 years old
3 Posts
0
12232
January 19th, 2005 14:00
services.exe crash, new unknown devices, empty device manager, ... after SP2 install
Hi,
2 day's ago Service Pack 2 for XP was released by a SUS server that we use in our intern network. However it seems that some machines have difficulties to run normally with SP2.
Symptoms:
1. At login prompt you get an error message saying "The instruction at "0x7c910f29", referenced memory at "0x00001000", the memory could not be read", process failing: services.exe
2. When logging in, after a minutes you get the error message: "The process c:\windows\system32\services.exe has terminated unexpectedly with status code
-1073741819"; you get a count down of 60 seconds and it will reboot,
3. When logging in, Windows is detecting multiple unknown devices and most of the time the device manager of Windows is empty,
4. The process services.exe is taking up to 100% CPU power in the task manager.
Affected systems:
* Dell optiplex GX240 and GX270 (for now)
Both symptoms 1 and 2 seem to be only present on DELL GX240 models and looks like they are caused by symptom 3, I assume the Plug and Play service from Windows.
These problems don't appear to be happening on my test machine, model optiplex GX260.
The GX270 models only seem to be suffering from symptom 3 and very rarely from symptom 4. After rebooting to save mode, symptom 4 seems to be disappearing.
Pictures of symptom3 in action, can be seen here:
http://www.fys.kuleuven.ac.be/vsm/helpdesk/errors.jpeg
http://www.fys.kuleuven.ac.be/vsm/helpdesk/errors2.jpeg
basically the model GX240 suffered from all symptoms and the model GX270 only from symptom 3 and 4 so far.
But since symptom 1 and 2 seemed to be related to symptom 3, I tried the following that appears to be solving my problem for now.
I deleted the key 'ENUM' in HKLM\System\CurrentControlSet and ControlSet1-3. I had to reset security permissions on all child objects before I could continue. Also a lot of keys with weird sign like '$#@' where in there. On a GX240 I booted in safe mode, got the error message but left it untouched, adjusted the registry, and then clicked OK so the machine would reboot.
After the reboot, (don't do this with a USB keyboard because it won't work anymore), all device settings are lost, and you need to enter the Device manager that is working fine again. As soon as you enter the Device Manager, windows will start to detect your hardware again and load the drivers. After a restart everything is working normal again (I assume).
Since this kind of stuff isn't happening with our non-Dell PC's, I am wondering if Dell is aware of these kind of problems?
Also wondering if other people have encountered these kind of problems?
Does anybody knows if these weird keys in ENUM are normal after installing SP2? Deleting these keys, do they have impact on services running on the system? McAfee Anti-Virus has some problems to run and also needs some registry tweaking to run again (even after re-install and weird enough you need to delete LEGACY keys in ENUM\Root again). For now it seems OK but I am not sure.
Kind regards,
g
2 day's ago Service Pack 2 for XP was released by a SUS server that we use in our intern network. However it seems that some machines have difficulties to run normally with SP2.
Symptoms:
1. At login prompt you get an error message saying "The instruction at "0x7c910f29", referenced memory at "0x00001000", the memory could not be read", process failing: services.exe
2. When logging in, after a minutes you get the error message: "The process c:\windows\system32\services.exe has terminated unexpectedly with status code
-1073741819"; you get a count down of 60 seconds and it will reboot,
3. When logging in, Windows is detecting multiple unknown devices and most of the time the device manager of Windows is empty,
4. The process services.exe is taking up to 100% CPU power in the task manager.
Affected systems:
* Dell optiplex GX240 and GX270 (for now)
Both symptoms 1 and 2 seem to be only present on DELL GX240 models and looks like they are caused by symptom 3, I assume the Plug and Play service from Windows.
These problems don't appear to be happening on my test machine, model optiplex GX260.
The GX270 models only seem to be suffering from symptom 3 and very rarely from symptom 4. After rebooting to save mode, symptom 4 seems to be disappearing.
Pictures of symptom3 in action, can be seen here:
http://www.fys.kuleuven.ac.be/vsm/helpdesk/errors.jpeg
http://www.fys.kuleuven.ac.be/vsm/helpdesk/errors2.jpeg
basically the model GX240 suffered from all symptoms and the model GX270 only from symptom 3 and 4 so far.
But since symptom 1 and 2 seemed to be related to symptom 3, I tried the following that appears to be solving my problem for now.
I deleted the key 'ENUM' in HKLM\System\CurrentControlSet and ControlSet1-3. I had to reset security permissions on all child objects before I could continue. Also a lot of keys with weird sign like '$#@' where in there. On a GX240 I booted in safe mode, got the error message but left it untouched, adjusted the registry, and then clicked OK so the machine would reboot.
After the reboot, (don't do this with a USB keyboard because it won't work anymore), all device settings are lost, and you need to enter the Device manager that is working fine again. As soon as you enter the Device Manager, windows will start to detect your hardware again and load the drivers. After a restart everything is working normal again (I assume).
Since this kind of stuff isn't happening with our non-Dell PC's, I am wondering if Dell is aware of these kind of problems?
Also wondering if other people have encountered these kind of problems?
Does anybody knows if these weird keys in ENUM are normal after installing SP2? Deleting these keys, do they have impact on services running on the system? McAfee Anti-Virus has some problems to run and also needs some registry tweaking to run again (even after re-install and weird enough you need to delete LEGACY keys in ENUM\Root again). For now it seems OK but I am not sure.
Kind regards,
g
DesignLaptops
2 Posts
0
January 19th, 2005 21:00
The C series Latitudes I have seem to be showing symptoms 2 and 3 primarily. These symptoms occur very shortly after loading SP2 from an update CD or from windows update.
10-20% - 60 second countdown on NT Authority shutdown after services.app fails.
70%+ - empty device manager, no network connections, and no way to add them.
I have been looking for a fix since mid-september, and so far haven't come up with anything of substance.
An image I built of a sucessful SP2 installation for Latitude D800s seems to hold up to replication. However, each new installation, it re-loads half of the system drivers on first run. Previous images of the same software, excepting WinXP SP1 have no such driver load problems.
BTW, These are being cloned to identically spec'd machines. Once in a while, on the D800s with SP2, I have to dump all the network drivers, (1394, Broadcom Ethernet, and Dell 1400 Wireless adapters) and reload them in order for the adapters to connect. Again, not the case with SP1.
I manange more than 200 Dell Latitude laptops, C810, C840, and 2 generations of D800s. and so far my recommendations to ALL of my clients have been to avoid the service pack 2 like a plague, unless I install it from a known good image. For the few that don't pay attention, and download it anyway, I usually end up re-imaging the partition back to my WinXP Pro SP1 image, which seems to be the only sure fix so far.
I will post if I find anything more.
gjelu
3 Posts
0
January 20th, 2005 11:00
This is what I do to solve my problems:
Step 1) If possible I delete the McAfee AV software
Step 2) Delete the ENUM registry key in HKLM\System\CurrentControlSet | ControlSet003 | ControlSet002 (if exists) | ControlSet001 (seems that ENUM key never exist in this key until I delete all ENUM keys and reboot....)
Step 3) Reboot after step 2, login and let Windows detect all 'new' hardware, the ENUM keys are regenerated and the problem with services.exe causing reboots should be solved.
Step 4) Reboot after step 3, if step 1 failed because of systematic reboots, uninstall McAfee, reboot the machine, reinstall the McAfee AV software. (This is needed because the Networks Associates McShield service won't start properly anymore). If Step 1 succeeded, I just install McAfee AV software.
Step 5) Reboot after step 4, it seems that by deleting the ENUM keys the sound is not working anymore. The soundcard is installed but in control Panel, Sound and audio devices doesn't detect Audio devices. I used the tip on this thread:
http://www.annoyances.org/exec/forum/winxp/t1066427444
to install "PnP software enumerator". Used a "swenum.inf" from W98SE cdrom and swenum.sys from the system32\Drivers folder. Installed the device with "Add hardware".
Step 6) Reboot after step 5 and everything is now working normally ( probably until I detect another glitch :p )
Services.exe doesn't crash anymore, McAfee is enabled and running fine, Device manager is populated, No new unknown devices at startup, Sound is working and systems are running stable again. Due to a number of reboots, these steps are taking me about 20 minutes per machine.
PS1: I installed always the latest flashbios.
Until now I had a DELL GX240 that were severely impacted by SP2 release, GX260 and GX270 are running stable but are detecting +10 new unknown devices at startup (btw also present on GX240 but it was _not_ running stable anymore).
Message Edited by gjelu on 01-20-2005 08:28 AM
DesignLaptops
2 Posts
0
January 26th, 2005 18:00
I am likely going to have to re-load this machine, but I will keep my eye on this thread, as I am still looking for a solution to running SP2 on these machines in the long run.
gjelu
3 Posts
0
January 27th, 2005 05:00
First I let the group Administrators take ownerschip of the ENUM key and all subcontainers and object. Once that is done, I reset all (security) permissions on all child objects to the same permissions as the ENUM key (with group Administrators full control).
In 99% of the cases this worked and I could delete the Key. Sometime not all keys could be deleted and one or two subkey's still existed. The strange part is, I could delete these when I manually deleted them, starting from the key at the bottom in the tree and working my way up to the Enum key. But this only happened twice or so.
cschiltz
5 Posts
0
June 1st, 2006 19:00
I've found it to be Security Update KB910437 - if you exclude it from the big (40+) batch of Windows Updates, reboot, wait 1 hour, install KB910437 by itself, then continue with any other updates/software, it seems to stabilize.
This, however, is using a Win XP Pro SP2 CD - I'm not upgrading to SP2 at any point, thank Cthulu.