- last edited on by
ROGBot
Hi All,
I was changing my to the second one via the onboard button, my system must have been unstable at the time as it decided to give me the updating BIOS screen and then just cut off and kept looping from there on.
I then tired to go back to BIOS one but that was the same problem, so I cleared the CMOS. After that I could access the BIOS again, although Windows won't boot with an error of "IO1_INITIALIZATION_FAILED".
So I tried to flash (EZ Flash 2 Utility) the BIOS and it processed way too quickly and it says updating BIOS a couple of times until it comes to the overclocking failed screen...
Any ideas on how to fix this?
Thanks,
Jamie
I was changing my to the second one via the onboard button, my system must have been unstable at the time as it decided to give me the updating BIOS screen and then just cut off and kept looping from there on.
I then tired to go back to BIOS one but that was the same problem, so I cleared the CMOS. After that I could access the BIOS again, although Windows won't boot with an error of "IO1_INITIALIZATION_FAILED".
So I tried to flash (EZ Flash 2 Utility) the BIOS and it processed way too quickly and it says updating BIOS a couple of times until it comes to the overclocking failed screen...
Any ideas on how to fix this?
Thanks,
Jamie
Arne Saknussemm wrote:
Use BIOS flashback method (maybe after leaving battery out and PSU off for an hour and clearing CMOS)
Although if you can get into BIOS then BIOS might be OK and you've done something to Windows install...
https://answers.microsoft.com/en-us/windows/forum/windows_10-performance/getting-blue-screen-error-i...
I can boot UnRAID although I can't start any Windows VM's or they crash, so I have a feeling that it's just Windows altogether not just that one install.
Also I have already followed the steps in that post, the next step is to reinstall which I really don't want to do.
Looks like the BIOS flashback method didn't work either 😞
I have a BIOS it's just the matter of whether it is 100%, I did the BIOS Flashback.
I removed all devices / drives apart from my NVMe drive that has my Windows installation, I still had the same problem. I followed the steps on the Windows forum also.
I ended up putting Windows on a USB to fresh install, but that gave me a MACHINE_CHECK_EXCEPTION.
I also tried my UnRAID install (https://lime-technology.com/) which is a Linux distro and has a couple of Windows VM's, this is installed on a portable hard drive that I can boot on any machine. The Windows VM's would crash the whole system.
I just feel that there is a bigger problem. It just seems to be Windows that I can't run no matter if it's a new or an old install.
I removed all devices / drives apart from my NVMe drive that has my Windows installation, I still had the same problem. I followed the steps on the Windows forum also.
I ended up putting Windows on a USB to fresh install, but that gave me a MACHINE_CHECK_EXCEPTION.
I also tried my UnRAID install (https://lime-technology.com/) which is a Linux distro and has a couple of Windows VM's, this is installed on a portable hard drive that I can boot on any machine. The Windows VM's would crash the whole system.
I just feel that there is a bigger problem. It just seems to be Windows that I can't run no matter if it's a new or an old install.
Sorry I'm just panicking as I have my dissertation to do and can't do it without that machine 😞
I've just tried a new approach using http://www.easyuefi.com/wintousb/, which creates a portable version of Windows.
I got this wonderful error:
I got this wonderful error:
Arne Saknussemm wrote:
Have you removed RAM and tried one stick at a time in recommended slot? removed all drives and peripherals...stripped system back.
Was it overclocked?
Do you have a spare drive about to try a clean normal win install.
I have tried moving the RAM .etc it was overclocked... It's on the failsafe defaults now though.
I've also tried remove all the peripherals / drives too.
I have tried a clean install although the installer crashes the system at different points, mainly at "Setup is Starting".
