Zitat von agentx007 im Beitrag #224

---

@Daserste1 Which Windows are you trying to install on it ?
(10 / 8[.1] / 7, x86/x64, etc.)

---

@d4nt3ch - take that 16GB and format to 1GB FAT32, don't let the board die, even if you upgraded to another platform bring it back to life so you can sell it and get some $$ back.
You caught a PCIE card on fire? If yes, maybe like you mentioned, that card did something to the Saber board?? Ohh, sorry, I read that wrong, and thought it just happened on your new board from this same card used on your saber when this brick happened.

So what do you plan to do with the saber X79 board now??

You're welcome, and thank you for the kind words of support too, we all try to help each other best we can

* Edit - @gdfath3r & @Daserste1 - if it is a clean install of Win7 to NVME you are trying to do, you have to slipstream NVME drivers into Win7 install.wim and boot.wim.
Or you could also do special dance I covered here to clone current Win7 install to NVME (or do clean install, then clone that, both same and covered in my process outlined below
Installing Clean Win7x64 on M2.2280 PCIe Gen3x4 SSD A-DATA SX8200 Pro

I am using win10 x64, thank you.
Win7 is not going to be supported anymore soon, so no point to mess with it.

@ Lost_N_BIOS the x79 board will be sitting in my junk of shame for a while.

I've lost hope on it for now. I really don't think partitioning that stick to 1gb will do anything since it's been the same result over and over again, blinky blinky fast blinky then solid blue.
-----------------------------

@Ntrako I am quite experienced when building systems and I will say that your steps I have tried several times. I really think the bios is toast, considering even on stock, if i were to reboot and try and enter bios (del at post) it wouldn't go through, on STOCK settings, default STOCK settings. And I have tried a new battery. Sometimes I could get in, other times I couldn't. The board is dead.

@d4nt3ch : Whereabouts are you?

@d4nt3ch - How much do you want for it, maybe I can fix it? I'd hate to see it sit unused if it can be saved, also hate to see it go to the trash bin too

@d4nt3ch
i can fix it too, i had this error before with my bios on this motherboard when i bought it..unlikely in the past i didnt had knowledge to fix this issue but now i get hard about mobo fixing(hardware and bios, not mods).
so its in your hands.
This mobo is not to go to rubish, at least not in 2019...i believe in 2028 maybe i will throw mine too but maybe, i have it for 8 years with no any errors~~

@gdfath3r I'm in Canada

@d4nt3ch - So, how much do you want for it?

Im in UK.....I just wanted to offer my help if you were local.....I mean in UK.
I used to live in Toronto for 7 years.

Zitat von gdfath3r im Beitrag #226

---

Zitat von agentx007 im Beitrag #224

---

@Daserste1 Which Windows are you trying to install on it ?
(10 / 8[.1] / 7, x86/x64, etc.)

---

Seems Win 7 to me.

I remember this advices from the time I had problems installing:

1) Is NVMe it formatted as GPT ?
2) Are you installing Windows in UEFI mode (CSM must be set to UEFI first on USB/Boot devices)

---

You can't install Win 7 from CD, because it doesn't support EFI booting.
Not having NVMe drivers is secondary issue (you can slipstream them).

@Daserste1 - Win7 can be installed from USB, but you must first edit/slipstream NVME drivers to Install.WIM and Boot.WIM, as mentioned above
Drivers here for anyone that needs later - https://ufile.io/d9mpdwu2 >> Here's one Easy way to do it, but there are many others too >> https://www.sevenforums.com/installation...tion-media.html

Yes, for Win10, no drivers needed during OS Install.

My samsung 970 evo 500gb died after 1 year of use. Symptoms: firmware errormod. What can cause this?