2008 R2 BSOD partmgr.sys when disk with OEM Partition (3rd party file system) is changed to 'Online'.

With and without SP1; Same partition does not BSOD with Server 2003 or Server 2008. 

Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.

Loading Dump File [C:\Windows\MEMORY.DMP]
Kernel Summary Dump File: Only kernel address space is available

WARNING: Whitespace at end of path element
Symbol search path is: SRV*C:\SymbolsCache*http://msdl.microsoft.com/download/symbols

Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: Server, suite: Enterprise TerminalServer SingleUserTS
Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
Machine Name:
Kernel base = 0xfffff800`01815000 PsLoadedModuleList = 0xfffff800`01a59670
Debug session time: Thu Jul 12 12:10:39.089 2012 (UTC - 4:00)
System Uptime: 0 days 19:45:44.285
Loading Kernel Symbols
...............................................................
................................................................
.......
Loading User Symbols

Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 7E, {ffffffffc0000005, fffff880010439a7, fffff88002196458, fffff88002195cb0}

Probably caused by : partmgr.sys ( partmgr! ?? ::FNODOBFM::`string'+813 )

Followup: MachineOwner
---------

3: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED (7e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff880010439a7, The address that the exception occurred at
Arg3: fffff88002196458, Exception Record Address
Arg4: fffff88002195cb0, Context Record Address

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

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

FAULTING_IP:
partmgr! ?? ::FNODOBFM::`string'+813
fffff880`010439a7 4c896808        mov     qword ptr [rax+8],r13

EXCEPTION_RECORD:  fffff88002196458 -- (.exr 0xfffff88002196458)
ExceptionAddress: fffff880010439a7 (partmgr! ?? ::FNODOBFM::`string'+0x0000000000000813)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

CONTEXT:  fffff88002195cb0 -- (.cxr 0xfffff88002195cb0)
rax=0000d8e600000000 rbx=fffffa8003ae5ae0 rcx=fffffa80038d79a8
rdx=fffff8a00e8d3500 rsi=fffffa8003ae5bc8 rdi=0000000000000000
rip=fffff880010439a7 rsp=fffff88002196690 rbp=fffffa8006528328
 r8=fffff880021966a0  r9=0000000000000060 r10=fffff80001a084e0
r11=fffff8a00e8d34e0 r12=fffffa8005ece000 r13=fffffa8003ae5bd8
r14=fffffa80038d7870 r15=fffffa80038d7870
iopl=0         nv up ei ng nz ac po cy
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010297
partmgr! ?? ::FNODOBFM::`string'+0x813:
fffff880`010439a7 4c896808        mov     qword ptr [rax+8],r13 ds:002b:0000d8e6`00000008=????????????????
Resetting default scope

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  0

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

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  ffffffffffffffff

READ_ADDRESS:  ffffffffffffffff

FOLLOWUP_IP:
partmgr! ?? ::FNODOBFM::`string'+813
fffff880`010439a7 4c896808        mov     qword ptr [rax+8],r13

BUGCHECK_STR:  0x7E

LAST_CONTROL_TRANSFER:  from fffff88001042176 to fffff880010439a7

STACK_TEXT: 
fffff880`02196690 fffff880`01042176 : 00000000`00000000 00000000`00000000 fffffa80`03c1ae90 00000000`00000000 : partmgr! ?? ::FNODOBFM::`string'+0x813
fffff880`02196790 fffff880`0109024a : fffffa80`03c1ad40 00000000`00070048 fffffa80`0393a9c0 fffffa80`0393a9c0 : partmgr!PmLegacyDeviceControl+0x116
fffff880`021967e0 fffff880`01092d36 : fffffa80`03c1ad40 00000000`00000000 fffff880`02196b18 fffff880`01092d10 : volmgrx!VmxpSendDeviceControl+0x8a
fffff880`02196870 fffff880`010a9a14 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : volmgrx!VmxpDiskGetPartitionInfoEx+0x26
fffff880`021968c0 fffff880`01063eda : fffff880`02196b18 fffffa80`03c1ad40 fffffa80`038d8e30 fffffa80`038d7800 : volmgrx!VmxPartitionArrivedImmediate+0x74
fffff880`021969c0 fffff880`01065266 : 00000000`00000010 fffffa80`038d8e30 fffff880`02196b08 00000000`00000000 : volmgr!VmpPartitionArrivedImmediate+0x5a
fffff880`02196ae0 fffff880`0105a171 : 00000000`00000000 00000000`00000000 fffffa80`038d8ce0 fffffa80`036c5170 : volmgr!VmpPartitionArrived+0x46
fffff880`02196b10 fffff800`01bb2979 : fffffa80`03ae5f28 fffff800`0189af8f fffffa80`036c5278 fffff800`01889bd2 : volmgr!VmInternalDeviceControl+0x91
fffff880`02196b40 fffff880`0104db0f : fffffa80`03ae5e10 fffffa80`038d8a20 fffffa80`038d8a20 00000000`00000000 : nt!IoForwardIrpSynchronously+0x75
fffff880`02196ba0 fffff880`01042c18 : fffffa80`03ae5ae0 fffff800`01a31280 fffffa80`036c5100 fffffa80`03ae5a00 : partmgr!PmGivePartition+0xaf
fffff880`02196bf0 fffff800`01b86633 : fffffa80`03ae5990 fffff800`01a31280 fffffa80`036c5170 fffffa80`036c5170 : partmgr!PmNotificationWorkItem+0x400
fffff880`02196c80 fffff800`0189d841 : fffff800`01a31200 fffff800`01b86600 fffffa80`036c5100 480005e4`00000002 : nt!IopProcessWorkItem+0x23
fffff880`02196cb0 fffff800`01b2ae6a : fffdf483`8d000000 fffffa80`036c5170 00000000`00000080 fffffa80`036ac040 : nt!ExpWorkerThread+0x111
fffff880`02196d40 fffff800`01884ec6 : fffff880`020cc180 fffffa80`036c5170 fffff880`020d6fc0 48000002`36850fd2 : nt!PspSystemThreadStartup+0x5a
fffff880`02196d80 00000000`00000000 : fffff880`02197000 fffff880`02191000 fffff880`02196300 00000000`00000000 : nt!KxStartSystemThread+0x16

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  partmgr! ?? ::FNODOBFM::`string'+813

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: partmgr

IMAGE_NAME:  partmgr.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4f641bc1

STACK_COMMAND:  .cxr 0xfffff88002195cb0 ; kb

FAILURE_BUCKET_ID:  X64_0x7E_partmgr!_??_::FNODOBFM::_string_+813

BUCKET_ID:  X64_0x7E_partmgr!_??_::FNODOBFM::_string_+813

Followup: MachineOwner
---------