Hi all,

This seems like a common problem on the internet but I haven't found a definitive solution anywhere.

Sometimes when booting up a Windows 10 VM, it will boot to a black screen in either a Basic or Enhanced session.

When I switch from the one to the other magically I can see that the VM has indeeded booted. The mere switching between the session types (Basic to Enhanced or vice versa) fixed the problem.

Obviously however it would be nice to not have to do this.

Does anyone know of the reason why this occurs and how to fix it once and for all? :) 

I am using the latest HyperV manager with the latest graphics drivers.

m

Hi

I have a problem where i would like to recover from an avhdx file. the parent is not there in the chain and my avhdx file is about 50GB. Any help on how this can be done or is there any software that i can use to recover the data on that file.

Anyone knows how to fix this bug?

https://docs.microsoft.com/en-us/windows-server/virtualization/hyper-v/best-practices-analyzer/dynamic-memory-is-enabled-but-not-responding-on-some-virtual-machines

This happens on alot of our VM's running a 2016 Hyper-V Cluster - hardware is HPE BL460c G9.

"This is expected behavior if the virtual machine is booting" - True dat!

any idea what is wrong if anything?

Log Name:      Microsoft-Windows-Hyper-V-Worker-Admin

Source:        Microsoft-Windows-Hyper-V-Worker

Date:          8/7/2011 11:39:51 PM

Event ID:      18560

Task Category: None

Level:         Critical

Keywords:      

User:          NETWORK SERVICE

Computer:      rocky

Description:

'Suse VM3 Prod' was reset because an unrecoverable error occurred on a virtual processor that caused a triple fault. If the problem persists, contact Product Support. (Virtual machine ID 6C3CFD6B-965D-4C56-B3AB-7BEBB6C9CFD4)

Event Xml:

<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">

  <System>

    <Provider Name="Microsoft-Windows-Hyper-V-Worker" Guid="{51DDFA29-D5C8-4803-BE4B-2ECB715570FE}" />

    <EventID>18560</EventID>

    <Version>0</Version>

    <Level>1</Level>

    <Task>0</Task>

    <Opcode>0</Opcode>

    <Keywords>0x8000000000000000</Keywords>

    <TimeCreated SystemTime="2011-08-08T04:39:51.569790700Z" />

    <EventRecordID>2610</EventRecordID>

    <Correlation />

    <Execution ProcessID="6172" ThreadID="5500" />

    <Channel>Microsoft-Windows-Hyper-V-Worker-Admin</Channel>

    <Computer>rocky</Computer>

    <Security UserID="S-1-5-20" />

  </System>

  <UserData>

    <VmlEventLog xmlns:auto-ns2="http://schemas.microsoft.com/win/2004/08/events" xmlns="http://www.microsoft.com/Windows/Virtualization/Events">

      <VmName>Suse VM3 Prod</VmName>

      <VmId>6C3CFD6B-965D-4C56-B3AB-7BEBB6C9CFD4</VmId>

    </VmlEventLog>

  </UserData>

</Event>

Hello Folks,

I bought a new desktop from Lenovo,  it was used.

the desktop is i7-3770 and Windows 10 pro with a BIOS supporting ( I have checked vie CMD command "systeminfo" and it show up with YES in all LINE), but when I go to Windows Features to select Hyper-v only the first box that I can select.

help me out please -_-

Good morning!

I'm running into a problem with Hyper-V and I don't have a lot of information to troubleshoot off of. I'm hoping the experience and knowledge here will help me zero in on a solve for this.

Basics:
I'm trying to enable replication of a single VM'd server from my client's office in Dothan to their office in Auburn (War Eagle!). I'm also trying tore-enable replication of two user VMs from Auburn to Dothan. Dothan's hypervisor is MS Hyper-V running in Windows Server 2019 DE. Auburn's hypervisor is MS Hyper-V running in WS2016 DE. The VM to be replicated from Dothan is WS2019 DE acting as a DC and an file server. The VMs being replicated from Auburn are Win10 Pro workstations. The purpose of all replication is simple redundancy; offsite backup of each VM in case of catastrophe. The WAN infrastructure is VPN over broadband. The organization uses ADDS with all users and machines in one domain.

