VERR_SUPDRV_TSC_DELTA_MEASUREMENT_FAILED Guru Meditation

[Entranced3]

I'm using VirtualBox 5 on a Windows 7 Ultimate x64 host with the extension pack, with a Windows 10 x64 Guest + Guest Additions installed, but I keep on getting the machine onto Guru Meditation since the first build of VirtualBox 5 Alpha. Tried new machines, but still at installing them it would go into Guru Meditation...

Guru Meditation -3743 (VERR_SUPDRV_TSC_DELTA_MEASUREMENT_FAILED)

Specs:

CPU - AMD FX8350
RAM - 16gb

Well... sometimes I can get into the machine, but it will go to a black screen in a while and I need to force shutdown it..

Any ideas why this is happening?...

[noteirak]

Never saw this error before, so that's a new one for me, and it seems new in 5.0
We'll need a vbox dev on this one!

[Perryg]

The error could be due to a few reasons but it has to do with TSC so I am putting my money with the CPU and in particular the new Paravirtualization feature.

But I do see some issues that I would address first. A) you are assigning all the cores to the guest and this can cause issues, and B) you are using EFI for the Windows 10 guest. Not necessary and even though it should work this is a new build of VirtualBox ( could have issues ) and a Windows build that is not fully supported yet.

[Entranced3]

The error could be due to a few reasons but it has to do with TSC so I am putting my money with the CPU and in particular the new Paravirtualization feature.

But I do see some issues that I would address first. A) you are assigning all the cores to the guest and this can cause issues, and B) you are using EFI for the Windows 10 guest. Not necessary and even though it should work this is a new build of VirtualBox ( could have issues ) and a Windows build that is not fully supported yet.

Well, I do thought about the same, but still with one core it shutsdown to the error; the EFI one is the last one to verify... When I'm on the mood I'll try to reinstall without EFI.

[Perryg]

Easiest thing to try first is the Paravirtual settings in the guest settings. Set it to legacy first and then disabled. See if either works to resolve the issue and then report the results here and/or bugtracker

[loukingjr]

FWIW, I have Windows 10 installed as a guest on OSX, Linux and Windows 8.1 hosts. No issues to speak of. None of my installs have EFI enabled.

[Ramshankar]

The problem is here:

Code: Select all

00:00:01.634241 TM: GIP - u32Mode=3 (Invariant) u32UpdateHz=100 u32UpdateIntervalNS=10000000 enmUseTscDelta=4 (Not Zero) fGetGipCpu=0x1 cCpus=8
00:00:01.634269 TM: GIP - u64CpuHz=3 666 171 728 (0xda855750)  SUPGetCpuHzFromGip => 3 666 171 728
00:00:01.634276 TM: GIP - CPU: iCpuSet=0x0 idCpu=0x0 idApic=0x0 iGipCpu=0x0 i64TSCDelta=0 enmState=3 u64CpuHz=3666171728(*) cErrors=0
00:00:01.634283 TM: GIP - CPU: iCpuSet=0x1 idCpu=0x1 idApic=0x1 iGipCpu=0x4 i64TSCDelta=9223372036854775807 enmState=3 u64CpuHz=3666130502(*) cErrors=0
00:00:01.634289 TM: GIP - CPU: iCpuSet=0x2 idCpu=0x2 idApic=0x2 iGipCpu=0x1 i64TSCDelta=719358 enmState=3 u64CpuHz=3411815081(*) cErrors=0
00:00:01.634295 TM: GIP - CPU: iCpuSet=0x3 idCpu=0x3 idApic=0x3 iGipCpu=0x3 i64TSCDelta=988620 enmState=3 u64CpuHz=3665955554(*) cErrors=0
00:00:01.634301 TM: GIP - CPU: iCpuSet=0x4 idCpu=0x4 idApic=0x4 iGipCpu=0x2 i64TSCDelta=1518669 enmState=3 u64CpuHz=3668361470(*) cErrors=0
00:00:01.634307 TM: GIP - CPU: iCpuSet=0x5 idCpu=0x5 idApic=0x5 iGipCpu=0x7 i64TSCDelta=1932423 enmState=3 u64CpuHz=3666158820(*) cErrors=0
00:00:01.634313 TM: GIP - CPU: iCpuSet=0x6 idCpu=0x6 idApic=0x6 iGipCpu=0x6 i64TSCDelta=2223111 enmState=3 u64CpuHz=3666162171(*) cErrors=0
00:00:01.634319 TM: GIP - CPU: iCpuSet=0x7 idCpu=0x7 idApic=0x7 iGipCpu=0x5 i64TSCDelta=2730319 enmState=3 u64CpuHz=3666155800(*) cErrors=0

We have code in 5.0 to measure the TSC delta between CPUs and for some reason the value for one them isn't computed properry (9223372036854775807 is INT64_MAX which is an 'invalid' value). Unfortunately, I don't yet know how this can happen but needless to say the code is rather complicated.

[Entranced3]

I completely uninstalled VirtualBox and was goin to reinstall to see if it would solve, maybe some config in a folder or whatever, but seen that Microsoft does not provide more Insiders builds, sadly, I can't test, so, thanks for all the answers.

[Entranced3]

Was able to get the 10240 build of Windows 10, with the latest VirtualBox and everything, still the same, tried changing the Paravirtualization settings but still the same, I tried everything, I think there isn't much to do sadly...

[Hortnon]

I also am having this issue, also with an FX-8350 processor, I've attached the vbox log

Edit:

All VM's now exhibit this behavior, and they didn't yesterday. I have Windows 8.1 host, and Linux, Windows 7, and Windows 10 as guests. They don't get to loading the OS so I doubt the guest OS makes a difference.

[Ramshankar]

This is a bug in the support driver (vboxdrv) and simply loading VMs or trying different guest OS is of no use. Reloading the driver (vboxdrv) might be worth trying.

[Hortnon]

How is that done? Reinstalling?

[Entranced3]

Would like to know too

[Zenok]

Same problem here everyday

How is that done? Reinstalling?

No. I reinstalled 10 times

[Ramshankar]

Could you please try installing this test build and see if it fixes the problem?

The link will expire in ~14 days automatically;
https://www.virtualbox.org/download/tes ... 22-Win.exe

We'd appreciate if you could please upload VBox.log from this build even if it happens to fix your problem. Would help us verify if things are truly fixed.