• Hi there and welcome to PC Help Forum (PCHF), a more effective way to get the Tech Support you need!
    We have Experts in all areas of Tech, including Malware Removal, Crash Fixing and BSOD's , Microsoft Windows, Computer DIY and PC Hardware, Networking, Gaming, Tablets and iPads, General and Specific Software Support and so much more.

    Why not Click Here To Sign Up and start enjoying great FREE Tech Support.

    This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

Solved Consistent computer slowdown/crashing

Status
Not open for further replies.

BroseidonR

PCHF Member
PCHF Donator
Nov 8, 2020
32
0
34
I built this PC in summer 2019 and had no problems for most of 2019. However, starting in the spring of this year, during streaming of Crosscode using StreamlabsOBS, the game visuals would freeze while sound and music can be heard, followed by a sound stutter of the last played effect, and then the screen going black for a little bit. When screen came back, the game would remain frozen while the rest of the computer was slow and laggy, with mouse movement only registering on screen every 10 seconds or so. At this point, I would generally reset the computer via the power button, after which there was a chance of the same thing occurring. It's interesting in that it happens with some games more (Hades, Crosscode, The Messenger, Gunfire Reborn) than others (Doom Eternal, Alien: Isolation, Huntdown), regardless of whether I'm streaming or not.
Recently, while streaming Hades through discord, I had a similar event. After restarting, someone recommended I run just Hades on its own while monitoring temperatures and CPU via Task Manager while playing. After playing Hades for an hour and a half, the issue occurred again. While temperatures stayed consistent throughout the time period, the overall CPU usage jumped to 100% while no programs showed any CPU usage. Also worth noting is that after about 3-5 min of the unresponsive computer, it suddenly snapped back to normal speed, with the game still being able to be played (could hear sound and interact with it via mouse) but the screen remained black.
I have posted the errors that appeared on the Reliability Reports below, with the first set being from earlier in the evening when I was playing Hades and streaming via Discord and the second set being from later when I was just playing Hades. Any help would be greatly appreciated.
If additional information is needed, please let me know. Thank you in advance.
Windows 10 Home (x64) Version 2004 (build 19041.572)
Install Language: English (United States)
System Locale: English (United States)
Installed: 8/11/2019 6:18:18 AM
Servicing Branch: Current Branch (CB)
Boot Mode: UEFI (Secure Boot likely not supported by this UEFI)

Processor
3.60 gigahertz AMD Ryzen 5 3600 6-Core
384 kilobyte primary memory cache
3072 kilobyte secondary memory cache
32768 kilobyte tertiary memory cache
64-bit ready
Multi-core (6 total)
Hyper-threaded (12 total)

Drives
1999.78 Gigabytes Usable Hard Drive Capacity
948.96 Gigabytes Hard Drive Free Space
Samsung SSD 860 EVO 1TB [Hard drive] (1000.20 GB) -- drive 1, rev RVT03B6Q, SMART Status: Healthy
Samsung SSD 860 EVO 1TB [Hard drive] (1000.20 GB) -- drive 0, , rev RVT03B6Q, SMART Status: Healthy

Main Circuit Board
Board: ASUSTeK COMPUTER INC. ROG STRIX B450-F GAMING Rev 1.xx
Bus Clock: 100 megahertz
UEFI: American Megatrends Inc. 2406 06/21/2019
Source
Windows

Summary
Hardware error

Date
‎10/‎16/‎2020 8:36 PM

Status
Not reported

Description
A problem with your hardware caused Windows to stop working correctly.

Problem signature
Problem Event Name: LiveKernelEvent
Code: 141
Parameter 1: ffff830ba6fed460
Parameter 2: fffff8078a772610
Parameter 3: 0
Parameter 4: 2cc8
OS version: 10_0_19041
Service Pack: 0_0
Product: 768_1
OS Version: 10.0.19041.2.0.0.768.101
Locale ID: 1033

Source
Windows

Summary
Hardware error

Date
‎10/‎16/‎2020 8:39 PM

Status
Not reported

Description
A problem with your hardware caused Windows to stop working correctly.

