Yes. I tried that. Same result
- - - Updated - - -
I feel like Asus never changed out my motherboard, I'm not sure what else it might be besides for chipset issues. Why it doesn't even want to recognize windows in any capacity has me mind blown!
I'm at a loss. It sounds like it is a driver issue with Windows 10.
I was thinking that as well. But. I can't find anyway to install drivers if it won't let me even get to a windows recovery. I've tried hirens CD boot. .. it won't let me boot to windows PE so I can't use any of those utilities. Anything Linux (which I have a whole seperate ssd I use) isn't an issue... Windows related my computer says hell no.
Some posts ago you were asked did you get to the install screen from the windows 10
that was on post 9
and you replied
What you did not say was what do you get to when you boot from the usb on the one time boot menu choosing the UEFI entry for the usb.No. i do not even get to that screen.
Which is what I asked on my reply to your thread on post 2
2. What you do not tell us is - what occurs when you try to install Windows 10 from an installation usb - by that I mean what are the error messages
does the install procedure see the drives
No I never get to the purple screen ever if I do uefi boot, or even efi shell from the bios ...It sits on the windows page with no spinning circle. Just the windows splash page.. the bios sees the drives, but in the install procedure, I can't even get to the place for it to even see the drives.
Since that problem occurred, have you tried a complete CMOS reset with power drain ? (remove battery)
The fact that it occurred suddenly makes me think of some kind of Single Even Effect. To be sure you need to completely Drain the MB and try your Windows installation with default loaded.
If the board doesn't come back, you need to RMA it again, Take a picture of the SN so when it comes back you can verify if you've been duped.
These Machines run Windows like beasts, your MB might be defective. ("somewhere" that Linux doesn't uses).
And also getting a CPU with integrated graphics can give you an edge when doing MB troubleshooting.
Verify if SATA AHCI / UEFI are enabled (should be).
Since you are nearly not able to boot anything, can you boot and run Memtest86 in UEFI ?
I agree on the motherboard, especially since it came back with no "cause" I actually had bought a warranty with the board when I bought it and just requested them to pay me out for it, so I'm looking to get another motherboard... And I have done memtest before Ubuntu loads....
jlynn77
Part of the problem is, and it is not your fault, you are seeing so many posts on your thread, some before you have chance to answer one of them, that you are missing answers to what is asked and that IMHO is partially the reason for the lack of progress
My colleague MaloK
has posted
but you only reply to the other part of his post regarding the RMA and memtest.Since that problem occurred, have you tried a complete CMOS reset with power drain ? (remove battery)
The fact that it occurred suddenly makes me think of some kind of Single Even Effect. To be sure you need to completely Drain the MB and try your Windows installation with default loaded.
=====================================================
I have also made particular queries which were not answered and I had to ask again.
AS I SAID this is not your fault - you need to work with ONE person on an issue asuch as yours, otherwise it is very difficult to make logical progress, especially for you.
You need (as I mentioned when I asked what drives you have )- to disconnect ALL drives except the one you are installing windows to
WHICH drive did you install Linux to and was that installed on the firmware configured UEFI or legacy.
I know it looks stupid but Single Event Latch-up (SEL), Single Event Gate Rupture (SEGR) and Single Event Burnout (SEB) occurring in non-volatile memory...
It's been tested in space but... It occurs everyday on the ground too. Theses events can Hard-Lock any computer until complete power cycling. And can also cause other soft errors in computing elements.
Clearing this out of the way. Makes a solid case of legitimate RMA for me.
Yes I have tried draining the mb ... And I changed the battery as well. I'd have to double check on the Linux drive but pretty sure I have it installed in UEFI. BUT like I said, I have that on one drive that I have been plugging and unplugging when I am trying different window installations. I formatted and out my NVME drive IN gpt to try install windows, but like I stated, I can't even get to the point of it recognizing windows.
Quote