• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

[SOLVED] Hardware/software restart not working in new Windows 8 build

RapidSnail

Diamond Member
SOLVED
Apparently, I was supposed to flash the new BIOS and Intel ME (see below) in order for the motherboard to work properly with Haswell refresh. Everything works perfectly now that I have done that!

I just completed a new build with the parts listed below. Assembly went smoothly with only an issue getting the initial POST (PSU needed to be recycled). Windows 8 was installed from a USB flash drive. The MSI Z87I AC BIOS was flashed to version 1.6 to ensure compatability with the i5-4690 Haswell refresh CPU. Drivers where installed from the CDs included with the motherboard.

The problem lies in restarting the PC, either by the hard button on the chassis, or in the OS, software, or BIOS ("save and restart"). What happens in either instance, is the screen goes black, as if maybe it is going through the restart process, but then nothing happens. After 5-10 seconds the display shows a "No signal detected" message and goes into standby. However, the PC hardware is still receiving power, as the case LEDs and system fans are still running. The only way out of this is to shut down the PC by holding the power button for a few seconds and then turn it back on.

For example, when updating Windows, the PC installed the updates and then tried to reboot, however, I was forced to manually power down and restart the computer after the screen went to standby. I must do the same thing when any other software or update requires a reboot. This was particularly unnerving when I was installing Windows and flashing the BIOS, as I got scared that something went wrong and had to power cycle the PC. Fortunately, I did this after the display went into standby, which signifies that the PC was trying to reboot, and did not brick the motherboard. Other than the inconvenience of hard-resetting the PC, there does not seem to be any negative consequence to doing this.

Of course I would like to figure out what could be causing this behavior so that the PC can function normally, especially since it is being used by individuals with little technological savvy. Any advice and input is greatly appreciated! 🙂

Hardware

CPU: Intel Core i5-4690 3.5GHz
CPU Cooler: Corsair H90
GPU: Intel HD 4600 IGP
Motherboard: MSI Z87I AC Mini ITX
RAM: G.Skill Ripjaws X Series 8GB DDR3-2400
SSD: Samsung 840 EVO 120GB
HDD: Western Digital Caviar Blue 1TB 3.5"
Case: BitFenix Prodigy Mini ITX
PSU: SeaSonic 620W 80+ Bronze
Monitor: Acer T272HUL 27.0" Touchscreen
 
Last edited:
Looks similar to the attached image (not mine) for the most part. I'm assuming that means it's UEFI as the BIOS on my six year old Abit LGA 775 board looks like a primitive keyboard-text interface by comparison.

msi-uefi-oc.jpg
 
I was able to figure out the problem with the help of MSI tech support! Apparently, I needed to flash the BIOS and Intel ME (see below) in order to allow comparability between the motherboard and Haswell refresh CPU. Once I reflashed BIOS/ME everything went to normal! Reboots and cold boots are lightning fast with fast boot options enabled. I can get to the desktop in about 3 seconds from power off!

Thanks to postmortemIA for contributing to the thread. Hopefully, this can help others with similar problems on Haswell refresh. 🙂

iAhd6WY.png

Of4WnoW.png
 
good to hear, believe or not I had similar experience with older C2D build when upgrading the CPU... BIOS update (included IME) had to be done with the new CPU itself. IT was not enough that I was already on latest... The problem was that thermal characteristics of one CPU were much different than the new one. I thought that wouldn't be your problem as you mentioned you upgraded the BIOS
 
Back
Top