Question After a lot of troubleshooting, my PC STILL doesn't work ?

Nov 3, 2021
16
0
10
My pc is acting really really weird.

So the problem is: the screen turns black and says no signal, pc fans ramp up to 100%. Pc itself and all rgb lights stay turned on. This happens when launching/playing games or when doing a gpu benchmark. I have noticed, the harder the game/benchmark is to run, the sooner the crash occurs. In games like rust it crashes in the main menu, in heaven benchmark it crashes too, but at random times.

Note: i can use the system without any problems at all when i am just watching youtube, using basic programs like word. The problem only occurs under (heavy) load

Another note: I was running msi afterburner checking the temps and clocks of gpu (it would run a few minutes of heaven benchmark before it would crash) . the clock for that gpu should be 1281 mhz, but it was bouncing all over the place between 1000mhz and 1190mhz, temps were 80 degrees. When testing the gpu in another system, the clock was hitting that 1281 mhz all the time. Temps were the same.

What i have tried so far:
  1. reinstall/update all drivers - no succes
  2. fully wipe system and reinstall windows - no succes
  3. tested the gpu in another system with the same games and benchmarks - no problems at all, so its not the gpu either
  4. Bought a new psu, i was 100% sure this would fix it but - no succes
  5. installed ram from another system that i know works - no succes
  6. cleaned the system and reapplied thermal paste on cpu - no succes
  7. i also benchmarked the cpu, temps were only 65 degrees and scores were good
I think the only thing that could be broken is the motherboard, but i am not sure, i need some help because i dont want to buy a new mobo just to find out that is not the fix either.

important (maybe): sometimes, when booting, pc is stuck on the motherboard logo screen, i just restart and that fixes it. Maybe thats another indication the mobo is gone?

Specs:
Ryzen 3 2200g
Asrock a320M dvs r3.0
rx 570 4gb (msi gaming x)
crucial ballistix 12 gb (4 + 8) 2400mhz (yes weird number, but with a 2x4gb = 8gb, it also crashed)
Seasonic G12 GC 550 (brand new)
kingston 240gb ssd
WD 1tb hdd
 
Last edited:
My pc is acting really really weird.

So the problem is: the screen turns black and says no signal, pc fans ramp up to 100%. Pc itself and all rgb lights stay turned on. This happens when launching/playing games or when doing a gpu benchmark. I have noticed, the harder the game/benchmark is to run, the sooner the crash occurs. In games like rust it crashes in the main menu, in heaven benchmark it crashes too, but at random times.

Note: i can use the system without any problems at all when i am just watching youtube, using basic programs like word. The problem only occurs under (heavy) load

What i have tried so far:
  1. reinstall/update all drivers - no succes
  2. fully wipe system and reinstall windows - no succes
  3. tested the gpu in another system with the same games and benchmarks - no problems at all, so its not the gpu either
  4. Bought a new psu, i was 100% sure this would fix it but - no succes
  5. installed ram from another system that i know works - no succes
  6. cleaned the system and reapplied thermal paste on cpu - no succes
  7. i also benchmarked the cpu, temps were only 65 degrees and scores were good
I think the only thing that could be broken is the motherboard, but i am not sure, i need some help because i dont want to buy a new mobo just to find out that is not the fix either.

important (maybe): sometimes, when booting, pc is stuck on the motherboard logo screen, i just restart and that fixes it. Maybe thats another indication the mobo is gone?

Specs:
Ryzen 3 2200g
Asrock a320M dvs r3.0
rx 570 4gb (msi gaming x)
crucial ballistix 12 gb (4 + 8) 2400mhz (yes weird number, but with a 2x4gb = 8gb, it also crashed)
Seasonic G12 GC 550 (brand new)
kingston 240gb ssd
WD 1tb hdd
Post a screenshot from crystal disk info for both disk.

Do you have the proper bios and mobo drivers?
 
Post a screenshot from crystal disk info for both disk.

Do you have the proper bios and mobo drivers?
i cant post that screenshot right now, i am not at home.

With mobo drivers do you mean chipset drivers? I installed them through amd , or should i go to the asrock site?
Bios has never been updated since i got the pc 3 1/2 years ago
 
This problem reminds me of my old mainboard back then that was slowly going bad, every time I used it with high load, it would crash the system, unless I would power cycle it one time, before really using it. This means, turning PC on (load into windows), switching it off, and then turning it on again. You have certainly one of the cheaper/weaker boards, could totally be that it’s the board, anything else is also unlikely.
 