History:
I'd successfully set up replication of the two VMs from Auburn to Dothan a few weeks ago. I ran into issues with Kerberos that were solved by editing the registry on each hypervisor so that Kerberos had to use TCP, and eliminating packet fragmentation at the VPN routers. Those VMs were replicating consistently until this past weekend. 

During the weekend, I had to reformat the volume where the VMs are stored in Dothan. The Auburn server is a mess that I inherited from the last IT guy, nothing is virtualized on this machine and I want some redundancy, so I was going to use DFS to replicate critical files from this server to Dothan. However, when I built Dothan I used ReFS for the storage volume, and since DFS won't run on ReFS, I decided to back up Dothan, burn down the storage volume, reformat with NTFS and restore. I used Win Server Backup in WS2019 to perform a bare metal (full) backup to an external disk. Before running the backups, I merged all checkpoints back into each VHD and created new thin-provisioned VHDs from my thick-provisioned VHDs. I successfully tested each VM with the thin-prov VHDs attached before shutting all VMs down and running the backup set.

Problem:
After formatting the storage volume NTFS, I ran into issues restoring Hyper-V directly from WSB. Instead, I restored the VHDs, built new VMs for my 1 server VM and 2 replicated user VMs, and reconnected the VHDs. Everything boots up in Hyper-V and the machines run normally. The server VM is up and running with no issues. All the data is there and I can remote into each machine. Once the dust had settled, I attempted to enable replication of the server VM from Dothan to Auburn but received the following error: https://1drv.ms/u/s!Av-G2MTFk-0ZgupOcDu6lQhOgOmLUQ?e=52vnr2

This is proving to be maddening for me because there's no data associated with the error. No code or whatnot. I'm not receiving any errors from the replication wizard in terms of "unable to determine configuration", authentication errors, or anything during the process to make me think these two servers can't talk to each other. They're talking about this replication, they're just not kicking it off. 

In an attempt to control for other variables, I decided to re-enable replication of the two VMs from Auburn to Dothan. When I tried, I got this error: https://1drv.ms/u/s!Av-G2MTFk-0ZgupPTJzbNDNF_oiPgw?e=hWtNbE

Unspecified errors are a joy...

I've done my rounds on search engines and tried everything I can think of, but I just keep running into this wall. These VMs were replicating fine before all of this. 

Misc:
The Dothan server uses two volumes for Hyper-V. Hyper-V configuration files and small VHDs are stored on E:, which is SSD-based. The Dothan server VM uses a small VHD on E: for it's operating system, and it's smart paging file is parked there too.

Large VHDs and all Hyper-V Replica (inbound-replicated VMs) is stored on D:. The Dothan server VM uses a VHD stored on D: for data storage in its role as a file server. Both my Auburn VMs are stored on D: when they replicate to Dothan, which is exactly how they were before I made all these changes over the weekend.

I've rebooted both hypervisors and I've checked all the VSS writers. No errors there. I can create standard and production checkpoints for each VM, the two VMs in Auburn and the server VM in Dothan. 

If anybody can help point me in the right direction on this, I would greatly appreciate it, and I'd be happy to take you for a beer anytime you're in this part of the American south!

-MB

Hi All,

I have a simple question that Google nor Bing can definitively answer. I have a cluster with 3 storage devices, Cluster Volume 1, 2 and 3.  I wan't to remove Cluster Volume 1. There is no data on that volume, so not worried about retaining any data. If I remove the volume from the cluster, do Volumes 2 & 3 stay at  2 & 3, which I would assume is the proper behaviour. I just want to make sure that the system doesn't reshuffle the volume numbers and cause all my vm's to go offline.

Ok, so this is a 2 part question. Say I want to add another volume later, will that become Volume 1 or 4?

Thanks in advance.

Event IDs on B2

Event ID 16300 Cannot load a virtual machine configuration: Unspecified error (0x80004005). (Virtual machine ID A10F389C-C365-4829-A748-36EAA9009690)

Event ID 33686 Hyper-V failed to enable replication relationship on the Replica server: Unspecified error (0x80004005).

Event IDs on B1

Hyper-V failed to enable replication for virtual machine 'VMNAME: Unspecified error (0x80004005). (Virtual machine ID A10F389C-C365-4829-A748-36EAA9009690)

This only happens to some VMs, those that previously used Certificate based replication.

1. Domain A VMs are replicated to Domain B via certificate based replication.
2. Domain A servers are running Hyper-V Server 2012R2 or 2016.
3. VM version is 5.
4. VM is failed over to Domain B Hyper-V replica server B1 running WS2019 Datacenter host and started, no errors.
5. VM is replicated to a different WS2019 Datacenter host B2 in Domain B and is failed over.  It's still using certificate based replication.
6. Replication is removed on all hosts.
7. VM is deleted on but B2.
8. VM is shutdown and upgraded to version 9.  VM starts and works fine.
9. VM is deleted from B1.
10. Enable replication fails from B2 to B1 with errors above.
11. I can create new VMs on B2 and replicate them with or without certificate based replication without error.
12. I have searched and removed all files/folders with A10F389C-C365-4829-A748-36EAA9009690 in their name on B1.
13. Where is B1 still storing information about A10F389C-C365-4829-A748-36EAA9009690?

-=Chris

I'm writing a code for backup based on RCT.

I've found that a reference point should be created for the RCT-based incremental backup.

However, when I tried to create reference points, I failed in creation of .rct files.

I've tried to create a reference point using the CreateReferencePoint method of

the Msvm_VirtualSystemReferecenPointService class with the input parameter:

inParams["ReferencePointType"] = 1; // RCT based

But, it did not create .rct file. Instead, a .hrl(Hyper-V Replication Log) file was created.

I've tried the other parameters, such as 0 (Log base) and 2 (Not in the reference manual).

The results were "Error code 32773", which looks "Invalid Parameters."

Please kindly advise me for the troubleshooting.

Thank you in Advance.

Min-Joon Kim.

Hello,

Need a bit of help. Can someone tell me if  Microsoft Server 2019 Essentials comes with licencing for Hyper-V so you can have a physical instance of Windows Server 2019 Essentials installed with the same copy of Windows Server 2019 Essentials running as a VM?

Basically I have one physical server but wanted to be sure that if I buy Essentials 2019 it can be used as a host and a VM

server 2016 host, server 2016 VM

I created a Dynamic size virtual HDD of 200GB.

The actual file size is 200GB.

The virtual HDD is no where near that full.

Is there a cause for it to be full size or any way to make it smaller?

Thanks

Hi all I have a question I have an old server run windows 2012 Hyper-V  standalone that runs virtual machines 2012 and I want to transfer them to a new server run Windows server 2016 Hyper-V standalone  what is the right way to do it

Thank you

sofy

Hi community, 

after your authorization,

i m very happy to present my contribution to you, it is a free tool created by myself, to help everyone use Hyper-V on local or remote server, and encourage the people to use Hyper-V.

all your feedback is welcome,

this is the link :

https://gallery.technet.microsoft.com/Hyper-Virtual-Easy-Manager-6384c1c6

if anyone has any  suggestions or improvement, please feel free to give me the advice

Hi all.  I'm sure this is a simple thing but I'd rather ask now, here in 2017, than go with posts I've found from 2011 and such.  

I've got a 2008 R2 Hyper-V host, very simple setup, with a single VM also running 2008 R2.  Hyper-V Manager has one VM showing, and if I click on it, it shows NO snapshots.  Yet if I go into Settings for the VM in Hyper-V Manager it shows that it is using the AVHD file, which is located in the same folder as where the original VHD file is.  The VHD file is dated in 2014, the avhd file is current as of today.  Notably, the VHD file is about 280GB size, the avhd is about 140GB.  

So it seems at some point snapshots were in use, however Hyper-V Manager shows that is not the case if one views the Snapshots pane of Hyper-V Manager home screen, but in the VM Settings itself I see the avhd file is in use.  

Can I merge these somehow?  

Thank you.  

Hi,

I have a Windows 7 VM on which I would like to play and rip CDs. I defined the CD/DVD drive to point on the physical CD/DVD drive.

When I insert an audio CD, the VM detects the insertion but it is not able nor to play nor to rip files.

On VM I can correctly play MP3 and other media. Only physical audio CD cannot play.

Any suggestion on how to solve the problem?

Thank you.

Plo

So apparently this is an incredibly rare error since googling it produces no results in english other than one cryptic page. This is a clean server I am doing a clean image for. The host is up to date and I tried both creating a new VM from installation media and even trying to mount a blank server VM I've used for installs before. Both fail with the same exact error. I've disabled virtualization based security in group policy but it still shows as running in system info, even after a reboot, so I'm assuming this is something new that requires a special work around, although I can't find what I'm doing wrong. I just setup a bunch of servers for another client a few months ago and none of these problems presented themselves.

Hi,

I would just like to know if this would work. I have 2x on premise server (Windows Server 2012 r2) which is the source server configured as Failover Cluster, then my target server is a Windows Server 2019 which i plan to configure as the Hyper-V Replica server. Would that still work even if the source and target server have different OS version?

Thank you!

Hello Windows Experts,

Please let me know the new "physical processor" specification for it to support Hyper-V in Windows server 2016. I noticed that some of the servers are no more supporting Hyper-V in Windows server 2016. (Hyper-V used to work fine previously on the same servers until Windows Server 2012)

- Sajit

Types of Sentences

Hi,

I have a Windows 2016 standard server that I have installed Hyper-V on.

I have created a VM and before I can install Windows Server on the VM or if even just leave it to power on, the physical machine blue screens.

The Memory.dmp file give me the following info:

Microsoft (R) Windows Debugger Version 10.0.17763.1 X86

Copyright (c) Microsoft Corporation. All rights reserved.

Loading Dump File [C:\Windows\MEMORY.DMP]

Kernel Bitmap Dump File: Kernel address space is available, User address space may not be available.

Symbol search path is: srv*

Executable search path is:

Windows 10 Kernel Version 14393 MP (16 procs) Free x64

Product: LanManNt, suite: TerminalServer SingleUserTS

Built by: 14393.3383.amd64fre.rs1_release.191125-1816

Machine Name:

Kernel base = 0xfffff802`1f888000 PsLoadedModuleList = 0xfffff802`1fb8b020

Debug session time: Thu Feb 27 23:04:52.935 2020 (UTC + 0:00)

System Uptime: 0 days 0:10:45.421

Loading Kernel Symbols

...............................................................

................................................................

....................................

Loading User Symbols

