Unexpected Stop Errors running Windows Server 2003 x64 w/sp2

We have a Windows Server 2003 x64 SP2 Terminal Server,that for the most part function just fine.  But it has as of yesterday had Blue Screen and Stop error occur twice, the other time being 6mths ago, I realize this isn't so bad, but I'd like to resolve or at least attempt to resolve the issue.

The Microsoft support article KB937455, seems to describe the errors that we are getting when it happened. Which are REASON Code:0x805000f both times with different bug strings.  Should I go ahead and apply the hotfix? file name is fix201603.

I've never applied a hotfix manually on a Server, guess I just never needed too. I hesitate as I don't want to make the situation worse by updating the NTFS file as this hotfix will do or cause another issue. I do not have a non-productive server to test the hotfix on as MS suggests,
so what pre-cautions should I take prior to install, other than backing up the data.

Our current NTSF.sys file is version 5.2.3790.3959 03/22/06.

FYI - We also have another Windows Server 2003 x86 SP2 that is the DC and File/Print Server.
CATHY-ITAsked:
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.

rindiCommented:
Zip your last 3 minidump files and attach them in your next comment. Where those files are depends on how the system is configured (Usually you'll find those files in \Windows\Minidump, just search for *.dmp files, and make sure you can see hidden files, as they are hidden).
0
CATHY-ITAuthor Commented:
Here are the memory dumps I found for dates I mentioned above and one other date March 14, 2011 that shows no events in the Log for that time and is around the time this new server replaced the orginal terminal server.
Server-Memory-Dumps.zip
0
rindiCommented:
One of the dumps point to the driver srtsp64.sys as the cause of the BSOD, and that is part of the Symantec Software. Another Dump showed snapvol.sys as the cause (I think that is part of the Volume Shadow Copy part of the OS), and the other dump didn't show too much to be of help. The problem is that all 3 dumps have a different cause and also a different crash code. That makes it hard to properly say what you need to do to fix this. I wouldn't apply the hotfix, particularly since you haven't had the issue very often.

What I'd suggest (and that I'd generally suggest for Terminal Servers), is to reboot the server regularly (maybe each weekend). On TS's it is possible that users are running software which doesn't properly release the resources when the software is closed, and that can cause memory issues etc when these add up. A reboot will clear such memory leaks.
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
Cloud Class® Course: CompTIA Healthcare IT Tech

This course will help prep you to earn the CompTIA Healthcare IT Technician certification showing that you have the knowledge and skills needed to succeed in installing, managing, and troubleshooting IT systems in medical and clinical settings.

CATHY-ITAuthor Commented:
May I ask, what are you using to look at the Memory dump files?  so I can see what you see and learn to read these dumps better. I'm using Nirsoft blue screenview and all though I see a whole list of drivers, it states that the two last crashes are caused by driver NTOSKRNL.exe
0
rindiCommented:
I use M$'s Debugging Tools for Windows:

http://msdn.microsoft.com/en-us/windows/hardware/gg463009
0
CATHY-ITAuthor Commented:
I'll install the MS Debugging tool and take a closer look myself. Otherwise, I'm not going to install this particular hotfix if there's a great chance that its not the solution.

Thanks for your input.
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
Microsoft Server OS

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.