Problem signature
Problem Event Name: LiveKernelEvent
Code: 141
Parameter 1: ffff830ba6fed460
Parameter 2: fffff8078a772610
Parameter 3: 0
Parameter 4: 1d54
OS version: 10_0_19041
Service Pack: 0_0
Product: 768_1
OS Version: 10.0.19041.2.0.0.768.101
Locale ID: 1033

Source
Windows

Summary
Hardware error

Date
‎10/‎16/‎2020 8:39 PM

Status
Not reported

Description
A problem with your hardware caused Windows to stop working correctly.

Problem signature
Problem Event Name: LiveKernelEvent
Code: 141
Parameter 1: ffff830ba9fd8460
Parameter 2: fffff8078a772610
Parameter 3: 0
Parameter 4: 18a4
OS version: 10_0_19041
Service Pack: 0_0
Product: 768_1
OS Version: 10.0.19041.2.0.0.768.101
Locale ID: 1033

Source
Windows

Summary
Hardware error

Date
‎10/‎16/‎2020 8:40 PM

Status
Not reported

Description
A problem with your hardware caused Windows to stop working correctly.

Problem signature
Problem Event Name: LiveKernelEvent
Code: 141
Parameter 1: ffff830ba6fed460
Parameter 2: fffff8078a772610
Parameter 3: 0
Parameter 4: 2100
OS version: 10_0_19041
Service Pack: 0_0
Product: 768_1
OS Version: 10.0.19041.2.0.0.768.101
Locale ID: 1033
Source
Windows

Summary
Hardware error

Date
‎10/‎16/‎2020 11:03 PM

Status
Not reported

Description
A problem with your hardware caused Windows to stop working correctly.

Problem signature
Problem Event Name: LiveKernelEvent
Code: 141
Parameter 1: ffff848550bd8050
Parameter 2: fffff807255e2610
Parameter 3: 0
Parameter 4: 319c
OS version: 10_0_19041
Service Pack: 0_0
Product: 768_1
OS Version: 10.0.19041.2.0.0.768.101
Locale ID: 1033

Source
Windows

Summary
Hardware error

Date
‎10/‎16/‎2020 11:06 PM

Status
Not reported

Description
A problem with your hardware caused Windows to stop working correctly.

Problem signature
Problem Event Name: LiveKernelEvent
Code: 141
Parameter 1: ffff848550bd8050
Parameter 2: fffff807255e2610
Parameter 3: 0
Parameter 4: 4
OS version: 10_0_19041
Service Pack: 0_0
Product: 768_1
OS Version: 10.0.19041.2.0.0.768.101
Locale ID: 1033

Source
Windows

Summary
Hardware error

Date
‎10/‎16/‎2020 11:06 PM

Status
Not reported

Description
A problem with your hardware caused Windows to stop working correctly.

Problem signature
Problem Event Name: LiveKernelEvent
Code: 117
Parameter 1: ffff848556eca050
Parameter 2: fffff807255e2610
Parameter 3: 0
Parameter 4: 0
OS version: 10_0_19041
Service Pack: 0_0
Product: 768_1
OS Version: 10.0.19041.2.0.0.768.101
Locale ID: 1033
 
Hi Veeg. I'm unsure by the instructions. When you say download, I'm gonna assume that I get that from the "Save Reliability History" option in Reliability Monitor. I've (attempted) attached that download below. I'm not sure what "tun" means, can you clarify.?
The "save reliability history" option gave me an .xml file, which the forum doesn't allow. How do you want me to post it?
 
Ok, I downloaded the app, ran it, at which point it generated a "SysnativeFileCollectionApp.zip". The forums will let me attach attach the zip, so I've done that. Please let me know if this is what you needed and if you need any additional info. Thank you
 

Attachments

  • SysnativeFileCollectionApp.zip
    634.3 KB · Views: 7
While we look at your Sysnative info, see the below'

If the computer is a desktop can you post the brand and model name or number of the power supply (PSU).

Download then run Speccy (free) and post the resultant url for us, details here, this will provide us with information about your computer hardware + any software that you have installed that may explain the present issue/s.

