Solved

Unexpected Stop Errors running Windows Server 2003 x64 w/sp2

Posted on 2012-04-03
6
1,160 Views
Last Modified: 2012-06-21
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.
0
Comment
Question by:CATHY-IT
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 3
  • 3
6 Comments
 
LVL 88

Expert Comment

by:rindi
ID: 37804969
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
 

Author Comment

by:CATHY-IT
ID: 37805777
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
 
LVL 88

Accepted Solution

by:
rindi earned 500 total points
ID: 37805880
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
Three Reasons Why Backup is Strategic

Backup is strategic to your business because your data is strategic to your business. Without backup, your business will fail. This white paper explains why it is vital for you to design and immediately execute a backup strategy to protect 100 percent of your data.

 

Author Comment

by:CATHY-IT
ID: 37806179
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
 
LVL 88

Expert Comment

by:rindi
ID: 37806210
I use M$'s Debugging Tools for Windows:

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

Author Comment

by:CATHY-IT
ID: 37823034
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

Featured Post

Comparison of Amazon Drive, Google Drive, OneDrive

What is Best for Backup: Amazon Drive, Google Drive or MS OneDrive? In this free whitepaper we look at their performance, pricing, and platform availability to help you decide which cloud drive is right for your situation. Download and read the results of our testing for free!

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Setting up a Microsoft WSUS update system is free relatively speaking if you have hard disk space and processor capacity.   However, WSUS can be a blessing and a curse. For example, there is nothing worse than approving updates and they just have…
Background Information Recently I have fixed file server permission issues for one of my client. The client has 1800 users and one Windows Server 2008 R2 domain joined file server with 12 TB of data, 250+ shared folders and the folder structure i…
If you're a developer or IT admin, you’re probably tasked with managing multiple websites, servers, applications, and levels of security on a daily basis. While this can be extremely time consuming, it can also be frustrating when systems aren't wor…
Monitoring a network: why having a policy is the best policy? Michael Kulchisky, MCSE, MCSA, MCP, VTSP, VSP, CCSP outlines the enormous benefits of having a policy-based approach when monitoring medium and large networks. Software utilized in this v…

705 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question