all those having troubles with Faulting Application Explorer.exe, version 6.0.2800.1106, faulting module ntdll.dll [fault addresses WILL VARY]--after much trouble and examination, we offer the following fix which Microsoft should provide--and have not.
The trouble lies within -->> ntdll.dll 6.0.2800.1106 <<--which is an absolute Turkey. Previous versions of this Mod worked fine, it is changed and advanced during the routine MS Critical Update Process, in my case installing the Update Rollup 1 for XP [K826939]. Other updates change this dll as well, forming the above [.1106] which locks and crashes.
If you remove the offending Update--the previous version will then be restored.
Then all will be fine, you think. Sounds simple. The problem is that Microsoft also created an incredible design fault--producing several Updates that MAY or MAY NOT be seen in the Add/Remove Programs. Swell. This is a problem for many of their Updates, feel free to complain. For this particular case you are getting rid of -->> ntdll.dll 6.0.2800.1106 <<--, so first MAKE A SYSTEM RESTORE POINT, and then try this:
1. Begin with a Registry Search [Regedit] for the OFFENDING UPDATE. You will find it. Expand until you have located the STRING [window on right] that holds the DELETE instruction. Mousey Highlight and copy this string. Close your Regedit;
2. Go to RUN--paste/insert your STRING--and hit OKAY [go]. This will bring up the UNINSTALL FUNCTION that you could not find in your Add/Remove Programs;
3. During UNINSTALL, you will need two items, (A) your XP Disc, and (B) the location of the ntdll.dll installation mod to instruct the process toward completion. Ntdll is located in your Sys32, and is not that difficult to find, simply browse, tap, continue. [If you are a newbie remember, you can always find the Ntdll by using the General Search function. Make a note of what file that is located in, then go back to BROWSE.] Follow the UNINSTALL INSTRUCTIONS, and you are nearly home free;
4. During the UNINSTALL, you might get warning messages like "...WINDOWS May Not Work Properly If Removal..." Etc. I did NOT get this, but an IT Professional buddy of mine did. Ignore these. Keep moving forward...
5. When the process completes, REBOOT. For extra measure, we shutdown completely, and then bring the system back.
Now test your OS. Smile. This has worked. Again, the problem is -->> ntdll.dll 6.0.2800.1106 <<--, which is some serious damn GiGo [Garbage In, Garbage Out.] If you use previous versions of the above dll, you shouldn't have any troubles.
For those who had this problem created by installing Critical Update 826939, Microsoft promises that when you remove this update rollup--the previous critical updates that this replaced will suddenly be restored in the Add/Remove Programs. Not true, at least on two systems, which typically run 100 percent. We're working on that, as well as letting Microsoft know how we feel about these issues...
In case you had our trouble, it's amusing to read the uninstall portion of this hotfix.
http://support.microsoft.com/default...b;en-us;815021
Linear Mode
