Re: BSOD with possible volsnap.sys as possible cause
- From: "Mike" <none>
- Date: Fri, 20 Jun 2008 16:12:01 -0700
Hi naphtali,
I'm not a super expert on SBS 2003 yet, but you may want to consider running
SBS best practices analyser. Here is a link to download it.
http://www.microsoft.com/downloads/details.aspx?FamilyId=3874527A-DE19-49BB-800F-352F3B6F2922&displaylang=en
Regarding your stop error, please post any event ID's from the System and
Application viewer. This link may also help resolve your BSOD code:
http://www.aumha.org/a/stop.php
"naphtali" <naphtali@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:A2FCC074-5D6F-475A-9288-68D7306C06A8@xxxxxxxxxxxxxxxx
Environment: Single server with SBS 2003 R2 SP2 on an HP ML350G5.
Approximately once a month the server produces a 0x000000D0 BSOD.
Examining
the .dmp file with WinDBG points to volsnap.sys as a possible cause.
Running
!thread and !process did not yield the Image name other than "Idle".
I cannot find any correlation to activities or processes on the server.
One
BSOD was at 5:00am and the others at random times during the work day.
Any ideas?
.
- Prev by Date: Re: Problems after SP2
- Next by Date: Re: BSOD bad_pool_header SBS 2003
- Previous by thread: From P2P to SBS 2003 Network
- Next by thread: RE: BSOD with possible volsnap.sys as possible cause
- Index(es):
Relevant Pages
|