To publish a Speccy profile to the Web:

In Speccy, click File, and then click Publish Snapshot.

In the Publish Snapshot dialog box, click Yes to enable Speccy to proceed.

Speccy publishes the profile and displays a second Publish Snapshot. You can open the URL in your default browser, copy it to the clipboard, or close the dialog box.

Edit by phillpower2: Thread not BSOD related, moving to Computer DIY support.
 
Good PSU so only thing I would suggest is that you check to make sure that all modular cables are securely attached at both ends.

Only one thing of note in Speccy and that is your RAM is not working at the correct speed for your CPU.

RAM
16.0GB Dual-Channel Unknown @ 1064MHz This should be reading at around 1600Mhz in Speccy.

Make sure that XMP is enabled in the BIOS so that the RAM gets OCd to the required 3200MHz.
 
Sorry should have mentioned DOCP, was typing in a rush as was late for dinner :oops:

You are correct, on earlier MBs DOCP was the AMD version of the Intel XMP setting but because RAM manufacturers were all labelling their RAM as being XMP standard therefore suggesting that it was only good for Intel builds AMD have dropped DOCP and now use XMP instead, XMP is not a trademark of Intel but is instead a universally recognised abbreviation of eXtreme Memory Profile, far easier to remember than the alternative Direct Over Clock Profile :unsure:

You are welcome btw :)
 
Hey Phil, thanks for checking in. I've been avoiding playing the games that have caused the crash. So while it hasn't been happening as often, it still occurs every once in a while. Most recently last week, after streaming on twitch Huntdown for about an hour and a half, it occurred while I was downloading the VoD.
 
Hello BroseidonR,

