Random restarts, need help!

Page 1 of 2 12 LastLast

  1. Posts : 7
    Win10
       #1

    Random restarts, need help!


    Hello All!

    A few weeks ago I began to experience random BSOD / random power loss...usually while PC is idle but has happened when gaming. Thinking it was PSU related, swapped two additional units (Seasonic and EVGA) and still ran into this issue. From there reinstalled the OS (Win10 20H2 OS Build 19042.685) , tried different RAM kits (with and without XMP enabled), and recently tried a new GPU...still the same issue. I believe I ran everything per specifications, but I am at wits end and could use some assistance (please and thank you!). PBO is currently disabled, but still getting random crashes.

    Logs can be found here: Attachment 311376
      My Computer

  2. Macboatmaster's Avatar
    Posts : 910
    10, 8.1 and 7 all Professional versions, and Linux Mint
       #2

    An initial examination of the logs shows there is no dump file.
    The reason for that is in the system event log
    Event[9443]:
    Log Name: System
    Source: volmgr
    Date: 2020-12-19T12:51:00.5970000Z
    Event ID: 49
    Task: N/A
    Level: Error
    Opcode: N/A
    Keyword: Classic
    User: N/A
    User Name: N/A
    Computer: DESKTOP-RU5AO8I
    Description:
    Configuring the Page file for crash dump failed. Make sure there is a page file on the boot partition and that is large enough to contain all physical memory.
    Check please that you have the settings correct for the dumps and the page file of correct size - - system managed on C is the best setting


    HOWEVER first try these
    There are a number of apparent errors with
    Log Name: Application
    Source: OVRServiceLauncher

    This will be related to your Oculus Headset or the like
    Oculus Setup: Rift S, Rift, Quest & Go | Oculus

    Uninstall your Oculus software


    ALSO CHECK that driver verifier is NOT running. You did at one time have it running
    Enable and Disable Driver Verifier in Windows 10

    as per part 3 disable.

    As at sometime you have had it set to verify drivers
      My Computer


  3. Posts : 7
    Win10
    Thread Starter
       #3

    Macboatmaster said:
    An initial examination of the logs shows there is no dump file.
    The reason for that is in the system event log


    Check please that you have the settings correct for the dumps and the page file of correct size - - system managed on C is the best setting


    HOWEVER first try these
    There are a number of apparent errors with
    Log Name: Application
    Source: OVRServiceLauncher

    This will be related to your Oculus Headset or the like
    Oculus Setup: Rift S, Rift, Quest & Go | Oculus

    Uninstall your Oculus software


    ALSO CHECK that driver verifier is NOT running. You did at one time have it running
    Enable and Disable Driver Verifier in Windows 10

    as per part 3 disable.

    As at sometime you have had it set to verify drivers
    Hi Macboatmaster,

    Thanks for the response! I uninstalled the Oculus software, and made sure that Driver Verifier is not running. Regarding the dump file, the file location never existed. I had to manually create a folder and point the dumps to it, so I guess now we wait. I have HWinfo in the background logging, currently going to let the PC idle and see if a restart happens. After that, I'll re-run V2 Log collector and hopefully windows generates the file this tine >.<
      My Computer

  4. Macboatmaster's Avatar
    Posts : 910
    10, 8.1 and 7 all Professional versions, and Linux Mint
       #4

    You do NOT have to manually create the folder
    You commission the dump file ability as here
    Configure Windows 10 to Create Minidump on BSOD

    automatic memory dump is the recognised setting for 10 and see post 17 for actual settings
    Have you checked the paging file is on C drive and set system managed.
      My Computer


  5. Posts : 7
    Win10
    Thread Starter
       #5

    Macboatmaster said:
    You do NOT have to manually create the folder
    You commission the dump file ability as here
    Configure Windows 10 to Create Minidump on BSOD

    automatic memory dump is the recognised setting for 10 and see post 17 for actual settings
    Have you checked the paging file is on C drive and set system managed.
    Dump location returned back to default (%SystemRoot%\MEMORY.DMP), and the paging file is on the C (primary)...and it is set to system managed.
      My Computer

  6. Macboatmaster's Avatar
    Posts : 910
    10, 8.1 and 7 all Professional versions, and Linux Mint
       #6

    Cheers
    Was Verifier running = please
      My Computer


  7. Posts : 7
    Win10
    Thread Starter
       #7

    Macboatmaster said:
    Cheers
    Was Verifier running = please
    If I understood correctly verifier needs to be running (for up to 48 hour) and if I get the BSOD/failure restart, stop verifier, run V2 Log collector, and post results...correct?
      My Computer

  8. Macboatmaster's Avatar
    Posts : 910
    10, 8.1 and 7 all Professional versions, and Linux Mint
       #8

    Please do not have Driver Verifier running.
    I know you posted
    and made sure that Driver Verifier is not running.
    but when I then asked -
    Was Verifier running = please
    and now you have replied -
    If I understood correctly verifier needs to be running (for up to 48 hour)
    I am not now sure if you have turned verifier on again.
    It is NOT necessary or indeed appropriate to run Verifier at this stage.

    There are IMHO more pressing issues to address
    1. You have installed a BETA BIOS
    SMBIOSBIOSVersion : F31e
    F31e was a Beta BIOS - Beta BIOS versions are not meant for installation on your main computer
    They are released for testing purposes, as with any other BETA driver.

    It is not something you should feel bad about as unless you know that a BIOS with a letter after it - on your motherboard site is a BETA version - as with the latest F31o -
    X570 AORUS XTREME (rev. 1.1) Support | Motherboard - GIGABYTE Global

    as far as I can see Gigabyte do not make it clear in that regard
    However please be assured that it is.

    Also I think you have windows installed in legacy bios version and NOT in UEFI
    I am NOT suggesting that is the cause of the problems, but there is no benefit to running that system on traditional BIOS - legacy rather than UEFI.
      My Computer


  9. Posts : 7
    Win10
    Thread Starter
       #9

    Macboatmaster said:
    Please do not have Driver Verifier running.
    I know you posted

    but when I then asked -


    and now you have replied -


    I am not now sure if you have turned verifier on again.
    It is NOT necessary or indeed appropriate to run Verifier at this stage.

    There are IMHO more pressing issues to address
    1. You have installed a BETA BIOS
    SMBIOSBIOSVersion : F31e
    F31e was a Beta BIOS - Beta BIOS versions are not meant for installation on your main computer
    They are released for testing purposes, as with any other BETA driver.

    It is not something you should feel bad about as unless you know that a BIOS with a letter after it - on your motherboard site is a BETA version - as with the latest F31o -
    X570 AORUS XTREME (rev. 1.1) Support | Motherboard - GIGABYTE Global

    as far as I can see Gigabyte do not make it clear in that regard
    However please be assured that it is.

    Also I think you have windows installed in legacy bios version and NOT in UEFI
    I am NOT suggesting that is the cause of the problems, but there is no benefit to running that system on traditional BIOS - legacy rather than UEFI.
    Ok, glad we are on the same page (driver verifier NOT running). Regarding the BIOS version, I had these random restart issues on F30 as well...and thought I'd have a Ryzen 5000 series cpu in hand close to launch (HA!). Regarding Windows, must have selected the wrong option when re-installing the OS. Previous install was done vis UEFI, and if that ends up being part of the solution I'll reinstall.
      My Computer

  10. Macboatmaster's Avatar
    Posts : 910
    10, 8.1 and 7 all Professional versions, and Linux Mint
       #10

    Cheers
    Please let me know if you get another crash with BSOD and if so send the dump file
    Or if there are any glitches without BSOD

    =========================================

    A further check of your logs shows that you have this graphic card
    EVGA RTX 3090 24 GB
    Please confirm that to be the case as I got it from the PCI\VEN
    NVIDIA GeForce RTX 3090
    DeviceID : VideoController1
    PNPDeviceID : PCI\VEN_10DE&DEV_2204&SUBSYS_39983842&REV_A1\4&2283F625&0&0019


    You have the EVGA Precision software installed.
    However you also have MSI Afterburner and the logs show that MSI Afterburner
    MSI Afterburner 4.6.2 4.6.2 MSI Co., LTD
    has apparently caused problems on many occasions when the application has crashed with a fatal error
    AppName=gpu_stressor.exe
    AppPath=C:\Program Files (x86)\MSI Afterburner\Bundle\OCScanner\gpu_stressor.exe

    I suggest you uninstall MSI Afterburner IF I AM correct that you have the EVGA card.

    I do appreciate MSI Afterburner works with any card not just MSI, but I do not think it best to run both the MSI and the EVGA Precision
    EVGA Precision X1 1.1.4.0 EVGA Corporation
    which - windows has reported problems with on one occasion.
    That MAY have been the running of both apps

    As I said, please uninstall MSI Afterburner and as mentioned at first on this post report any problems please
    Last edited by Macboatmaster; 20 Dec 2020 at 10:02.
      My Computer


 
Page 1 of 2 12 LastLast

  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 10:52.
Find Us




Windows 10 Forums