asked on

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.

rindi

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).

CATHY-IT

ASKER

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

ASKER CERTIFIED SOLUTION

rindi

membership

This solution is only available to members.

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

Start Free Trial

CATHY-IT

ASKER

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

rindi

I use M$'s Debugging Tools for Windows:

http://msdn.microsoft.com/en-us/windows/hardware/gg463009

CATHY-IT

ASKER

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.