This problem reminds me of my old mainboard back then that was slowly going bad, every time I used it with high load, it would crash the system, unless I would power cycle it one time, before really using it. This means, turning PC on (load into windows), switching it off, and then turning it on again. You have certainly one of the cheaper/weaker boards, could totally be that it’s the board, anything else is also unlikely.
yeah i am guessing its the board as well. Also because i think i have tested all of the other possible causes and found nothing
 
I suggest going back a bit:

First look in Reliability History and Event Viewer to determine if either one or both are capturing some error codes, warnings, or even informational events that occur just before or at the time of the crashes.

Start with Reliability History: Much more end user friendly and the time line format can be very revealing.

Second, take advantage of Task Manager and Resource Monitor (use both tools but only one at a time) to observe system performance. Begin with light work or browsing, then ramp up to more demanding apps and then into games. Observe what changes. Especially anything that precedes a crash.

Observe what resources are being used, to what extent (%), and what is using any given resource. Pay attention to unknown or unexpected apps that may be running.

Third, go to Update History. Look for any failed or problem updates.

Another tool that could also help is Process Explorer (Microsoft, free):

https://docs.microsoft.com/en-us/sysinternals/downloads/process-explorer

Discover what Windows is doing, seeing, and capturing with respect to the problems noted.

No harm in taking a closer look - something could turn up....
 
I suggest going back a bit:

First look in Reliability History and Event Viewer to determine if either one or both are capturing some error codes, warnings, or even informational events that occur just before or at the time of the crashes.

Start with Reliability History: Much more end user friendly and the time line format can be very revealing.

Second, take advantage of Task Manager and Resource Monitor (use both tools but only one at a time) to observe system performance. Begin with light work or browsing, then ramp up to more demanding apps and then into games. Observe what changes. Especially anything that precedes a crash.

Observe what resources are being used, to what extent (%), and what is using any given resource. Pay attention to unknown or unexpected apps that may be running.

Third, go to Update History. Look for any failed or problem updates.

Another tool that could also help is Process Explorer (Microsoft, free):

https://docs.microsoft.com/en-us/sysinternals/downloads/process-explorer

Discover what Windows is doing, seeing, and capturing with respect to the problems noted.

No harm in taking a closer look - something could turn up....
thank you, i will defenitly try that
 
I suggest going back a bit:

First look in Reliability History and Event Viewer to determine if either one or both are capturing some error codes, warnings, or even informational events that occur just before or at the time of the crashes.

Start with Reliability History: Much more end user friendly and the time line format can be very revealing.

Second, take advantage of Task Manager and Resource Monitor (use both tools but only one at a time) to observe system performance. Begin with light work or browsing, then ramp up to more demanding apps and then into games. Observe what changes. Especially anything that precedes a crash.

Observe what resources are being used, to what extent (%), and what is using any given resource. Pay attention to unknown or unexpected apps that may be running.

Third, go to Update History. Look for any failed or problem updates.

Another tool that could also help is Process Explorer (Microsoft, free):

https://docs.microsoft.com/en-us/sysinternals/downloads/process-explorer

Discover what Windows is doing, seeing, and capturing with respect to the problems noted.

No harm in taking a closer look - something could turn up....
I have tested. When i go from browsing to heaven benchmark for example, the gpu usage goes to 100% (logical), cpu to 21% and ram to 20%. Seems pretty normal to me. It still crashed by the way. The gpu clocks were still bouncing between 1000 mhz and 1190.

Every time a crash occors this is what Reliability History says: Windows hardwarefault. Livekernelevent, code 144, parameter 1009 (and some more stuff i cant post if u want)

I have never really used Reliability History so i don't know what this all means, but i honestly think this has nothing to do with the crash, its just me shutting down the pc because the screen went black, but i am not sure about that.

In both reliability History and event viewer, there are no faults, info or critical errors leading up to the crash. The only error i fan find is that one i have mentioned, But that one happens when i restart the pc and has nothing to do with the crash itself.

No failed updates either.

I even went in msi afterburner and lowered to mhz for gpu to 1150mhz, hoping it would stay there but now the average mhz went even lower, sometimes going the 900mhz.

I am on a dead end
 
There is no guarantee that a new motherboard will solve the problem.

Live Kernel Event 144:

