F5F Stay Refreshed Hardware Desktop Account settings caused a major system issue preventing posts.

Account settings caused a major system issue preventing posts.

Account settings caused a major system issue preventing posts.

E
EvanEmma38
Junior Member
13
03-07-2018, 12:09 AM
#1
COMPUTER CONFIGURATION: Motherboard Model: Gigabyte X399 Arous Pro REV1.0 with BIOS F2 CPU: AMD Ryzen Threadripper 2970WX 24 CORES RAM: G.SKILL Trident Z RGB 2 sticks of 16GB F4-3200C16D-32GTZR GPU: NVIDIA Quadro RTX 4000 PSU: Thermaltake 850W RGB Gold Observations: The system failed to boot, yet displayed video signals on the screen. Fans operated normally, and the AMD X399 PRO chipset lights illuminated. Noted: Status LEDs indicated CPU activity for roughly 20 seconds showing codes 0d or possibly Dd—uncertain if it was an uppercase D or zero. Then transitioned to codes 15, C2, B7, and DRAM status, remaining there for similar periods. Eventually, it attempted VGA, BOOT, and then resumed in a continuous loop until the machine shut down. After restarting, it tried the same sequence again. Possible causes: Recent Windows update, compromised account privileges, or integration issues with Windows Hello during login. The Logitech Brio 4k webcam worked without problems. When running admin tasks or downloading files, the User Account Configuration dialog appeared, prompting a YES/NO choice—previously functional but now blocked by Windows Hello integration. Glitches occurred when attempting to confirm ownership. Troubleshooting steps included entering Safe Mode via Command Prompt with "SHUTDOWN /R /O -T 00," accessing UEFI settings, and navigating through startup options. However, issues persisted. Logical steps tried: resetting CMOS with jumper wires, clearing CMOS battery, removing and reinserting the power cable, resetting BIOS via manual instructions, changing RAM channels, swapping GPU slots, disabling M.2 SSDs, and adjusting ATX power connections. None resolved the problem. Rebuilding the system offered no improvement. The LED codes remained unchanged, suggesting persistent hardware or firmware faults. I followed all guides meticulously, yet the cycle continued indefinitely until power was cut. If this helps, please review the attached article for further guidance. Thank you for your time and support.
E
EvanEmma38
03-07-2018, 12:09 AM #1

COMPUTER CONFIGURATION: Motherboard Model: Gigabyte X399 Arous Pro REV1.0 with BIOS F2 CPU: AMD Ryzen Threadripper 2970WX 24 CORES RAM: G.SKILL Trident Z RGB 2 sticks of 16GB F4-3200C16D-32GTZR GPU: NVIDIA Quadro RTX 4000 PSU: Thermaltake 850W RGB Gold Observations: The system failed to boot, yet displayed video signals on the screen. Fans operated normally, and the AMD X399 PRO chipset lights illuminated. Noted: Status LEDs indicated CPU activity for roughly 20 seconds showing codes 0d or possibly Dd—uncertain if it was an uppercase D or zero. Then transitioned to codes 15, C2, B7, and DRAM status, remaining there for similar periods. Eventually, it attempted VGA, BOOT, and then resumed in a continuous loop until the machine shut down. After restarting, it tried the same sequence again. Possible causes: Recent Windows update, compromised account privileges, or integration issues with Windows Hello during login. The Logitech Brio 4k webcam worked without problems. When running admin tasks or downloading files, the User Account Configuration dialog appeared, prompting a YES/NO choice—previously functional but now blocked by Windows Hello integration. Glitches occurred when attempting to confirm ownership. Troubleshooting steps included entering Safe Mode via Command Prompt with "SHUTDOWN /R /O -T 00," accessing UEFI settings, and navigating through startup options. However, issues persisted. Logical steps tried: resetting CMOS with jumper wires, clearing CMOS battery, removing and reinserting the power cable, resetting BIOS via manual instructions, changing RAM channels, swapping GPU slots, disabling M.2 SSDs, and adjusting ATX power connections. None resolved the problem. Rebuilding the system offered no improvement. The LED codes remained unchanged, suggesting persistent hardware or firmware faults. I followed all guides meticulously, yet the cycle continued indefinitely until power was cut. If this helps, please review the attached article for further guidance. Thank you for your time and support.