Guru Meditation -1607 (VERR_PGM_HANDLER_NOT_FOUND) (#19007)

Discussions about using Windows guests in VirtualBox.
caspertone
Posts: 54
Joined: 2. Apr 2014, 10:27

Guru Meditation -1607 (VERR_PGM_HANDLER_NOT_FOUND) (#19007)

Post by caspertone »


ModEdit; related ticket: #19007: VERR_PGM_HANDLER_NOT_FOUND
Hi,
Currently my host is W10 1903 with up to date patches, and VBox 6.12 and ext. pack.
Guest, W10 1903 with up to date patches, and GA 6.12 installed

Everytime I apply the monthly operating system patches, when the VM reboots, I get a guru meditation.
VM gets down. Rebooting the VM seems to solve the issue, but it is not smooth....

I got the following information from the log:
00:34:18.830243 VMMDev: Guest Log: VBoxMP::DriverEntry: VBox WDDM Driver for Windows 8+ version 6.0.12r133076, 64 bit; Built Sep  3 2019 10:51:36
00:34:18.830471 VMMDev: Guest Log: VBoxMP::DriverEntry: OsVersion(10, 0, 18362)
00:34:18.831016 VMMDev: Guest Log: VBoxMP::DriverEntry: WDDM: VGA configuration version 1
00:34:18.831122 VMMDev: Guest Log: VBoxMP::DriverEntry: WDDM: VGA configuration: 3D 1, hardware type 1
00:34:18.831243 VMMDev: Guest Log: VBoxMP::DriverEntry: WDDM: 3D is supported, hardware type 1
00:34:19.144123 HDA: Codec reset
00:34:19.144144 HDA: Reset
00:34:19.171225 HDA: Codec reset
00:34:19.171249 HDA: Reset
00:34:19.207374 xHCI: Hardware reset
00:34:19.207431 xHCI: root hub-attached device reset completed with VINF_SUCCESS
00:34:19.207452 xHCI: root hub-attached device reset completed with VINF_SUCCESS
00:34:19.226393 xHCI: USB Operational
00:34:20.222427 HDA: Codec reset
00:34:21.098337 NAT: Link up
00:34:30.971745 NAT: Guest address guess changed from 10.0.2.15 to 169.254.1.247 by gratuitous arp
00:34:31.955498 VMMDev: Guest Log: VBoxMP::vboxWddmPickResources: found the VBE card
00:34:31.955590 VMMDev: Guest Log: VBoxMP::DxgkDdiStartDevice: Handling complex topologies disabled
00:34:31.956216 VMMDev: Guest Log: VBoxMP::DxgkDdiStartDevice: using HGSMI
00:34:31.956369 2D is supported!
00:34:31.957141 VMMDev: Guest Log: VBoxMP::vboxWddmVModesAdd: WARNING! :resolution 1152x864 not accepted by the frontend
00:34:31.957623 VMMDev: Guest Log: VBoxMP::vboxWddmVModesAdd: WARNING! :resolution 1280x960 not accepted by the frontend
00:34:31.957809 VMMDev: Guest Log: VBoxMP::vboxWddmVModesAdd: WARNING! :resolution 1280x1024 not accepted by the frontend
00:34:31.957994 VMMDev: Guest Log: VBoxMP::vboxWddmVModesAdd: WARNING! :resolution 1400x1050 not accepted by the frontend
00:34:31.958268 VMMDev: Guest Log: VBoxMP::vboxWddmVModesAdd: WARNING! :resolution 1600x1200 not accepted by the frontend
00:34:31.958535 VMMDev: Guest Log: VBoxMP::vboxWddmVModesAdd: WARNING! :resolution 1920x1440 not accepted by the frontend
00:34:31.958955 VMMDev: Guest Log: VBoxMP::DxgkDdiStartDevice: WDDM: VRAM 0xe0000000/0x8000000, FIFO 0xfde00000/0x200000, IO 0xfff0/0x10
00:34:31.970163 VMMDev: Guest Log: VBoxMP::DxgkDdiQueryAdapterInfo: DXGKQAITYPE_QUERYSEGMENT3 treating as unsupported!
00:34:32.048816 Display::i_handleDisplayResize: uScreenId=0 pvVRAM=000000000ed70000 w=1366 h=768 bpp=32 cbLine=0x1558 flags=0x1 origin=0,0
00:34:32.302942 Changing the VM state from 'RUNNING' to 'GURU_MEDITATION'
00:34:32.302973 Console: Machine state changed to 'GuruMeditation'
00:34:32.303220 !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
00:34:32.303221 !!
00:34:32.303221 !!         VCPU1: Guru Meditation -1607 (VERR_PGM_HANDLER_NOT_FOUND)
00:34:32.304341 !!
00:34:32.304356 !!
00:34:32.304357 !! {mappings, <NULL>}
00:34:32.304358 !!
00:34:32.304397 
00:34:32.304397 The mappings are DISABLED.
00:34:32.304400 00000000fd800000 - 00000000febfffff  Hypervisor Memory Area
00:34:32.304404 00000000fec00000 - 00000000ffbfffff  Above 4GB Base RAM
Any hint?

Thanks in advance,
CT
Last edited by socratis on 21. Oct 2019, 09:48, edited 2 times in total.
Reason: Added ticket related information.
scottgus1
Site Moderator
Posts: 20965
Joined: 30. Dec 2009, 20:14
Primary OS: MS Windows 10
VBox Version: PUEL
Guest OSses: Windows, Linux

Re: VCPU1: Guru Meditation -1607 (VERR_PGM_HANDLER_NOT_FOUND)

Post by scottgus1 »

We usually need full a log, zipped and posted with the forum's Upload Attachment tabs.

You can also start troubleshooting your issue by googling the UNDERSCORE_SPACED_CAPITALIZED_WORDS in the error message, then add the site restrictor "site:forums.virtualbox.org", like this:

VERR_PGM_HANDLER_NOT_FOUND site:forums.virtualbox.org

Several recent results suggest that this error may happen when a guest is resumed after a save-state. Save-stated guests require a whole lot of everything on the host to remain as it was when the guest was save-stated. Some Windows updates can sufficiently alter the landscape such that a save-stated guest won't start.

The log with this guru meditation in it will tell how the guest was stopped last time. If the guest was in fact save-stated over the host update, then the solution is to be sure the guest is fully shut down from within the guest OS, not save-stated, before rebooting the host for updates, or shut down not save state all the time.
caspertone
Posts: 54
Joined: 2. Apr 2014, 10:27

Re: VCPU1: Guru Meditation -1607 (VERR_PGM_HANDLER_NOT_FOUND)

Post by caspertone »

@scottgus1

Thanks for the reply,

Note that I already searched with google and inside the forums, but to no avail to my actual issue. There are some threas about VERR_PGM_HANDLER_NOT_FOUND but issues and solutions seem not to be applicable. I already checked the use of screen driver as well as having enough memory for screen as well as for the machine.

The topic is not related to a saved stated, it just happens ALWAYS when after a monthly OS patch the VM is "udpated and rebooted".

log attached as per request.

Thanks in advance,
CT
Attachments
VBOX.zip
(83.57 KiB) Downloaded 18 times
scottgus1
Site Moderator
Posts: 20965
Joined: 30. Dec 2009, 20:14
Primary OS: MS Windows 10
VBox Version: PUEL
Guest OSses: Windows, Linux

Re: VCPU1: Guru Meditation -1607 (VERR_PGM_HANDLER_NOT_FOUND)

Post by scottgus1 »

About 15 lines from the beginning in the log there's this:
00:00:05.654722 Console: Machine state changed to 'Restoring'
You might recognize this line from your googling. The 'Restoring' means the guest was save-stated when it was shut down before. The line would say 'Starting' if the guest were not save-stated. FWIW, if a guest is save-stated the guest window appears to pop right in, already booted up and possibly logged in and running programs, not going through a boot process.

Therefore the "save-state" part of the googled solutions you found appears to be the precise reason why you're getting crashes.

Find out why your guest is being save-stated and prevent it from being so when the host reboots for updates.
caspertone
Posts: 54
Joined: 2. Apr 2014, 10:27

Re: VCPU1: Guru Meditation -1607 (VERR_PGM_HANDLER_NOT_FOUND)

Post by caspertone »

@scottgus1

Thanks for the response.
Perhaps you can help me to understand it, cause until I understand it I will be unable to solve my issue.

Perhaps the VM was not cold booted, but was run from saved stated. But if I restart/shutdown the operating system withing the VM, that was either cold booted either started from a saved state, the boot is normal, no guru meditation.

Do you mean that the guru meditation happens when I start a VM from a saved state and then after the monthly patch, then and only then, the reboot is somehow "dirty" because the VM was not cold booted? If so, the only solution is to shutdown the VM and cold boot before patching?

Might not be a bug, but looks like one to me...

Thanks
scottgus1
Site Moderator
Posts: 20965
Joined: 30. Dec 2009, 20:14
Primary OS: MS Windows 10
VBox Version: PUEL
Guest OSses: Windows, Linux

Re: VCPU1: Guru Meditation -1607 (VERR_PGM_HANDLER_NOT_FOUND)

Post by scottgus1 »

caspertone wrote:the guru meditation happens when I start a VM from a saved state and then after the monthly patch, then and only then, the reboot is somehow "dirty"
This appears to be the case. Windows 10 updates are not what Windows updates used to be. It could be a bug. Try looking through the Bugtracker and Windows Guests subforums, as well as links you found while Googling, to see if anyone posted a Bugtracker ticket. Post your info & log on that ticket or start a new ticket.
caspertone
Posts: 54
Joined: 2. Apr 2014, 10:27

Re: VCPU1: Guru Meditation -1607 (VERR_PGM_HANDLER_NOT_FOUND)

Post by caspertone »

Thanks again!
Seems someone else got ahead of me - https://www.virtualbox.org/ticket/19007 - Already reported also my case.

So, I vanish from this thread... I look forward to the bug solution.

CT
Last edited by socratis on 16. Oct 2019, 05:58, edited 1 time in total.
Reason: Removed unnecessary verbatim quote of the whole previous message.
socratis
Site Moderator
Posts: 27330
Joined: 22. Oct 2010, 11:03
Primary OS: Mac OS X other
VBox Version: PUEL
Guest OSses: Win(*>98), Linux*, OSX>10.5
Location: Greece

Re: VCPU1: Guru Meditation -1607 (VERR_PGM_HANDLER_NOT_FOUND)

Post by socratis »

The log of 'caspertone' wrote:
00:00:05.440796 VirtualBox VM 6.0.12 r133076 win.amd64 (Sep  3 2019 10:36:06) release log
00:00:05.654722 Console: Machine state changed to 'Restoring'
00:00:06.781521 Changing the VM state from 'CREATED' to 'LOADING'
00:00:06.782103 SSM: File header: Format 2.0, VirtualBox Version 6.0.12 r133076, 64-bit host, cbGCPhys=8, cbGCPtr=8
00:34:32.302942 Changing the VM state from 'RUNNING' to 'GURU_MEDITATION'
00:34:32.302973 Console: Machine state changed to 'GuruMeditation'
00:34:32.303220 !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
00:34:32.303221 !!
00:34:32.303221 !!         VCPU1: Guru Meditation -1607 (VERR_PGM_HANDLER_NOT_FOUND)
00:34:32.304341 !!
00:34:32.304356 !!
00:34:32.304357 !! {mappings, <NULL>}
00:34:32.304358 !!
00:34:32.304397 
00:34:32.304397 The mappings are DISABLED.
00:34:32.304400 00000000fd800000 - 00000000febfffff  Hypervisor Memory Area
00:34:32.304404 00000000fec00000 - 00000000ffbfffff  Above 4GB Base RAM
I'm starting to see more and more VERR_PGM_HANDLER_NOT_FOUND errors. I'm going to try and get the gist out of them. Since your thread is the oldest (I think), I'm going to use it as the base. Don't be surprised if there's a lot of merging in the next couple of days.

Tying also the thread to the ticket, in the first post and the title.
Do NOT send me Personal Messages (PMs) for troubleshooting, they are simply deleted.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
caspertone
Posts: 54
Joined: 2. Apr 2014, 10:27

Re: Guru Meditation -1607 (VERR_PGM_HANDLER_NOT_FOUND) (#19007)

Post by caspertone »

Last edited by caspertone on 4. Nov 2019, 23:33, edited 1 time in total.
socratis
Site Moderator
Posts: 27330
Joined: 22. Oct 2010, 11:03
Primary OS: Mac OS X other
VBox Version: PUEL
Guest OSses: Win(*>98), Linux*, OSX>10.5
Location: Greece

Re: Guru Meditation -1607 (VERR_PGM_HANDLER_NOT_FOUND) (#19007)

Post by socratis »

caspertone,
We are. No need to post in every thread, I'm trying to tie them all up. If you want to help, start analyzing the logs like 'fth0' and I have been doing.
Do NOT send me Personal Messages (PMs) for troubleshooting, they are simply deleted.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
caspertone
Posts: 54
Joined: 2. Apr 2014, 10:27

Re: Guru Meditation -1607 (VERR_PGM_HANDLER_NOT_FOUND) (#19007)

Post by caspertone »

Thanks.
I already did what I can...
Read the logs as to where I could, testing, open this thread (OP), publish the log, opening the bug.
Now looks that it is getting more traction...
Last edited by caspertone on 4. Nov 2019, 23:33, edited 1 time in total.
scottgus1
Site Moderator
Posts: 20965
Joined: 30. Dec 2009, 20:14
Primary OS: MS Windows 10
VBox Version: PUEL
Guest OSses: Windows, Linux

Re: Guru Meditation -1607 (VERR_PGM_HANDLER_NOT_FOUND) (#19007)

Post by scottgus1 »

caspertone wrote:finally
caspertone wrote:take seriously
Might want to lay off expressions like these. Frustrating the folks trying to help you by implying they're slacking won't help you....
caspertone
Posts: 54
Joined: 2. Apr 2014, 10:27

Re: Guru Meditation -1607 (VERR_PGM_HANDLER_NOT_FOUND) (#19007)

Post by caspertone »

Reworded my comments to avoid any quarrel.
In any case, I felt my information not being taken (seriously expression not being able to translate to english) as helpers patronized me somewhat and not embracing too enthusiastically the possibility of a bug...
Always gratitude for help either.
CT
scottgus1
Site Moderator
Posts: 20965
Joined: 30. Dec 2009, 20:14
Primary OS: MS Windows 10
VBox Version: PUEL
Guest OSses: Windows, Linux

Re: Guru Meditation -1607 (VERR_PGM_HANDLER_NOT_FOUND) (#19007)

Post by scottgus1 »

caspertone wrote:not being able to translate to english
Ah, ok, you're not a native English speaker. You sound really good at it, though! 8)

Soon as the developers work this out they'll get a fix in. Meanwhile, the workaround seems to be to not save-state your VMs.
caspertone
Posts: 54
Joined: 2. Apr 2014, 10:27

Re: Guru Meditation -1607 (VERR_PGM_HANDLER_NOT_FOUND) (#19007)

Post by caspertone »

My intention has never been to offend anyone but I surely wished to point that I felt that my pointing to a bug was somehow dismissed like a children crying. And I felt that the "community" was just dragging their feet in taking this point as a reality. What I felt was I was patronized to follow the standard steps to correct a misconfiguration, not feeling that the counterpart could imagine that it was perhaps a real bug - even when I had explained that I had already tried the standard response steps...
In any case, I understand that contribution is voluntary and that there is no obligation to furnish help. But sometimes I feel that longstanding members of the community seem to be tired to answer to non documented users and from time to time the sound condescending.
Remember my english is not native so my words might sound very strong to native speakers while I really do not intend to cause distress...
CT
Post Reply