3 weeks ago
This is the first PC that I've built in about 10 years. I thought it would be a simple exercise but so far it's been nothing but frustrating.
The chain of events:
After some initial issues configuring the BIOS I was eventually able to install a fresh copy of Windows 11 Pro, download/install windows updates, and the driver/tools listed on the support page. Windows appeared to be running normally. I noticed CoPilot was installed and attempted to disable it. It was getting late and I was tired so I don't remember exactly but I think I enabled XMP in the BIOS and turned off the computer. In the morning I put the side panels on the case and moved it across the room next to the desk I'll be using. When I tried to turn on the computer it wouldn't POST and just gave me a 99 Q-Code with a green LED below.
Things I've tried to resolve the issue over the last several days:
Components in the build:
My hope is some very smart person will be able to point to something stupid/silly I'm doing wrong. It would be great to actually be able to use this computer that I've spent so much money to build...
Solved! Go to Solution.
3 weeks ago
let do something. remove all drivies MINUS the os one. Let do a test. IF ALL FAIL then rrma.
Ise at the time. sorry this. but is the only way. 1 m2 on m2_1 and monitor the situacion. make sure the bios is up to date and and load defaults. IF POST let me known have windows ready usb just in case DO NOT USE any bugus, cut side etc of windows. and we make some changes also. one at the time. better this than get another board and was the nvmes all allong. just in case. and please 1 kit. make sure the 2 stick are from the corresponding kit.
c
3 weeks ago - last edited 3 weeks ago
1. aside those 3 nvmes there is something else?
2. any of those drive have data?
code 99 on green is boot / drives
For testing lose 1 kit of ram. You can not mix it, and will not post anyway. so let dig one at the time first we need to fix that and enter bios
Use ONLY the last bios Do not drop bios even "code 029 is or was apply"
3 weeks ago
1. There's only those three name drives. I don't have any SATA drives installed.
2. One drive has Windows installed and should be the boot drive. One drive has a couple steam games installed. I think the last drive was empty but allocated in Windows.
3. At the moment I don't have the name drives installed in the hyper card because I thought it would eliminate one variable. When I did have it installed I had it in the bottom slot (the G4).
3 weeks ago
let do something. remove all drivies MINUS the os one. Let do a test. IF ALL FAIL then rrma.
Ise at the time. sorry this. but is the only way. 1 m2 on m2_1 and monitor the situacion. make sure the bios is up to date and and load defaults. IF POST let me known have windows ready usb just in case DO NOT USE any bugus, cut side etc of windows. and we make some changes also. one at the time. better this than get another board and was the nvmes all allong. just in case. and please 1 kit. make sure the 2 stick are from the corresponding kit.
c
2 weeks ago
I marked your answer as the correct answer since this was the basic plan we used during our Discord call/chat to diagnose that the motherboard was defective.
Since the motherboard was defective I returned it to the store, and bought a replacement motherboard directly from Asus/ROG.
3 weeks ago - last edited 3 weeks ago
and also
I send you a private msg