Consistent computer slowdown/crashing

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • BroseidonR
    PCHF Member
    • Nov 2020
    • 32

    #1

    Consistent computer slowdown/crashing

    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.

    [SPOILER=β€œPC Specs”]
    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[/SPOILER]
    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
  • veeg
    PCHF Director
    • Jul 2016
    • 8982

    #2
    Hello

    Download and tun then post that log..

    @phillpower2 jmarket

    Comment

    • BroseidonR
      PCHF Member
      • Nov 2020
      • 32

      #3
      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?

      Comment

      • veeg
        PCHF Director
        • Jul 2016
        • 8982

        #4
        Sorry didn’t notice the link didn’t post..

        This one: SysnativeBSODCollectionApp | Sysnative Forums

        Comment

        • BroseidonR
          PCHF Member
          • Nov 2020
          • 32

          #5
          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

          Comment

          • phillpower2
            PCHF Administrator
            • Sep 2016
            • 15209

            #6
            While we look at your Sysnative info, see the below’

            [COLOR=rgb(44, 130, 201)]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.

            [COLOR=rgb(44, 130, 201)]Edit by phillpower2: Thread not BSOD related, moving to Computer DIY support.[/COLOR][/COLOR]

            Comment

            • BroseidonR
              PCHF Member
              • Nov 2020
              • 32

              #7
              Speccy: http://speccy.piriform.com/results/3...gVmoOBQ2dHXfxa

              Unsure if it counts as a desktop as I built it from parts. Let me know if you need anything else.

              Comment

              • phillpower2
                PCHF Administrator
                • Sep 2016
                • 15209

                #8
                Originally posted by phillpower2
                [COLOR=rgb(44, 130, 201)]If the computer is a desktop can you post the brand and model name or number of the power supply (PSU).
                [/COLOR]
                [COLOR=rgb(44, 130, 201)]
                Not sure how you missed providing the above most important information :sneaky:[/color]

                Comment

                • BroseidonR
                  PCHF Member
                  • Nov 2020
                  • 32

                  #9
                  Originally posted by phillpower2
                  Not sure how you missed providing the above most important information :sneaky:
                  My bad, I misread the previous post. It’s a EVGA G3 550 W 80+ Gold Certified Fully Modular ATX Power Supply

                  Comment

                  • phillpower2
                    PCHF Administrator
                    • Sep 2016
                    • 15209

                    #10
                    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 @ [COLOR=rgb(226, 80, 65)]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.[/COLOR]

                    Comment

                    • BroseidonR
                      PCHF Member
                      • Nov 2020
                      • 32

                      #11
                      Alright, think I got it, though ASUS apparently calls it DOCP. No other settings I need to fiddle with, I set it to β€œD.O.C.P. Standard”? Thanks for pointing that out!

                      Comment

                      • phillpower2
                        PCHF Administrator
                        • Sep 2016
                        • 15209

                        #12
                        Sorry should have mentioned DOCP, was typing in a rush as was late for dinner ops:

                        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

                        Comment

                        • phillpower2
                          PCHF Administrator
                          • Sep 2016
                          • 15209

                          #13
                          Any further problems BroseidonR?

                          Comment

                          • BroseidonR
                            PCHF Member
                            • Nov 2020
                            • 32

                            #14
                            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.

                            Comment

                            • phillpower2
                              PCHF Administrator
                              • Sep 2016
                              • 15209

                              #15
                              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.

                              [COLOR=rgb(44, 130, 201)]Edit to add: A new Speccy url as well please.[/COLOR]

                              Comment

                              Working...