![]() ![]() ![]() ![]() (Dell Inc -> Dell Inc.) C:\Program Files\Dell\DellDataVault\DDVRulesProcessor.exe (Dell Inc -> Dell Inc.) C:\Program Files\Dell\DellDataVault\DDVDataCollector.exe (Dell Inc -> Dell Inc.) C:\Program Files\Dell\DellDataVault\DDVCollectorSvcApi.exe (Dell Inc -> ) C:\Program Files (x86)\Dell Digital Delivery Services\Dell.D3.WinSvc.exe (Atheros Communications, Inc.) C:\Program Files (x86)\Jumpstart\jswpbapi.exe (Apowersoft Ltd -> Apowersoft) C:\Program Files (x86)\Apowersoft\Apowersoft Screen Recorder Pro 2\Apowersoft Screen Recorder Pro 2.exe (Adobe Systems Incorporated -> Adobe Systems Incorporated) C:\Program Files (x86)\Common Files\Adobe\OOBE\PDApp\IPC\AdobeIPCBroker.exe (Adobe Systems Incorporated -> Adobe Systems Incorporated) C:\Program Files (x86)\Common Files\Adobe\Adobe Desktop Common\HEX\Adobe CEF Helper.exe (Adobe Systems Incorporated -> Adobe Systems Incorporated) C:\Program Files (x86)\Common Files\Adobe\Adobe Desktop Common\ElevationManager\AdobeUpdateService.exe (Adobe Systems Incorporated -> Adobe Systems Incorporated) C:\Program Files (x86)\Adobe\Adobe Creative Cloud\ACC\Creative Cloud.exe > Adobe Systems, Incorporated) C:\Program Files (x86)\Common Files\Adobe\AdobeGCClient\AGSService.exe > Adobe Systems, Incorporated) C:\Program Files (x86)\Common Files\Adobe\AdobeGCClient\AGMService.exe (Adlice -> ) C:\Program Files\RogueKiller\RogueKiller64.exe () C:\Program Files (x86)\Clipdiary\Clipdiary.exe ![]() (If an entry is included in the fixlist, the process will be closed. Platform: Windows 10 Pro Version 1809 17763.678 (X64) Language: English (United States) Loaded Profiles: reznov (Available Profiles: reznov) Ran by reznov (administrator) on DESKTOP-4F34DJR (Dell Inc. Gotcha! Since the Ring-0 address was not revealed, I cannot guess the physical or virtual hardware component involved (with the exception that it's handled by the PDM), so this seems to be a dead end at the moment.Scan result of Farbar Recovery Scan Tool (FRST) (圆4) Version: 25-08-2019 From the VirtualBox source code, I can make the educated guess that the order came from pdmCritSectEnter(), where MMHyperCCToR3() was called to obtain the Ring-3 address from a Ring-0 address, and it has a developer's prophecy: "You'll be damned if this is not in the HMA! ". In VMMR3HmRunGC(), the previous call to SUPR3CallVMMR0Fast() prepared the call to PDMR3CritSectEnterEx(), but the Ring-3 address was 0 and finally led to the crash. The EMT thread crashed with the following call stack: vmR3EmulationThreadWithId() > EMR3ExecuteVM() > VMMR3HmRunGC() > vmmR3ServiceCallRing3Request() > PDMR3CritSectEnterEx() > PDMCritSectEnterDebug(). Some bits and pieces in case a VirtualBox developer reads this: I've analyzed the crash information from the latest VirtualBox 6.1.16 log files, but AFAICS, they unfortunately do not reveal the real source of the problem. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |