2400G installed, now lost M.2 boot
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=7725
Printed Date: 12 May 2024 at 1:30pm
Software Version: Web Wiz Forums 12.04 - http://www.webwizforums.com
Topic: 2400G installed, now lost M.2 boot
Posted By: stree
Subject: 2400G installed, now lost M.2 boot
Date Posted: 19 Feb 2018 at 12:26am
|
" rel="nofollow - my asr X370 MB with R3 1200, Samsung evo 960 M.2 256GB boot, Firecuda storage 2.8GB Crucial has been running fine since its first build, a logical contender for a Raven ridge upgrade. So today lifted out the MB, swapped CPU for APU, refitted MB nd recabled and switched on No boot device found. Rebooted and into BIOS, windows Boot manager still there inc samsung nvme 960 as part of its title, the the seagate firecuda, then a EUFI option ( forget exact wording of this one, but not an option I hve ever nominated) BUT. strange thing is, I used to get , Win Boot manager as 1st boot, 2nd boot then was the 960 M.2 itself, then the seagte storage, but now the 960 M.2 does not appear by itself, only as a nomination in Win boot manager. I have removed and reseated the M.2 but no change. I noticed that on the BIOS exit page there is an option to reset UEFI defaults, so I tried this and the 960 appeared as listed again ( on that page at least , where it wasnt before) So I saved and exitted and rebooted. Exactly as before. No bootable device no M.2 960 showing anywhere. Run out of ideas, so wondering if anyone has any ideas about this? ------------- ASRock X370-ITX BIOS 4.50 R5 2600 Cryorig C7 EVGA GTX 950 75w 2x8GB Ballistix Sport LT 2933 960Evo M.2 256GB, Firecuda 1TB Win 10 Pro 64 1803 G-Unique Archdaemon 300 Watt Lian-li Q21B |
Replies:
Posted By: datonyb
Date Posted: 19 Feb 2018 at 12:43am
|
there was a post earlier about another model asrock board same issue cured with the later beta bios eg...... 4.63a ------------- [url=https://valid.x86.fr/jpg250]  [/url]3800X, powercolor reddevil vega64, gskill tridentz3866, taichix370, evga750watt gold |
Posted By: datonyb
Date Posted: 19 Feb 2018 at 12:45am
|
try a proper bios clear/reset eg take out the button battery,pemove kettle lead from psu (the plug to wall),press and hold case power button 30 secs then refit everything and try a restart (be warned it takes ages first boot after clearing cmos) ------------- [url=https://valid.x86.fr/jpg250] [/url]3800X, powercolor reddevil vega64, gskill tridentz3866, taichix370, evga750watt gold |
Posted By: stree
Date Posted: 19 Feb 2018 at 12:49am
|
Thanks. I did not realise there was such a BIOS for this MB X370 fatality gaming ITX I will have a look, but first do a BIOS reset. First thing I did when I powered down to replace the CPU with the 2400G was CMOS jumper and CMOS batt, after disconnecting powerbrick and holding start button in for 30 seconds. No harm tring again though ------------- ASRock X370-ITX BIOS 4.50 R5 2600 Cryorig C7 EVGA GTX 950 75w 2x8GB Ballistix Sport LT 2933 960Evo M.2 256GB, Firecuda 1TB Win 10 Pro 64 1803 G-Unique Archdaemon 300 Watt Lian-li Q21B |
Posted By: datonyb
Date Posted: 19 Feb 2018 at 12:53am
|
i dont know even if there is a later bios for your board mate ,just see a post earlier with same issue cured with an updated bios have i mentioned i hate new bios versions ?  sometimes seem to bring new problems to cure old onesbe prepared to also consider a fresh install of windows maybe ? ot at least a boot repair ------------- [url=https://valid.x86.fr/jpg250] [/url]3800X, powercolor reddevil vega64, gskill tridentz3866, taichix370, evga750watt gold |
Posted By: stree
Date Posted: 19 Feb 2018 at 1:01am
|
" rel="nofollow - insitu boot repair or m.2 hooked to another PC? and hopefully windows repair rather than reinstall....although at a pinch I could reinstall and drag what I want back from win-old files... done that before ------------- ASRock X370-ITX BIOS 4.50 R5 2600 Cryorig C7 EVGA GTX 950 75w 2x8GB Ballistix Sport LT 2933 960Evo M.2 256GB, Firecuda 1TB Win 10 Pro 64 1803 G-Unique Archdaemon 300 Watt Lian-li Q21B |
Posted By: probie101
Date Posted: 19 Feb 2018 at 11:57am
|
Have same issue after BIOS update for Ryzen 3 2200G. Finally got video but lost my Samsung EVO 960 as well. Do let me know if you have found an answer. My first AMD after 20 years of Intel. Pretty disappointing. Tried the reset several times. ------------- 10101 |
Posted By: stree
Date Posted: 19 Feb 2018 at 6:19pm
|
" rel="nofollow - I don`t know why I assumed a Windows repair is needed, it is not even getting near windows, it is the boot drive that is missing, not the boot media. I think the issue is with BIOS and something in UEFI or Legacy mode settings that I have not worked out yet. I know there are settings in these that must be altered for the installation of windows installlation files and that is what has me thinking that because I cleared the BIOS prior to installing the 2400G i somehow lost these settings. Probie, not sure why you did not have the GPU part working,are you definite you have the up to date BIOS for Raven ridge? You do not mention what motherboard you have, or what your full build is. It can help other help you if you list the spec in your signature box. Lastly, do not let this put you off AMD and send you back to Intel without at least overcoming these initial issues and giving AMD a fair crack of the whip! ------------- ASRock X370-ITX BIOS 4.50 R5 2600 Cryorig C7 EVGA GTX 950 75w 2x8GB Ballistix Sport LT 2933 960Evo M.2 256GB, Firecuda 1TB Win 10 Pro 64 1803 G-Unique Archdaemon 300 Watt Lian-li Q21B |
Posted By: nanohead
Date Posted: 20 Feb 2018 at 12:58am
|
There should be no real reason that the M.2 disappears as a boot option. UEFI vs legacy can be confusing. If you installed windows out of the box, and didn't make any modifications to the BIOS settings, then it will install it as a UEFI boot partition. The board will either see or not see the M.2 drive. There are ton of settings that can influence this. Clearing BIOS (power cable out, let the voltage drain out for a few minutes, flash the power switch with cable out to clear PS caps, etc) might help. |
Posted By: stree
Date Posted: 20 Feb 2018 at 2:22am
|
Thanks for input: I forgot to mention, I did a full CMOS clear as soon as the board was powered down for the CPU-APU swap, kettle lead out, start button held down for count of 40, CMOS clear jumper switched to clear pins, CMOS battery disconnectd via 2 pin connector block on motherboard. It is not practical to lift out the battery on this MB because it is the type that is in a plastic jacket strapped to the back of the I_O ports. These 2 items were left in the "clear" position for about 40 minutes and the BIOS was back to default when it did boot into BIOS. Upon the first failure to boot from the M.2 the CMOS clear was undertaken once more. I think the problem lies in a BIOS settings somewhere, Legacy etc, and I will be having another look at the options there. Point of interest. The M.2 originally had Windows 10-64 installed from an ISO file whilst on an ASrock AB350 fatality gaming ITX, when I got an X370 fatality gaming ITX I just lifted the drives ram CPU etc from the AB350 with BIOS 3.10 and an R3-1200, and straight to the X370. The x370 booted first try and ha been running fine with no issues. The X370 at that stage had BIOS 3.0 I updated the BIOS on the x370 to 3.6 Bridge, then to latest 4.4, then undertook the CPU-APU swap. I doubt the non-boot is a Windows issue because Windows is not even coming into play, I am convinced it is a BIOS setting issue and as I said I am going to look again. A bit long winded ,but I wanted to give the full picture otherwise it is unfair on those trying to help. ------------- ASRock X370-ITX BIOS 4.50 R5 2600 Cryorig C7 EVGA GTX 950 75w 2x8GB Ballistix Sport LT 2933 960Evo M.2 256GB, Firecuda 1TB Win 10 Pro 64 1803 G-Unique Archdaemon 300 Watt Lian-li Q21B |
Posted By: stree
Date Posted: 20 Feb 2018 at 3:26am
|
" rel="nofollow - Had a look at the BIOS via F11 ( select boot device) Choice of : UEFI, Win boot manager with M.2 samsung 960 in brackets Samsung 960 M.2 256 Seagate Firecuda ( which is my data drive ) also on that page is "Boot Default" and "Load UEFI defaults" I tried each of those 6 choices, and for each, the result was the same, a black square section of screen, about 100mm x 100 mm on my screen, and the page frozen with no interaction...........after a minute or so the goes to BIOS start page I also tried disabling CSD, with same black box result. Does this sound like a corrupt BIOS install? Seems to be more than just the M.2 not being selected for boot.........or maybe it is down to the M.2? I am lost on what this might be now and what I maight be able to do with it ------------- ASRock X370-ITX BIOS 4.50 R5 2600 Cryorig C7 EVGA GTX 950 75w 2x8GB Ballistix Sport LT 2933 960Evo M.2 256GB, Firecuda 1TB Win 10 Pro 64 1803 G-Unique Archdaemon 300 Watt Lian-li Q21B |
Posted By: MisterJ
Date Posted: 20 Feb 2018 at 3:50am
|
stree, please post a screenshot of your F11 screen. To do this hit F12 while on the screen having a FAT formatted USB plugged. 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: SoniC
Date Posted: 20 Feb 2018 at 3:54am
|
@stree when everything else fails, try to carefully remove, check the AM4 socket under a magnifying glass and re-seat your CPU. And I really mean when you are out of other options (posted by other friendly users here) and just before RMAing your board . Memory problems and PCIe Problems can indicate some bent pins. Especially with SR4/TR4 socket, but also AM4 is prone to this. ------------- -=SoniC=- TR x1950, ASRock X399 FPG (v. 3.33A), G.Skill 3200 CL14 64GB, Enermax LiqTech 280, AMD Vega 64 LC, 10x HDDs (mostly Hitachi), 2x M.2 (970EVO,960Pro), Xonar DX, AX1200i PSU |
Posted By: stree
Date Posted: 20 Feb 2018 at 3:59am
|
MisterJ, OK, thanks, I will do that.it will be tomorrow now. Thanks for offering to have a look. SoniC. As a very last option yes, but I am always careful to just let the CPU drop in under its own steam, if it hesitates it is positioned wrongly......I would never use the slightest force etc. But as a very last option, it would be inspected, so yes, thanks. ------------- ASRock X370-ITX BIOS 4.50 R5 2600 Cryorig C7 EVGA GTX 950 75w 2x8GB Ballistix Sport LT 2933 960Evo M.2 256GB, Firecuda 1TB Win 10 Pro 64 1803 G-Unique Archdaemon 300 Watt Lian-li Q21B |
Posted By: nanohead
Date Posted: 20 Feb 2018 at 4:04am
|
" rel="nofollow - That actually makes a huge difference. It is actually mirroring the behavior I had when I swapped in the 2400G for the R5 1600 yesterday. A couple of questions. Can you get into BIOS? And if so, can you see the M.2 in the drive table? There is something oddly quirky about the 4.40 BIOS. I have an M.2 that works fine, but I have a SATA SSD as my second disk that is sometimes there and sometimes not in BIOS. It always shows up in Windows, but not always in the drive table in BIOS, which is odd. Drives have 2 distinct states. One is to the hardware (in BIOS/Firmware) and the other is in the OS. It is entirely possible that the motherboard/firmware see it fine, but windows is puking on it because of a corrupt signature file because of all the change that image of windows has had (1200, B350, then 1200 X370, then new CPU with integrated GPU. It might seem like you never get to Windows, but in reality, you're failing when UEFI turns over control to Windows, and the signature is corrupt. Might be a stretch, but seen this happen loads of times when new hardware is introduced to an existing Windows installation. |
Posted By: JohnM
Date Posted: 20 Feb 2018 at 3:42pm
| This is a known problem with UEFI BIOS P4.40. It affects some NVMe devices (eg. Samsung 960 EVO) but not others (eg. Toshiba OCZ RD400). They are not recognised in the M.2 socket. The problem has been reported to ASRock by a number of people and they have reproduced it. If you have an M.2 to PCIe x4 adapter card you can use your SSD in the motherboard PCIe slot as a temporary work-around. There is a beta BIOS on the web site but the links don't work. I think this will be resolved quite soon. |
Posted By: stree
Date Posted: 20 Feb 2018 at 6:19pm
|
Thanks JohnM, that behaviour plus the further issues that you outline in your post in the BIOS thread mirror the problems I am having, exactly. Although the problem is enough to prvent me from using that machine, it is a relief that I am not the unwitting cause of the problems. PS: Have to add that these issues under BIOS 4.4 were not present with the CPU prior to the 2400G. I was running an R3-1200 and it performed perfectly well, no issues at all, the finger is firmly pointed at the 2400G, or the 2400G and its performance under BIOS 4.4 that being the problem. ------------- ASRock X370-ITX BIOS 4.50 R5 2600 Cryorig C7 EVGA GTX 950 75w 2x8GB Ballistix Sport LT 2933 960Evo M.2 256GB, Firecuda 1TB Win 10 Pro 64 1803 G-Unique Archdaemon 300 Watt Lian-li Q21B |
Posted By: abasees
Date Posted: 03 Mar 2018 at 10:38am
| Still having issues with some motherboard, CPU and SSD in the M2_1 socket on BIOS verison P4.60 |
Posted By: stree
Date Posted: 03 Mar 2018 at 8:06pm
" rel="nofollow -
You sure it is the same motherboard? We are talking about the X70 Gaming ITX, and there is no BIOS version P4.60 for that board ------------- ASRock X370-ITX BIOS 4.50 R5 2600 Cryorig C7 EVGA GTX 950 75w 2x8GB Ballistix Sport LT 2933 960Evo M.2 256GB, Firecuda 1TB Win 10 Pro 64 1803 G-Unique Archdaemon 300 Watt Lian-li Q21B |
abasees wrote:Posted By: abasees
Date Posted: 04 Mar 2018 at 6:30am
|
Sorry I have the AB350 PRO4 board my bad, but still same issue across a few boards it looks like... I currently have it plugged in the M2_2 socket.
|
Posted By: stree
Date Posted: 04 Mar 2018 at 12:56pm
|
" rel="nofollow - Maybe the issues are the same, but every board has a different BIOS, and it could be confusing looking for a BIOS version that doea not exist! At worst, if you do manage to start a BIOS update that is not for your board you will probably brick your board. Anyway, is 4.6 the latest version for your MB ? If so, is there a later BETA BIOS at the bottom of the list? If so, try that. Do a CMOS clear before updating, just good practice to do so. ------------- ASRock X370-ITX BIOS 4.50 R5 2600 Cryorig C7 EVGA GTX 950 75w 2x8GB Ballistix Sport LT 2933 960Evo M.2 256GB, Firecuda 1TB Win 10 Pro 64 1803 G-Unique Archdaemon 300 Watt Lian-li Q21B |