asked on

Windows 2003 Enterprise Terminal Server Stop Error

I have a Windows 2003 Enterprise running Terminal Services that's been crashing, and I rec'd this error message, was hoping someone could tell me what caused it:

The reason supplied by user JYINJ01\Administrator for the last unexpected shutdown of this computer is: System Failure: Stop error
Reason Code: 0x805000f
Bug ID:
Bugcheck String: 0x000000d0 (0x037a037d, 0x00000002, 0x00000001, 0x80564364)
Comment: 0x000000d0 (0x037a037d, 0x00000002, 0x00000001, 0x80564364)

ASKER CERTIFIED SOLUTION

Luc Franken

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

itcnbwise

ASKER

OK, it found about 20 files or so. Should I just remove them, or do I have to try and figure out which printer they are for and use the add/remove programs to remove them?

Luc Franken

You shouldn't remove them. That'll cause all hardware wich they belong to to fail.

You'll have to find out what hardware they relate to, just do them one by one.
Uninstall the device from the device manager in safe mode and then reboot the computer. Windows should automatically try to update the drivers. (see what drivers are loaded at IRQ2 to start with)

LucF

itcnbwise

ASKER

Thanks! Will give it a shot and let you know ...

Luc Franken

Ok, good luck.

LucF

itcnbwise

ASKER

Well, I should add this server is only used for Terminal Services - there is not actually any hardware plugged into it (there are no printers physically connected). The drivers are just used when people log into the server, and Terminal Services redirects print output to their local PC and printer.

Luc Franken

Drivers are used for ALL hardware, really everything, the monitor/videocard/modem/network card/harddisk controller etc. etc. Not just for printers :)

LucF

itcnbwise

ASKER

Oh, I know, but the only files the utility found which were unsigned are printer drivers.

Luc Franken

:( Hmm... strange.

Please check what driver was loaded at 0x80564364 or 0x037a037d as in one of those places the troubling driver is loaded.
To do so, find your latest dumpfile and then use pstat to make the list as explained here:

How to gather information after a memory dump in Windows XP
http://support.microsoft.com/?kbid=314084

LucF

itcnbwise

ASKER

Thanks, LucF, for all your help! In the KB article you posted, I tried this:

"An alternate method is to open the \\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management registry key. In this key, create or edit the ProtectNonPagedPool value, and set it equal to DWORD 1. Then reboot. Then the system will unmap all freed nonpaged pool. This will prevent drivers from corrupting the pool. (This does not protect the pool from DMA hardware, however.)"

And it worked! Well, at least no crashes yet :) But it appears almost all the errors have gone away. Word crashed once or twice since I applied the fix, but before, it was crashing 20 times a day.

Luc Franken

That's great news!

Glad to help,

LucF