Hypervisor Error and dpc_watchdog_error, and irql_not_less_or_equal error BSOD

Take all minidump files, zip them and upload them to the cloud.

First copy and paste all the minidump files you have to your desktop and store them in a ZIP file. Then upload the ZIP file to the cloud on a website like OneDrive, Google Drive or Dropbox.

Choose to share or right click and get the share link.

Please post the link to the ZIP file here so it can be reviewed.

I do, here is another HYPERVISOR error I experienced earlier in the day. I have a few more from the last few days if you need additional logs as well.

HYPERVISOR_ERROR (20001)
The hypervisor has encountered a fatal error.
Arguments:
Arg1: 0000000000000011
Arg2: 000000000028340f
Arg3: 0000000000001005
Arg4: ffffe8000173bda0

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

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 6062

    Key  : Analysis.Elapsed.mSec
    Value: 6419

    Key  : Analysis.IO.Other.Mb
    Value: 0

    Key  : Analysis.IO.Read.Mb
    Value: 0

    Key  : Analysis.IO.Write.Mb
    Value: 0

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

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

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

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0x20001

    Key  : Bugcheck.Code.TargetModel
    Value: 0x20001

    Key  : Failure.Bucket
    Value: 0x20001_11_28340f_USBXHCI!Isoch_TransferData_Initialize

    Key  : Failure.Hash
    Value: {69070f1f-80b4-43ea-552b-6614f784a4ba}

    Key  : Hypervisor.Enlightenments.ValueHex
    Value: 1497cf94

    Key  : Hypervisor.Flags.AnyHypervisorPresent
    Value: 1

    Key  : Hypervisor.Flags.ApicEnlightened
    Value: 1

    Key  : Hypervisor.Flags.ApicVirtualizationAvailable
    Value: 0

    Key  : Hypervisor.Flags.AsyncMemoryHint
    Value: 0

    Key  : Hypervisor.Flags.CoreSchedulerRequested
    Value: 0

    Key  : Hypervisor.Flags.CpuManager
    Value: 1

    Key  : Hypervisor.Flags.DeprecateAutoEoi
    Value: 0

    Key  : Hypervisor.Flags.DynamicCpuDisabled
    Value: 1

    Key  : Hypervisor.Flags.Epf
    Value: 0

    Key  : Hypervisor.Flags.ExtendedProcessorMasks
    Value: 1

    Key  : Hypervisor.Flags.HardwareMbecAvailable
    Value: 1

    Key  : Hypervisor.Flags.MaxBankNumber
    Value: 0

    Key  : Hypervisor.Flags.MemoryZeroingControl
    Value: 0

    Key  : Hypervisor.Flags.NoExtendedRangeFlush
    Value: 0

    Key  : Hypervisor.Flags.NoNonArchCoreSharing
    Value: 1

    Key  : Hypervisor.Flags.Phase0InitDone
    Value: 1

    Key  : Hypervisor.Flags.PowerSchedulerQos
    Value: 0

    Key  : Hypervisor.Flags.RootScheduler
    Value: 0

    Key  : Hypervisor.Flags.SynicAvailable
    Value: 1

    Key  : Hypervisor.Flags.UseQpcBias
    Value: 0

    Key  : Hypervisor.Flags.Value
    Value: 4853999

    Key  : Hypervisor.Flags.ValueHex
    Value: 4a10ef

    Key  : Hypervisor.Flags.VpAssistPage
    Value: 1

    Key  : Hypervisor.Flags.VsmAvailable
    Value: 1

    Key  : Hypervisor.RootFlags.AccessStats
    Value: 1

    Key  : Hypervisor.RootFlags.CrashdumpEnlightened
    Value: 1

    Key  : Hypervisor.RootFlags.CreateVirtualProcessor
    Value: 1

    Key  : Hypervisor.RootFlags.DisableHyperthreading
    Value: 0

    Key  : Hypervisor.RootFlags.HostTimelineSync
    Value: 1

    Key  : Hypervisor.RootFlags.HypervisorDebuggingEnabled
    Value: 0

    Key  : Hypervisor.RootFlags.IsHyperV
    Value: 1

    Key  : Hypervisor.RootFlags.LivedumpEnlightened
    Value: 1

    Key  : Hypervisor.RootFlags.MapDeviceInterrupt
    Value: 1

    Key  : Hypervisor.RootFlags.MceEnlightened
    Value: 1

    Key  : Hypervisor.RootFlags.Nested
    Value: 0

    Key  : Hypervisor.RootFlags.StartLogicalProcessor
    Value: 1

    Key  : Hypervisor.RootFlags.Value
    Value: 1015

    Key  : Hypervisor.RootFlags.ValueHex
    Value: 3f7

    Key  : WER.OS.Branch
    Value: ni_release

    Key  : WER.OS.Version
    Value: 10.0.22621.1

