[RESOLVED, by TSD]1950x will not boot media comp.
Printed From: ASRock.com
Category: Technical Support
Forum Name: AMD Motherboards
Forum Description: Question about ASRock AMD motherboards
URL: https://forum.asrock.com/forum_posts.asp?TID=6072
Printed Date: 26 Jun 2024 at 11:23pm
Software Version: Web Wiz Forums 12.04 - http://www.webwizforums.com
Topic: [RESOLVED, by TSD]1950x will not boot media comp.
Posted By: MisterJ
Subject: [RESOLVED, by TSD]1950x will not boot media comp.
Date Posted: 14 Sep 2017 at 2:30am
I just completed my latest build which follows:
I tried adding this to my signature and far exceeded the 200 character limit. The memory is a single borrowed stick from my R7. The machine powered up and booted immediately to a message saying no OS found. I plugged in a USB stick with WinPE. It appears to boot displaying the windows logo but then just sits there. I made sure Secure Boot was disabled and it was. I tried a Windows install DVD and it does the same thing. Everything looks normal in the BIOS. I used Instant Flash to update to P1.50, microcode stayed at 800F11/800129. I am starting my research and would appreciate anything anyone has to offer. A RANT! I am using borrowed memory because G.Skill says the TR BIOS (AGESA) will not support 3600 MHz. I will open a ticket on ASRock and AMD on the down level AGESA (1.0.0.3 in BIOS P1.50). I hope anyone interested in TR will do the same. Thanks and enjoy, John. ------------- Fat1 X399 Pro Gaming, TR 1950X, RAID0 3xSamsung SSD 960 EVO, G.SKILL FlareX F4-3200C14Q-32GFX, Win 10 x64 Pro, Enermx Platimax 850, Enermx Liqtech TR4 CPU Cooler, Radeon RX580, BIOS 2.00, 2xHDDs WD |
Replies:
Posted By: datonyb
Date Posted: 14 Sep 2017 at 2:40am
|
may i suggest using just one 960 and try to boot from a usb formated fat 32 and using the media creation usb installer direct from windows select install uefi when pc first starts to post now as for the ram theres plenty of people using gskill 3600 tridentz on x370 boards most can get it to run at 3200 some can get it to run at 3600 despite it not saying so first things first let try to get a operating system on the new build first ------------- [url=https://valid.x86.fr/jpg250]  [/url]3800X, powercolor reddevil vega64, gskill tridentz3866, taichix370, evga750watt gold |
Posted By: datonyb
Date Posted: 14 Sep 2017 at 2:42am
|
https://www.microsoft.com/en-gb/software-download/windows10" rel="nofollow - https://www.microsoft.com/en-gb/software-download/windows10 2 nd option down create usb/dvd installion device ------------- [url=https://valid.x86.fr/jpg250] [/url]3800X, powercolor reddevil vega64, gskill tridentz3866, taichix370, evga750watt gold |
Posted By: datonyb
Date Posted: 14 Sep 2017 at 2:47am
|
oooohhhhhhh you can update bios on that baord without even a cpu or ram installed  ------------- [url=https://valid.x86.fr/jpg250] [/url]3800X, powercolor reddevil vega64, gskill tridentz3866, taichix370, evga750watt gold |
Posted By: MisterJ
Date Posted: 14 Sep 2017 at 2:52am
|
Thanks, datonyb. I have been doing my W10 (W7 before) installs for a long time by booting WinPE (built using ADK). I then start a flat install (disk drive), so one of SSDs contains my install files. The other two are new with nothing on them. I saw the FlashBack feature, but did not want to be a pioneer. G.Skill has some neat FlareX coming and they should (X399 TR only) be on the qualified list. Thanks much and enjoy, John. ------------- Fat1 X399 Pro Gaming, TR 1950X, RAID0 3xSamsung SSD 960 EVO, G.SKILL FlareX F4-3200C14Q-32GFX, Win 10 x64 Pro, Enermx Platimax 850, Enermx Liqtech TR4 CPU Cooler, Radeon RX580, BIOS 2.00, 2xHDDs WD |
Posted By: MisterJ
Date Posted: 14 Sep 2017 at 4:53am
|
" rel="nofollow - I removed all SSDs and the USB stick and disconnected all in back that I did not have to have. I booted the W10 DVD and it started accessing it for maybe a minute, then just quit. Thinking time. Ideas? Enjoy, John. ------------- Fat1 X399 Pro Gaming, TR 1950X, RAID0 3xSamsung SSD 960 EVO, G.SKILL FlareX F4-3200C14Q-32GFX, Win 10 x64 Pro, Enermx Platimax 850, Enermx Liqtech TR4 CPU Cooler, Radeon RX580, BIOS 2.00, 2xHDDs WD |
Posted By: wardog
Date Posted: 14 Sep 2017 at 5:27am
|
" rel="nofollow - Two things come to mind.......... Only one SSD, connected to M2_1 Catch that this board has three power connections? 4-pin, 8-pin, and 24-pin? Consider your wim used is now outdated? For TR I'd consider using the latest official 10 build released. Not one of the Preview ones. |
Posted By: wardog
Date Posted: 14 Sep 2017 at 5:29am
|
BTW "Fatal1ty X399 Professional Gaming, Threadripper 1950X" You suck!  |
Posted By: MisterJ
Date Posted: 14 Sep 2017 at 5:48am
|
Thanks, wardog. I am nowhere close to the .wim file and I created it last week - a little down level but still W10.1703.15063.540. I think your second comment may be the closest! I tried enabling compatibility and could not even boot into BIOS. I did a clear CMOS, then booted an old W7 install disk. It went to the first install window with no problem. Only trouble is my mouse and KB are wireless and W7 has no drivers. If you will read my last post, I have removed everything except Monitor and power. W10 install DVD won't boot but W7 does. The W10 install disk boots just fine on this machine (R7). I will quit for today but may move this optical drive to my TR machine tomorow. Thanks and enjoy, John. ------------- Fat1 X399 Pro Gaming, TR 1950X, RAID0 3xSamsung SSD 960 EVO, G.SKILL FlareX F4-3200C14Q-32GFX, Win 10 x64 Pro, Enermx Platimax 850, Enermx Liqtech TR4 CPU Cooler, Radeon RX580, BIOS 2.00, 2xHDDs WD |
Posted By: wardog
Date Posted: 14 Sep 2017 at 5:55am
|
Windows 7 you need to use: http://www.asrock.com/microsite/win7install/" rel="nofollow - http://www.asrock.com/microsite/win7install/ |
Posted By: wardog
Date Posted: 14 Sep 2017 at 6:11am
Clarification: To enable USB mice and KBs you need to use the above patcher on Windows 7. Too, I wonder, on one of your attempts  , use the SATA Floppy Image available on your MB's dl pages. RAID or otherwise.I unzip it right to the 10 USB install stick and F6 it where it asks what drive you want to use to install to. It'll present 3 dirs, with the top one being RAID drivers pre-install. I dl/'d the media tool last night. 1703.15063.0 |
wardog wrote:Posted By: MisterJ
Date Posted: 14 Sep 2017 at 7:25am
|
Thanks, Wardog. I am sorry I mentioned W7. I have no interest in installing W7 on my system, I only used the disk to see if it would function and it does. Enjoy, John. ------------- Fat1 X399 Pro Gaming, TR 1950X, RAID0 3xSamsung SSD 960 EVO, G.SKILL FlareX F4-3200C14Q-32GFX, Win 10 x64 Pro, Enermx Platimax 850, Enermx Liqtech TR4 CPU Cooler, Radeon RX580, BIOS 2.00, 2xHDDs WD |
Posted By: wardog
Date Posted: 14 Sep 2017 at 9:26am
NP John. I only pointed it out as your issue with 7 there on x399 system. hehe, No. Not unless you ha(d)(ve) an important program that the programmers left at 7. |
Posted By: parsec
Date Posted: 14 Sep 2017 at 11:12am
|
" rel="nofollow - It sounds like the optical drive you are using on the X399 board does not support UEFI, while the one on your Ryzen 7 PC does. Not all optical drives support UEFI. Did you check what is shown in the boot order for the optical drive in the X399 board, when you have the Windows 10 installation disk in it? Does it have the prefix "UEFI:" and then the optical drive name? It's also possible that the boot order entry on the X399 system will have the "UEFI:" prefix, but if the optical drive does not support UEFI, it won't work correctly. The hint here is the Windows 7 disk started normally, since the Windows 7 installation files do not support UEFI without a modification. It's entry in the boot order would not have the "UEFI:" prefix. Windows 10 installation media will normally default to the "UEFI:" prefix. Windows 7 also does not have an NVMe driver, so would fail when trying to install to an NVMe SSD. Did you use the same technique, booting WinPE, on your Ryzen 7 PC? ------------- http://valid.x86.fr/48rujh" rel="nofollow"> 
|
Posted By: wardog
Date Posted: 14 Sep 2017 at 12:22pm
Lord, I haven't used an ODD to install an OS for years and years. parsec, it seems to me it should have "installed' regardless of UEFI: <ODD> or not. |
Posted By: wardog
Date Posted: 14 Sep 2017 at 12:32pm
" rel="nofollow -
Bumping my post count.......... Doesn't 7 choke on correct updated USB drivers missing? Isn't that all the Patcher remedies? |
Posted By: MisterJ
Date Posted: 15 Sep 2017 at 3:32am
|
" rel="nofollow - RESOLVED! First, I want to apologize for even mentioning booting the W7 install DVD. I never wanted to install W7, just see if it was possible to boot anything on this machine. I certainly did not need old bugs to chase. The fact that it did boot gave me a way forward. I made a WinPE CD ROM and it booted fine. Then I made a WinPE USB stick with no extra files like were on the old one. It booted fine also. I then used the USB stick to do a flat install from one one of the SSDs and all went fine. The system is running fine. I suspect I have a similar problem to this thread: http://forum.asrock.com/forum_posts.asp?TID=5860&KW=2016&PN=1&title=x399-taichi-with-tr-wont-install-server-2016 I also suspect this is a BIOS problem. Since, at least for me, it seems to be boot device size dependent, I suspect that the BIOS is using a 32 bit variable for addressing data (>4GB) on the device. I do not know if this is an ASRock or an AMD problem, so I will open a ticket on both. The fact that the BIOS and AGESA are so down level on Threadripper should be a shame to both. I hope it is fixed soon. Thanks and enjoy, John. ------------- Fat1 X399 Pro Gaming, TR 1950X, RAID0 3xSamsung SSD 960 EVO, G.SKILL FlareX F4-3200C14Q-32GFX, Win 10 x64 Pro, Enermx Platimax 850, Enermx Liqtech TR4 CPU Cooler, Radeon RX580, BIOS 2.00, 2xHDDs WD |
Posted By: datonyb
Date Posted: 15 Sep 2017 at 3:55am
|
and only on the last reply did i notice the thread was started by john im not used to you having a problem good luck with the new build mate ------------- [url=https://valid.x86.fr/jpg250] [/url]3800X, powercolor reddevil vega64, gskill tridentz3866, taichix370, evga750watt gold |
Posted By: wardog
Date Posted: 15 Sep 2017 at 3:58am
|
[RESOLVED] !!!!!!!!!! John, not for a minute can I believe a very recent from the ground up platform would not have 48-bit LBA. That would go down as a World Class blunder if this was true. Let me read that link you provided. And go back to your original to see the components used again. |
Posted By: wardog
Date Posted: 15 Sep 2017 at 4:21am
|
Hmmmm, John, To be clear, you do or do not have 10 installed? hehe 'cuz you keep interjecting 7, you last post left me confused this time  If 10 is not, have you tried as I suggested and used F6 on install using the SATA Floppy Image drivers available on the MBs download page(s)? It contains both flavors of controller drivers. |
Posted By: MisterJ
Date Posted: 15 Sep 2017 at 5:22am
|
Thanks, datonyb. wardog, good grief! I have said several times I have NO interest in W7. How many times do I have to say I am sorry I even mentioned W7. The SATA floopy (see the DL page for spelling) is for RAID use. I have no RAID. I also said I was not interested in chasing old problems. I have W10 x64 Professional installed on my TR. All is well, I have no issues. W10 installed without F6 floopy drivers. All my special drivers are injected into the .wim files using DISM. I have W10 x64 Pro installed. I posted this in my first post:
Thanks and enjoy, John. ------------- Fat1 X399 Pro Gaming, TR 1950X, RAID0 3xSamsung SSD 960 EVO, G.SKILL FlareX F4-3200C14Q-32GFX, Win 10 x64 Pro, Enermx Platimax 850, Enermx Liqtech TR4 CPU Cooler, Radeon RX580, BIOS 2.00, 2xHDDs WD |
Posted By: wardog
Date Posted: 15 Sep 2017 at 10:15am
 Mmk |
Posted By: MisterJ
Date Posted: 23 Sep 2017 at 11:56pm
|
ASRock TSD responded to my ticket and informs me that TR supports W10 RS1 and RS2. RS1 requires disabling IOMMU in the BIOS. I see no mention of this restriction in the ASRock site on the X399. When first told, I did not even know what RS1 and RS2 were. Here is a good reference: https://en.wikipedia.org/wiki/Windows_10_version_history RS1, Redstone 1, is W10.1607 and RS2 is W10.1703. In my case the version of W10 I was installing was RS2, but I was using an older version of WinPE which obviously was not supported. Building WinPE using the latest ADK (1703) solved my problem not the smaller size as I suspected. I suspect this same restriction may be preventing the Server 2016 installing. A wild guess is to try disabling IOMMU. Here is am image sent me from an AMD document: https://postimages.org/" rel="nofollow">  Enjoy, John. ------------- Fat1 X399 Pro Gaming, TR 1950X, RAID0 3xSamsung SSD 960 EVO, G.SKILL FlareX F4-3200C14Q-32GFX, Win 10 x64 Pro, Enermx Platimax 850, Enermx Liqtech TR4 CPU Cooler, Radeon RX580, BIOS 2.00, 2xHDDs WD |