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)
LVL 4
itcnbwiseAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

LucFEMEA Server EngineerCommented:
Hi itcnbwise,

Bug Check 0xD0: DRIVER_CORRUPTED_MMPOOL
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/ddtools/hh/ddtools/BCCodes_35bd3573-61ca-4dbf-8e96-5206e7b83bc1.xml.asp

I suggest you to start with checking for unsigned drivers.
Start => Run => "sigverif"

Try finding MS signed drivers for all unsigned ones.

Greetings,

LucF
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
itcnbwiseAuthor Commented:
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?
0
LucFEMEA Server EngineerCommented:
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
0
Cloud Class® Course: Microsoft Office 2010

This course will introduce you to the interfaces and features of Microsoft Office 2010 Word, Excel, PowerPoint, Outlook, and Access. You will learn about the features that are shared between all products in the Office suite, as well as the new features that are product specific.

itcnbwiseAuthor Commented:
Thanks!  Will give it a shot and let you know ...
0
LucFEMEA Server EngineerCommented:
Ok, good luck.

LucF
0
itcnbwiseAuthor Commented:
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.
0
LucFEMEA Server EngineerCommented:
Drivers are used for ALL hardware, really everything, the monitor/videocard/modem/network card/harddisk controller etc. etc. Not just for printers :)

LucF
0
itcnbwiseAuthor Commented:
Oh, I know, but the only files the utility found which were unsigned are printer drivers.
0
LucFEMEA Server EngineerCommented:
:( 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
0
itcnbwiseAuthor Commented:
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.
0
LucFEMEA Server EngineerCommented:
That's great news!

Glad to help,

LucF
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Server 2003

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.