F5F Stay Refreshed Software Operating Systems Device cleared automatically

Device cleared automatically

Device cleared automatically

Pages (2): 1 2 Next
L
Leart_ZHK9
Member
203
03-22-2019, 09:17 PM
#1
Im having a really strange problem with my newish build where ill install windows 10 and a couple of days later ill get a BSOD with different error messages every time. When i turn the pc back on it tells me theres no os to boot! The drive will show in bios. The strange thing is that i have tried with multiple different drives including: ADATA 256gb NVME m.2 drive ADATA 120gb NVME m.2 drive Samsung 860 256gb sata m.2 drive Cruical bx500 1tb sata 2.5inch drive All have had a similar problem... The most recent drive i tried was the 1tb sata drive and this time i didnt get a BSOD instead i shutdown the PC normally and then the next day booted the PC back up and got a message saying "An operating system wasn't found. Try disconnecting any drives that dont contain an operating system." This is a slightly different message to the other drive although i cant remember what the message was. Anyway disconnecting the other drives results in the same message. Upon booting a recovery disk iv tried startup repair and that wont run, system restore tell me i must specify which windows installation to restore. In cmd i try bootrec /fix mbr which is successful then bootrec /fix boot which says "element not found" then bootrec /rebuildbcd which finds an os and i try to add it to the boot list but this also says element not found... Notably when using rebuldbcd on all the drives other than the 1tb SATA it will tell me that "total identified Windows installations:0". All drives work fine in both this pc and others and i can reinstall the os with not problem but on this pc over the next couple of days os appears to be wiped again. PC Specs: Ryzen 7 3800x (also tried with r5 3600) Gigabyte Aorus Elite B450 16gb (2x8) TForce Ram GTX 1070 Wifi card Deepcool Gammax AIO CPU cooler At the moment as far as drives go i have the Crucial 1tb sata ssd, the samsung 860 m.2 and a wd blue 4tb hdd. Just guessing but maybe it has somthing to do with the installation media im using? (just a bootable usb) Or a motherboard problem? Maybe a driver issue? Iv been trying to fix this for months now ill likey just end up parting it out and selling it all but hopefully i can avoid that..
L
Leart_ZHK9
03-22-2019, 09:17 PM #1

Im having a really strange problem with my newish build where ill install windows 10 and a couple of days later ill get a BSOD with different error messages every time. When i turn the pc back on it tells me theres no os to boot! The drive will show in bios. The strange thing is that i have tried with multiple different drives including: ADATA 256gb NVME m.2 drive ADATA 120gb NVME m.2 drive Samsung 860 256gb sata m.2 drive Cruical bx500 1tb sata 2.5inch drive All have had a similar problem... The most recent drive i tried was the 1tb sata drive and this time i didnt get a BSOD instead i shutdown the PC normally and then the next day booted the PC back up and got a message saying "An operating system wasn't found. Try disconnecting any drives that dont contain an operating system." This is a slightly different message to the other drive although i cant remember what the message was. Anyway disconnecting the other drives results in the same message. Upon booting a recovery disk iv tried startup repair and that wont run, system restore tell me i must specify which windows installation to restore. In cmd i try bootrec /fix mbr which is successful then bootrec /fix boot which says "element not found" then bootrec /rebuildbcd which finds an os and i try to add it to the boot list but this also says element not found... Notably when using rebuldbcd on all the drives other than the 1tb SATA it will tell me that "total identified Windows installations:0". All drives work fine in both this pc and others and i can reinstall the os with not problem but on this pc over the next couple of days os appears to be wiped again. PC Specs: Ryzen 7 3800x (also tried with r5 3600) Gigabyte Aorus Elite B450 16gb (2x8) TForce Ram GTX 1070 Wifi card Deepcool Gammax AIO CPU cooler At the moment as far as drives go i have the Crucial 1tb sata ssd, the samsung 860 m.2 and a wd blue 4tb hdd. Just guessing but maybe it has somthing to do with the installation media im using? (just a bootable usb) Or a motherboard problem? Maybe a driver issue? Iv been trying to fix this for months now ill likey just end up parting it out and selling it all but hopefully i can avoid that..

