- Jan 19, 2018
- 3
- 0
- 520
Specs:
CPU: Ryzen 1800x
Motherboard: Asus Crosshair VI Hero
RAM: HyperX FURY DDR4 HX424C15FB2K2/16G 2400MHz (2 sticks of 8GB)
M.2 Storage: Samsung 960 Evo 250GB
Additional HDD storage (Which was not connected during OS install): Seagate 1TB
GPU: Asus Rog Strix-Gtx1080-A8G
PSU: Corsair
AIO: NZXT Kraken x61
OS: Windows 10 Education, then I moved to Windows 10 Pro
No overclocking to CPU or RAM has been done
During the installation, the additional drive was not connected to the motherboard.
The USB for both Windows 10 Education/Pro x64 of the installations I have performed using the GPT partition scheme for UEFI and FAT32 file system as it is pretty much standard for a new system these days.
CSM -> Disabled
Secure boot state -> Enabled
OS Type -> Windows UEFI mode
+ Installed Default Secure Boot Keys
Okay, so I really don't know where to start. I bought all my parts in the last week of November and the first week of December. Sadly I had to wait another 10+ days for my AM4 mounting bracket to get shipped from the USA and I ended up going home for the holidays and leaving my build unfinished. After nearly a month I managed to build it YEY, but sadly the excitement didn't last for long. Before the first installation began, I cleared the CMOS.
It all started with a clean install of Windows 10 Education x64 (yes I am a student). At first, the system booted without a problem. After the install, I noticed that the Q-CODE 24 was being displayed and tried to google it, turned out to be normal. Reference from a post on tomshardware:
"Qcode 24 is nothing to worry about as this is the readout when you successfully Boot to Windows."
Link to Q-CODE image below:
https://imgur.com/a/xU3XE
Installed all necessary drivers and proceeded with flashing the bios to Version 3008. I even got the chance to test it in in a couple of games and it didn't seem to have any issues or what so ever. The problems started after windows decided to crash while performing the 'important' security patches. From this point on the pc decided not to boot to Windows. My first choice was to repair the OS as normally anybody would do so. The OS repaired itself and everything looked fine at the start. I started as usual by installing all the necessary drivers and system crashed again while I the NVME driver was being installed. After a second fail attempt I decided to flash the BIOS to the previous version, which didn't help at all. This time the system crashed while installing the Graphics card drivers.
As you would get at this point I got the same exact crash even after going for Windows 10 Pro. What caught my eye was that the system was going through the Power-On-Self-Tests without any issues. Right after this the Windows logo would appear as normal with the loading animation moving and followed by a black screen with no image output from the system. Oddly tho the HDD light would continue to flicker.
So far I have tried to troubleshoot the following on my own without any improvements:
1. Contacted Asus about my unusual problems, but I am still waiting for their response.
2. Switched off the graphics card in my system with the exact same 1080 I have.
3. Tried rotating the RAM sticks between the DIM's and running single channel.
4. Installed the OS on the additional storage drive in exactly the same sequence I did before.
5. Tried out using MBR partition scheme for BIOS or UEFI.
I am still yet to try with another RAM sticks which I would try and get from a friends PC, but I highly doubt they will be compatible with my motherboard.
CPU: Ryzen 1800x
Motherboard: Asus Crosshair VI Hero
RAM: HyperX FURY DDR4 HX424C15FB2K2/16G 2400MHz (2 sticks of 8GB)
M.2 Storage: Samsung 960 Evo 250GB
Additional HDD storage (Which was not connected during OS install): Seagate 1TB
GPU: Asus Rog Strix-Gtx1080-A8G
PSU: Corsair
AIO: NZXT Kraken x61
OS: Windows 10 Education, then I moved to Windows 10 Pro
No overclocking to CPU or RAM has been done
During the installation, the additional drive was not connected to the motherboard.
The USB for both Windows 10 Education/Pro x64 of the installations I have performed using the GPT partition scheme for UEFI and FAT32 file system as it is pretty much standard for a new system these days.
CSM -> Disabled
Secure boot state -> Enabled
OS Type -> Windows UEFI mode
+ Installed Default Secure Boot Keys
Okay, so I really don't know where to start. I bought all my parts in the last week of November and the first week of December. Sadly I had to wait another 10+ days for my AM4 mounting bracket to get shipped from the USA and I ended up going home for the holidays and leaving my build unfinished. After nearly a month I managed to build it YEY, but sadly the excitement didn't last for long. Before the first installation began, I cleared the CMOS.
It all started with a clean install of Windows 10 Education x64 (yes I am a student). At first, the system booted without a problem. After the install, I noticed that the Q-CODE 24 was being displayed and tried to google it, turned out to be normal. Reference from a post on tomshardware:
"Qcode 24 is nothing to worry about as this is the readout when you successfully Boot to Windows."
Link to Q-CODE image below:
https://imgur.com/a/xU3XE
Installed all necessary drivers and proceeded with flashing the bios to Version 3008. I even got the chance to test it in in a couple of games and it didn't seem to have any issues or what so ever. The problems started after windows decided to crash while performing the 'important' security patches. From this point on the pc decided not to boot to Windows. My first choice was to repair the OS as normally anybody would do so. The OS repaired itself and everything looked fine at the start. I started as usual by installing all the necessary drivers and system crashed again while I the NVME driver was being installed. After a second fail attempt I decided to flash the BIOS to the previous version, which didn't help at all. This time the system crashed while installing the Graphics card drivers.
As you would get at this point I got the same exact crash even after going for Windows 10 Pro. What caught my eye was that the system was going through the Power-On-Self-Tests without any issues. Right after this the Windows logo would appear as normal with the loading animation moving and followed by a black screen with no image output from the system. Oddly tho the HDD light would continue to flicker.
So far I have tried to troubleshoot the following on my own without any improvements:
1. Contacted Asus about my unusual problems, but I am still waiting for their response.
2. Switched off the graphics card in my system with the exact same 1080 I have.
3. Tried rotating the RAM sticks between the DIM's and running single channel.
4. Installed the OS on the additional storage drive in exactly the same sequence I did before.
5. Tried out using MBR partition scheme for BIOS or UEFI.
I am still yet to try with another RAM sticks which I would try and get from a friends PC, but I highly doubt they will be compatible with my motherboard.
Facebook
Twitter
Instagram