- #BCMWL63 PAGE FAULT INSTALL#
- #BCMWL63 PAGE FAULT PRO#
- #BCMWL63 PAGE FAULT PC#
- #BCMWL63 PAGE FAULT FREE#
I've tried changing the boot sequence in the BIOS, to point once again to the original MBR 960 drive, where non-EFI Boot Manager and Win7 and a previously installed and working Macrium Reflect Recovery are on the Boot Menu. So again, it's seemingly not related to the version of Reflect. Same failure on the Z170 machine and same works perfectly on all other machines. I've tried older versions of Macrium Reflect (as opposed to the current ). And no doubt the same explantion applies to the identical symptom when just booting to Recovery via Boot Manager. So it's not the USB rescue media itself which is at fault, but rather something odd about the setup on the Z170 machine itself which is causing this. And yet this very same USB rescue media works perfectly in my other Skylake desktop machine (only running Win7, but with its NVMe boot drive formatted GPT) as well as a Skylake laptop. Furthermore, the exact same result occurs when I try to boot with freshly created standalone bootable USB rescue media. It's 100% a failure with no usability, and I'm force to hard re-boot with the POWER button. but with no mouse or keyboard control, and no disk drives shown (not NVMe, not SATA, not USB). However when I boot to that Macrium Reflect Recovery item it seems to go through the normal WinPE loading process followed by some additional drivers, and then the program window appears. a third item on the EFI Boot Manager menu, for EFI Boot Manager on the 850). I then went to Macrium Reflect Home "Other tasks", create rescue media, to add Macrium Reflect Recovery to the boot menu (i.e. So now I can boot to either Win10 (by default) or Win7.
![bcmwl63 page fault bcmwl63 page fault](https://1.bp.blogspot.com/-1D4uXjYN_fw/YAZsmyfp6WI/AAAAAAAAGQE/EilEgRqq3bIG4zWsENqu2hmnJ6j-GOzMgCLcBGAsYHQ/s640/Fix%2Bbcmwl63a.sys%2B2.jpg)
#BCMWL63 PAGE FAULT PRO#
And I also changed the boot device sequence in the BIOS to load from "Boot Manager (EFI) on the 850", instead of "960 Pro (non-EFI)". I then manually added a second boot item to this second EFI Boot Manager menu on the 850, namely Win7 over on my MBR 960 drive. Everything then went fine, and I ended up with a second EFI-enabled Boot Manager partition on the 850, along with the expected WinRE partition and the true Win10 C-partition.
#BCMWL63 PAGE FAULT FREE#
To solve that issue, I carved out 150GB on my 1TB Samsung 850 Pro SATA3 SSD which was partitioned GPT, and pointed the Win10 installer to that free space.
#BCMWL63 PAGE FAULT INSTALL#
It said "you have a UEFI machine, so you must install Win10 go a GPT drive". The problem is that when I tried to add Win10 to free space on that non-MBR drive, the Win10 installer wouldn't let me. I never thought I'd put Win10 on this machine (which was a Win7 HTPC, running WMC) so I just casually made the brand new 960 MBR when I did the Win7 install. Win7 (and non-EFI Boot Manager) is on a 512GB Samsung 960 Pro NVMe SSD, unfortunately partitioned MBR.
![bcmwl63 page fault bcmwl63 page fault](https://i.ytimg.com/vi/SWiOTTxxZuk/maxresdefault.jpg)
So it's something about either the BIOS setup or the fact that I just this past weekend installed Win10 as a second bootable Windows (to dual-boot with Win7 which had been the only Windows on this machine since it was built in January 2017). I can use the very same USB rescue media on other PCs, and it works perfectly.
![bcmwl63 page fault bcmwl63 page fault](https://www.wintips.org/wp-content/uploads/2015/05/image_thumb4.png)
#BCMWL63 PAGE FAULT PC#
This problem is 100% unique to my homebuilt desktop PC based on ASUS Z170-Deluxe motherboard. Also, no external USB backup drive is shown, so even if I had mouse/keyboard there would be nothing to navigate to in order to select it and then "restore image". "rescue"), either from Windows Boot Manager or from standalone bootable USB rescue media, everything seems to load fine except that when it's finished and the program window is displayed I have no USB mouse or USB keyboard. For some reason when I run Macrium Reflect Recovery (i.e. I honestly don't know what happened here, but my guess is that it just happened yesterday.