PEB is paged out (Peb.Ldr = 0000000f`657bc018). Type ".hh dbgerr001" for details

Loading unloaded module list

.......

*******************************************************************************

*                                                                            *

*                       Bugcheck Analysis                                    *

*                                                                            *

*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 133, {1, 1e00, fffff8021fc2d540, 0}

*************************************************************************

***                                                                  ***

***                                                                  ***

***   Either you specified an unqualified symbol, or your debugger  ***

***   doesn't have full symbol information.  Unqualified symbol     ***

***   resolution is turned off by default. Please either specify a  ***

***   fully qualified symbol module!symbolname, or enable resolution ***

***   of unqualified symbols by typing ".symopt- 100". Note that    ***

***   enabling unqualified symbol resolution with network symbol    ***

***   server shares in the symbol path may cause the debugger to    ***

***   appear to hang for long periods of time when an incorrect     ***

***   symbol name is typed or the network symbol server is down.    ***

***                                                                  ***

***   For some commands to work properly, your symbol path          ***

***   must point to .pdb files that have full type information.     ***

***                                                                  ***

***   Certain .pdb files (such as the public OS symbols) do not     ***

***   contain the required information.  Contact the group that     ***

***   provided you with these symbols if you need this command to    ***

***   work.                                                         ***

***                                                                  ***

***   Type referenced: TickPeriods                                  ***

***                                                                  ***

*************************************************************************

Probably caused by : ntkrnlmp.exe ( nt!KeAccumulateTicks+42a )

Followup:    MachineOwner

---------

0: kd> !analyze -v

*******************************************************************************

*                                                                            *

*                       Bugcheck Analysis                                   *

*                                                                            *

*******************************************************************************

DPC_WATCHDOG_VIOLATION (133)

The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL

or above.

Arguments:

Arg1: 0000000000000001, The system cumulatively spent an extended period of time at

         DISPATCH_LEVEL or above. The offending component can usually be

         identified with a stack trace.

Arg2: 0000000000001e00, The watchdog period.

Arg3: fffff8021fc2d540, cast to nt!DPC_WATCHDOG_GLOBAL_TRIAGE_BLOCK, which contains

         additional information regarding the cumulative timeout

Arg4: 0000000000000000

Debugging Details:

------------------

*************************************************************************

***                                                                  ***

***                                                                  ***

***   Either you specified an unqualified symbol, or your debugger  ***

***   doesn't have full symbol information.  Unqualified symbol     ***

***   resolution is turned off by default. Please either specify a  ***

***   fully qualified symbol module!symbolname, or enable resolution ***

***   of unqualified symbols by typing ".symopt- 100". Note that    ***

***   enabling unqualified symbol resolution with network symbol    ***

***   server shares in the symbol path may cause the debugger to    ***

***   appear to hang for long periods of time when an incorrect     ***

***   symbol name is typed or the network symbol server is down.    ***

***                                                                  ***

***   For some commands to work properly, your symbol path          ***

***   must point to .pdb files that have full type information.     ***

***                                                                  ***

***   Certain .pdb files (such as the public OS symbols) do not     ***

***   contain the required information.  Contact the group that     ***

***   provided you with these symbols if you need this command to   ***

***   work.                                                         ***

***                                                                  ***

***   Type referenced: TickPeriods                                  ***

***                                                                  ***

*************************************************************************

KEY_VALUES_STRING: 1

STACKHASH_ANALYSIS: 1

TIMELINE_ANALYSIS: 1

DUMP_CLASS: 1

DUMP_QUALIFIER: 401

BUILD_VERSION_STRING: 14393.3383.amd64fre.rs1_release.191125-1816

SYSTEM_MANUFACTURER: HP

SYSTEM_PRODUCT_NAME: ProLiant DL360 Gen9

SYSTEM_SKU: 843374-425

BIOS_VENDOR: HP

BIOS_VERSION: P89

BIOS_DATE: 10/25/2017

BASEBOARD_MANUFACTURER: HP

BASEBOARD_PRODUCT: ProLiant DL360 Gen9

DUMP_TYPE: 1

BUGCHECK_P1: 1

BUGCHECK_P2: 1e00

BUGCHECK_P3: fffff8021fc2d540

BUGCHECK_P4: 0

DPC_TIMEOUT_TYPE: DPC_QUEUE_EXECUTION_TIMEOUT_EXCEEDED

CPU_COUNT: 10

CPU_MHZ: 832

CPU_VENDOR: GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 4f

CPU_STEPPING: 1

CPU_MICROCODE: 6,4f,1,0 (F,M,S,R) SIG: B00002C'00000000 (cache) B00002C'00000000 (init)

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

BUGCHECK_STR: 0x133

PROCESS_NAME: dwm.exe

CURRENT_IRQL: d

ANALYSIS_SESSION_HOST: Server2016

ANALYSIS_SESSION_TIME: 02-28-2020 10:33:02.0542

ANALYSIS_VERSION: 10.0.17763.1 x86fre

LAST_CONTROL_TRANSFER: from fffff8021f933e0a to fffff8021f9e4e00

STACK_TEXT: 

fffff802`21a1bd88 fffff802`1f933e0a : 00000000`00000133 00000000`00000001 00000000`00001e00 fffff802`1fc2d540 : nt!KeBugCheckEx

fffff802`21a1bd90 fffff802`1f931058 : 0000ce61`e90ef725 00000000`00000000 ffffd981`30b37918 fffff780`00000320 : nt!KeAccumulateTicks+0x42a

fffff802`21a1bdf0 fffff802`1f80f4e5 : fffff802`1f85b6b0 fffff802`1f85b6b0 00000000`00000001 00000000`00000000 : nt!KeClockInterruptNotify+0xb8

fffff802`21a1bf40 fffff802`1f8e6236 : ffff8080`05947350 ffffd981`2ed67280 ffffd981`2ed67288 fffff802`1f9e621a : hal!HalpTimerClockIpiRoutine+0x15

fffff802`21a1bf70 fffff802`1f9e65fa : ffffd981`30b37380 00000000`00000000 fffff080`ddba0e28 ffff8080`00000000 : nt!KiCallInterruptServiceRoutine+0x106

fffff802`21a1bfb0 fffff802`1f9e6ae7 : ffff8080`0570d228 00000000`058c3110 00000000`00000000 fffff802`1fa7750c : nt!KiInterruptSubDispatchNoLockNoEtw+0xea

ffffd981`30b37300 fffff802`1f94765e : 00000000`058c3110 00000000`00000000 00000000`00000000 fffff802`1fa77041 : nt!KiInterruptDispatchNoLockNoEtw+0x37

ffffd981`30b37490 fffff802`1f946197 : 00000000`00000001 00000000`001d01e0 00000000`00000080 fffff802`1f9105e3 : nt!MiPfnShareCountIsZero+0x42e

ffffd981`30b374e0 fffff802`1f91418d : 00000000`00000000 fffff080`ddba0ff8 ffffd981`30b37750 9c000001`c652d867 : nt!MiDeletePteRun+0x507

ffffd981`30b37650 fffff802`1f90bd57 : ffffc300`317d1880 ffffd981`30b37939 ffffc300`32789a60 fffff802`1f8ffd78 : nt!MiDeleteVirtualAddresses+0xd5d

ffffd981`30b37870 fffff802`1f8e5955 : 000001bb`7429ffff 000001bb`7429ffff 000001bb`73da0000 ffffc300`32789a60 : nt!MiDeleteVad+0x277

ffffd981`30b379a0 fffff802`1fcf98bd : 00000000`00000000 000001bb`73da0000 00000000`00000000 00000000`00000000 : nt!MiFreeVadRange+0x4d

ffffd981`30b379e0 fffff802`1f9f4903 : ffffc300`31e485c0 00000000`ffffffff 00000000`00000000 ffffc300`3233c960 : nt!NtFreeVirtualMemory+0x2dd

ffffd981`30b37b00 00007ffd`60d65e04 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13

0000000f`659fea28 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffd`60d65e04

THREAD_SHA1_HASH_MOD_FUNC: 8ff6605fc97e89cc1ae4e27ff955ac4a7c511c79

THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 08f97060e3daed93bce1aa5a5fd3880a672c6751

THREAD_SHA1_HASH_MOD: a46c1b556d92394c8d3f63eb407b2ed053afd34a

FOLLOWUP_IP:

nt!KeAccumulateTicks+42a

fffff802`1f933e0a cc             int    3

FAULT_INSTR_CODE: cccccccc

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: nt!KeAccumulateTicks+42a

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 5ddcba81

STACK_COMMAND: .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET: 42a

FAILURE_BUCKET_ID: 0x133_ISR_nt!KeAccumulateTicks

BUCKET_ID: 0x133_ISR_nt!KeAccumulateTicks

PRIMARY_PROBLEM_CLASS: 0x133_ISR_nt!KeAccumulateTicks

TARGET_TIME: 2020-02-27T23:04:52.000Z

OSBUILD: 14393

OSSERVICEPACK: 0

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK: 272

PRODUCT_TYPE: 2

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

OSEDITION: Windows 10 LanManNt TerminalServer SingleUserTS

OS_LOCALE: 

USER_LCID: 0

OSBUILD_TIMESTAMP: 2019-11-26 05:39:13

BUILDDATESTAMP_STR: 191125-1816

BUILDLAB_STR: rs1_release

BUILDOSVER_STR: 10.0.14393.3383.amd64fre.rs1_release.191125-1816

ANALYSIS_SESSION_ELAPSED_TIME: 1bf6

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:0x133_isr_nt!keaccumulateticks

FAILURE_ID_HASH: {65350307-c3b9-f4b5-8829-4d27e9ff9b06}

Followup:    MachineOwner

---------

Thanks