04-10-2024 10:26 PM - edited 04-11-2024 01:40 AM
I bought G513QR in June 2021, and faced this problem in March 2022 at the first time.
I thought "I'm just unlucky" and submitted RMA, then My G513QR has returned me with changed main board.
The problem was indeed resolved at that time, but the same problem occurred again in April 2023.
Same as before, changed main board.
And now, the same problem occurred AGAIN in April 2024.
like this↓
I suspect that it is no longer bad luck or my fault, but a defect in the product itself.
The same failure behavior over the same period of time indicates that the quality of the product is somewhat stable, but there may be a design or management problem.
In 2021 and 2022, I used G513QR without any changes in components or settings.
I can't speak too strongly about this failure as I have changed parts and settings (overclocked) since the 2023 repair, but having faced the same problem twice in the past, I have come to distrust this product.
I have filed an RMA, but am concerned that the mainboard replacement will recur next year.
I asked the ASUS Customer Service Center (APAC) about this, but was unable to get anything more out of them than "we won't know until we see it at the repair center".
Is there anything I can do to address the problem? Or can ASUS do something about this problem?
info
2021,2022: I just used stock G513QR at gaming and study
2023:I changed RAM, added M.2 SSD, and overclock RAM, GPU, CPU
CPU:AMD Ryzen 9 5900HX (curve optimizer all core -7)
RAM:Team SO-DIMM DDR4 3200MHz 16GB*2 TED432G3200C22DC-S01AM
OCed to 3800MHz, MCLK==FCLK==UCLK up to 1900 and tightened timing
RAM OCed since 2023 after repair
SSD(added to empty slot):Monster Storage 2TB NVMe SSD PCIe Gen 4×4 MS950G75PCIe4-02TB
GPU:Nvidia RTX 3070 OCed VRAM 7300MHz and undervoltage & underclock GPU core.
05-05-2024 07:45 PM
This issue has been resolved by changing the model, so there will be no further updates in this thread.
Since I don't have a G513QR on hand at this time, I'm unable to verify this issue, but I'm leaving it here so that users of the same model are aware of this issue.