new CPU black screen

[danlar]

hi, im trying to upgrade a G3420 to a 4770k on a Asrock h81m dgs 2.0 mobo but i get black screen with the 4770k.. is it a bios reset or upgrade i need to fix it? current bios version is p1.20

[WarmedxMints]

No update should be required. Check the cpu is installed correctly. It may just be a faulty cpu.

[danlar]

Originally posted by WarmedxMints:

No update should be required. Check the cpu is installed correctly. It may just be a faulty cpu.

huh that sounds bad.. im pretty sure i installed it correctly.. thought it might be because it thinks its meant to be a G3420 running and not the 4770k and i had to update or reset something for it to accept the new CPU :/

[Bad 💀 Motha]

Intel CPUs may be pin-less on the CPU-side, however, if they are not 100% perfectly aligned in the stock, it won't boot.

Careful remove the CPU and then take a flashlight and inspect the socket on the board. Go over looking at it carefully from a few angles and see if any pins are bent. If/when you reinstall your CPU, ensure it's completely flush before applying the clamping system.

No it doesn't "think" anything, CPUs, RAM... everything is looked at on a first time basis every single time you cold boot.

Simply try reset cmos jumper and then try booting again.
Many boards no longer have any reset cmos pins.
If this is true for you, turn off main PSU power switch, remove cmos coin battery.
Then press and hold Case Power Button for about 15 secs. Then reinstall battery and power system back on and the BIOS will now be all Default settings.

[danlar]

Originally posted by Bad_Motha:

Intel CPUs may be pin-less on the CPU-side, however, if they are not 100% perfectly aligned in the stock, it won't boot.

Careful remove the CPU and then take a flashlight and inspect the socket on the board. Go over looking at it carefully from a few angles and see if any pins are bent. If/when you reinstall your CPU, ensure it's completely flush before applying the clamping system.

No it doesn't "think" anything, CPUs, RAM... everything is looked at on a first time basis every single time you cold boot.

thanks

[Bad 💀 Motha]

Please read my edit...

[danlar]

Originally posted by Bad_Motha:

Please read my edit...

ok ill try that :)

[Bad 💀 Motha]

Just please be aware of any changes you had prior, so you can reapply any relevant ones.
Such as maybe enabling XMP for your RAM, a certain SATA Mode perhaps... and also things regarding power management and boot order.

[danlar]

Originally posted by Bad_Motha:

Just please be aware of any changes you had prior, so you can reapply any relevant ones.
Such as maybe enabling XMP for your RAM, a certain SATA Mode perhaps... and also things regarding power management and boot order.

:/ yeah i have no clue about those things.. any chance it can be default settings im running? or can it run on defualt?

[Bad 💀 Motha]

In most configs, there is nothing to change anyways.

> Time & Date
> Boot Drive Order (make your OS SSD or HDD first, nothing else should be listed, or those should be below the OS drive to avoid any unwanted booting attempts from say Optical Disc or USB Drives)
> If do not need, disable all power management and wake on lan. This helps prevent things like PC auto powering on unattended, etc.
> Check SATA Mode, but given your board, AHCI should already be the default, which is what you want for modern OS. IDE Mode is only for Legacy OS'

[danlar]

Originally posted by Bad_Motha:

In most configs, there is nothing to change anyways.

> Time & Date
> Boot Drive Order (make your OS SSD or HDD first, nothing else should be listed, or those should be below the OS drive to avoid any unwanted booting attempts from say Optical Disc or USB Drives)
> If do not need, disable all power management and wake on lan. This helps prevent things like PC auto powering on unattended, etc.
> Check SATA Mode, but given your board, AHCI should already be the default, which is what you want for modern OS. IDE Mode is only for Legacy OS'

hmm ok thanks

[danlar]

thank you Bad_Motha clearing cmos/bios reset fixed it.