Let`s see if MTB flags up anything new;

Download MiniToolBox and save the file to the Desktop.

Close the browser and run the tool, check the following options;

List last 10 Event Viewer Errors
List Installed Programs
List Devices (Only Problems)
List Users, Partitions and Memory size

Click on Go.

Post the resulting log in your next reply for us if you will.

Edit to add: A new Speccy url as well please.
 
Huh, let's try that attachment again
.....
Ok, I'm having problems attaching the txt file. It shows as attached in the reply preview (icon visible but no picture) but when I save, it disappears. MTB was supposed to give a .txt file, right?
 
MiniToolBox by Farbar Version: 17-06-2016
Ran by Broseidon Rex (administrator) on 21-11-2020 at 23:37:57
Running from "C:\Users\Broseidon Rex\AppData\Local\Temp\scoped_dir12576_1771378850"
Microsoft Windows 10 Home (X64)
Model: System Product Name Manufacturer: System manufacturer
Boot Mode: Normal
***************************************************************************

========================= Event log errors: ===============================

Application errors:
==================
Error: (11/18/2020 05:56:30 PM) (Source: VSS) (User: )
Description: Volume Shadow Copy Service error: Unexpected error calling routine QueryFullProcessImageNameW. hr = 0x80070006, The handle is invalid.
.


Operation:
Executing Asynchronous Operation

Context:
Current State: DoSnapshotSet

Error: (11/13/2020 08:57:19 PM) (Source: Application Hang) (User: )
Description: The program DOOMEternalx64vk.exe version 1.0.0.1 stopped interacting with Windows and was closed. To see if more information about the problem is available, check the problem history in the Security and Maintenance control panel.

Process ID: 55c

Start Time: 01d6ba293e9087cc

Termination Time: 4294967295

Application Path: C:\Program Files (x86)\Steam\steamapps\common\DOOMEternal\DOOMEternalx64vk.exe

Report Id: 867ababa-aed7-4f2d-9080-f9d43593221f

Faulting package full name:

Faulting package-relative application ID:

Hang type: DOOMEternalx64vk.exe0

Error: (11/13/2020 07:27:26 PM) (Source: Application Error) (User: )
Description: Faulting application name: AiChargerAP.exe, version: 3.0.0.0, time stamp: 0x531699f7
Faulting module name: AiChargerAP.exe, version: 3.0.0.0, time stamp: 0x531699f7
Exception code: 0xc0000409
Fault offset: 0x00001393
Faulting process id: 0x3264
Faulting application start time: 0xAiChargerAP.exe0
Faulting application path: AiChargerAP.exe1
Faulting module path: AiChargerAP.exe2
Report Id: AiChargerAP.exe3
Faulting package full name: AiChargerAP.exe4
Faulting package-relative application ID: AiChargerAP.exe5

Error: (11/13/2020 07:11:09 PM) (Source: Application Error) (User: )
Description: Faulting application name: AiChargerAP.exe, version: 3.0.0.0, time stamp: 0x531699f7
Faulting module name: AiChargerAP.exe, version: 3.0.0.0, time stamp: 0x531699f7
Exception code: 0xc0000409
Fault offset: 0x00001393
Faulting process id: 0x334c
Faulting application start time: 0xAiChargerAP.exe0
Faulting application path: AiChargerAP.exe1
Faulting module path: AiChargerAP.exe2
Report Id: AiChargerAP.exe3
Faulting package full name: AiChargerAP.exe4
Faulting package-relative application ID: AiChargerAP.exe5

Error: (11/13/2020 04:41:57 PM) (Source: Application Hang) (User: )
Description: The program GameBar.exe version 5.420.10222.0 stopped interacting with Windows and was closed. To see if more information about the problem is available, check the problem history in the Security and Maintenance control panel.

Process ID: 3e00

Start Time: 01d6ba04699a8c8b

Termination Time: 4294967295

Application Path: C:\Program Files\WindowsApps\Microsoft.XboxGamingOverlay_5.420.10222.0_x64__8wekyb3d8bbwe\GameBar.exe

Report Id: cbdbe290-fb6b-4597-a107-e128bf903a80

Faulting package full name: Microsoft.XboxGamingOverlay_5.420.10222.0_x64__8wekyb3d8bbwe

Faulting package-relative application ID: App

Hang type: GameBar.exe0

Error: (11/04/2020 08:37:02 PM) (Source: Application Hang) (User: )
Description: The program dwm.exe version 10.0.19041.508 stopped interacting with Windows and was closed. To see if more information about the problem is available, check the problem history in the Security and Maintenance control panel.

Process ID: 2724

Start Time: 01d6b313e99eb7d3

Termination Time: 6743

Application Path: C:\Windows\System32\dwm.exe

Report Id: 2f0a9da5-65a6-4fbd-a131-e19e537eeb9c

Faulting package full name:

Faulting package-relative application ID:

Hang type: dwm.exe0

Error: (11/04/2020 08:35:15 PM) (Source: Application Hang) (User: )
Description: The program dwm.exe version 10.0.19041.508 stopped interacting with Windows and was closed. To see if more information about the problem is available, check the problem history in the Security and Maintenance control panel.

Process ID: 39f0

Start Time: 01d6b313b2f80506

Termination Time: 6642

Application Path: C:\Windows\System32\dwm.exe

Report Id: 2ad99307-edd6-45c6-9890-96bb4e775886

Faulting package full name:

Faulting package-relative application ID:

Hang type: dwm.exe0

Error: (11/04/2020 08:33:44 PM) (Source: Application Hang) (User: )
Description: The program dwm.exe version 10.0.19041.508 stopped interacting with Windows and was closed. To see if more information about the problem is available, check the problem history in the Security and Maintenance control panel.

Process ID: 35f8

Start Time: 01d6b31383e27ade

Termination Time: 4901

Application Path: C:\Windows\System32\dwm.exe

Report Id: 0354ddb5-9d49-4ace-b1b4-72ace971fbc1

Faulting package full name:

Faulting package-relative application ID:

Hang type: dwm.exe0

Error: (11/04/2020 08:32:16 PM) (Source: Application Hang) (User: )
Description: The program dwm.exe version 10.0.19041.508 stopped interacting with Windows and was closed. To see if more information about the problem is available, check the problem history in the Security and Maintenance control panel.

Process ID: f60

Start Time: 01d6b24680cd8750

Termination Time: 60000

Application Path: C:\Windows\System32\dwm.exe

Report Id: 248d53a3-8066-41a3-a01c-0197836794a5

Faulting package full name:

Faulting package-relative application ID:

Hang type: dwm.exe0

Error: (10/29/2020 06:00:43 PM) (Source: Application Error) (User: )
Description: Faulting application name: AUDIODG.EXE, version: 10.0.19041.546, time stamp: 0x15d80ff5
Faulting module name: NAHIMICV3apo.dll, version: 10.0.10011.16384, time stamp: 0x595e4369
Exception code: 0xc0000005
Fault offset: 0x0000000000379f91
Faulting process id: 0x17e4
Faulting application start time: 0xAUDIODG.EXE0
Faulting application path: AUDIODG.EXE1
Faulting module path: AUDIODG.EXE2
Report Id: AUDIODG.EXE3
Faulting package full name: AUDIODG.EXE4
Faulting package-relative application ID: AUDIODG.EXE5


System errors:
=============
Error: (11/19/2020 09:33:04 PM) (Source: Service Control Manager) (User: )
Description: The AsusUpdateCheck service did not shut down properly after receiving a preshutdown control.

Error: (11/19/2020 09:31:32 PM) (Source: Service Control Manager) (User: )
Description: The <Event xmlns='http://schemas.microsoft.com/win/2004/08/events/event'><System><Provider Name='Service Control Manager' Guid='{555908d1-a6d7-4695-8e1e-26931d2012f4}' EventSourceName='Service Control Manager'/><EventID Qualifiers='49152'>7043</EventID><Version>0</Version><Level>2</Level><Task>0</Task><Opcode>0</Opcode><Keywords>0x8080000000000000</Keywords><TimeCreated SystemTime='2020-11-20T02:31:32.9810977Z'/><EventRecordID>5730</EventRecordID><Correlation ActivityID='{d57bf6be-ba1c-0000-8a89-7dd51cbad601}'/><Execution ProcessID='892' ThreadID='5756'/><Channel>System</Channel><Computer>DESKTOP-B9SK57C</Computer><Security/></System><ProcessingErrorData><ErrorCode>13</ErrorCode><DataItemName></DataItemName><EventPayload>410073007500730055007000640061007400650043006800650063006B00000020000000410073007500730055007000640061007400650043006800650063006B000000</EventPayload></ProcessingErrorData></Event> service did not shut down properly after receiving a preshutdown control.

Error: (11/18/2020 05:59:42 PM) (Source: Microsoft-Windows-WindowsUpdateClient) (User: NT AUTHORITY)
Description: Installation Failure: Windows failed to install the following update with error 0x800f0988: 2020-11 Cumulative Update for Windows 10 Version 2004 for x64-based Systems (KB4586781).

Error: (11/15/2020 07:03:56 PM) (Source: Microsoft-Windows-WindowsUpdateClient) (User: NT AUTHORITY)
Description: Installation Failure: Windows failed to install the following update with error 0x80246010: 2020-11 Cumulative Update for Windows 10 Version 2004 for x64-based Systems (KB4586781).

Error: (11/13/2020 07:25:02 PM) (Source: Service Control Manager) (User: )
Description: The AsusUpdateCheck service did not shut down properly after receiving a preshutdown control.

Error: (11/13/2020 07:24:46 PM) (Source: Microsoft-Windows-Bits-Client) (User: NT AUTHORITY)
Description: The BITS service failed to start. Error 2147500053.

Error: (11/13/2020 06:58:45 PM) (Source: Service Control Manager) (User: )
Description: The AsusUpdateCheck service did not shut down properly after receiving a preshutdown control.

Error: (11/13/2020 06:58:30 PM) (Source: Microsoft-Windows-Bits-Client) (User: NT AUTHORITY)
Description: The BITS service failed to start. Error 2147500053.

Error: (11/12/2020 09:01:57 PM) (Source: Service Control Manager) (User: )
Description: The AsusUpdateCheck service did not shut down properly after receiving a preshutdown control.

Error: (11/12/2020 09:01:44 PM) (Source: DCOM) (User: NT AUTHORITY)
Description: 1115UsoSvcUnavailable{B91D5831-B1BD-4608-8198-D72E155020F7}


Microsoft Office Sessions:
=========================
Error: (11/18/2020 05:56:30 PM) (Source: VSS)(User: )
Description: QueryFullProcessImageNameW0x80070006, The handle is invalid.


Operation:
Executing Asynchronous Operation

Context:
Current State: DoSnapshotSet

Error: (11/13/2020 08:57:19 PM) (Source: Application Hang)(User: )
Description: DOOMEternalx64vk.exe1.0.0.155c01d6ba293e9087cc4294967295C:\Program Files (x86)\Steam\steamapps\common\DOOMEternal\DOOMEternalx64vk.exe867ababa-aed7-4f2d-9080-f9d43593221fTop level window is idle

Error: (11/13/2020 07:27:26 PM) (Source: Application Error)(User: )
Description: AiChargerAP.exe3.0.0.0531699f7AiChargerAP.exe3.0.0.0531699f7c000040900001393326401d6ba1ceda75932C:\Program Files (x86)\ASUS\ASUS Ai Charger\AiChargerAP.exeC:\Program Files (x86)\ASUS\ASUS Ai Charger\AiChargerAP.exe4d12975a-e5d3-469b-9b99-8537608f966a

Error: (11/13/2020 07:11:09 PM) (Source: Application Error)(User: )
Description: AiChargerAP.exe3.0.0.0531699f7AiChargerAP.exe3.0.0.0531699f7c000040900001393334c01d6ba1aa76a5933C:\Program Files (x86)\ASUS\ASUS Ai Charger\AiChargerAP.exeC:\Program Files (x86)\ASUS\ASUS Ai Charger\AiChargerAP.exea3665aa0-0c9b-4733-9268-40b2c029d265

Error: (11/13/2020 04:41:57 PM) (Source: Application Hang)(User: )
Description: GameBar.exe5.420.10222.03e0001d6ba04699a8c8b4294967295C:\Program Files\WindowsApps\Microsoft.XboxGamingOverlay_5.420.10222.0_x64__8wekyb3d8bbwe\GameBar.execbdbe290-fb6b-4597-a107-e128bf903a80Microsoft.XboxGamingOverlay_5.420.10222.0_x64__8wekyb3d8bbweAppNavigation

Error: (11/04/2020 08:37:02 PM) (Source: Application Hang)(User: )
Description: dwm.exe10.0.19041.508272401d6b313e99eb7d36743C:\Windows\System32\dwm.exe2f0a9da5-65a6-4fbd-a131-e19e537eeb9cUnknown

Error: (11/04/2020 08:35:15 PM) (Source: Application Hang)(User: )
Description: dwm.exe10.0.19041.50839f001d6b313b2f805066642C:\Windows\System32\dwm.exe2ad99307-edd6-45c6-9890-96bb4e775886Unknown

Error: (11/04/2020 08:33:44 PM) (Source: Application Hang)(User: )
Description: dwm.exe10.0.19041.50835f801d6b31383e27ade4901C:\Windows\System32\dwm.exe0354ddb5-9d49-4ace-b1b4-72ace971fbc1Unknown

Error: (11/04/2020 08:32:16 PM) (Source: Application Hang)(User: )
Description: dwm.exe10.0.19041.508f6001d6b24680cd875060000C:\Windows\System32\dwm.exe248d53a3-8066-41a3-a01c-0197836794a5Unknown

Error: (10/29/2020 06:00:43 PM) (Source: Application Error)(User: )
Description: AUDIODG.EXE10.0.19041.54615d80ff5NAHIMICV3apo.dll10.0.10011.16384595e4369c00000050000000000379f9117e401d6adad1c1eb0e6C:\WINDOWS\system32\AUDIODG.EXEC:\WINDOWS\system32\NAHIMICV3apo.dll7aa0ae69-121d-42d0-a36f-f9e8b385c0f0
 
Status
Not open for further replies.