PC Boot/Shutdown problems

GEE93

Commendable
May 15, 2016
15
0
1,520
So this post is basically two problems in one but posting together as unsure if related.

The first issue is on boot up my pc seems to be working fine, everything seems in working order apart from no signal is output to my monitor and it stays off, it doesn’t happen all the time but when it does leaving it does nothing so I have to restart and hope it works the next time.

The second issue is on shutdown my pc will close applications, the monitor will go off but then the pc itself keeps running for 5-10 mins and one time it even restarted after that duration.

Any suggestions would be greatly appreciated I’ve already tried multiple things for both some including changing boot timer, turning of the fast startup, disk clean up but none seem to work. If you need any additional info from me just ask

Thanks for your help in advance :)
 
Solution
What are the system components?

Settings in the BIOS can get corrupted or overwritten. That is the purpose of clearing the CMOS. It returns the BIOS to the default settings, and in most cases allows you to boot the computer. Without the feature, you have a catch 22 that you need to enter the BIOS to reset the BIOS. But you can't enter the BIOS because it will not boot. It would brick the system.

As to what happened, either a driver or a portion of the operating system became corrupted or overwritten (meaning that it is now missing or invalid).

Updating the BIOS corrects or replaces the corrupted files. It also allows updates in the BIOS version to address known issues (like device compatibility for example).
I would recommend going into the BIOS and resetting it to the defaults. Then re-enter the boot order, memory settings or XMP, fans, etc . Then save everything on exit.

Next to correct the monitor problem, i would recommend reseating the memory. Remove each memory stick one at a time, clean the contacts, blow out the slot, firmly reinstall, and then repeat for the remaining sticks. Also make sure that memory sets are installed in the same color coded slots. Make sure that the lever on the memory slot is all of the way up.


Then do the same procedure to reseat the graphics card. Then firmly reconnect and PCIE power cables to the graphics card (if needed).

Then remove the monitor cable and power cord from the monitor for a minute or so then reconnect every thing. That will reset the monitor.

Then reboot and evaluate your repair work.
 
Hi terry4536, thanks for the response with regards to fixing my monitor problem I did re-seat the ram yesterday and ensured they were in the correct slots and my computer appeared to boot up fine. With regards to resetting my BIOS what do you think the problem could be? My cpu is OC but it worked fine for months and its only recently that I have had problems; none of my hardware has changed.
 
What are the system components?

Settings in the BIOS can get corrupted or overwritten. That is the purpose of clearing the CMOS. It returns the BIOS to the default settings, and in most cases allows you to boot the computer. Without the feature, you have a catch 22 that you need to enter the BIOS to reset the BIOS. But you can't enter the BIOS because it will not boot. It would brick the system.

As to what happened, either a driver or a portion of the operating system became corrupted or overwritten (meaning that it is now missing or invalid).

Updating the BIOS corrects or replaces the corrupted files. It also allows updates in the BIOS version to address known issues (like device compatibility for example).
 
Solution
I'm Having a similar issue for some months now and couldn't find a solution as this issue is random.
My fix: unplug the monitor power cord and plug it back on... yup, it takes 2-3s though

I have an RX480/8Gb with a 4k Korean monitor. I've tried many different cables but my guess is a bug within AMD driver regarding the communication with the monitor which doesn't wake up after a while. i don't think it can be related to any RAM/CPU or anything hardware... more likely poor monitor firmware or faulty graphic driver (or another windows bug, lol)