Black screen with sound followed by manual restart with no dump

Page 1 of 3 123 LastLast

  1. Posts : 11
    Windows 10
       #1

    Black screen with sound followed by manual restart with no dump


    setup:
    i9 9900k
    Gigabyte 3080 VISION OC
    PSU: corsair hxi 750w
    32gb ram 3200mhz
    ROG STRIX Z390-F GAMING
    winver: Screenshot - 491dd1e44c317af8df42c56cd27c8801 - Gyazo

    For the past few weeks I've been having random black screen freezes, where the sound goes on for a few more second followed by a complete freeze.
    Dumps are enabled: Screenshot - ca3572433f4d644f8a0e992c30580e3d - Gyazo
    Using NotMyFault (https://docs.microsoft.com/en-us/sys...ads/notmyfault) dump are working fine.
    Mini dump from "self triggered" bsod:
    Screenshot - 553b0c897876cf894f20970c78354182 - Gyazo

    However when this happens I have the following event in event viewer.
    Screenshot - 412f23396186fbb745305a78276c17ab - Gyazo
    - System
    - Provider
    [ Name] volmgr
    - EventID 161
    [ Qualifiers] 49156
    Version 0
    Level 2
    Task 0
    Opcode 0
    Keywords 0x80000000000000
    - TimeCreated
    [ SystemTime] 2020-12-04T14:32:12.4597853Z
    EventRecordID 12825
    Correlation
    - Execution
    [ ProcessID] 4
    [ ThreadID] 572
    Channel System
    Computer DESKTOP-FP5PJN6
    Security
    - EventData
    \Device\HarddiskVolume7
    000000000100000000000000A10004C081000200010000C000000000000000000000000000000000


    It seem to happen at random times.
    I reinstalled my graphics driver using DDU via Safe mode.

    As a side note, I have the 3080 for around one month now, and this only started happening for the past week-ish.
    Hah 6 of these events in the past 7 days, two of them happened more or less back to back.

    To troubleshoot, I left a game on the main screen overnight a few time, GPU underload, CPU underload and it went for 10+ hours straight with no problems.

    SSD Health status is good in CrystalDiskInfo(97% for windows partition)

    Is there anything else I can check to point me in the right direction ?
    Could it be the PSU ?


    later edit: temperatures are well within limits for both CPU and GPU
    later later edit: no OC on either CPU or GPU
    later later later edit:
    1. sfc /scannow
    2. DISM /Online /Cleanup-Image /RestoreHealth
    ran both, no issues

    Attachment 309186

    - - - Updated - - -

    The mini dump from the .zip is not related to the crashes I've been having, that's a self triggered bsod to check if dumps are being generated

    - - - Updated - - -

    aida64 extreme has been running with all stress tests enabled for the past 2 hours(and still going)
    GPU power draw at 100% load was constant at ~306w
    CPU max power draw was 148 then "regulated" to 95W throughout the test
    GPU core temp was around 64-66 degrees
    CPU temps were ~65 degrees

    Screenshot - 644776f52f63add2b5ff7fe38c20117f - Gyazo

    - - - Updated - - -

    A bit over 3 hours now, on aida64. Manually stopped the test.
    Will play the game for a bit then run aida64 again overnight

    - - - Updated - - -

    another useful thing I might have left out, my pc more or less run 24/7, with a manual restart in the morning and a manual restart about 6PM GMT.
    During the day I use it as a workstation with BDO(Black desert online) in the background(either minimized in the tray running at 3fps, or in the background if I watch the market) and overnight my character does "afk" stuff usually minimized ,however in my last few overnight tests I left it in the foreground with no black screen issue( but it did black screen during the day)
    Last edited by evildoll; 04 Dec 2020 at 12:56. Reason: winver
      My Computer


  2. Posts : 13,961
    Windows 10 Pro X64 21H1 19043.1503
       #2

    No real dumps in the zip file then, bummer. WER data from msinfo32 shows only the dump you forced.

    Looks like you had 7 BSODs.

    Attachment 309199

    This is the System Event log info around it:

    Attachment 309200

    Without dumps it's hard to know what the cause is.

    I recommend enabling Driver Verifier to see if that shakes out a bad driver.

    Driver Verifier-- tracking down a mis-behaving driver.

    Following the instructions in the above link will check for problems in all non-Microsoft drivers.

    What we're looking for is a verifier generated BSOD with a mini dump that will tell us what driver caused it. If you get a BSOD, rerun the V2 log collector as soon as possible and upload the resulting zip file. Also see if there is a new C:\Windows \MEMORY.DMP file. If there is, copy it to another location then zip it an upload to a file sharing site like OneDrive and post a link to it here.

    To check if verifier is active, open a Command Prompt and enter:

    verifier /query

    If not active it will respond with

    No drivers are currently verified.

    Follow instructions here to decide which drivers you want to test. 3-5 is a good start. Add 3-5 more every two hours until all are selected or you get a BSOD.

    Enable and Disable Driver Verifier in Windows 10

    Familiarize yourself with how to get out of Driver verifier from the above link and from the first link.

    One other thing, check the PSU voltages in UEFI setup then using HWMONITOR.
      My Computers


  3. Posts : 11
    Windows 10
    Thread Starter
       #3

    Ztruker said:
    No real dumps in the zip file then, bummer. WER data from msinfo32 shows only the dump you forced.

    Looks like you had 7 BSODs.

    Attachment 309199

    This is the System Event log info around it:

    Attachment 309200

    Without dumps it's hard to know what the cause is.

    I recommend enabling Driver Verifier to see if that shakes out a bad driver.

    Driver Verifier-- tracking down a mis-behaving driver.

    Following the instructions in the above link will check for problems in all non-Microsoft drivers.

    What we're looking for is a verifier generated BSOD with a mini dump that will tell us what driver caused it. If you get a BSOD, rerun the V2 log collector as soon as possible and upload the resulting zip file. Also see if there is a new C:\Windows \MEMORY.DMP file. If there is, copy it to another location then zip it an upload to a file sharing site like OneDrive and post a link to it here.

    To check if verifier is active, open a Command Prompt and enter:

    verifier /query

    If not active it will respond with

    No drivers are currently verified.

    Follow instructions here to decide which drivers you want to test. 3-5 is a good start. Add 3-5 more every two hours until all are selected or you get a BSOD.

    Enable and Disable Driver Verifier in Windows 10

    Familiarize yourself with how to get out of Driver verifier from the above link and from the first link.

    One other thing, check the PSU voltages in UEFI setup then using HWMONITOR.
    Thanks alot, will have a look at driver verifier the next few days(I'll be out for the weekend).

    Voltages in HW Monitor throughout the Aida64 test seemed fine.
    Screenshot - c7de7cbfcf84936568417cfb62257c59 - Gyazo

    edit: just a small question, the link you provided wrt. driver verifier mentions different setting to be used. Which one should I follow ?
    https://www.tenforums.com/attachment...d-settings.jpg
    or
    the other one

    edit2: how can I add more drivers to be verified ? do I need to stop the verifier and restart the whole process ,or can I simply open the verifier app(which should already be running) select more driver, reboot etc. I guess what I'm asking is if I need to stop driver verifier every time, in between adding more drivers to be checked.

    - - - Updated - - -

    Ztruker said:
    No real dumps in the zip file then, bummer. WER data from msinfo32 shows only the dump you forced.

    Looks like you had 7 BSODs.

    Attachment 309199

    This is the System Event log info around it:

    Attachment 309200

    Without dumps it's hard to know what the cause is.

    I recommend enabling Driver Verifier to see if that shakes out a bad driver.

    Driver Verifier-- tracking down a mis-behaving driver.

    Following the instructions in the above link will check for problems in all non-Microsoft drivers.

    What we're looking for is a verifier generated BSOD with a mini dump that will tell us what driver caused it. If you get a BSOD, rerun the V2 log collector as soon as possible and upload the resulting zip file. Also see if there is a new C:\Windows \MEMORY.DMP file. If there is, copy it to another location then zip it an upload to a file sharing site like OneDrive and post a link to it here.

    To check if verifier is active, open a Command Prompt and enter:

    verifier /query

    If not active it will respond with

    No drivers are currently verified.

    Follow instructions here to decide which drivers you want to test. 3-5 is a good start. Add 3-5 more every two hours until all are selected or you get a BSOD.

    Enable and Disable Driver Verifier in Windows 10

    Familiarize yourself with how to get out of Driver verifier from the above link and from the first link.

    One other thing, check the PSU voltages in UEFI setup then using HWMONITOR.
    quoting to make sure you'll see me previous post edits + to add the below:

    Screenshot - dda30b068815c3f2b57d4cf0deb3770f - Gyazo
    Screenshot - 875fca0e575baeadc335da7b2d7fc42d - Gyazo

    These are the only non Microsoft drivers I have installed.
    Any particular ones I should start with ?
    Last edited by evildoll; 04 Dec 2020 at 15:57.
      My Computer


  4. Posts : 13,961
    Windows 10 Pro X64 21H1 19043.1503
       #4

    I would uninstall Bit Defender completely and run with Windows Defender for now. Use the Bit Defender removal tool.


    Next check the Intel drivers and test for a couple hours and if okay then add the Logitech drivers then run for up to 48 hours or until you get a BSOD. If you do get one, reset Verifier then run V2 and upload the zip. Make sure you understand how to get rid of Verifier before you use it. Both of the links I post have info on how to do that.

    Also, if there is a C:\Windows\MEMORY.DMP file, zip it and upload that to a file sharing site and post a link to it here.
      My Computers


  5. Posts : 11
    Windows 10
    Thread Starter
       #5

    Ztruker said:
    I would uninstall Bit Defender completely and run with Windows Defender for now. Use the Bit Defender removal tool.


    Next check the Intel drivers and test for a couple hours and if okay then add the Logitech drivers then run for up to 48 hours or until you get a BSOD. If you do get one, reset Verifier then run V2 and upload the zip. Make sure you understand how to get rid of Verifier before you use it. Both of the links I post have info on how to do that.

    Also, if there is a C:\Windows\MEMORY.DMP file, zip it and upload that to a file sharing site and post a link to it here.
    Understood, thank you very much.
    I'm uninstalling bit defender now.
    I also managed to get rid of asio2.sys which is was some lingering Asus AISuite3 driver.

    I also ran aida64 last night, full force, for 8 hours, with no problems.
      My Computer


  6. Posts : 40,002
    windows 10 professional version 1607 build 14393.969 64 bit
       #6

    Please open administrative command prompt and type or copy and paste:

    Code:
    move "C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20201204-1631.dmp" "%USERPROFILE%\Desktop"

    Post a share link using one drive, drop box, or google drive.



    Run:

    Tuneup.bat - Click here to go to the BSOD batch repository to download and run this batch file.
      My Computer



  7. Posts : 11
    Windows 10
    Thread Starter
       #7

    zbook said:
    Please open administrative command prompt and type or copy and paste:

    Code:
    move "C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20201204-1631.dmp" "%USERPROFILE%\Desktop"

    Post a share link using one drive, drop box, or google drive.



    Run:

    [FONT="]Tuneup.bat[/FONT] - Click here to go to the BSOD batch repository to download and run this batch file.
    Here's the results and the dmp file: WeTransfer download link for that .dmp file


    ###########################################################
    # 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="DESKTOP-FP5PJN6" get AutomaticManagedPagefile
    wmic Computersystem where name="DESKTOP-FP5PJN6" set AutomaticManagedPagefile=True
    wmic Computersystem where name="DESKTOP-FP5PJN6" 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.572

    Image Version: 10.0.19042.662

    [==========================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.572

    Image Version: 10.0.19042.662

    [==========================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.
    Volume label is Windows.

    Stage 1: Examining basic file system structure ...
    989440 file records processed.
    File verification completed.
    Phase duration (File record verification): 5.56 seconds.
    12655 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.18 milliseconds.

    Stage 2: Examining file name linkage ...
    685 reparse records processed.
    1249740 index entries processed.
    Index verification completed.
    Phase duration (Index verification): 17.72 seconds.
    0 unindexed files scanned.
    Phase duration (Orphan reconnection): 1.50 seconds.
    0 unindexed files recovered to lost and found.
    Phase duration (Orphan recovery to lost and found): 0.36 milliseconds.
    685 reparse records processed.
    Phase duration (Reparse point and Object ID verification): 4.91 milliseconds.

    Stage 3: Examining security descriptors ...
    Security descriptor verification completed.
    Phase duration (Security descriptor verification): 37.30 milliseconds.
    130151 data files processed.
    Phase duration (Data attribute verification): 0.82 milliseconds.
    CHKDSK is verifying Usn Journal...
    37968704 USN bytes processed.
    Usn Journal verification completed.
    Phase duration (USN journal verification): 108.47 milliseconds.

    Windows has scanned the file system and found no problems.
    No further action is required.

    243567615 KB total disk space.
    139249128 KB in 494687 files.
    367444 KB in 130152 indexes.
    0 KB in bad sectors.
    1108067 KB in use by the system.
    65536 KB occupied by the log file.
    102842976 KB available on disk.

    4096 bytes in each allocation unit.
    60891903 total allocation units on disk.
    25710744 allocation units available on disk.
    Total duration: 24.94 seconds (24949 ms).

    C:\WINDOWS\system32>wmic recoveros get autoreboot
    AutoReboot
    FALSE


    C:\WINDOWS\system32>wmic recoveros set autoreboot = false
    Updating property(s) of '\\DESKTOP-FP5PJN6\ROOT\CIMV2:Win32_OSRecoveryConfiguration.Name="Microsoft Windows 10 Pro|C:\\WINDOWS|\\Device\\Harddisk0\\Partition4"'
    Property(s) update successful.

    C:\WINDOWS\system32>wmic recoveros get autoreboot
    AutoReboot
    FALSE


    C:\WINDOWS\system32>wmic recoveros get DebugInfoType
    DebugInfoType
    3


    C:\WINDOWS\system32>wmic recoveros set DebugInfoType = 7
    Updating property(s) of '\\DESKTOP-FP5PJN6\ROOT\CIMV2:Win32_OSRecoveryConfiguration.Name="Microsoft Windows 10 Pro|C:\\WINDOWS|\\Device\\Harddisk0\\Partition4"'
    Property(s) update successful.

    C:\WINDOWS\system32>wmic recoveros get DebugInfoType
    DebugInfoType
    7


    C:\WINDOWS\system32>wmic pagefile list /format:list


    AllocatedBaseSize=5120
    CurrentUsage=0
    Description=C:\pagefile.sys
    InstallDate=20201202222327.439505+120
    Name=C:\pagefile.sys
    PeakUsage=0
    Status=
    TempPageFile=FALSE




    C:\WINDOWS\system32>wmic Computersystem where name="DESKTOP-FP5PJN6" get AutomaticManagedPagefile
    AutomaticManagedPagefile
    TRUE


    C:\WINDOWS\system32>wmic Computersystem where name="DESKTOP-FP5PJN6" set AutomaticManagedPagefile=True
    Updating property(s) of '\\DESKTOP-FP5PJN6\ROOT\CIMV2:Win32_ComputerSystem.Name="DESKTOP-FP5PJN6"'
    Property(s) update successful.

    C:\WINDOWS\system32>wmic Computersystem where name="DESKTOP-FP5PJN6" get AutomaticManagedPagefile
    AutomaticManagedPagefile
    TRUE


    C:\WINDOWS\system32>bcdedit /enum {badmemory}

    RAM Defects
    -----------
    identifier {badmemory}
    Press any key to continue . . .
    ---------------------------
    ---------------------------
    ---------------------------
    ---------------------------
    I'll try and make some time and run driver verifier the next days
      My Computer


  8. Posts : 13,961
    Windows 10 Pro X64 21H1 19043.1503
       #8

    The dmp shows a video problem occurred:

    Code:
    VIDEO_TDR_TIMEOUT_DETECTED (117)
    The display driver failed to respond in timely fashion.
    (This code can never be used for a real bugcheck.)
    Arguments:
    Arg1: ffff8c84e76bb050, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
    Arg2: fffff8022c062298, The pointer into responsible device driver module (e.g owner tag).
    Arg3: 0000000000000000, The secondary driver specific bucketing key.
    Arg4: 000000000000056c, Optional internal context dependent data.
    Do you still have the old video card? If yes can you remove the 3080 and install the old card and test. Since you've already installed the latest Nvidia driver using DDU this is looking more like a hardware problem, unless you are doing some over clocking. Are you?
      My Computers


  9. Posts : 11
    Windows 10
    Thread Starter
       #9

    Ztruker said:
    The dmp shows a video problem occurred:

    Code:
    VIDEO_TDR_TIMEOUT_DETECTED (117)
    The display driver failed to respond in timely fashion.
    (This code can never be used for a real bugcheck.)
    Arguments:
    Arg1: ffff8c84e76bb050, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
    Arg2: fffff8022c062298, The pointer into responsible device driver module (e.g owner tag).
    Arg3: 0000000000000000, The secondary driver specific bucketing key.
    Arg4: 000000000000056c, Optional internal context dependent data.
    Do you still have the old video card? If yes can you remove the 3080 and install the old card and test. Since you've already installed the latest Nvidia driver using DDU this is looking more like a hardware problem, unless you are doing some over clocking. Are you?
    Yep, still have the old card. I'm running driver verifier right not, will do it overnight.
    Used to have an underclock+overclock on the 3080 but removed it after the black screens but it still happened.

    I ordered a new PSU today as mine was kinda due an update as-well, corsair hx750i, however it's 5 years old.
    If I don't have any black screens tonight, and it still happens after I swap in the new PSU, it's clearly the GPU to blame.
      My Computer


  10. Posts : 40,002
    windows 10 professional version 1607 build 14393.969 64 bit
       #10

    Post a share link using one drive, drop box, or google drive.
      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 08:16.
Find Us




Windows 10 Forums