Bios update possibly killed pc?

[Peja]

Hi all, 

 

I recently built a new pc, used my original windows that's installed on a m2 drive and just transferred it over, games and everything else were on different hard drives and everything worked beautifully! Then 2 days ago I decided to update the BIOS to the latest version (Asus ROG Crosshair VIII Formula mobo and update v1201)

 

On first startup everything seemed fine, then I started playing games and my fps would just start to drop until it was below 10, and freeze the pc. Even when the fps was high at the start of launching a game, it would still feel very jerky / weird as if I was playing on really low fps.

 

I then thought that I just might need a fresh start and reinstall Windows games etc so I wiped all drives and tried to reinstall Windows, but now all I keep getting is the option to choose 64 or 32 bit, once it starts loading files and finishes it brings me to a error screen, ntoskrnl.exe is missing, tried 3 different installation media's and nothing seems to work, any way of fixing this problem or is my mobo maybe stuffed (I don't believe it to be the case as I can get into bios and it detects all ram, cpu, hdd everything! ).

 

Pc specs are:

Ryzen 9 3950x

Asus ROG Crosshair VIII Formula Motherboard

Gskill Trident Z Neo 64gig c16 3600 ram

Asus 1080ti Poseidon graphics card 

3x Samsung hdd;

1x 970 evo m.2 ( for windows)

1x 960 pro m.2 (for my main games)

1x 860 evo (for everything else)

Corsair 1200 psu 

[Whiro]

Did you tried resetting bios ?

[Peja]

Yeah, if you mean clear cmos, that's already been done.

[WereCatf]

7 minutes ago, Peja said:

Yeah, if you mean clear cmos, that's already been done.

If you have XMP enabled in BIOS, disable it and see if that fixes the issue. If not, then download and run memtest86+ for an hour or two and see if it reports any RAM-errors. If not, try dropping your CPU-speed down and see if that fixes things.

[Peja]

Xmp is a Intel thing? I'm on an amd platform, everything is default settings nothing's over clocked, and I can't really download anything as I can't even install windows so I have nothing to really work with. I can get into BIOS and that's about it.

[Guest]

Can you not revert back to the original bios version ?

[Peja]

I'm unsure, that's one thing that I haven't tried as I wasn't sure it was something you should do.

 

Also the update before this one said you cannot revert to older BIOS versions after it so I'm unsure if that's also the case with this one.

[Guest]

You can give it a try and see if it will let you. I have seen people roll back their bios but it might not have been on an Asus board. That is why I like Gigabyte as they have dual bios on a lot of their boards.

 

You can try using the bios flashback button on the back of the board. Just make sure to follow the instructions i.e renaming the bios file.

[Otto_iii]

Windows crapped itself, your hardware is likely, i'm 99% sure, absolutely fine. 

If BIOS was corrupted you wouldn't be able to get into BIOS or anything and would need to RMA mobo, basically nothing would happen if you tried to boot.  You are atleast getting past boot screen, can get into BIOS, and then onto a point windows craps out.  Windows install just seemed to have corrupted, which isn't too surprising if you are using a install from a different system.  Even though Windows 10 can transfer from different hardware its likely you will have issues, updating the BIOS which could have changed things like the CPU instructions likely made it so you finally ran into a big one.  


If you can get onto your own backup computer, if not that then a friends/family computer and make a bootable Windows 10 install onto a USB, boot from that, clear and format the current drives (if you need data from current boot drive then recover it by plugging them in on another working PC first/and or buy a new small hdd/ssd to install windows onto and boot from) then there shouldn't be a problem after the fact. 

This is one of the easier and clearer windows install guides i know, pay attention closely from 3 to 7 minutes in for information about clearing current drive

 

[Peja]

5 minutes ago, Otto_iii said:

Windows crapped itself, your hardware is likely, i'm 99% sure, absolutely fine. 

If BIOS was corrupted you wouldn't be able to get into BIOS or anything and would need to RMA mobo, basically nothing would happen if you tried to boot.  You are atleast getting past boot screen, can get into BIOS, and then onto a point windows craps out.  Windows install just seemed to have corrupted, which isn't too surprising if you are using a install from a different system.  Even though Windows 10 can transfer from different hardware its likely you will have issues, updating the BIOS which could have changed things like the CPU instructions likely made it so you finally ran into a big one.  


If you can get onto your own backup computer, if not that then a friends/family computer and make a bootable Windows 10 install onto a USB, boot from that, clear and format the current drives (if you need data from current boot drive then recover it by plugging them in on another working PC first/and or buy a new small hdd/ssd to install windows onto and boot from) then there shouldn't be a problem after the fact. 

