PC Crashing to Black Screen  

Page 1 of 2 12 LastLast

  1. Posts : 9
    Windows 10 Home
       #1

    PC Crashing to Black Screen


    Hello, I have been having issues with my pc crashing for a few months now. The crashes steadily got worse over time. The crash involves my pc freezing for 2 - 3 seconds and then the monitor going black but the pc doesnt restart itself it will stay on until i shut it off. My mouse and keyboard will shut off but turn back on for a few seconds when i hit a key/button then turn back off. The crashes mainly happen when there is alot of media usage, and by this i mean Tidal music app is open playing music, youtube is up on my browser, any website with a lot of picture/video extensions. It will crash the odd time while gaming.

    I did format my pc a few days ago but the crashes have continued and maybe added more problems. >.< I have been doing some research here for similar posts/problems. i've ran p95 without any errors, heaven benchmark completes with no crashes or artifacts, ran sfc /scannow which did once find corrupted files but it seems it fixed them since it completes error free when i run it now. I went ahead and ran tuneup.bat as well which i will post further down in this thread. Event Viewer has Kernel Power 41 with bugcheck codes 0'd and (70368744177664),(2) keyword? Hopefully my pc aint to far gone :P Ty for the help too

    Windows Version - 20H2(Build 19042.822)
    Link to V2 log files - KKONA-(2021-02-28_21-05-24).zip
    tuneup.bat info in next thread vvvvvvvv

    - - - Updated - - -

    Code:
    ###########################################################
    # The following commands will be run in sequence.         #
    # The first 5 will take quite a while to run, be patient. #
    ###########################################################
    
    sfc /scannow
    dism /online /cleanup-image /scanhealth
    dism /online /cleanup-image /restorehealth
    sfc /scannow
    
    chkdsk /scan
    
    wmic recoveros get autoreboot
    wmic recoveros set autoreboot = false
    wmic recoveros get autoreboot
    wmic recoveros get DebugInfoType
    wmic recoveros set DebugInfoType = 7
    wmic recoveros get DebugInfoType
    
    wmic pagefile list /format:list
    wmic Computersystem where name="KKONA" get AutomaticManagedPagefile
    wmic Computersystem where name="KKONA" set AutomaticManagedPagefile=True
    wmic Computersystem where name="KKONA" get AutomaticManagedPagefile
    
    bcdedit /enum {badmemory}
    
    
    C:\Windows\system32>sfc /scannow
    
    Beginning system scan.  This process will take some time.
    
    Beginning verification phase of system scan.
    Verification 100% complete.
    
    Windows Resource Protection did not find any integrity violations.
    
    C:\Windows\system32>dism /online /cleanup-image /scanhealth
    
    Deployment Image Servicing and Management tool
    Version: 10.0.19041.844
    
    Image Version: 10.0.19042.844
    
    [==========================100.0%==========================] No component store corruption detected.
    The operation completed successfully.
    
    C:\Windows\system32>dism /online /cleanup-image /restorehealth
    
    Deployment Image Servicing and Management tool
    Version: 10.0.19041.844
    
    Image Version: 10.0.19042.844
    
    [==========================100.0%==========================] The restore operation completed successfully.
    The operation completed successfully.
    
    C:\Windows\system32>sfc /scannow
    
    Beginning system scan.  This process will take some time.
    
    Beginning verification phase of system scan.
    Verification 100% complete.
    
    Windows Resource Protection did not find any integrity violations.
    
    C:\Windows\system32>chkdsk /scan
    The type of the file system is NTFS.
    
    Stage 1: Examining basic file system structure ...
      378624 file records processed.
    File verification completed.
     Phase duration (File record verification): 6.65 seconds.
      8854 large file records processed.
     Phase duration (Orphan file record recovery): 0.00 milliseconds.
      0 bad file records processed.
     Phase duration (Bad file record checking): 0.80 milliseconds.
    
    Stage 2: Examining file name linkage ...
      197 reparse records processed.
      551388 index entries processed.
    Index verification completed.
     Phase duration (Index verification): 11.71 seconds.
      0 unindexed files scanned.
     Phase duration (Orphan reconnection): 469.15 milliseconds.
      0 unindexed files recovered to lost and found.
     Phase duration (Orphan recovery to lost and found): 0.76 milliseconds.
      197 reparse records processed.
     Phase duration (Reparse point and Object ID verification): 4.36 milliseconds.
    
    Stage 3: Examining security descriptors ...
    Security descriptor verification completed.
     Phase duration (Security descriptor verification): 43.31 milliseconds.
      86383 data files processed.
     Phase duration (Data attribute verification): 0.66 milliseconds.
    CHKDSK is verifying Usn Journal...
      41936640 USN bytes processed.
    Usn Journal verification completed.
     Phase duration (USN journal verification): 219.25 milliseconds.
    
    Windows has scanned the file system and found no problems.
    No further action is required.
    
     999571819 KB total disk space.
     301549696 KB in 267583 files.
        176068 KB in 86384 indexes.
             0 KB in bad sectors.
        519327 KB in use by the system.
         65536 KB occupied by the log file.
     697326728 KB available on disk.
    
          4096 bytes in each allocation unit.
     249892954 total allocation units on disk.
     174331682 allocation units available on disk.
    Total duration: 19.13 seconds (19136 ms).
    
    C:\Windows\system32>wmic recoveros get autoreboot
    AutoReboot
    FALSE
    
    
    C:\Windows\system32>wmic recoveros set autoreboot = false
    Updating property(s) of '\\KKONA\ROOT\CIMV2:Win32_OSRecoveryConfiguration.Name="Microsoft Windows 10 Home|C:\\Windows|\\Device\\Harddisk1\\Partition3"'
    Property(s) update successful.
    
    C:\Windows\system32>wmic recoveros get autoreboot
    AutoReboot
    FALSE
    
    
    C:\Windows\system32>wmic recoveros get DebugInfoType
    DebugInfoType
    7
    
    
    C:\Windows\system32>wmic recoveros set DebugInfoType = 7
    Updating property(s) of '\\KKONA\ROOT\CIMV2:Win32_OSRecoveryConfiguration.Name="Microsoft Windows 10 Home|C:\\Windows|\\Device\\Harddisk1\\Partition3"'
    Property(s) update successful.
    
    C:\Windows\system32>wmic recoveros get DebugInfoType
    DebugInfoType
    7
    
    
    C:\Windows\system32>wmic pagefile list /format:list
    
    
    AllocatedBaseSize=4608
    CurrentUsage=43
    Description=C:\pagefile.sys
    InstallDate=20210225141216.774701-360
    Name=C:\pagefile.sys
    PeakUsage=46
    Status=
    TempPageFile=FALSE
    
    
    
    
    C:\Windows\system32>wmic Computersystem where name="KKONA" get AutomaticManagedPagefile
    AutomaticManagedPagefile
    TRUE
    
    
    C:\Windows\system32>wmic Computersystem where name="KKONA" set AutomaticManagedPagefile=True
    Updating property(s) of '\\KKONA\ROOT\CIMV2:Win32_ComputerSystem.Name="KKONA"'
    Property(s) update successful.
    
    C:\Windows\system32>wmic Computersystem where name="KKONA" get AutomaticManagedPagefile
    AutomaticManagedPagefile
    TRUE
    
    
    C:\Windows\system32>bcdedit /enum {badmemory}
    
    RAM Defects
    -----------
    identifier              {badmemory}
    
    C:\Windows\system32>Echo off
       ###################################################################################
       #    How to capture batch file data and post in your thread in the BSOD forum     #
       #                                                                                 #
       #      Batch files and instructions for use in BSOD debugging[Part Two-Four]      #
       #                                                                                 #
       #        Press [V] to visit the above web page for detailed instructions.         #
       #        Press [C] to close this window.                                          #
       ###################################################################################
      My Computer


  2. Posts : 21,421
    19044.1586 - 21H2 Pro x64
       #2

    @Nimox hello and welcome to TF ,

    Are the PC drivers and BIOS update to date according to PC manufacturer website?

    You mentioned "sfc /scannow" output was good. How about "dism /online /cleanup-image /RestoreHealth" run from powershell with network connect?

    EDIT:
    saw your post 2, so n/mind.
      My Computer


  3. Posts : 9
    Windows 10 Home
    Thread Starter
       #3

    That at the end there in tuneup, does that mean its my memory that needs replacing?

    - - - Updated - - -

    I have never did a bios update for this mobo, i have read around that i shouldnt. Drivers up to date as well. Dism was ran and came back saying everything was good
      My Computer


  4. Posts : 21,421
    19044.1586 - 21H2 Pro x64
       #4

    Nimox said:
    That at the end there in tuneup, does that mean its my memory that needs replacing?

    - - - Updated - - -

    I have never did a bios update for this mobo, i have read around that i shouldnt. Drivers up to date as well. Dism was ran yesterday and came back saying everything was good

    I don't see anything indicating your RAM is bad, but please wait for BSOD experts to respond. In the mean time you could try to run Memtest86 MemTest86 - Official Site of the x86 and ARM Memory Testing Tool to test your RAM.
      My Computer


  5. Posts : 21,421
    19044.1586 - 21H2 Pro x64
       #5

    Nimox said:
    That at the end there in tuneup, does that mean its my memory that needs replacing?

    - - - Updated - - -

    I have never did a bios update for this mobo, i have read around that i shouldnt. Drivers up to date as well. Dism was ran and came back saying everything was good
    Not sure what/where you saw this. Can you post a link.

    I know BIOS-phobia is prevalent with many people on the interweb, but I trust the BIOS engineers and have never had a problem updating my BIOS' - though I prefer to only update if BIOS has been released 6 months or longer.
      My Computer


  6. Posts : 9
    Windows 10 Home
    Thread Starter
       #6

    Honestly i read it from a few different reddit posts of people updating to the newer BIOS for the asrock b450 pro 4 that had alot of issues from it. Haha. Also i find ASRocks BIOS section to be very confusing...ASRock > B450 Pro4 So i just never really updated.



    Edit - Atm running 3.10 BIOS that my mobo came out of the box with. Should i try updating to 3.50 and see if it fixes the crashing issue? It seems the newer versions are not recommended for Ryzen 5 2600 Pinnacle Ridge.
      My Computer


  7. Posts : 21,421
    19044.1586 - 21H2 Pro x64
       #7

    Nimox said:
    Honestly i read it from a few different reddit posts of people updating to the newer BIOS for the asrock b450 pro 4 that had alot of issues from it. Haha. Also i find ASRocks BIOS section to be very confusing...ASRock > B450 Pro4 So i just never really updated.
    I would definitely heed to their warnings like "*ASRock do NOT recommend updating this BIOS if you are going to use Pinnacle, Raven or Summit Ridge CPU on your system." - I don't have one of these motherboards, so let's see if someone who does responds.
      My Computer


  8. Posts : 9
    Windows 10 Home
    Thread Starter
       #8

    Sorry ill stop editing my posts and ill wait for a response instead., Haha
      My Computer


  9. Posts : 21,421
    19044.1586 - 21H2 Pro x64
       #9

    Nimox said:
    Sorry ill stop editing my posts and ill wait for a response instead., Haha
    Please feel free to edit
      My Computer


  10. Posts : 9
    Windows 10 Home
    Thread Starter
       #10

    So i took the time and updated my bios to 3.50 and will run a few stress tests over night and whatever else to to see if my pc will still crash. Ill give another update by mid afternoonish today.
      My Computer


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd
All times are GMT -5. The time now is 13:48.
Find Us




Windows 10 Forums