![]() This was probably caused by the following module: hcmon.sys (hcmon+0x2DF1)īugcheck code: 0xA (0x18, 0x2, 0x0, 0xFFFFF801A241C680)įile path: C:\WINDOWS\system32\drivers\hcmon.sysīug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above. ![]() On Sat 11:56:01 AM GMT your computer crashed If there's any additional information I can provide, please let me know and I would be happy to do that. I used WhoCrashed to analyze the dump files and it indicated that the VMWare USB monitor (hcmon.sys) might be causing the issue (see below).Ĭan anyone offer any pointers of things that I might try to eliminate the BSOD? I'm using VMWare Workstation 12.5.2 build-4638234 if it makes any difference. I also tried VirtualBox for a while and the same issue doesn't occur. I've repeated the process of uninstalling VMWare and using the system for a while (with numerous instances of it going into sleep mode) before reinstalling VMWare and the behaviour is the same ever time - shortly after reinstalling VMWare, the problem starts to reoccur. I suspect that VMWare is causing the issue because it doesn't occur once VMWare Workstation has been uninstalled. The BSOD occurs during the resume process after the system has been put into sleep mode. I'm having a problem with VMWare Workstation Pro causing a blue screen of death on a Windows 10 圆4 host.
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |