![]() |
[Z68 Extreme4] HD7850 -> RX480 upgrade woes |
Post Reply ![]() |
Page <12 |
Author | |||||
parsec ![]() Moderator Group ![]() ![]() Joined: 04 May 2015 Location: USA Status: Offline Points: 4996 |
![]() ![]() ![]() ![]() ![]() |
||||
If you are fine with using the Legacy ROM setting, then there is no reason to install Windows again, unless you simply want to use Windows 10. Forgot to tell you some mandatory UEFI installation techniques that even Windows 10 will require. In case you aren't aware of this... Whatever Win 10 installation media you use, before the installation starts check the boot order and find the installation media. It should be the only other drive connected to (or powered up) in the PC besides the target OS drive. You should find an entry for the Win 10 installation media that looks something like this: "UEFI: <installation media name>". You need to select the boot order entry with the "UEFI:" prefix, which causes a UEFI booting Windows installation. Not sure if you are using an HDD or an SSD as the Windows 10 drive. I assume the SSD. No idea if any or all HDDs support using the EFI boot loader. EDIT: See Additional Information I added at the bottom of this post, related to the following paragraph. If you want a full blown UEFI booting Windows installation, the CSM option must be set to Disabled. That of course requires the video source to support the UEFI GOP protocol, which does not seem to be the case, so you can't set CSM to Disabled. What you can do with CSM enabled, is set the CSM sub-option, Launch Storage OpROM Policy option to UEFI Only. That will cause the OS drive to be GPT formatted, and have four partitions created by the Windows installer, including a legacy MBR partition. Any or all of this is not required, but selecting the "UEFI:" entry for the Windows installation media is required. Regarding choosing the PCI ROM Priority setting of UEFI ROM with your previous video card, the result of that was nothing. The chances of the HD 7850 supporting UEFI/GOP are very small, so that setting was simply ignored, if not changed to Legacy automatically. That you had the video display failure with the new video card implies that the new card does support UEFI/GOP, but your Windows 7 installation of course did not, resulting in no signal to the monitor. Of course we are going by what you tell us, so it is impossible to know what else might be going on, so this is just guess work. About updating the UEFI, just to check, you have the Z68 Extreme4, not the Z68 Extreme4 Gen3 board, correct? Given that, the latest UEFI/BIOS version (a Beta version, L2.21A) is from 2013, so I don't see that version as helping in general with a very current video card. But in checking into that, I noticed something else, which caused me to check your board's manual. Additional Information Since the manuals are rarely updated to match the UEFI/BIOS updates, I see nothing about any PCI ROM Priority option, or related options. I'm not saying they are not there, just that I cannot determine exactly what they are doing. Also, after reading the description of the L2.21A Beta UEFI/BIOS version, which adds Windows 8 support, no doubt including Secure Boot, I imagine the UEFI booting related settings were changed. I believe they would be similar to the next generation chipset boards, like the Z77 Extreme4, which I still have. The UEFI booting/CSM settings have not changed since the Z77 boards (no reason to do so), but I now realize your board's UEFI/BIOS version does not have a CSM setting, at least with the 1.50 version, and likely only with the L2.21A Beta version. Bottom line, none of this is really significant, just use the Legacy ROM setting, it only matters during POST anyway. |
|||||
![]() |
|||||
Fa1lson ![]() Newbie ![]() Joined: 21 Feb 2017 Status: Offline Points: 8 |
![]() ![]() ![]() ![]() ![]() |
||||
We're in business! Win10 successfully installed, Radeon drivers installed, new card successfully benchmarked.
*phew* More to say I have, but wanted to issue a quick update to prevent unnecessary effort by y'all on my behalf. Must also digest your intriguing post, parsec. I will return... |
|||||
ASRock Z68 Extreme4 (P1.50 BIOS)
Intel Core i5-2500K @ stock Kingston HyperX 1600C9D3T1K2/8GX 2x4Gb DDR3 Intel 510 Series 120GB SATA3 6GB/s SSD (+ 5 spinners) Windows 7 Professional SP1 |
|||||
![]() |
|||||
Fa1lson ![]() Newbie ![]() Joined: 21 Feb 2017 Status: Offline Points: 8 |
![]() ![]() ![]() ![]() ![]() |
||||
Yes indeed.
I used an old spare HDD to successfully install win10, but will of course reinstall on SSD if I decide to accept win10 as my OS. But I had a fun old time getting the UEFI-prefixed entry to appear in the boot order. What ended up working was inserting a win7 install disk in my BD-ROM. With the freshly-burned win10 disc in the drive I actually got the 'no monitor signal' problem again, and had to clear CMOS data. With the drive empty, no amount of rebooting would persuade the UEFI prefix to appear. Weird, and glad I could work around it.
I want this to be the case so very much (as I have no interest in win10 aside from its support for the new card's DirectX 12 ability). But as mentioned in first post, Dr. Debug status code AE ('Legacy boot event') results when I attempt to boot my old win7 install. Am I missing something? I do hope so! Edit: Are you maybe thinking I could do something like this: https://social.technet.microsoft.com/wiki/contents/articles/14286.converting-windows-bios-installation-to-uefi.aspx ? Edited by Fa1lson - 22 Feb 2017 at 10:21pm |
|||||
ASRock Z68 Extreme4 (P1.50 BIOS)
Intel Core i5-2500K @ stock Kingston HyperX 1600C9D3T1K2/8GX 2x4Gb DDR3 Intel 510 Series 120GB SATA3 6GB/s SSD (+ 5 spinners) Windows 7 Professional SP1 |
|||||
![]() |
Post Reply ![]() |
Page <12 |
Tweet
|
Forum Jump | Forum Permissions ![]() You cannot post new topics in this forum You cannot reply to topics in this forum You cannot delete your posts in this forum You cannot edit your posts in this forum You cannot create polls in this forum You cannot vote in polls in this forum |