This is one of the easier and clearer windows install guides i know, pay attention closely from 3 to 7 minutes in for information about clearing current drive

 

Hi Otto, 

 

I have created two different bootable drives now and similar result unfortunately :(, I will give it a go once more even though. I'm currently getting these same results using an actual win10 retail usb that is only about 2 weeks old from a friend's recent build.

 

That video you posted is something I've already watched and tried multiple times, along with some other videos, and nothing seems to be working for me unfortunately, hence why I turned to the forums in the end :(.

 

My last option might be trying to revert the BIOS back to original, but am kind of scared to try that to be honest!

[Peja]

16 minutes ago, lee32uk said:

You can give it a try and see if it will let you. I have seen people roll back their bios but it might not have been on an Asus board. That is why I like Gigabyte as they have dual bios on a lot of their boards.

 

You can try using the bios flashback button on the back of the board. Just make sure to follow the instructions i.e renaming the bios file.

I will give this a try once there's absolutely nothing left to try, as I'm scared of what could happen if I do this haha!

[Mark Kaine]

58 minutes ago, Peja said:

Xmp is a Intel thing? I'm on an amd platform, everything is default settings nothing's over clocked, and I can't really download anything as I can't even install windows so I have nothing to really work with. I can get into BIOS and that's about it.

Nope. Usually it's a BIOS thing

 

3 minutes ago, Caroline said:

y tho

Yep,  never update your BIOS if the system is working fine 

[Peja]

Fresh build and all videos etc recommend to update bios. Also I'm a bit of an idiot that always likes to have everything up to date, and that BIOS update was just nagging me lol.

[Peja]

16 minutes ago, Caroline said:

y tho

 

does it works if you try to boot a linux live disc?

if you're using USB are you trying to create media using rufus? if so, use something else

I don't have a linux live disc, and I wasn't using Rufus, just had 2 fresh usbs laying around and did it through windows download option that let's you create a Bootable Windows usb.

[Otto_iii]

47 minutes ago, Peja said:

Hi Otto, 

 

I have created two different bootable drives now and similar result unfortunately :(, I will give it a go once more even though. I'm currently getting these same results using an actual win10 retail usb that is only about 2 weeks old from a friend's recent build.

 

That video you posted is something I've already watched and tried multiple times, along with some other videos, and nothing seems to be working for me unfortunately, hence why I turned to the forums in the end :(.

 

My last option might be trying to revert the BIOS back to original, but am kind of scared to try that to be honest!

Sorry to hear that, just wanted to check as usually i'd think it would work

Going to guess you already have as i'd doubt you haven't looked into this if you already watched reinstal etc video, but have you tried anything like this with current install?

or some alternatives, further here

23 minutes ago, Peja said:

Fresh build and all videos etc recommend to update bios. Also I'm a bit of an idiot that always likes to have everything up to date, and that BIOS update was just nagging me lol.

Nothing wrong with that, i wouldn't feel too bad, doubt this was your fault. 

[Peja]

Problem is, I can't get pass this screen at all!

[Whiro]

Did you tried loading windows on another drive? Maybe try ssd and see if that working.

[Peja]

I don't have windows at all, all my drives are completely empty with nothing on them (reformatted), straight after selecting win 10 64 I get that other screenabout missing kernel. 

 

I don't even get the option to choose a drive that I'd like to install windows on or anything

[Peja]

Also, just flashed BIOS back to original version and still same issue.

[Whiro]

Reading some windows forum ppl suggested that it may be a issue with drive connection

 

“ I would check/replace the sata cable. You might also try and putting the data cable on a different sata controller/port. files are being corrupted as the are being transferred from storage. It could be the drive, the data cable, even a bad connection on a power cable can make and break a connection several times a second. generally the bugcheck suberror code can help but it would most likely show an io error“ 

 

What I would do is try to take out all drives, including your m.2, plug the ssd using different port you using now and than try to install windows. If that not gonna work maybe there is some problem with your installation usb drive?!? I usually using rufus to create bootable drives.

[Peja]

Hi,

I have already tried all those things you have suggested, I have 3 different bootable drives two created by me and one is a genuine win10 usb only two weeks old. 

 

I have tried the m2 and also the other sata ssd, tried plugging the 860 evo into 3 different ports now and nothing seems to work. 

[Whiro]

What about downgrading bios to previous one?? Any chance doing that? 

[Peja]

Have done that, finally it let me install windows,  after reseating everything a few times, but am now getting stuck on code 0D detect hdd.