| 5 | | Replying to [ticket:19326 come_raczy]: |
| 6 | | > Host Operating system is newly imaged Windows 10. |
| 7 | | > |
| 8 | | > To reproduce: |
| 9 | | > |
| 10 | | > * download and install VirtualBox 6.1.4 with all defaults |
| 11 | | > * start the VirtualBox Manager |
| 12 | | > * plug the HP Univeral G2 into the laptop |
| 13 | | > |
| 14 | | > This will crash the Windows 10 host with a Blue Screen Of Death: "PNP DETECTED FATAL ERROR". |
| 15 | | > |
| 16 | | > The problem happens only when docking. |
| 17 | | > Operations while undocked are fine. |
| 18 | | > Operations while docked are fine. |
| 19 | | > Undocking works fine. |
| 20 | | > |
| 21 | | > There isn't any VM involved (therefore no VM log). This is only from having the VirtualBox Manager started. |
| 22 | | > |
| 23 | | > This is specific to versions 6.1.x. I have checked with 6.1.0, 6.1.2 and 6.1.4. I have tried installing VirtualBox both docked and undocked. I have also installed as an Administrator. The BSOD happened in all cases. |
| 24 | | > |
| 25 | | > The problem does not happen with 6.0.x. I am currently using 6.0.16 without any problems. |
| 26 | | > |
| 27 | | > This has been verified on two different HP Zbook 15u G5 (i7-8650u - 32GB RAM) and one HP EliteBook 840 G5. I tried both with the factory BIOS and the latest available BIOS (Jan 17 2020). It has also been verified on two different universal docks G2 - again, both with the factory firmware and with the latest available firmware. |
| 28 | | > |
| 29 | | > I am attaching one of the VBoxSVC log file right agter undocking and docking. The last 3 lines of the log files were produced while undocking. No additional logging was produced when docking. |
| | 5 | Edit : more info ; back to VB 6.0.22, works perfectly. |
| | 6 | |
| | 7 | '''On Sun 28/06/2020 18:53:13 your computer crashed or a problem was reported'''[[BR]] |
| | 8 | crash dump file: C:\WINDOWS\Minidump\062820-12078-01.dmp[[BR]] |
| | 9 | This was probably caused by the following module: ntoskrnl.exe (nt+0x1C23A0)[[BR]] |
| | 10 | Bugcheck code: 0xCA (0x2, 0xFFFF9489C6EE1B80, 0x0, 0x0)[[BR]] |
| | 11 | Error: PNP_DETECTED_FATAL_ERROR[[BR]] |
| | 12 | file path: C:\WINDOWS\system32\ntoskrnl.exe[[BR]] |
| | 13 | product: Microsoft® Windows® Operating System[[BR]] |
| | 14 | company: Microsoft Corporation[[BR]] |
| | 15 | description: NT Kernel & System[[BR]] |
| | 16 | Bug check description: This indicates that the Plug and Play Manager encountered a severe error, probably as a result of a problematic Plug and Play driver.[[BR]] |
| | 17 | The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time. |
| | 18 | |
| | 19 | |
| | 20 | |
| | 21 | '''On Sun 28/06/2020 18:53:13 your computer crashed or a problem was reported'''[[BR]] |
| | 22 | crash dump file: C:\WINDOWS\MEMORY.DMP[[BR]] |
| | 23 | This was probably caused by the following module: vboxusbmon.sys (VBoxUSBMon+0x2A8F)[[BR]] |
| | 24 | Bugcheck code: 0xCA (0x2, 0xFFFF9489C6EE1B80, 0x0, 0x0)[[BR]] |
| | 25 | Error: PNP_DETECTED_FATAL_ERROR[[BR]] |
| | 26 | file path: C:\WINDOWS\system32\drivers\vboxusbmon.sys[[BR]] |
| | 27 | product: Oracle VM VirtualBox[[BR]] |
| | 28 | company: Oracle Corporation[[BR]] |
| | 29 | description: VirtualBox USB Monitor Driver[[BR]] |
| | 30 | Bug check description: This indicates that the Plug and Play Manager encountered a severe error, probably as a result of a problematic Plug and Play driver.[[BR]] |
| | 31 | A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: vboxusbmon.sys (VirtualBox USB Monitor Driver, Oracle Corporation).[[BR]] |
| | 32 | Google query: vboxusbmon.sys Oracle Corporation PNP_DETECTED_FATAL_ERROR |
