Hypervisor_error

Question

My surface laptop 4 keeps crashing every 5 hours (if i'm lucky)

I hope someone can help with this issue

Here are the lines from dmp file:

************ Path validation summary **************
Response                         Time (ms)     Location
Deferred                                       srv*
Symbol search path is: srv*
Executable search path is: 
Windows 10 Kernel Version 22000 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Edition build lab: 22000.1.amd64fre.co_release.210604-1628
Machine Name:
Kernel base = 0xfffff800`44800000 PsLoadedModuleList = 0xfffff800`45429750
Debug session time: Wed Jan 12 13:02:15.958 2022 (UTC + 1:00)
System Uptime: 0 days 5:02:34.248
Loading Kernel Symbols
...............................................................
................................................................
................................................................
......................................................
Loading User Symbols

Loading unloaded module list
.........................
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff800`44c159c0 48894c2408      mov     qword ptr [rsp+8],rcx ss:0018:ffffbf80`df70ecb0=0000000000020001
2: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

HYPERVISOR_ERROR (20001)
The hypervisor has encountered a fatal error.
Arguments:
Arg1: 0000000000000011
Arg2: 00000000002429c1
Arg3: 0000000000001003
Arg4: fffff81b08b42980

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

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 3000

    Key  : Analysis.DebugAnalysisManager
    Value: Create

    Key  : Analysis.Elapsed.mSec
    Value: 2996

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

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

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

    Key  : WER.OS.Branch
    Value: co_release

    Key  : WER.OS.Timestamp
    Value: 2021-06-04T16:28:00Z

    Key  : WER.OS.Version
    Value: 10.0.22000.1

FILE_IN_CAB:  MEMORY.DMP

TAG_NOT_DEFINED_202b:  *** Unknown TAG in analysis list 202b

DUMP_FILE_ATTRIBUTES: 0x1800

BUGCHECK_CODE:  20001

BUGCHECK_P1: 11

BUGCHECK_P2: 2429c1

BUGCHECK_P3: 1003

BUGCHECK_P4: fffff81b08b42980

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXPNP: 1 (!blackboxpnp)

BLACKBOXWINLOGON: 1

PROCESS_NAME:  System

STACK_TEXT:  
ffffbf80`df70eca8 fffff800`44d46afb     : 00000000`00020001 00000000`00000011 00000000`002429c1 00000000`00001003 : nt!KeBugCheckEx
ffffbf80`df70ecb0 fffff800`44c5a746     : 00000000`00000000 fffff800`44a0cb9c ffffbf80`df57ea10 ffffbf80`df70ed30 : nt!HvlSkCrashdumpCallbackRoutine+0x6b
ffffbf80`df70ecf0 fffff800`44c21a82     : 00000000`00000000 ffffbf80`df70eef0 00000000`00000000 00000000`00000000 : nt!KiProcessNMI+0x24e636
ffffbf80`df70ed30 fffff800`44c21803     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxNmiInterrupt+0x82
ffffbf80`df70ee70 fffff800`44b98d2d     : 00000000`00000000 0000002a`44c98b76 ffffaa8c`2b6f76d0 00003178`1f928d2a : nt!KiNmiInterrupt+0x243
ffffa98f`d2a3ee90 fffff800`44ada1d1     : 00000000`00000811 ffffbf80`df680100 00000000`00000002 00000000`00000811 : nt!PpmIdleGuestExecute+0x1d
ffffa98f`d2a3eed0 fffff800`44ad99e6     : fffff800`404f54c0 fffff800`44a1356a 00000000`00040006 fffff800`44c4f057 : nt!PpmIdleExecuteTransition+0x661
ffffa98f`d2a3f370 fffff800`44c198c4     : 00000000`00000000 ffffbf80`df68c240 ffffaa8c`4a303080 00000000`00001ab6 : nt!PoIdle+0x3a6
ffffa98f`d2a3f540 00000000`00000000     : ffffa98f`d2a40000 ffffa98f`d2a39000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x54

SYMBOL_NAME:  nt!HvlSkCrashdumpCallbackRoutine+6b

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

STACK_COMMAND:  .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET:  6b

FAILURE_BUCKET_ID:  0x20001_11_2429c1_nt!HvlSkCrashdumpCallbackRoutine

OS_VERSION:  10.0.22000.1

BUILDLAB_STR:  co_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {0257a84d-5edf-9526-9099-c6673d07ff49}

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

** Moved Windows / Windows 11 / Performance and system failures

Answer 1

Hello StevenK_M,

I'm sorry to say this, but the problem is back. Do you think your solution, downloading a specific surface recovery will make a difference from the general Windows 11 I downloaded and installed?

I also tried installing the new driver package for the surface again and installing the displaydriver is causing a BSOD.

Any suggestions?

Answer 2

Thank you. I already did a complete reinstall of Windows 11. It seems to be working. The only bsod I got was during the installation of the manually downloaded drivers of the surface. I think it’s the video card driver. So don’t manually install surface drivers 😉

Answer 3

Thanks for keeping us posted, NicoWD.

In this case, we suggest that you reset your Surface using a USB Recovery Image. This option reimages the entire device, including the partition on the hard drive. It is the most complete form of reset.  You must have at least 16GB/32GB of USB Flash drive and it must be formatted to FAT32 prior to downloading the Recovery Image.

Note: This removes all the files and apps on your device. You will need to back up your data and reinstall the desktop apps or run updates after the completion.

To download the Recovery Image:

1. Visit the page at http://www.surface.com/support/warranty-service-and-recovery/downloadablerecoveryimage
2. Sign in with your Microsoft Account (this is the email address we asked you for at the start of the call)
3. From the list of Surface devices available, select the device that you need a recovery image for
   Please note that while you will only be presented with devices that are currently registered on your account, you will also be presented with the option to get an image for a different type of device. If you try to use this option, you will be prompted to enter the serial number for that device
4. Download the recovery image using the button on the page
5. When the download bar pops up at the bottom of your screen, save the file in a location you will be able to find it.

Format USB Drive:

1. Insert your USB drive into the USB port of your PC.
2. From the desktop, open File Explorer
3. Tap and hold or right-click on the USB drive and choose Format
4. Select FAT32 as the file system and enter a Volume label to name the USB drive, such as RECOVERY, and then tap or click Start
5. Tap or click OK to erase the contents of the USB drive
6. Tap or click OK when the format is complete

Create a recovery drive:

1. On your Surface or PC, open recovery image that you downloaded by double-clicking it
2. At the top of the window tap on Extract and then Extract all. Select the USB drive you formatted earlier for the location and click Extract.

Perform USB recovery image:

1. Turn the Surface off by pressing the power button
2. Insert the USB recovery drive into the USB port
3. Press and hold the volume-down (-) rocker
4. Press and release the power button
5. When the Surface logo appears, release the volume-down (-) rocker
6. When prompted, choose your language options and keyboard layout
7. Select Troubleshoot
8. Select Recover from a drive. If prompted for a recovery key, select Skip this drive at the bottom of the screen.
9. If prompted, select Repartition the drives.

Hope this helps.

Answer 4

Hello StevenK,

I tried all of these steps, did them again just to be sure. No effect, the system did the same thing again today @ 16:06 UTC +1

Anything else I can try? Do I need to go back to Windows 10?

Regards,

NicoWD

Answer 5

Hello NicoWD,

Thanks for reaching Microsoft Community. We're sorry to learn that your device keeps on crashing. We'll do our best to help.

May I know what version of Windows you have? Does this issue happen after an update or just while using the device? Were there also third party software or antivirus on your device?

In the meantime, please follow these methods and observe your device:

1. Run the Surface Diagnostic Toolkit and check for Windows Update. Ensure all pending updates are installed.
2. Manually install drivers and firmware for Surface Check what is the current OS Build of your Windows version by typing winveron the search barnear the Windows logo. Go to Download driver and firmware for Surface**,**choose (your Surface model) then click Download.
   Choose the .msi file closest to your current OS Build and click Next.
   After downloading, run and install the .msi then Restart.
3. Run the System File Checker in Windows (microsoft.com).

Kindly also follow the methods on Windows stops responding on Surface (microsoft.com).

I hope this helps. Feel free to respond on this thread to keep us posted.

Regards,

StevenK