Windows Server 2008 R2 VM Hung Memory Dump Meaning

Hello,
Our Windows 2008 R2 server running MS SQL 2008 R2 was not accessible even within the vsphere console. My only option was to power off and start up the server. The only event that I could find was the event id 1001 "BugCheck" which had the following:  "The bugcheck was 0x000000d1 (0x0000000000000000, 0x0000000000000002, 0x0000000000000000, 0xfffff88001a9556b)" The Bug Check String is "DRIVER_IRQL_NOT_LESS_OR_EQUAL".
I downloaded Blue Screen View and nothing shows in the "caused by driver" column.
Any idea on what could be or where to look for the cause? This is the first time this has happened and there were no changes to the system recently.
Thanks.
johnnvaAsked:
Who is Participating?
 
Andrew Hancock (VMware vExpert / EE MVE^2)Connect With a Mentor VMware and Virtualization ConsultantCommented:
Okay, a couple of recommendations.

1. Update you ESXi 5.1 host software, it's very old, update to at least 5.1 U3 Build 2323236. This was released in December 2014, the version of ESXi 5.1 you are using is General Release, released on September 2012!

It's very old, many bugs have been fixed since the first release!

2. REPLACE the E1000 legacy to the virtualised VMXNET3 interface, it's faster, less over head on the host, less issues in the VM, it's only designed for installations, not production.
0
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
Could you give us some background on the Host Version, is VMware Tools installed ?

are you using e1000 or VMXNET3 interface ?
0
 
Lee W, MVPTechnology and Business Process AdvisorCommented:
This appears to be a known issue with a known workaround (but may not be easy or possible for YOU to implement).
http://support.microsoft.com/kb/2507083.

Since this is VMWare, Consider disabling USB functionality.
0
 
johnnvaAuthor Commented:
Thanks for the response.
The Host version is 5.1 (799733) and VMware Tools is installed.
We are using the e1000 interface. We've had this running for over a year and have not run onto this issue before.

John
0
 
johnnvaAuthor Commented:
Probably not a bad idea to update the host. I'll also look into the VMXNET3 interface.
Thanks for your help.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.