F5F Stay Refreshed Hardware Desktop Asus Crosshair VI hero launches smoothly. ROG branding appears lengthy.

Asus Crosshair VI hero launches smoothly. ROG branding appears lengthy.

Asus Crosshair VI hero launches smoothly. ROG branding appears lengthy.

Pages (2): 1 2 Next
G
62
10-05-2017, 03:15 PM
#1
Recently added some improvements to my system. The components are listed below, with new items highlighted in parentheses: Asus ROG Crosshair VI Hero (mobo) AMD Ryzen 7 1700X Asus Strix GTX 1080 8GB Corsair Vengeance RGB 2x8GB 3200mhz Corsair Vengeance RGB PRO 2x8gb 3200mhz (NEW PART) Samsung 970 EVO M.2 1TB *main drive* (NEW PART) Samsung 850 EVO 250GB SSD *secondary storage* Corsair CS650M PSU After completing the installation, I ran Samsung's migration utility to move all Windows and personal files onto the new M.2 slot. Everything proceeded smoothly. The system booted instantly—impressive! I was thrilled. The next phase involved sanitizing the previous SSD and converting it into a storage device, following Samsung’s instructions and using their erase tool to securely wipe its contents. After erasing, when I restarted Windows, the tool detected the drive but reported no available drivers. Additionally, Windows failed to list it among its storage options. In Device Manager, an unknown device appeared. I checked the BIOS settings and confirmed the M.2 was recognized, though it wouldn’t allow me to select it as a boot device (possibly because it was empty). Assuming I kept all BIOS configurations unchanged, I saved, exited, and the machine powered back on. This time, initializing took considerably longer, then the ROG logo appeared on screen for at least 20 seconds before disappearing. The first boot using the M.2 slot completed in under eight seconds from powering on. After some research, I resolved the SSD problems and successfully configured it as a regular drive. That’s the resolution. What bothers me most is the prolonged startup time and the lingering ROG logo display after powering up. I updated the motherboard BIOS to the latest version, but no changes were reflected. All Windows drivers remain current. I’m uncertain if any BIOS adjustments might have caused this issue. I plan to share a video or screenshot of my settings to help others identify the problem. Looking forward to your insights! Thanks!
G
GalaxyofSkulls
10-05-2017, 03:15 PM #1

Recently added some improvements to my system. The components are listed below, with new items highlighted in parentheses: Asus ROG Crosshair VI Hero (mobo) AMD Ryzen 7 1700X Asus Strix GTX 1080 8GB Corsair Vengeance RGB 2x8GB 3200mhz Corsair Vengeance RGB PRO 2x8gb 3200mhz (NEW PART) Samsung 970 EVO M.2 1TB *main drive* (NEW PART) Samsung 850 EVO 250GB SSD *secondary storage* Corsair CS650M PSU After completing the installation, I ran Samsung's migration utility to move all Windows and personal files onto the new M.2 slot. Everything proceeded smoothly. The system booted instantly—impressive! I was thrilled. The next phase involved sanitizing the previous SSD and converting it into a storage device, following Samsung’s instructions and using their erase tool to securely wipe its contents. After erasing, when I restarted Windows, the tool detected the drive but reported no available drivers. Additionally, Windows failed to list it among its storage options. In Device Manager, an unknown device appeared. I checked the BIOS settings and confirmed the M.2 was recognized, though it wouldn’t allow me to select it as a boot device (possibly because it was empty). Assuming I kept all BIOS configurations unchanged, I saved, exited, and the machine powered back on. This time, initializing took considerably longer, then the ROG logo appeared on screen for at least 20 seconds before disappearing. The first boot using the M.2 slot completed in under eight seconds from powering on. After some research, I resolved the SSD problems and successfully configured it as a regular drive. That’s the resolution. What bothers me most is the prolonged startup time and the lingering ROG logo display after powering up. I updated the motherboard BIOS to the latest version, but no changes were reflected. All Windows drivers remain current. I’m uncertain if any BIOS adjustments might have caused this issue. I plan to share a video or screenshot of my settings to help others identify the problem. Looking forward to your insights! Thanks!

