Parallels Tools causing BSOD (17.0.1)

Man, PD17 is kind of a stinker (see also https://forum.parallels.com/threads/cannot-use-keyboard-after-restoring-to-snapshot-pd17.354501/)...
So - when updating parallels tools on a windows machine running 17.0 (to parallels tools 17.0.1), I get the following kernel panic (BSOD) due to a driver verifier violation (I am a driver developer, so I run my VMs with driver verifier enabled).
You can download the full dump from http://www.toonetown.com/nathan/projects/MEMORY-2021-09-20.DMP.
I believe this is due to the unloading of version 17.0...as a hard reset allows parallels tools to continue and complete correctly.
Technical Report 379335941 has been submitted.

 

Hello, please sorry for the delay in response.
We've involved the Parallels Engineering Team in this case and once we get any updates we will let you know
Also could you reupload the full dump please?

 

The full dump is still available at the above link. It is far too large to upload to the forum or via a troubleshooting report.

 

Just updated to 17.1.1 and still getting this BSOD when upgrading parallels tools when running with driver verifier.

 

Hi,

Sorry to bother you toonetown, but I'm wondering if I'm experiencing the same issue as you. I don't have your developer skill at the driver level, but my VM keeps restarting in the middle of the parallels tools install (that's what I posted https://forum.parallels.com/threads...ble-to-reinstall-after-17-1-1-upgrade.355933/).

You're talking about a "hard reset", how do you do that ? I don't have anything to uninstall the previous version.

Don't bother answering if it doesn't make sense to you or you don't have the time ;-)

 

Well, out of despair, I tried one more time to boot in safe mode, after many other operations (deleting files, expired certificates... I can't remember everything), and it worked out !
Really sorry for having written here. Unfortunately I can't delete my previous message.

 

It might be the same issue...but if you don't remember enabling driver verifier within your Windows VM, I don't think it would be.
It is possible that it still is a kernel panic and that is causing the crash. Check for a file in your van called c:\windows\MEMORY.dmp. If there is one, something is crashing - upload that dump file to parallels support for them to look at it.
My mention of a "hard reset" was due to me just clicking on "Reset" menu option on the VM. If I see that it starts to dump, I can do that and then the tools install will continue after a reboot. However, this is due to my setup of full memory dumps and driver verifier. I don't think that would apply in your case either.
I'd suggest looking for a memory dump file, and if there is one, post it to your original thread.
Good luck! As I called out in my first message in this thread, there seems to be quite a few issues with version 17, unfortunately.

 

Thanks for your explanation. Indeed, I don't think it's related, and I can't find this MEMORY.dmp file.
Well, my issue is resolved for this upgrade, I hope next time will be more smooth.
Good luck to you too

 

This driver verifier crash is still happening...I got the crash when upgrading to 17.1.2 and installing the new parallels tools in my VM. New dump file is available at http://www.toonetown.com/nathan/projects/MEMORY-2022-03-22.DMP

 

Your BSOD is occuring in your filesystem driver (prl_fs) - due to deleting uninitialized lookaside lists:

Code:

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

DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
A device driver attempting to corrupt the system has been caught.  This is
because the driver was specified in the registry as being suspect (by the
administrator) and the kernel has enabled substantial checking of this driver.
If the driver attempts to corrupt the system, BugChecks 0xC4, 0xC1 and 0xA will
be among the most commonly seen crashes.
Arguments:
Arg1: 00000000000000cb, Deleting uninitialized lookaside list.
Arg2: fffff80e50a521c0, Lookaside list address.
Arg3: 0000000000000000
Arg4: 0000000000000000

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


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 3406

    Key  : Analysis.DebugAnalysisManager
    Value: Create

    Key  : Analysis.Elapsed.mSec
    Value: 12764

    Key  : Analysis.Init.CPU.mSec
    Value: 1483

    Key  : Analysis.Init.Elapsed.mSec
    Value: 50197

    Key  : Analysis.Memory.CommitPeak.Mb
    Value: 92

    Key  : WER.OS.Branch
    Value: vb_release

    Key  : WER.OS.Timestamp
    Value: 2019-12-06T14:06:00Z

    Key  : WER.OS.Version
    Value: 10.0.19041.1


FILE_IN_CAB:  MEMORY-2022-03-22.DMP

BUGCHECK_CODE:  c4

BUGCHECK_P1: cb

BUGCHECK_P2: fffff80e50a521c0

BUGCHECK_P3: 0

BUGCHECK_P4: 0

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXWINLOGON: 1

PROCESS_NAME:  System

STACK_TEXT: 
ffffb30e`9e01b9b8 fffff803`361ede34     : 00000000`000000c4 00000000`000000cb fffff80e`50a521c0 00000000`00000000 : nt!KeBugCheckEx
ffffb30e`9e01b9c0 fffff803`361fe75c     : 00000000`00000000 fffff803`35f8e9c0 00000000`00000000 fffff80e`50a521c0 : nt!VerifierBugCheckIfAppropriate+0xe0
ffffb30e`9e01ba00 fffff803`361fe14e     : fffff80e`50a521c0 ffffd486`b2610100 00000000`00000000 ffffd486`b25f2710 : nt!ViLookasideDelete+0x80
ffffb30e`9e01ba50 fffff80e`50a5e98d     : fffff803`35f8e9c0 00000000`00000000 00000000`00000000 ffffb30e`9f7c9750 : nt!VerifierExDeleteNPagedLookasideList+0xe
ffffb30e`9e01ba80 fffff80e`50a55366     : 00000000`00000000 00000000`00000000 00000000`00000000 ffffd486`ada91840 : prl_fs+0x1e98d
ffffb30e`9e01bab0 fffff803`36069453     : ffffd486`b2098040 ffffd486`ada91840 fffff803`36543440 00000000`00000000 : prl_fs+0x15366
ffffb30e`9e01bb30 fffff803`35ad76d5     : ffffd486`00000000 00000000`00000000 ffffd486`b2098040 ffffd486`00000000 : nt!IopLoadUnloadDriver+0xdaa93
ffffb30e`9e01bb70 fffff803`35b74a15     : ffffd486`b2098040 00000000`00000080 ffffd486`adaba080 000fa40f`b19bbdff : nt!ExpWorkerThread+0x105
ffffb30e`9e01bc10 fffff803`35c1dc78     : fffff803`345f3180 ffffd486`b2098040 fffff803`35b749c0 cfcfcfcf`cfcfcfcf : nt!PspSystemThreadStartup+0x55
ffffb30e`9e01bc60 00000000`00000000     : ffffb30e`9e01c000 ffffb30e`9e016000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28


SYMBOL_NAME:  prl_fs+1e98d

MODULE_NAME: prl_fs

IMAGE_NAME:  prl_fs.sys

STACK_COMMAND:  .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET:  1e98d

FAILURE_BUCKET_ID:  0xc4_cb_VRF_prl_fs!unknown_function

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {7ea8cd4d-6216-51c2-37c0-c6750e2652dd}

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

 

This is still happening with 18.1.1 - is there any word on when it will be addressed?

 

Still happening with 19.1.0...am I really the only person in the world who runs with driver verifier? (I only do it because I'm a driver developer and need it in my VM for testing...)