We have a Win2k terminal server w/sp4. The server is blue screening almost
every day. Sometimes twice a day. The server has plenty of hardware
resources - nothing is being maxed out. The server is a Proliant ML370 G3
dual processor machine. I have worked with HP support and updated every
possible driver, firmware, and bios. the HP tech says it's an operating
system issue. The process referenced in the blue screen is ntoskrnl.exe.
The hexidecimal#s caught by HPs log is the following: 0x00000001E:
(0xc0000044,0x804a475c,0x00000000,0x00000000) Any help would be great

"Paul" <(E-Mail Removed)> wrote in message
news:3AFB5BBB-60DF-4D05-AB07-(E-Mail Removed)...
> We have a Win2k terminal server w/sp4. The server is blue screening
almost
> every day. Sometimes twice a day. The server has plenty of hardware
> resources - nothing is being maxed out. The server is a Proliant ML370 G3
> dual processor machine. I have worked with HP support and updated every
> possible driver, firmware, and bios. the HP tech says it's an operating
> system issue. The process referenced in the blue screen is ntoskrnl.exe.
> The hexidecimal#s caught by HPs log is the following: 0x00000001E:
> (0xc0000044,0x804a475c,0x00000000,0x00000000) Any help would be great

I would rebuild it, then create an image that be be used
in case it happens again.