New
#11
I think you proved SSD was okay as issues moved to HDD.
So is Windows boot media 1809 or older 1803?
Good news that Ubuntu runs.
I think you proved SSD was okay as issues moved to HDD.
So is Windows boot media 1809 or older 1803?
Good news that Ubuntu runs.
I also have this problem!
AMD RYZEN 2200G BOX
8GBx1 DDR4 AMD 7 PERFORMANCE SERIES 2400
ASROCK A320M HDV LASTEST BIOS
SSD WD GREEN 240GB
After five or 4 tries i have managed to successful installed 1803. But now i have a lot of bsods
If you just got then it is 1809. This tutorial shows you have to query.
See Full Details about a Windows 10 ISO file
You can go here and get 1803.
https://www.heidoc.net/joomla/techno...-download-tool
You said there were likely BIOS updates. There is a certain element of risk associated with updating the BIOS and you and only you can decide if you wish to undertake. I have not had one go bad. Trick is, read instructions, be patient and don't do it when there are storms in the area that may cause power issues.
I suggest 1803 (April 2018) as there are still some blocks on 1809.
@Fishaffair... Please start a new thread and post the info requested in the stickies. This will allow members to investigate cause of BSOD's.
Thanks for the responses Ken,
I tried to install Windows 10 1809 again, this time with a brand new USB. I made it through the initial setup, but after restarting I got a RESOURCE_NOT_OWNED BSOD, and that process looped 3 times (same error) before I stopped it.
I have since installed Ubuntu on my other SSD, in an effort to be able to use it to do whatever testing I can ( atleast I can get to an OS).
I will try and use 1803 next.
Hi DevoidOfHope,
Could you verify your system specs please, because they don't seem to be right. Specifically your CPU since the i5-6700k doesn't exist, but maybe there are more things incorrect?
Thanks for pointing that out, it should be i5-6600k!
Could you remove as much as possible hardware, i.e. the GPU, network card, SSD/HDD, until you have the absolute minimum required to boot and install Windows.
The GPU has been removed, as well as all but one drive. I am currently running Memtest86 7.5 as I'm told it is better for DDR4 RAM, but before I was only using one stick of RAM. Otherwise the only nonessential hardware is my keyboard and mouse.
@Caledon Ken
I tried the 1803 version of Windows 10, this time on the new USB to no avail.
I've been trying to see if I can get a minidump file for the BSOD RESOURCE_NOT_OWNED, but it doesn't look like they are being generated. I'm going to keep trying to see if I can get one to generate.
Edit: I actually just noticed something interesting as I putt around the Command Prompt. In the past few weeks, the X and H keys on my mechanical USB keyboard have seemingly not been working well. It takes multiple presses to work. However, right now in the Command Prompt, they are working fine.
I had assumed it was my keyboard failing, but maybe this is a clue?
2nd Edit: Removing the keyboard didn't change the outcome. Same RESOURCE_NOT_OWNED BSOD.
Last edited by DevoidOfHope; 03 Dec 2018 at 18:03.