Help me , please!!! GIGABYTE GA-880GA-UD3H (rev. 2.2) Phenom II X6 1990 T , error in start USB-HDD , BStartard! duet bytes of system memory tested ok ... WTF? HEEELP )))! AND NOT SSD

Hi All!

I am trying this with X58 Motherboard (Alienware Area 51 ALX 2010). using 970 EVO Plus with NVME adapter on PCIe 2.0 x16.

When setting up the DUET Disk, I received the following error on both 2015/2020 version, "*Dxe.efi The system cannot find the file specified". Also, when booting the USB I get BSTART, stuck on SYSTEM MEMORY TEST OK. What to do?

hey @MaSx

may use on the first page
"Current download link for DUET (EDK2015) with REFIND included" the 2015 version because of the old X58 i do have the same chipset and the 2015 version is much better for the old chipset.

and if it is not working disable all devices in bios and try it again and if you may have a usb 3.0 controller on your board you can do a firmware updatet if it fits to your system.

you can try this if you have this usb 3.0 chipset : but read the warnings !!!!

Zitat von noInk im Beitrag #629

---

@CelsiuS

Since I got new hardware with I've re-checked on the NEC Renesas uPD720200.
To get the uPD720200 USB 3.0 device to work properly you need to update its ROM with at least the FW Version 3.0.3.4


- board work.

The DX58SO2 uPD720200 [SubSystemVendorID] 8086 [SubSystemID] 5332 came with the 3.0.2.5 FW version and didn't worked.


- board would likely stuck during the memory check.


If you plan to update the onboard uPD720200 be sure to use your board uPD720200 [SubSystemVendorID] & [SubSystemID] and make and save a backup before anything.
These are the configuration file I used for mine DX58SO2 your might differ.
Use "W200FW36 /srom 0" command to know the uPD720200 [SubSystemVendorID] & [SubSystemID] of your board and adjust accordingly the [SubSystemVendorID] & [SubSystemID] value within the INI file.
DO NOT USE blindly. See the warning and search about.
If you brick something I won't be able to help.

( Adjust accordingly both INI )
DEFAULT.ini is configured as auto-sense for 8086&5332
DX58SO2.ini is configured as on-board device for 8086&5332

In mine case I used the following command:

1
2
3
4
5
6
7
 

[INFO] W200FW36 /srom ? 
[GETID] W200FW36 /srom 0 
[BACKUP] W200FW36 /srom 0 /dump backup.bin
[FLASH] W200FW36 /srom 0 /write F303408.MEM DX58SO2.ini
[VERIFY] W200FW36 /srom 0 /verify F303408.MEM DX58SO2.ini
 
 

Using a wrong hardware ID or wrong FW could render the device inoperable.

---

@noInk

Hey just want to give some feedback it is working awesome!
I updated to a Samsung 2TB M2 SSD and did some light overclocking to 4.0 Ghz and added a Intel AX200 in already available onboard wifi cardholder for 10 € and bought a 2.5 GB NIC for 17€ by ali with Realtek RTL8125.

I had no bootfailure since June/July no bluescreen nothing, by more or less daily use. In conlcusion it is great !

Since Zen 3 I am thinking about to switch to a 5950X with Gigabyte X570 Xtreme. But the 10 year old (CPU, Mainboard, Powersupply, 16GB of RAM and custom
water pump) shit it running like it is new .. so i think i will wait for Zen 4 :D




Asus Rampage III Extreme Black Edition Chipset Intel X58 Modded Bios and Meltdown/Spectre Microcode patch
Intel I7 X990 Extreme BC 3.47 Ghz to OC to 4.0Ghz
48GB DDR3 RAM (CPU limit is 24GB ,Mainboard limit is 48GB, it works very well)
NVME 2TB Samsung M2 SSD with PCI Express adapter 4 lanes 2.0
INTEL AX200
USB device to boot 16 GB Intenso USB stick
Gigabyte GeForce GTX 1660 6GB

Zitat von RonamITI im Beitrag #871

---

Help me , please!!! GIGABYTE GA-880GA-UD3H (rev. 2.2) Phenom II X6 1990 T , error in start USB-HDD , BStartard! duet bytes of system memory tested ok ... WTF? HEEELP )))! AND NOT SSD

---

Zitat von mujuli im Beitrag #873

---

hey @MaSx

may use on the first page
"Current download link for DUET (EDK2015) with REFIND included" the 2015 version because of the old X58 i do have the same chipset and the 2015 version is much better for the old chipset.

and if it is not working disable all devices in bios and try it again and if you may have a usb 3.0 controller on your board you can do a firmware updatet if it fits to your system.

