Hey guys,

Just seeing if anyone has run into this issue or has any ideas on troubleshooting this as my Bing-foo seems to not be working with me.

So earlier this evening i went to add a virtual CD-Rom drive and ISO to an active VM within my Hyper-visor cluster (using SCVMM 2012 R2) and the entire host node that was supporting that VM decided it was going to nope right out of that and just BSOD'ed with error 0x3B within a few seconds after the task started. Now the host eventually came back up and the VM's that were on that node successfully recovered on another node in the cluster, and the VM that I was trying to reconfigure appears to have kept its new configuration and is functioning normally (seems strange to me to be honest). 

The bug check for the Hypervisor is below but i am not able to discern any clear reason for the issue. Drivers have been updated within the last 3ish months, updates are current, and i have been able to perform this feat (adding a virtual CD-rom drive with ISO) on a VM in this cluster before without this happening. Error log is clean up until after the reboot.

SYSTEM_SERVICE_EXCEPTION (3b)

An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff80196a0efae, Address of the instruction which caused the bugcheck
Arg3: ffffd00020617990, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.

Debugging Details:
------------------

TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s".

FAULTING_IP:
vhdmp!VhdmpiInitializeBackingStoreChainForBalancer+26
fffff801`96a0efae 4883bb8802000000 cmp     qword ptr [rbx+288h],0

CONTEXT:  ffffd00020617990 -- (.cxr 0xffffd00020617990)
rax=0000000000000000 rbx=ffffffffffffffff rcx=fffff80196a4fd80
rdx=0000000000000000 rsi=ffffe00181a6ee00 rdi=0000000000000000
rip=fffff80196a0efae rsp=ffffd000206183c0 rbp=0000000000000001
 r8=0000000000000001  r9=0000000000000000 r10=fffff80196a4fef0
r11=ffffd000206183c0 r12=ffffe00185bf7500 r13=ffffe0018974be01
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010286
vhdmp!VhdmpiInitializeBackingStoreChainForBalancer+0x26:
fffff801`96a0efae 4883bb8802000000 cmp     qword ptr [rbx+288h],0 ds:002b:00000000`00000287=????????????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT_SERVER

BUGCHECK_STR:  0x3B

PROCESS_NAME:  vmwp.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff80196a77fb2 to fffff80196a0efae

STACK_TEXT: 
ffffd000`206183c0 fffff801`96a77fb2 : fffff801`96a4fd80 00000000`00000000 ffffe001`81a6ee00 ffffe001`81a6ee00 : vhdmp!VhdmpiInitializeBackingStoreChainForBalancer+0x26
ffffd000`206183f0 fffff801`96a19a2b : fffff801`96a4fd80 fffff801`96a4fd01 ffffd000`20618498 ffffe001`85bf7440 : vhdmp!VhdmpiActivateProposedBackingStoreChain+0xfe
ffffd000`20618460 fffff801`96a195e6 : 00000000`00000000 00000000`00000000 ffffe001`85bf7440 ffffe001`85bf7518 : vhdmp!VhdmpiIsoModifyBackingStore+0xa3
ffffd000`20618490 fffff801`96a6bc0c : 00000000`00000000 ffffd000`20618540 fffff801`96a4d7a0 ffffc001`00000000 : vhdmp!VhdmpiIsoEjectMediaThread+0x102
ffffd000`206184d0 fffff801`96a2d656 : 00000000`00000001 ffffe001`8974bfb0 ffffe001`8974bee0 00000000`000009b8 : vhdmp!VhdmpiStartAsyncOp+0x268
ffffd000`20618580 fffff801`96a0333b : ffffe001`8974bee0 ffffe001`7e1ba8c0 00000000`00000000 fffff800`5c504493 : vhdmp!VhdmpiIsoControlObjectDeviceControlHandler+0x1ca
ffffd000`206185b0 fffff801`96a031e6 : ffffe001`8974bee0 ffffe001`7f1bf100 00000000`002d1901 ffffffff`00000000 : vhdmp!VhdmpiControlObjectIrpHandler+0x117
ffffd000`206185e0 fffff801`9716b55b : ffffe001`8974bee0 00000000`002d19e0 00000000`00000000 00000000`00000000 : vhdmp!VhdmpFirstLevelIrpHandler+0x6e
ffffd000`20618630 ffffe001`8974bee0 : 00000000`002d19e0 00000000`00000000 00000000`00000000 00000000`00000000 : vhdparser+0x155b
ffffd000`20618638 00000000`002d19e0 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0xffffe001`8974bee0
ffffd000`20618640 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 ffffc001`b7550f00 : 0x2d19e0

FOLLOWUP_IP:
vhdmp!VhdmpiInitializeBackingStoreChainForBalancer+26
fffff801`96a0efae 4883bb8802000000 cmp     qword ptr [rbx+288h],0

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  vhdmp!VhdmpiInitializeBackingStoreChainForBalancer+26

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: vhdmp

IMAGE_NAME:  vhdmp.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  54504a1d

STACK_COMMAND:  .cxr 0xffffd00020617990 ; kb

FAILURE_BUCKET_ID:  X64_0x3B_vhdmp!VhdmpiInitializeBackingStoreChainForBalancer+26

BUCKET_ID:  X64_0x3B_vhdmp!VhdmpiInitializeBackingStoreChainForBalancer+26

Followup: MachineOwner

Your Bing-foo most likely showed you that the 3b code is almost always related to a driver.  The fact that you say they are current does not guarantee they are bug free.  But I would check again to ensure that nothing has changed in the last 3ish months.  It could be that you did hit a bug that nobody else has run into yet.  If it happens again, I would start paying more attention.  Generally, though, I ignore one-time bug-checks because it takes too much time to trace down root cause for a single instance.  If it happens more often, then I obviously pursue it.  Errors that can be replicated are much easier to track down than a one-time, random occurrence.

Hi ,

Additional, if you want to perform the further research on the BSOD, I would like to suggest that you contact Microsoft Customer Service and Support (CSS) via telephone so that a dedicated Support Professional can assist with your request. It is not the best place to talk about the BSOD issue because it is not effective for us to debug the crash dump file here in the forum.

To obtain the phone numbers for specific technology request please take a look at the web site listed below:

http://support.microsoft.com/default.aspx?scid=fh;EN-US;OfferProPhone#faq607

Hope the issue will be resolved soon.

Best Regards,