Search the Community

Hi, I have had this problem for a couple of months and its driving me mad. All of our existing machines appear to be running fine on the network but every time I build a new machine it hangs or BSOD's at "Applying your personal settings". I have had this problem on at least 2 different models of PC, possibly 4 (I can't remember now) - Optiplex 760, Optiplex 790 and also possibly on Optiplex 740 and Optiplex 780 (All of our PC's are Dell). But I have the same models working fine on the network, it's only when I try to install/re-install XP. So forgetting everything that I've done in the last couple of months to try fix it because I can't remember everything, here's what's happened in the last two days. I did the following steps on both of the Optiplex 790's at the same time. 1) Set up two Dell Optiplex 790's and installed XP Pro SP3 (using an ISO I downloaded from Microsoft Volume Licensing site). 2) Installed all of the latest drivers (from Dell's website using service tag) except for one of the chipset and the graphics drivers as they needed .NET Framework first. I also upgraded the BIOS at the same time. 3) Installed all available Windows Updates (excluding PowerShell, Windows Search, Browser Choice and Security Essentials or what ever it's called) 4) Installed last two drivers (mentioned in step 2) 6) Formatted D: drive. 5) Installed Adobe Flash Player, Reader and Shockwave from their website. 6) Installed Microsoft Office 2007 Enterprise from CD. 7) Installed Microsoft Updates and installed all of the updates available for Office along with Silverlight 8) Installed a driver from Microsoft Updates. I can't remember the exact name but it was something to do with Intel SOL. (I can probably check the update history if I need to get the name) 9) Installed Adobe CS5 Web Premium from CD. 10) Installed Adobe Acrobat 9 from CD. 11) Joined the computer to our domain and left both machines in the default "Computers" container in AD. 12) Logged in as the domain Administrator account. - At "Applying your personal settings" one machine rebooted (Probably a BSOD but they are set to reboot instead of displaying it by default) and the other just sat on that screen doing nothing for about 17 hours. 13) Logged in as the local Administrator account and enabled UserEnv logging and Winlogon logging, then rebooted. 14) Logged in as domain Administrator account and both machines logged in successfully... :@ 15) Logged out and logged in using my own account (Domain Admins & Administrators). Both machines rebooted. At this point I started using just one of the machines 16) Booted with it set to display any BSOD's instead of rebooting. 17) Logged in with my account and got a BSOD (0xC000021A) 18) Booted the same machine and used msconfig to disable all startup programs (then rebooted). 19) Logged in with my account and this time at "Applying your personal settings" I got a winlogon.exe error saying "The instruction at 0x7c911766 referenced memory at something. The memory could not be read". - When I clicked OK the PC rebooted obviously because winlogon was terminated. 20) On same machine logged in as local Administrator account again. 21) Used msconfig to disable all Non-Microsoft services and rebooted. 22) Logged on with my account and it rebooted again at the same place... As you can see these are clean installs of XP there is no imaging involved and they should only be loading our default policy which is linked to the domain and contains things like password expiry and "Always wait for the network at computer startup and logon". When I originally started having the problem I'm sure I remember that if you managed to get an account to log in by repeatedly deleting the local profile and logging back in until it worked, that account would always be able to log in to that machine in future (or so it appeared). So maybe it could be something to do with generating the user profiles. That's all I can remember right now, may think of other things later. If you need more information just ask Thanks in advance, Dan