Windows Forum

Ask something
Discussion Locked

1 User Profile BSODs under Win2K

0 helpful
12 replies

by kevin.square 1 view

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

I'm out of idea's. Win2k laptop. One user profile (domain user) works fine if laptop is connected to network but blue screens if off network. I blew away the \docs&setting\profile dir and deleted registry key for that profile.
(hklm\sw\ms\winNT\curver\profilelist)

No domain policies or mandatory/roaming profile.

Connected to network and logged on as 2 different domain users so it could create/cache logon. Shut down laptop, disconnect from network, reboot and log in as domain user 1 with no problem. Same again for user 2 and winlogon blue screen.

c...21a (Fatal System Error) Windows Logon Process system process terminated unexpectedly.
Status 0xc...5 (0x..0, 0x...0)

ths
ks

12 replies

by admin

At what point do you get the blue screen? Are there any scripts that run during logon? Did anything in the system change before you started getting the blue screen (ie hardware, software)? What type of rights does the user have? Are there any differences between user 1 and user 2?

by kevin.square

Started by disabling powermgmt, then removing likely problem applications (FSecure then Chempax) but that didn't work.

Short story was it was fine if connected to LAN during his logon but would BSOD almost immediately and consistently if disconnected from network.

Most of testing I did after having copied everything under his profile to a 'save' directory then deleting his profile and any related registry entries.

I logged on as ProblemUser and as OKUser while network connected so itwould create the local cached profiles. Then rebooting off the network I could log on as OKUser with no problem but as Problemuser it would choke. I changed his password (have since changed it back), removed home drive mapping and logon script each with no luck.

Anyway, the last thing I did was remove the HP4P printer driver. Is that what it was, I just don't know. Why didn't it cause the same problem for the OKUser profile, don't know.

It had to be something on this machine because I could do the same things on another laptop using ProblemUser account and it was fine.

by kevin.square

So where's the sense. Boot the puppy up with a LAN connection and log on as Problemuser with no problem. Pull the LAN connection, log off, then log on again (no reboot, still disconnected) and toasted.

This discussion is closed to new replies.