F5F Stay Refreshed Hardware Desktop Are there unusual items appearing only after BIOS post?

Are there unusual items appearing only after BIOS post?

Are there unusual items appearing only after BIOS post?

R
relaxingbedo
Member
55
06-18-2021, 09:07 PM
#1
The main post was updated to remove the white grainy line under the Aorus Eagle that appears every boot. The scratch line now occurs consistently after every Windows installation, unlike before which it was intermittent. I've performed CMOS clears, BIOS resets, updates, and hardware changes except for the motherboard, memory (single slot test with two sticks), and CPU. All components in QVL are fully supported. The retailer staff mentioned this issue occurs with specific hardware setups and isn't a major concern, but it happens frequently? I suspect the problem lies with the CPU or motherboard, as I've verified all other parts except for removing NVMe drives. The system runs on an i5-13400F, RTX 3060 or RTX 1060, DDR5 4800MHz Kingstong Fury Beast, 750W SF Leadex 3 or 650W Seasoning MKII, Seagate DX01 SSD or Mushkin Vortex Redline Gen 4 NVMe, and a Samsung or LG monitor at 60Hz. Stock BIOS settings are enabled except for CSM to access NVMe, which I needed for NVMe access. Operating system is Windows 10.
R
relaxingbedo
06-18-2021, 09:07 PM #1

The main post was updated to remove the white grainy line under the Aorus Eagle that appears every boot. The scratch line now occurs consistently after every Windows installation, unlike before which it was intermittent. I've performed CMOS clears, BIOS resets, updates, and hardware changes except for the motherboard, memory (single slot test with two sticks), and CPU. All components in QVL are fully supported. The retailer staff mentioned this issue occurs with specific hardware setups and isn't a major concern, but it happens frequently? I suspect the problem lies with the CPU or motherboard, as I've verified all other parts except for removing NVMe drives. The system runs on an i5-13400F, RTX 3060 or RTX 1060, DDR5 4800MHz Kingstong Fury Beast, 750W SF Leadex 3 or 650W Seasoning MKII, Seagate DX01 SSD or Mushkin Vortex Redline Gen 4 NVMe, and a Samsung or LG monitor at 60Hz. Stock BIOS settings are enabled except for CSM to access NVMe, which I needed for NVMe access. Operating system is Windows 10.

L
leonardo0803
Member
180
06-20-2021, 02:22 PM
#2
CPU:
CPU cooler:
Motherboard:
Ram:
SSD/HDD:
GPU:
PSU:
Chassis:
OS:
Monitor:
Include the age of the PSU along with its make and model.
BIOS version for your motherboard at this moment?
L
leonardo0803
06-20-2021, 02:22 PM #2

CPU:
CPU cooler:
Motherboard:
Ram:
SSD/HDD:
GPU:
PSU:
Chassis:
OS:
Monitor:
Include the age of the PSU along with its make and model.
BIOS version for your motherboard at this moment?

T
TheCreeper200
Junior Member
8
06-27-2021, 03:38 PM
#3
CPU: intel i5 13400f
CPU cooler: air, cooling 226xt
Motherboard: b760m aorus pro ax ddr5
Ram: 2x8 Kingston fury beast ddr5
SSD/HDD: Mushkin vortex redline gen 4 nvme / Seagate sshd
GPU: rtx 3060 windforce
PSU: superflower 750w ion gold
Chassis: phanteks p4a
OS: win 10 64bit
Monitor: Samsung sync 24inch
Everything appears to be from about a week ago (PSU is now -1, possibly due to delay).
HDD was used first, then NVMe.
Bios was set to f2 default, but the issue persisted. After flashing to f11 it still occurred. Seems like these details aren't important.
T
TheCreeper200
06-27-2021, 03:38 PM #3

CPU: intel i5 13400f
CPU cooler: air, cooling 226xt
Motherboard: b760m aorus pro ax ddr5
Ram: 2x8 Kingston fury beast ddr5
SSD/HDD: Mushkin vortex redline gen 4 nvme / Seagate sshd
GPU: rtx 3060 windforce
PSU: superflower 750w ion gold
Chassis: phanteks p4a
OS: win 10 64bit
Monitor: Samsung sync 24inch
Everything appears to be from about a week ago (PSU is now -1, possibly due to delay).
HDD was used first, then NVMe.
Bios was set to f2 default, but the issue persisted. After flashing to f11 it still occurred. Seems like these details aren't important.