A faulty two-week-old computer? I would have taken it back, as you did. But I would not have had it repaired. I would have taken a refund ... and bought something else.
When you buy something new you're entitled to a fault-free product. Accept no less.
Hello,
I am not sure if you have resolved this problem or not. I have the same problem as you. However, one thing that I notice is this problem started happening for me after I swap my motherboard, CPU, CPU cooler, and added additional RAM sticks. These are my new hardware:
ASUS ROG STRIX B550-F (WIFI)
Ryzen 5600X
32 GB Corsair Vengeance 3200 mhz CL16 (All identical)
Kraken X63
As you can see, we have the same MOBO and I believe the MOBO is causing this problem as I was running a Ryzen 2600 with B450 MOBO and I didn't have any problems. After searching around for a solution, one thing that I notice is when I ran Reliability Monitor I notice that Armoury Crate related applications stopped working. If you don't mind, may you run Reliability Monitor and see if you notice the same thing?
So yeah, I tried to ignore this problem for months. Sure its annoying as hell, but for a while (october-november) I didnt have as many freezes ("only" 5 in two months time) and since it performs well when gaming, I tried to live with it.
But now I just cant anymore. The problem started appreaing again in december, only to increase from there. In january alone I had 11 freezes, but in february so far I've had at least one freeze/crash per day. It is absolutely cancer and I can't take this shit anymore.
I will try this, but I dont believe it to be the cause, because then the crashes/freezes should occur in load (when more power is consumed) and not mostly in idle or semi-idle? But i'll try.
I would have done this, but since i bought parts and not a prebuilt, they wouldnt refund. I even had them assemble it and paid for that, still nothing.
i really regret buying this pc as it cost me about 3300€. I have bought many gaming pcs in my life, both pre-builts and parts that i've assembled myself or paid to have assembled. From here on I will only buy prebuilts as then (in my shithole country) at least I can return it as one faulty product if anything happens.
I appreciate any suggestions! Can you elaborate a bit on what Reliability Monitor does and how to use it?
- - - Updated - - -
From what I gathered looking at Realibility Monitor, it's not much..
Every time the system has frozen/crashed, I have noted down the date + time (and sometimes what I was doing, but this turned out to be of no point since there's no real pattern)
It seems I can only go back 1 month in reliability monitor, so here is that data, compared to my noted down (approx) time of system freeze/crash. This data is from 2022-01-22 to 2022-02-21.
My noted freezes/crashes (all were followed by a hard reset) Date & Time in red + what windows reliability monitor found for that day in black.
2022-01-23 03:30
03:31 Windows was not properly shut down.
2022-01-25 19:19
19:20 Windows was not properly shut down.
2022-02-07 19:16
2022-02-07 19:35
19:23 Windows was not properly shut down
19:24 THXHelper051A.exe Stopped working
19:24 THXHelper22AD.exe Stopped working
19:25 THXHelper22ad.exe Stopped working
19:25 THXHelper051a.exe Stopped working
19:37 Windows was not properly shut down
2022-02-08 14:20
14:23 Windows stopped working
Description
The computer has rebooted from a bugcheck. The bugcheck was: 0x0000010e (0x0000000000000017, 0xffffc90190703000, 0x0000000000000000, 0xffffffffc00002b6). A dump was saved in: C:\Windows\MEMORY.DMP.
Report Id: 716bcd09-f622-4afc-a769-34fe3910a4e6.
14:23 Windows machine error
Description
a problem with your hardware caused windows to stop working correctly
Problem Signature
Problem Event Name: LiveKernelEvent
Code: 1a1
Parameter 1: ffffa20fde697040
Parameter 2: 0
Parameter 3: 0
Parameter 4: 0
OS-version: 10_0_19043
Service Pack: 0_0
Product: 768_1
OS-version: 10.0.19043.2.0.0.768.101
Language Variant-ID: 2057
2022-02-12 00:33
00:34 Windows was not properly shut down
00:36 THXService stopped working
18:57 Windows machine error
Description
a problem with your hardware caused windows to stop working correctly
Problem signature
Problem Event Name: LiveKernelEvent
Code: 141
Parameter 1: ffff8287525e2460
Parameter 2: fffff8077a9ba9c4
Parameter 3: 0
Parameter 4: 0
OS-version: 10_0_19043
Service Pack: 0_0
Product: 768_1
OS-version: 10.0.19043.2.0.0.768.101
Language variant-ID: 2057
2022-02-15 02:50
2022-02-15 19:58
12:20 Windows was not properly shut down.
17:15 THXService stopped working
19:58 Windows was not properly shut down.
2022-02-17 20:16
20:19 Windows was not properly shut down.
20:21 THXService stopped working
2022-02-19 00:04
00:05 Windows was not properly shut down
2022-02-20 21:01
20:51 THXService stopped working
21:01 Windows was not properly shut down
2022-02-21 18:51
2022-02-21 18:52
2022-02-21 21:43
18:41 18:57 Windows machine error
Description
a problem with your hardware caused windows to stop working correctly
Problem signature
Problem Event Name: LiveKernelEvent
Code: 141
Parameter 1: ffff9b08c9c98050
Parameter 2: fffff8075d37a9c4
Parameter 3: 0
Parameter 4: 0
OS-version: 10_0_19043
Service Pack: 0_0
Product: 768_1
OS-version: 10.0.19043.2.0.0.768.101
Language Variant-ID: 2057
18:41 THXService Stopped working
18:53 Windows was not properly shut down
21:44 Windows was not properly shut down
21:45 THXService Stopped working
---------------------------------------------------------------
Basically, all this is telling me is when I perform a hard reset, that notes an error of windows shut down. Some kind of issue with THXservice (this is part of the headphones driver with razer synapse) but that isnt always showing up...
Those hardware/machine errors I don't know how to interpret?
Hello. Have you found a solution yet? You've described my EXACT issue. Only I'm running intel i7-10700k asus z490-p mobo. Same thing took it to repair shop and all the guy could find wrong with mine is my Integrated Graphics is faulty. But I never use that. Use a 3090. Please let me know if you've gotten anywhere officially since this is really starting to get to me as well.
Quote