2400G installed, now lost M.2 boot |
Post Reply | Page <123> |
Author | |
stree
Groupie Joined: 17 Dec 2015 Location: Lincolnshire Status: Offline Points: 264 |
Post Options
Thanks(0)
|
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 |
|
MisterJ
Senior Member Joined: 19 Apr 2017 Status: Offline Points: 1097 |
Post Options
Thanks(0)
|
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
|
|
SoniC
Newbie Joined: 23 May 2017 Status: Offline Points: 183 |
Post Options
Thanks(0)
|
@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 |
|
stree
Groupie Joined: 17 Dec 2015 Location: Lincolnshire Status: Offline Points: 264 |
Post Options
Thanks(0)
|
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 |
|
nanohead
Newbie Joined: 07 Feb 2018 Status: Offline Points: 80 |
Post Options
Thanks(0)
|
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. |
|
JohnM
Groupie Joined: 20 Feb 2018 Location: UK Status: Offline Points: 267 |
Post Options
Thanks(0)
|
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.
|
|
stree
Groupie Joined: 17 Dec 2015 Location: Lincolnshire Status: Offline Points: 264 |
Post Options
Thanks(0)
|
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. Edited by stree - 20 Feb 2018 at 7:07pm |
|
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
Newbie Joined: 03 Mar 2018 Status: Offline Points: 7 |
Post Options
Thanks(0)
|
Still having issues with some motherboard, CPU and SSD in the M2_1 socket on BIOS verison P4.60
|
|
stree
Groupie Joined: 17 Dec 2015 Location: Lincolnshire Status: Offline Points: 264 |
Post Options
Thanks(0)
|
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
Newbie Joined: 03 Mar 2018 Status: Offline Points: 7 |
Post Options
Thanks(0)
|
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.
|
|
Post Reply | Page <123> |
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 |