C
Carnlife
Junior Member
29
10-11-2017, 10:34 PM
#2
Enable Fast Boot through the BIOS settings. Press F2 to access BIOS, then select F7 to start the process. Set Fast Boot as active. Verify that the M.2 device is recognized as the boot drive.
C
Carnlife
10-11-2017, 10:34 PM #2

Enable Fast Boot through the BIOS settings. Press F2 to access BIOS, then select F7 to start the process. Set Fast Boot as active. Verify that the M.2 device is recognized as the boot drive.

O
Obeey_Me123
Junior Member
15
10-13-2017, 08:32 AM
#3
Unstable RAM configurations and frequent retraining during each boot. Lowering the setting to 2933 or 2800 might resolve the issue. The original IMC settings are unreliable based on personal experience.
O
Obeey_Me123
10-13-2017, 08:32 AM #3

Unstable RAM configurations and frequent retraining during each boot. Lowering the setting to 2933 or 2800 might resolve the issue. The original IMC settings are unreliable based on personal experience.

H
henrikre
Member
220
10-13-2017, 01:13 PM
#4
M.2 is configured as the boot device, and fast startup is activated.
H
henrikre
10-13-2017, 01:13 PM #4

M.2 is configured as the boot device, and fast startup is activated.

Z
Zork9898
Junior Member
1
10-13-2017, 01:50 PM
#5
I haven't adjusted the RAM settings at all. It's operating at 2239 (stock). Also, what is the first generation IMC? lol
Z
Zork9898
10-13-2017, 01:50 PM #5

I haven't adjusted the RAM settings at all. It's operating at 2239 (stock). Also, what is the first generation IMC? lol

C
CoolboyGR
Member
201
10-19-2017, 11:21 PM
#6
RAM training involves BIOS testing various timing settings for stability. Enable DOCP/XMP and observe any changes. If booting doesn't succeed, adjust the memory settings to 2933 or 2800. The Integrated Memory Controller on the CPU manages memory operations, and older CPUs (like the 1700x) find it more challenging to handle multiple memory sticks compared to newer models.
C
CoolboyGR
10-19-2017, 11:21 PM #6

RAM training involves BIOS testing various timing settings for stability. Enable DOCP/XMP and observe any changes. If booting doesn't succeed, adjust the memory settings to 2933 or 2800. The Integrated Memory Controller on the CPU manages memory operations, and older CPUs (like the 1700x) find it more challenging to handle multiple memory sticks compared to newer models.

X
xWaseem09
Member
161
10-22-2017, 12:00 AM
#7
Enable quick startup via BIOS settings in Windows GO, configure boot options for multi-core performance
X
xWaseem09
10-22-2017, 12:00 AM #7

Enable quick startup via BIOS settings in Windows GO, configure boot options for multi-core performance

M
McPollo11
Junior Member
8
10-22-2017, 05:25 AM
#8
Completed the task. It aligns with expectations. Before the SSD problems, initial booting with the new RAM worked smoothly.
M
McPollo11
10-22-2017, 05:25 AM #8

Completed the task. It aligns with expectations. Before the SSD problems, initial booting with the new RAM worked smoothly.

D
DerpUniverse
Member
203
10-27-2017, 07:30 PM
#9
Sure, feel free to share more thoughts!
D
DerpUniverse
10-27-2017, 07:30 PM #9

Sure, feel free to share more thoughts!

F
flarbi
Member
199
10-27-2017, 11:59 PM
#10
The system will no longer have additional memory available for running processes or storing data.
F
flarbi
10-27-2017, 11:59 PM #10

The system will no longer have additional memory available for running processes or storing data.

Pages (2): 1 2 Next