Very consistent BSOD with build 1940

[plarusa]

While using a USB to serial adapter, I see the following very frequent system crash (WXP pro SP2). I am certain this problem is induced by parallels workstation, because I have used this device with windows XP for several years without any problems. I have reported similar problems with prior parallels builds.

DRIVER_CORRUPTED_MMPOOL (d0)
Arguments:
Arg1: 00000008, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000000, value 0 = read operation, 1 = write operation
Arg4: 805492ec, address which referenced memory
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is
caused by drivers that have corrupted the system pool. Run the driver
verifier against any new (or suspect) drivers, and if that doesn't turn up
the culprit, then use gflags to enable special pool. You can also set
HKLM\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\ProtectNonPagedPool
to a DWORD 1 value and reboot. Then the system will unmap freed nonpaged pool,
preventing drivers (although not DMA-hardware) from corrupting the pool.

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


READ_ADDRESS: GetUlongFromAddress: unable to read from 8055ec48
00000008

CURRENT_IRQL: 2

FAULTING_IP:
nt!MiAllocatePoolPages+58
805492ec 3918 cmp dword ptr [eax],ebx

CUSTOMER_CRASH_COUNT: 2

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0xD0

PROCESS_NAME: sqlservr.exe

LAST_CONTROL_TRANSFER: from 8054abe1 to 805492ec

STACK_TEXT:
f6e7dbdc 8054abe1 00000000 00001000 00000000 nt!MiAllocatePoolPages+0x58
f6e7dc44 804e6be4 0000000c 00001000 20206f49 nt!ExAllocatePoolWithTag+0x10b
f6e7dc68 80579ae4 00000004 00001000 20206f49 nt!ExAllocatePoolWithQuotaTag+0x46
f6e7dd00 8057bfa5 00000080 0000022c 00000000 nt!IopXxxControlFile+0x554
f6e7dd34 804de7ec 00000080 0000022c 00000000 nt!NtDeviceIoControlFile+0x2a
f6e7dd34 7c90eb94 00000080 0000022c 00000000 nt!KiFastCallEntry+0xf8
WARNING: Frame IP not in any known module. Following frames may be wrong.
00ecfef0 00000000 00000000 00000000 00000000 0x7c90eb94


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!MiAllocatePoolPages+58
805492ec 3918 cmp dword ptr [eax],ebx

SYMBOL_STACK_INDEX: 0

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP: 42250ff9

SYMBOL_NAME: nt!MiAllocatePoolPages+58

IMAGE_NAME: memory_corruption

FAILURE_BUCKET_ID: 0xD0_nt!MiAllocatePoolPages+58

BUCKET_ID: 0xD0_nt!MiAllocatePoolPages+58

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

 

[SeekerBlog]

That is bad news for my requirements. I just posted a query regarding support the Edgeport/8 eight port serial adapter that we require:

http://forum.parallels.com/thread5015.html

It appears that you have been on the bleeding edge of this issue for some time

Steve

 

[SeekerBlog]

I forgot to query - if you require only one serial port, will the Parallel Tools emulated serial port work for you?

My read of the downloaded manual is there is support for 4 emulated serial ports. Sadly we really do require eight of these nasty, ancient ports.

Steve

 

[plarusa]

For this particular application, I need to connect to external serial devices so USB to serial is the way to go. I have been able to do this type of thing flawlessly for years with VMWare for Windows and Linux, but never with Parallels Workstation for Mac. Generally speaking, the USB emulation is unacceptably buggy, and Parallels is not explaining why it remains so nearly a year since the first public beta.