Newly Installed NTLite causes BSOD on Launch (KVM)

I have windows on a KVM VM on my proxmox box and when I went to launch the app, my vm crashed and I don't understand why.

Can we not use this app in VMs? Windows doesn't work so well on my desktop "out of the box" so I was hoping to build a image that worked better for it in a VM first. My desktop primarily runs Linux Mint.

The app is the latest from the website, I tried both stable and beta.
 

Attachments

  • Screenshot_2020-09-22 QEMU (win10) - noVNC.png
    Screenshot_2020-09-22 QEMU (win10) - noVNC.png
    159.9 KB
  • BlueScreenView_tEqriNeQlu.png
    BlueScreenView_tEqriNeQlu.png
    56.5 KB
Hi,

my first reaction is no way, but I did see something similar on one of my web servers back in the day, using Server 2008R2 (Windows 8.1 base) in a remote VM, potentially KVM.
Is that maybe the same version of Windows you're using?

Haven't had the time to debug it, assumed it's some reg tweak I set as it was heavily tweaked for remote/vm optimizations.
Other than that never saw any issues for years running it on a VM or a remote server.

That said, there are some weird timestamps in the second screenshot of your files below, going far into the future.
Try updating KVM if not the latest, the OS under it, or if nothing of this helps, please PM or email me that dump file just to give it a glance without any guarantees.

Thanks.
 
I updated my host, proxmox, to the latest. I have version 5.1.0 of qemu for my kvm. My vm is Win10 Pro 2004.
I just did another test and it bluescreened as soon as I launched ntlite. I don't know what the timestamps are weird in the dump file.
 

Attachments

  • 100620-11828-01.dmp
    776.8 KB
Thanks for the dump file.

In it not much, but the error code did point me to this. Seems like a few games have the same issue with KVM.
If the configuration change looks legit, please try the proposed change to the KVM on that topic and let me know if it helped.

If not, is there any %temp%\ntlite.log file with content in it to see if the tool started to its base logic?
 
hmm. I did that change to the KVM and it worked. IDK why it works but it does. I do pass the host type for the cpu to the vm in an effort to help it perform as fast as it can with the resources I give it.

there was never a ntlite.log file before it'd bsod. there is one now. no errors in it.
 

Protecting access to MSRs​

In order to provide a robust security platform, MSRs must be protected from misuse from malicious kernel mode code. To enforce this, the hypervisor monitors and controls access to all MSRs. The hypervisor maintains a list of known MSR indices, and will only allow kernel mode code to access MSRs, or specific bits within MSRs, which are known to be reasonable and deemed safe. The hypervisor will block access to any MSR which is unknown to the hypervisor, or any MSR which is known through its published definition to represent a security risk. In some cases, partial access may be allowed.

When the hypervisor has blocked access to an MSR, it will log an event to the Windows System log in Event Viewer, specifying details of the attempted access.

Given the vast number of functions controlled by MSRs, it is not possible to predict the side effects of preventing MSR access to the software that initiated it. Well-written software should handle errors and failure cases gracefully, however, this is not always the case.

https://learn.microsoft.com/en-us/w...esource-protections#protecting-access-to-msrs


Here is the log that is showing the MSR read accesses 0x1c9 , 0x680 & 0x6c0 that are causing issues:

Code:
[ 3788.322347] kvm_msr_ignored_check: 14 callbacks suppressed
[ 3788.322348] kvm [11861]: ignored rdmsr: 0x1c9 data 0x0
[ 3788.322425] kvm [11861]: ignored rdmsr: 0x680 data 0x0
[ 3788.322459] kvm [11861]: ignored rdmsr: 0x6c0 data 0x0
[ 3788.322511] kvm [11861]: vcpu0, guest rIP: 0xfffff80039bfa652 vmx_set_msr: BTF|LBR in IA32_DEBUGCTLMSR 0x1, nop
[ 3788.322572] kvm [11861]: ignored rdmsr: 0x1c9 data 0x0
[ 3788.322617] kvm [11861]: ignored rdmsr: 0x680 data 0x0
[ 3788.322649] kvm [11861]: ignored rdmsr: 0x6c0 data 0x0
[ 3788.322694] kvm [11861]: vcpu0, guest rIP: 0xfffff80039bfa652 vmx_set_msr: BTF|LBR in IA32_DEBUGCTLMSR 0x1, nop
[ 3788.322770] kvm [11861]: ignored rdmsr: 0x1c9 data 0x0
[ 3788.322801] kvm [11861]: ignored rdmsr: 0x680 data 0x0
[ 3788.322833] kvm [11861]: ignored rdmsr: 0x6c0 data 0x0
[ 3788.322938] kvm [11861]: vcpu0, guest rIP: 0xfffff80039bfa652 vmx_set_msr: BTF|LBR in IA32_DEBUGCTLMSR 0x1, nop
[ 3788.322992] kvm [11861]: ignored rdmsr: 0x1c9 data 0x0
[ 3788.323034] kvm [11861]: vcpu0, guest rIP: 0xfffff80039bfa652 vmx_set_msr: BTF|LBR in IA32_DEBUGCTLMSR 0x1, nop
[ 3788.323093] kvm [11861]: vcpu0, guest rIP: 0xfffff80039bfa652 vmx_set_msr: BTF|LBR in IA32_DEBUGCTLMSR 0x1, nop
[ 3788.323156] kvm [11861]: vcpu0, guest rIP: 0xfffff80039bfa652 vmx_set_msr: BTF|LBR in IA32_DEBUGCTLMSR 0x1, nop
[ 3788.323323] kvm [11861]: vcpu0, guest rIP: 0xfffff80039bfa652 vmx_set_msr: BTF|LBR in IA32_DEBUGCTLMSR 0x1, nop
 
Last edited:
Back
Top