BUGCHECK_CODE:  20001

BUGCHECK_P1: 11

BUGCHECK_P2: 28340f

BUGCHECK_P3: 1005

BUGCHECK_P4: ffffe8000173bda0

FILE_IN_CAB:  081324-8000-01.dmp

FAULTING_THREAD:  fffff8007474c700

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXPNP: 1 (!blackboxpnp)

BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

STACK_TEXT:  
fffff800`7a26aca8 fffff800`73f45551     : 00000000`00020001 00000000`00000011 00000000`0028340f 00000000`00001005 : nt!KeBugCheckEx
fffff800`7a26acb0 fffff800`73ed4326     : 00000000`00000100 fffff800`73d6a17c ffff8001`eb73f340 fffff800`7a26ad30 : nt!HvlSkCrashdumpCallbackRoutine+0x81
fffff800`7a26acf0 fffff800`73e23d82     : 00000000`00000100 fffff800`7a26aef0 00000000`00000000 00000000`00000000 : nt!KiProcessNMI+0x16b206
fffff800`7a26ad30 fffff800`73e23aee     : 00000000`00000100 fffff800`7a26aef0 00000000`00000000 00000000`00000000 : nt!KxNmiInterrupt+0x82
fffff800`7a26ae70 fffff800`88cc49bc     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiNmiInterrupt+0x26e
fffff800`7a246fd0 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : USBXHCI!Isoch_TransferData_Initialize+0x7c

STACK_COMMAND:  .thread /r /p 0xfffff8007474c700 ; kb

SYMBOL_NAME:  USBXHCI!Isoch_TransferData_Initialize+7c

MODULE_NAME: USBXHCI

IMAGE_NAME:  USBXHCI.SYS

IMAGE_VERSION:  10.0.22621.4034

BUCKET_ID_FUNC_OFFSET:  7c

FAILURE_BUCKET_ID:  0x20001_11_28340f_USBXHCI!Isoch_TransferData_Initialize

OS_VERSION:  10.0.22621.1

BUILDLAB_STR:  ni_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {69070f1f-80b4-43ea-552b-6614f784a4ba}

PROCESS_NAME:  Unknown

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

Do you have other minidump files? Apart from the one you sent in this post

Hi Johnathan, thanks for getting back to me. I followed the steps in the link you provided. After restarting my PC I was unable to start Windows and performed the additional tasks you've provided. I took a look at my minidump files and did not see any new dump files.

Not sure if I messed something up or if this is the expected result.

My name is Jonathan Deives. I'm an Independent Advisor and I will be happy to help you today.

The minidump files do not indicate any driver or hardware causes, only memory corruption.

Try forcing Windows to show failed drivers and produce minidump files, enable Driver Verifier for this.

Make the BSOD happen 3 times and then see if the files were created.

Before running Driver Verifier, create a new system restore point.

https://answers.microsoft.com/en-us/windows/for...

If you have problems starting Windows after enabling Driver Verifier, follow these steps:

Start your PC, as soon as Windows tries to load (spinning dots appear), press and hold the power button for 5 to 10 seconds to perform a forced shutdown

Do this two or three times.

Windows will boot into the Recovery Environment.

Go to Troubleshoot > Advanced Option > Startup Settings and click Restart.

When restarting, press 4 to enter safe mode.

Open command prompt as administrator, run these two commands and restart your PC.

verifier /reset

verifier /bootmode resetonbootfail