qmgoqwe Posted October 11, 2020 Share Posted October 11, 2020 (edited) I have installed MacOS and Windows on the following hardware: AMD Ryzen 7 3700X MSI B450M Mortar Max Sapphire Radeon Pulse RX 5600 XT 6G Samsung 860 QVO, 1 TB SSD (PciRoot(0x0)/Pci(0x1,0x3)/Pci(0x0,0x1)/Sata(0x5,0xFFFF,0x0)) - MacOS on this disk Kingston A2000 SSD 1TB M.2 2280 NVMe (PciRoot(0x0)/Pci(0x1,0x1)/Pci(0x0,0x0)/NVMe(0x1,15-AD-CD-26-28-B7-26-00)) - Windows on this disk OpenCore 0.6.1 MacOS 10.15.7 both disks GPT UEFI Both OSs boot nicely and work as a charm when selecting either of the disks as boot disks in the BIOS. However, trying to boot Windows 10 from the Opencore Bootmanager (no matter whether PickerMode=internal or OpenCanopy) causes a Windows Blue Screen ("SYSTEM THREAD EXCEPTION NOT HANDLED"). To be on the safe side, I have added an appropriate entry to Misc->Entries: <key>Arguments</key> <string></string> <key>Auxiliary</key> <false/> <key>Comment</key> <string>Not signed for security reasons</string> <key>Enabled</key> <true/> <key>Name</key> <string>Windows 10</string> <key>Path</key> <string>PciRoot(0x0)/Pci(0x1,0x1)/Pci(0x0,0x0)/NVMe(0x1,15-AD-CD-26-28-B7-26-00)/HD(1,GPT,2E9695CB-0F9A-4005-AADB-2FF9C96AD02C,0x800,0x32000)/\EFI\Microsoft\Boot\bootmgfw.efi</string> It points to the Windows 10 bootmanager on the Windows disk's EFI partition. What's wrong with that? Why does this cause a BSOD? It is not clear to me why it works when booting from BIOS but not here. config.plist attached (but maybe it has no relevance for the problem). config.plist Edited October 11, 2020 by qmgoqwe Quote Link to comment Share on other sites More sharing options...
1Revenger1 Posted October 12, 2020 Share Posted October 12, 2020 Usually if it blue screens like that - it's related to Booter->Quirks or ACPI. I'd also suggest setting PlatformInfo->UpdateSBMIOSMode to "Custom" and Kernel->Quirks->CustomSMBIOSGUID = true if you do not want the Mac SMBIOS being applied to windows. What does SSDT-SHC0.aml look like? 1 Quote Link to comment Share on other sites More sharing options...
qmgoqwe Posted October 14, 2020 Author Share Posted October 14, 2020 I have tried to apply your proposed changes PlatformInfo->UpdateSBMIOSMode to "Custom" Kernel->Quirks->CustomSMBIOSGUID = true This alone didn't change anything. Blue screen as before. I have attached the aml file you requested. SSDT-SHC0.aml Quote Link to comment Share on other sites More sharing options...
qmgoqwe Posted October 23, 2020 Author Share Posted October 23, 2020 Still no progress with this problem... Any ideas? Please find attached the dsl files for the two aml files I'm actually using. To me they look good in the sense that they check the OS before returning a modification If (_OSI ("Darwin")) { Return (Zero) } Else { Return (0x0F) } so they should not affect the Windows boot process, am I not right? Help would me much appreciated! SSDT-EC-USBX-DESKTOP.dsl SSDT-SHC0.dsl Quote Link to comment Share on other sites More sharing options...
1Revenger1 Posted October 23, 2020 Share Posted October 23, 2020 (edited) oops! Sorry, didn't see your older post (am now following this thread so I should actually get notifications). I don't see anything wrong specifically with the SSDTs, I'm guessing they're fine (could always disable them and try booting windows to check though). It may be some quirks under Booter->Quirks as well - or your AMD system has the same issue that my AMD system has where OpenRuntime just has issues booting windows. I have to custom build OC with a bit removed (though I think I'm gonna put in a bug report about it and see if it can be fixed) Edited October 23, 2020 by 1Revenger1 Quote Link to comment Share on other sites More sharing options...
qmgoqwe Posted October 26, 2020 Author Share Posted October 26, 2020 On 10/23/2020 at 8:25 PM, 1Revenger1 said: oops! Sorry, didn't see your older post (am now following this thread so I should actually get notifications). I don't see anything wrong specifically with the SSDTs, I'm guessing they're fine (could always disable them and try booting windows to check though). It may be some quirks under Booter->Quirks as well - or your AMD system has the same issue that my AMD system has where OpenRuntime just has issues booting windows. I have to custom build OC with a bit removed (though I think I'm gonna put in a bug report about it and see if it can be fixed) @1Revenger1 what would your Opencore look like then? Quote Link to comment Share on other sites More sharing options...
HenryV Posted November 4, 2020 Share Posted November 4, 2020 Make sure that both secure boot and TPM are disabled in the bios and that windows was installed in EFI mode or has been configured after the install to boot in EFI mode. Move the BCD files to the main Windows partition as they are not there by default. Verify that your machine is booting in EFI mode and not CSM. Verify that your boot EFI boot partition has boot and ESP flags set. Make sure you shut down windows while holding down the shift key until completely shut down. You would do well to use GRUB2 as your main boot loader and chainload windows bootloader and chainload clover or open core to boot macOS. Your GRUB2 grub.cfg boot entries should look similar to these where xxxx-xxxx is the UUID of the boot partition: menuentry 'Windows Boot Manager (on /dev/sda1)' --class windows --class os $menuentry_id_option 'osprober-efi-xxxx-xxxx' { insmod part_gpt insmod fat set root='hd0,gpt1' if [ x$feature_platform_search_hint = xy ]; then search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt1 --hint-efi=hd0,gpt1 --hint-baremetal=ahci0,gpt1 xxxx-xxxx else search --no-floppy --fs-uuid --set=root xxxx- fi chainloader /efi/Microsoft/Boot/bootmgfw.efi } menuentry "Clover"{ insmod part_gpt search --no-floppy --set=root --fs-uuid xxxx-xxxx chainloader /EFI/CLOVER/CLOVERX64.efi # or whatever path you use } menuentry "Open Core"{ insmod part_gpt search --no-floppy --set=root --fs-uuid xxxx-xxxx chainloader /EFI/OC/OpenCore.efi # or whatever path you use } ############################################ Quote Link to comment Share on other sites More sharing options...
neuromask Posted January 4, 2021 Share Posted January 4, 2021 Had same problem with Opencore and Windows blue screen or stuck/freeze on boot/login. Fixed! OC config params to change: DevirtualiseMmio - False SyncRuntimePermissions - True 2 Quote Link to comment Share on other sites More sharing options...
fueg o Posted December 30, 2021 Share Posted December 30, 2021 (edited) On 1/4/2021 at 9:30 AM, neuromask said: Had same problem with Opencore and Windows blue screen or stuck/freeze on boot/login. Fixed! OC config params to change: DevirtualiseMmio - False SyncRuntimePermissions - True Thank you so much! I had the same issue and that fixed it!!! EDIT: After some testing I realized that I still had some conflict in windows with the dsdt/ssdt that I needed and I ended up setting up rEFInd to manage the multi boot. I mostly followed this quick guide with some tweaks: https://github.com/zachs78/MacOS-XPS-9500-OpenCore/issues/11#issuecomment-722946708 Edited December 31, 2021 by fueg o Quote Link to comment Share on other sites More sharing options...
koratmusician Posted May 13, 2022 Share Posted May 13, 2022 use to work fine with intel. now with my Ryzentosh i can never boot windows from Opencore its always. acpi_bios_error , I did everthing from this post but still no luck ( my windows install on HDD not SSD ) Quote Link to comment Share on other sites More sharing options...
MaLd0n Posted May 13, 2022 Share Posted May 13, 2022 8 hours ago, koratmusician said: its always. acpi_bios_error https://www.olarila.com/topic/24542-opencore_no_acpi-opencore-with-additional-featureschanges-implemented-how-to-use-this-fork/ Quote Link to comment Share on other sites More sharing options...
koratmusician Posted May 14, 2022 Share Posted May 14, 2022 (edited) On 5/13/2022 at 7:32 PM, MaLd0n said: https://www.olarila.com/topic/24542-opencore_no_acpi-opencore-with-additional-featureschanges-implemented-how-to-use-this-fork/ i just found that SSDT-GPU-SPOOF.aml made windows blues screen. ( i use RX550 ) i did add If (_OSI ("Darwin")) to my gpu spoof ssdt and it boot to windows just fine now Edited May 15, 2022 by koratmusician Quote Link to comment Share on other sites More sharing options...
STLVNUB Posted May 14, 2022 Share Posted May 14, 2022 (edited) You Guys Are Doing Things The Hard Way Download Win10/11 Download Windows Install App MAKE SURE YOUR TARGET DRIVE IS FAT32 Run Windows Install, Pretty Straight Forward, Select Right Disk For Your Windows I.e. Disk0s2 THIS IS JUST EXAMPLE, CHECK WHAT DRIVE IT IS WITH DISK UTILITYI WILL NOT BE HELD RESPONSIBLE This Will Install A NEW Copy Of Windows To That Disk OR USB It Will Putt A Proper ESP On Said Disk That Is EFI Folder With A Boot/Bootx64.efi This WILL boot With OC NO Worries I GUARANTEE It Saves A Lot Of Time And Heart Ache Edited May 14, 2022 by STLVNUB 2 Quote Link to comment Share on other sites More sharing options...
koratmusician Posted May 15, 2022 Share Posted May 15, 2022 On 10/24/2020 at 12:16 AM, qmgoqwe said: Still no progress with this problem... Any ideas? Please find attached the dsl files for the two aml files I'm actually using. To me they look good in the sense that they check the OS before returning a modification If (_OSI ("Darwin")) { Return (Zero) } Else { Return (0x0F) } so they should not affect the Windows boot process, am I not right? Help would me much appreciated! SSDT-EC-USBX-DESKTOP.dsl SSDT-SHC0.dsl yes i have problems with my gpu spoof so i add If (_OSI ("Darwin")) to ssdt gpu spoof and now windows boot fine no bluee screen Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.