you can try this if you have this usb 3.0 chipset : but read the warnings !!!!

Zitat von noInk im Beitrag #629

---

@CelsiuS

Since I got new hardware with I've re-checked on the NEC Renesas uPD720200.
To get the uPD720200 USB 3.0 device to work properly you need to update its ROM with at least the FW Version 3.0.3.4


- board work.

The DX58SO2 uPD720200 [SubSystemVendorID] 8086 [SubSystemID] 5332 came with the 3.0.2.5 FW version and didn't worked.


- board would likely stuck during the memory check.


If you plan to update the onboard uPD720200 be sure to use your board uPD720200 [SubSystemVendorID] & [SubSystemID] and make and save a backup before anything.
These are the configuration file I used for mine DX58SO2 your might differ.
Use "W200FW36 /srom 0" command to know the uPD720200 [SubSystemVendorID] & [SubSystemID] of your board and adjust accordingly the [SubSystemVendorID] & [SubSystemID] value within the INI file.
DO NOT USE blindly. See the warning and search about.
If you brick something I won't be able to help.

( Adjust accordingly both INI )
DEFAULT.ini is configured as auto-sense for 8086&5332
DX58SO2.ini is configured as on-board device for 8086&5332

In mine case I used the following command:

1
2
3
4
5
6
7
 

[INFO] W200FW36 /srom ? 
[GETID] W200FW36 /srom 0 
[BACKUP] W200FW36 /srom 0 /dump backup.bin
[FLASH] W200FW36 /srom 0 /write F303408.MEM DX58SO2.ini
[VERIFY] W200FW36 /srom 0 /verify F303408.MEM DX58SO2.ini
 
 

Using a wrong hardware ID or wrong FW could render the device inoperable.

---

---

Hello there,

i have a problem ^^. I've been trying to use my nvme ssd in my old computer as a boot drive for 2 days now, but it doesn't really work. To be clear i have managed to install windows 10 multiple times already, but the system has (short) bluescreens which come sooner and sooner after each restart and after a few restarts i can't even reach the desktop. Additionally, for some reason sometimes installing windows doesn't even work. It gives me errors such as these:



Afterwards it can happen that i cannot even see the nvme ssd listed anymore:



To be frank, the entire thing isn't really consistent at all, it does not seem to follow any clear deterministic pattern (although it probably does ^^).

I've tried quite a few things already. I used the 2020 and 2015 version, i disabled VT and VT-d in the bios. I recreated the windows installation usb drive, i used the drive to successfully install windows on a different machine on a nvme drive. I tested two different nvme drives (WD Black sn750, Samsung Evo 970) and disabled pretty much every on-board device in the bios:



What i have usually do:
I create an windows 10 usb stick.
I create a bootable usb stick using USBSetup as following: CLEAN, FORMAT, BOOT, DUET, REFIND
I format the nvme ssd in my laptop using diskpart with "clean" (after selecting the device of course).
I insert the ssd and the DUET+REFIND stick in my computer, i start the computer and boot into refind.
I plug in the windows usb stick and press ESC, then i boot the USB stick from there and beginn the installation process. This sometimes works, sometimes not. But even if installation works the system isn't stable.

My system:
Motherboard: Asus P6T Deluxe x58
BIOS Version: 2209
CPU: x5650
RAM: 16GB (4x4GB, triple channel, 1400MT)
SSD: 512GB Samsung Evo 970/512GB WD Black sn750
GPU: R9 290 Tri-X (although i hardly suspect this matters)

I have an usb3 hub plugged in my motherboard, but since that motherboard has no native usb3 support i strongly suspect it is just running as an usb2 hub. Besides that i only have an usb mouse and keyboard connected (mouse into the hub, keyboard directly).

Additionally, i have a gigabit network card plugged in since the ethernet ports of my motherboard have caused some issues in the past.

Anyone here has an idea what the problem is? Do i need to add some driver? Or is perhaps my network card or usb-hub the problem?

Update #1:
Removing the usb3 hub and the network card did not help at fixing the problems while installing. I reduced the usb2 speed and could now see the red text "BStartart!" before refind shows up.
I installed windows 10 on the nvme ssd on my laptop and inserted it into my computer. I disabled the audio port and disconnected my ethernet cable from the network card and i was able to boot into the os. It ran stable for more than 30 minutes, but obviously without internet i did not have access to proper drivers. When i connected my computer to the internet i could download the graphics driver but during the install process i experienced a bluescreen. I also experienced bluescreens while trying to run benchmarks (userbenchmark & crystaldiskmark).