https://docs.microsoft.com/en-us/an...t-livekernelevent-144-error-regular-bsod.html

Any number of possibilities it appears. And you can easily find other links regarding Live Kernel Event 144. (Do avoid third party links offering software etc. offering to fix the problem. Some of those links will appear no matter what problem you are trying to solve. (Likewise avoid Registry edits. Last resort.)

As I understand the posts to date you have reinstalled drivers, replaced hardware, and so forth per your original post. And taken other actions that would (or should) fix problems with corrupted Windows' files and device drivers.

However, because you had to again shut down the pc after the crashes those shutdowns could have once more caused file corruption.

Try running "sfc /scannow" and "dism" to repair any thus corrupted files.

What about Resource Monitor and Task Manager? Were you able to observe system performance to determine if some change in resource usage leads up to the crashes.

Agree: all of those tools are indeed confusing and initially difficult to understand. And it may take some time and effort to learn how to navigate about and understand the information being presented. Not perfect tools by any means but they can prove helpful either directly or by eliminating possibilities.

(Note: as a matter of elimination, were you able to try other known working video cables, video connections, and monitors?)

What all is running the background: being launched during startup or triggered later via Task Scheduler? Any monitoring utilities or other tools?

Still very much worth the effort to delve into things before going replacing the motherboard. Costly and time consuming.

= = = =

It may well be that the motherboard is the culprit. I have no vested interest one way or another.

Go back to a basic configuration as possible: hardware, software, configuration settings, - everything. Disable known items in Task Manager > Startup that are not truly needed all of the time. Investigate unknown items that may be found there.

Objective being to once again obtain stable performance as a starting point. If so then begin making incremental changes that work towards the desired full configuration. Step by step allowing time between actions.

Make another effort to methodically troubleshoot as much as possible. Pay attention to the tools and logs.

When complete you can then decide whether or not to replace the motherboard. And be a bit more certain that the motherboard is the problem.

Your call....
 
There is no guarantee that a new motherboard will solve the problem.

Live Kernel Event 144:

https://docs.microsoft.com/en-us/an...t-livekernelevent-144-error-regular-bsod.html

Any number of possibilities it appears. And you can easily find other links regarding Live Kernel Event 144. (Do avoid third party links offering software etc. offering to fix the problem. Some of those links will appear no matter what problem you are trying to solve. (Likewise avoid Registry edits. Last resort.)

As I understand the posts to date you have reinstalled drivers, replaced hardware, and so forth per your original post. And taken other actions that would (or should) fix problems with corrupted Windows' files and device drivers.

However, because you had to again shut down the pc after the crashes those shutdowns could have once more caused file corruption.

Try running "sfc /scannow" and "dism" to repair any thus corrupted files.

What about Resource Monitor and Task Manager? Were you able to observe system performance to determine if some change in resource usage leads up to the crashes.

Agree: all of those tools are indeed confusing and initially difficult to understand. And it may take some time and effort to learn how to navigate about and understand the information being presented. Not perfect tools by any means but they can prove helpful either directly or by eliminating possibilities.

(Note: as a matter of elimination, were you able to try other known working video cables, video connections, and monitors?)

What all is running the background: being launched during startup or triggered later via Task Scheduler? Any monitoring utilities or other tools?

Still very much worth the effort to delve into things before going replacing the motherboard. Costly and time consuming.

= = = =

It may well be that the motherboard is the culprit. I have no vested interest one way or another.

Go back to a basic configuration as possible: hardware, software, configuration settings, - everything. Disable known items in Task Manager > Startup that are not truly needed all of the time. Investigate unknown items that may be found there.

Objective being to once again obtain stable performance as a starting point. If so then begin making incremental changes that work towards the desired full configuration. Step by step allowing time between actions.

Make another effort to methodically troubleshoot as much as possible. Pay attention to the tools and logs.

When complete you can then decide whether or not to replace the motherboard. And be a bit more certain that the motherboard is the problem.

Your call....
thanks alot for your advice man, its really detailed.

I decided to take out my gpu and open it up. I didn't do this before because it looked clean on the outside. When i openend it i saw that the thermal paste was completly dry, there were even some gaps on the gpu chip with no thermal paste at all, Put some new paste on and it worked like it was brand new.

Weird thing is that the temps looked normal (even with the old paste), about 75- 80 degrees, but apperently replacing the thermal paste fixed the issue

Thanks again for your help