Solved

SBS 2011 Std Crashing (iSCSI related)

Posted on 2013-11-29
4
458 Views
Last Modified: 2014-08-17
Hello,

We have a VM Server running ESXi 5.1. One of the hosts is running SBS 2011 Std.

Physical server details :-

HP ProLiant DL380 G7
Dual Intel Xeon E5620 2.4Ghz
RAM: 32GB

----------------------------------------------

The SBS Host is crashing periodically and analysis of the dump files point to the likely cause being the Microsoft iSCSI Initiator. We used to have several NAS drives connected via iSCSI but this is no longer the case so have disabled the service. However, the SBS is still crashing for the same reason. I've searched the web and EE for a solution without much success thus far so am hoping someone will be able to assist please.

Crash Dump Analysis below :-

On Fri 29/11/2013 04:16:32 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: msiscsi.sys (msiscsi+0x72B6)
Bugcheck code: 0xA (0x4, 0x2, 0x1, 0xFFFFF80001ADB471)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\msiscsi.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Microsoft iSCSI Initiator Driver
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.
0
Comment
Question by:Neos-IT
  • 2
4 Comments
 
LVL 35

Expert Comment

by:Cris Hanna
ID: 39686351
First things
SBS Best Practice Advisor (make sure you get up to 1.4)
0
 
LVL 20

Expert Comment

by:compdigit44
ID: 39694201
Any software/hardware changes on the server lately? Both the ESXi host and Windows VM.

Do any other servers connect to your iSCSI SAN. If so, are they having storage issues?

Have you checked the logs on your iSCSI SAN and network switches.
0
 

Accepted Solution

by:
Neos-IT earned 0 total points
ID: 40255293
Apologies for not getting back to you on this.

This was very weird. Can't be for certain but looks like it was due to an old backup job that was still pointing to a location that no longer exists. Server hasn't crashed since changing this.
0
 

Author Closing Comment

by:Neos-IT
ID: 40265942
Can't say with certainty it was the cause of the problem.
0

Featured Post

Industry Leaders: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

Question has a verified solution.

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

In this article, I will show you HOW TO: Perform a Physical to Virtual (P2V) Conversion the easy way from a computer backup (image).
This article outlines why you need to choose a backup solution that protects your entire environment – including your VMware ESXi and Microsoft Hyper-V virtualization hosts – not just your virtual machines.
Teach the user how to join ESXi hosts to Active Directory domains Open vSphere Client: Join ESXi host to AD domain: Verify ESXi computer account in AD: Configure permissions for domain user in ESXi: Test domain user login to ESXi host:
How to Install VMware Tools in Red Hat Enterprise Linux 6.4 (RHEL 6.4) Step-by-Step Tutorial

749 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