R
R3kty
Member
133
03-22-2019, 09:40 PM
#2
does the hdd stay connected during installation? if yes, attempt to install windows with all storage devices removed except the one you're installing on, then reconnect the remaining drives after the install.
R
R3kty
03-22-2019, 09:40 PM #2

does the hdd stay connected during installation? if yes, attempt to install windows with all storage devices removed except the one you're installing on, then reconnect the remaining drives after the install.

W
WhatsThePack
Member
215
03-23-2019, 03:17 AM
#3
It worked successfully. I'll proceed with it!
W
WhatsThePack
03-23-2019, 03:17 AM #3

It worked successfully. I'll proceed with it!

D
DrunkMemories
Member
74
03-28-2019, 06:32 AM
#4
It seems your BIOS is taking a break. Consider replacing the battery. Your original system likely functions properly, just configure your BIOS settings.
D
DrunkMemories
03-28-2019, 06:32 AM #4

It seems your BIOS is taking a break. Consider replacing the battery. Your original system likely functions properly, just configure your BIOS settings.

S
SwagLord3579
Junior Member
8
03-28-2019, 08:31 AM
#5
I tried the installation again without any extra drives. It’s happening once more... This time it won’t boot at all. I’m going to give it a try. It’s brand new, but the battery seems okay—though maybe it’s been sitting around for a while.
S
SwagLord3579
03-28-2019, 08:31 AM #5

I tried the installation again without any extra drives. It’s happening once more... This time it won’t boot at all. I’m going to give it a try. It’s brand new, but the battery seems okay—though maybe it’s been sitting around for a while.

D
DiegoNick
Member
76
04-16-2019, 07:51 AM
#6
Previously I swapped the battery in a 2-week-old motherboard, which is feasible. Make sure your BIOS settings haven’t changed. Do you even set up your BIOS?
D
DiegoNick
04-16-2019, 07:51 AM #6

Previously I swapped the battery in a 2-week-old motherboard, which is feasible. Make sure your BIOS settings haven’t changed. Do you even set up your BIOS?

E
Emma_Iersel
Junior Member
5
04-16-2019, 07:58 AM
#7
I have another battery ready to try. I usually just adjust the XMP profile, ensure SATA mode is AHCI, and keep fast boot off. I also make sure the BIOS is current. Are there any specific settings in the BIOS you’d like to modify?
E
Emma_Iersel
04-16-2019, 07:58 AM #7

I have another battery ready to try. I usually just adjust the XMP profile, ensure SATA mode is AHCI, and keep fast boot off. I also make sure the BIOS is current. Are there any specific settings in the BIOS you’d like to modify?

A
A_Sound
Senior Member
486
04-23-2019, 04:41 PM
#8
What will stay clear for you in the future is whether your bios reset correctly.
A
A_Sound
04-23-2019, 04:41 PM #8

What will stay clear for you in the future is whether your bios reset correctly.

K
kotomchi
Member
61
04-24-2019, 12:19 AM
#9
Verify you have the most recent AMD chipset drivers installed. I encountered a similar problem where my computer wouldn’t boot, and once it did, everything was unstable. A chipset update resolved the issue. Also, adjusted the BIOS to factory defaults or set it to AHCI, and configured your first boot device to the drive with the OS. Other potential concerns might include a faulty Windows 10 installation image.
K
kotomchi
04-24-2019, 12:19 AM #9

Verify you have the most recent AMD chipset drivers installed. I encountered a similar problem where my computer wouldn’t boot, and once it did, everything was unstable. A chipset update resolved the issue. Also, adjusted the BIOS to factory defaults or set it to AHCI, and configured your first boot device to the drive with the OS. Other potential concerns might include a faulty Windows 10 installation image.

X
xMelanie
Junior Member
2
04-25-2019, 12:22 AM
#10
Chipset drivers aren't connected to the boot process. They activate once the system starts.
X
xMelanie
04-25-2019, 12:22 AM #10

Chipset drivers aren't connected to the boot process. They activate once the system starts.

Pages (2): 1 2 Next