Blue-screen-of-death only when login in

[Guest]

Greetings,

I have an HP DL380 Server running Windows 2000 Standard Server with SP4 in
Windows 2000 Domain.
This server is used only as a Print and File Server.
Everything was working fine until today, and, as far as I know, nothing was
changed on that Server.

After I type my Domain UserName, Password and click the "OK" button to
login, I keep getting the blue-screen-of-death stating:

*** STOP: 0x0000001E (0xC0000005, 0x8052318B, 0x00000000, 0x00000FF8)
KMODE_EXCEPTION_NOT_HANDLED
*** Address 8052318B base at 80400000 DateStamp 41773335 - ntoskrnl.exe
Beginning dump of physical memory.
Dumping physical memory to disk:

I get this problem ONLY when I try to login locally or via Terminal Service.
If I do not login, the Server is working just fine.
I could:
1. print to the Shared Printers hosted by the Server
2. access the Server's shared folders
3. map its C$ or D$ drive from my workstation
4. ping its IP Address

This problem persists even after I selected the "Last Known Good
Configuration" option during the boot.

Any suggestion?

Sincerely,
Ibnu

 

[Pegasus \(MVP\)]

Greetings,

I have an HP DL380 Server running Windows 2000 Standard Server with SP4 in
Windows 2000 Domain.
This server is used only as a Print and File Server.
Everything was working fine until today, and, as far as I know, nothing was
changed on that Server.

After I type my Domain UserName, Password and click the "OK" button to
login, I keep getting the blue-screen-of-death stating:

*** STOP: 0x0000001E (0xC0000005, 0x8052318B, 0x00000000, 0x00000FF8)
KMODE_EXCEPTION_NOT_HANDLED
*** Address 8052318B base at 80400000 DateStamp 41773335 - ntoskrnl.exe
Beginning dump of physical memory.
Dumping physical memory to disk:

I get this problem ONLY when I try to login locally or via Terminal Service.
If I do not login, the Server is working just fine.
I could:
1. print to the Shared Printers hosted by the Server
2. access the Server's shared folders
3. map its C$ or D$ drive from my workstation
4. ping its IP Address

This problem persists even after I selected the "Last Known Good
Configuration" option during the boot.

Any suggestion?

Sincerely,
Ibnu

See if the condition persists after renaming your profile
folder to a different name, thus forcing a new profile folder
to be created.

 

[Guest]

Greetings Pegasus,

Thank you very much for the suggestion.
I will try it tomorrow evening, and let you know how it goes.

Cheers.

 

[Guest]

Hi Pegasus,

I still get the blue-screen when I try to login even after I:
1. rename my profile
2. clear event viewer
3. delete my profile

Any other suggestion?

 

[Pegasus \(MVP\)]

Something runs at logon time that kills your server.
Check your startup folder, your logon script and
your registry RUN key:
HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Run

 

[Guest]

Pegasus,

Thank you very much for the information.
I will try it tonight.

Thanks again,
Ibnu