Blinking Cursor After CMOS Wipe

[TypoKign1]

After an over clocking failure, I had to wipe my CMOS. Now, I get a blinking white cursor after the BIOS loads.

If I had to guess, I would say it's happening because I have partitioned my SSD in order to dual-boot Win10 and Ubuntu. Before the wipe, I would boot into Grub after the BIOS.

Thanks!

 

[DeadlyDays]

Is the bios booting from the drive that has GRUB loaded, or is it defaulting to a drive that has a corrupting windows boot manager. Would be my initial suspicion.

 

[TypoKign1]

Is the bios booting from the drive that has GRUB loaded, or is it defaulting to a drive that has a corrupting windows boot manager. Would be my initial suspicion.

Grub and Windows are on two different partitions of the same drive. This drive is the first priority in the BIOS

 

[Chugalug_]

Is the bios booting from the drive that has GRUB loaded, or is it defaulting to a drive that has a corrupting windows boot manager. Would be my initial suspicion.

Grub and Windows are on two different partitions of the same drive. This drive is the first priority in the BIOS

Are you able to change the order in which the partitions boot?
Because as I remember, back in windows 7 people used to have issues with Ubuntu Grub booting first on partitioned drives.... I don't know if the same applies here, but its worth a try if you can change the boot order to windows first.

 

[TypoKign1]

Is the bios booting from the drive that has GRUB loaded, or is it defaulting to a drive that has a corrupting windows boot manager. Would be my initial suspicion.

Grub and Windows are on two different partitions of the same drive. This drive is the first priority in the BIOS

Are you able to change the order in which the partitions boot?
Because as I remember, back in windows 7 people used to have issues with Ubuntu Grub booting first on partitioned drives.... I don't know if the same applies here, but its worth a try if you can change the boot order to windows first.

I couldn't find a way to boot from a specified partition in the BIOS 🙁

Any other suggestions?

 

[DeadlyDays]

everything was working up to clearing the bios settings yes? and no changes after the wipe and immediately this problem yes?

 

[TypoKign1]

everything was working up to clearing the bios settings yes? and no changes after the wipe and immediately this problem yes?

Everything was a-ok before wiping.

After wiping I only changes a few CPU settings (Virtualization, vt-d, and nxmp if I recall correctly)

 

[Chugalug_]

everything was working up to clearing the bios settings yes? and no changes after the wipe and immediately this problem yes?

Everything was a-ok before wiping.

After wiping I only changes a few CPU settings (Virtualization, vt-d, and nxmp if I recall correctly)

Did you attempt to initially boot without changing any settings? or did you just change these off the bat? because my guess is that the system may not have fully recognised the drive seeing as it was booting a new drive. Try wiping it again and booting without changing any settings. Sounds a bit strange, but has happened to a friend before.

 

[TypoKign1]

everything was working up to clearing the bios settings yes? and no changes after the wipe and immediately this problem yes?

Everything was a-ok before wiping.

After wiping I only changes a few CPU settings (Virtualization, vt-d, and nxmp if I recall correctly)

Did you attempt to initially boot without changing any settings? or did you just change these off the bat? because my guess is that the system may not have fully recognised the drive seeing as it was booting a new drive. Try wiping it again and booting without changing any settings. Sounds a bit strange, but has happened to a friend before.

Didn't help 🙁

 

[Chugalug_]

everything was working up to clearing the bios settings yes? and no changes after the wipe and immediately this problem yes?

Everything was a-ok before wiping.

After wiping I only changes a few CPU settings (Virtualization, vt-d, and nxmp if I recall correctly)

Did you attempt to initially boot without changing any settings? or did you just change these off the bat? because my guess is that the system may not have fully recognised the drive seeing as it was booting a new drive. Try wiping it again and booting without changing any settings. Sounds a bit strange, but has happened to a friend before.

Didn't help 🙁

Afraid that's as much as I know, best bet to send it to your local IT store and get them to troubleshoot the hardware.

 

[DeadlyDays]

Try booting it from a bootdisk(basically just a disk with GRUB on it), if it works try reinstalling GRUB.

EDIT, is your motherboard in IDE or AHCI mode for interfacing with the drives, and is that what it was before. Also is this actually UEFI, if so, I've had the case where there are two instance of the boot drive and booting the other one worked.