BSOD with possible volsnap.sys as possible cause

[tynana]

I’m having a HP ProLiant ML350 G5 running with SBS 2003 R2 SP2. I’m using this since a year now but from past 4 months, atleast once a month I receive BSOD on this server with error 0x000000D0. While troubleshooting I came through the .dmp file with WinDBG points to volsnap.sys as a possible cause.

Can anyone please tell me what can I do to stop this problem? Thank you.

[LeonL]

Hello tynana, I’ll first suggest you to better download, install and run SBS best practices analyser. You can get the same from here http://www.microsoft.com/downloads/d...displaylang=en. As far as the BSOD error is concerned, just check the Event viewer. If there is any log generated regarding this, please post it back here.

You should also try contacting HP and ask them if they have any diagnostic software? If they have any such software it will help you to verify the integrity of the underlying hardware.

[Landon]

Can suggest you few workarounds, hope anyone of them helps you out. Just follow these:

1. Please contact HP to check if there is any Hardware Failures and ensure all parts of the hardware on SBS are running fine.
2. If your server is having a number of third party applications which you don’t require, please delete them as Some 3rd-party software on SBS may cause the issue.
3. Try clean boot.

[tynana]

Thank you very much for your help Landon. I called up HP and they suggested me their diagnostics tool. I ran the same and found there is no hardware related problem in my box. Also there is no such third party tool which may be creating the problem.

What now?

[tynana]

Ok, here is the thing. I talked to other MS support personnel and am currently
testing a fix of the latest HP RAID controller drivers (6.12.4.32) along with
the MS hotfix 932755.Now the problem solved. Thanks for all your helps.