Update #2:
I reset the BIOS, disabled VT and VT-d and set SATA to use AHCI instead of IDE. I disconnected the ethernet cable and installed Windows 10 on a cleaned nvme ssd. I then transfered crystaldiskmark and the graphics driver installer via usb on the computer. The ssd benchmark worked (even though it only ran with pci 2.0), and the installation of the amd driver seemed to work, but when i restarted the computer i got a bluescreen. I did use the 2020 version, i'm gonna try to use the 2015 version next in this configuration. If that doesn't work i will also try to use an old nvidia card to see if it's caused by my graphics card.

I have seen multiple mentions of NVME driver .efi files that that are supposed to be located in the binary release of refind, but the only files i found there are apparently for file systems i am probably not using (at least i think i don't):

Do i need some .efi file? Which one? And where exactly do i find that file if i need it?

I would be thankful to any kind of help. Thank you very much for reading.

Regards

Hi, thanks for the guide.

I have managed to get it working on my old AMD machine. The only trouble I have is that I can't seem to set the boot order in DUET/Refined, doesn't seem to matter what I do, the default option (ie the one that boots when I don't make a selection) is always my old SATA SSD not the NVME drive. The NVME boots fine when I select it. Both are running Win 10, I've seen solution for linux but nothing windows.

Where do I set my default OS?

Zitat von tommytau im Beitrag #878

---

Hi, thanks for the guide.

I have managed to get it working on my old AMD machine. The only trouble I have is that I can't seem to set the boot order in DUET/Refined, doesn't seem to matter what I do, the default option (ie the one that boots when I don't make a selection) is always my old SATA SSD not the NVME drive. The NVME boots fine when I select it. Both are running Win 10, I've seen solution for linux but nothing windows.

Where do I set my default OS?

---

Hi, very helpful guide, but I'm having a problem that I can't seem to find the solution for in 59 pages.

My setup is on a Dell T5500 w/ dual x5680 on a Intel 5520 chipset (which I believe is the same as the x58). I have detached all of the legacy sata/ssd drives which were in a raid 0 boot via a bios mod as guided through fernando and these forums, which served me well. I have only installed the nvme adapter w/ 512gb nvme drive that I want to install Win10 and boot from. The drive was appropriately recognized in diskmgr in existing Win10.

Following guide in first post "Clean Install Windows 10"
1) Duet Refind USB creation ---SUCCESS
2) Boot the PC with the DUET USB connected and wait for it to reach the graphical boot manager ---- SUCCESS
3) Connect the WINDOWS 10 ESD-USB and refresh the visual representation list by hitting the ESC keyboard KEY to make the "Boot Fallbcak boot loader from ESD-USB" option appear. --- SUCCESS
4) Launch the EFI WINDOWS 10 installer from the WINDOWS 10 ESD-USB by selecting the "Boot Fallbcak boot loader from ESD-USB" --- SUCCESS

Unfortunately, this is where the Windows Logo (Blue) on a Black Screen Loads and subsequently the spinning circle of dots presents but goes into an infinite loop never presenting the welcome screen/install menu.

Is there a verbose install mode to look at logs for what might be hanging up? Maybe someone knows the Windows boot process better to give me some suggestions to try? Any insights appreciated.

Hey, i think someone had a similar problem in the thread. Try disabling Virtualization and virtual io (VT-D) in the BIOS.

Zitat von duLouser im Beitrag #881

---

Hey, i think someone had a similar problem in the thread. Try disabling Virtualization and virtual io (VT-D) in the BIOS.

---

@noInk

HPE ProLiant DL380p Gen8 Server , chipset c600 , Integrated Matrox G200 ( No Uefi capable)

I found out that with integrated video i cant reach to Refind screen,no boot

But when i use with an external video card i am able to boot and everything is fine.

Is there any way to change something in DUET to make it work with integrated video matrox g200 ?

Happy New Year everyone!!

I was wondering if anyone know what the BSTARTER error is about and how to fix this?

Also, how can I hide these messages or say keep the screen blank until Windows logo. I prefer to keep them hidden than show any message to be seamless even though there may be some delay until Windows Logo shows up but I am okay with that.

Just as a follow up for those interested. I did get Windows to boot on my nvme drive. It took a fair bit of research and trial and error. In the end, it was clover method that worked for me but I had to clone existing sata drive to nvme, then mbr2gpt, then boot. I will note that the instructions on the clover thread are a little dated as the folder directory has changed for the newest/current Clover 5127 release once installed on USB via BDU. It is likely still relevant to find the appropriate directories to copy the nvme dxe driver. I actually had a few BSOD's on install via BDU, which are never fun, but all seemed to recover fine. Seems relevant to check BDU options are correct which wasn't highlighted in the thread.