BSOD at least twice a month - uncertain cause

Page 3 of 8 FirstFirst 12345 ... LastLast

  1. Posts : 58
    Windows 10 Pro 64 bit v1809
    Thread Starter
       #21

    Yup - the last BSOD stated MEMORY_MANAGEMENT and I let the counter run to 100% before rebooting

    Next time, I will run the BETA log collector and find & zip the memory.dmp file

    I wish there were a way to disable to automatic cleanup of minidumps and the MEMORY.DMP file
      My ComputerSystem Spec


  2. Posts : 58
    Windows 10 Pro 64 bit v1809
    Thread Starter
       #22

    Had another BSOD, but this time the Stop Code is SYSTEM_SERVICE_EXCEPTION (as opposed to Memory Management). It happened when I woke the computer from Standby and logged into Windows (a few seconds into the login)

    Here is the screenshot: Imgur: The magic of the Internet

    Here is the link for the Dropbox share with the BETA log collector file + MEMORY.DMP (both zipped and unzipped): Dropbox - BSOD - Simplify your life
      My ComputerSystem Spec


  3. Posts : 25,509
    windows 10 professional version 1607 build 14393.969 64 bit
       #23

    For any BSOD please post:
    a) A new BETA log collector zip
    b) memory.dmp if the file size is < 1.5 GB
    c) please keep these files separate so that the BETA zip file can be viewed while the memory dump is downloading.

    Code:
    Crash dump found at C:\WINDOWS\MEMORY.DMP
    Creation date: 01/21/2019 09:44:50
    Size on disk: 1308 MB

    1) Please post a new separate BETA log collector zip into the thread.

    2) Open administrative command prompt and type or copy and paste:
    3) sfc /scannow
    4) dism /online /cleanup-image /restorehealth
    5) chkdsk /scan
    6) wmic RecoverOS set AutoReboot = False
    7) When these have completed > right click on the top bar or title bar of the administrative command prompt box > left click on edit then select all > right click on the top bar again > left click on edit then copy > paste into the thread

    It can be easy to miss BSOD when automatically restart is checked.
    When there is a BSOD and automatically restart is unchecked you should see a BSOD window with bugcheck and : (
    Sometimes you may see a misbehaving driver in the form *.sys
    At the very beginning of a BSOD you may see a % counter
    If you see the % counter allow it to rise to 100% before rebooting so that there is sufficient time to create the dump file
    Step #6 will modify the startup and recovery system so that automatically restart is unchecked.


    8) uninstall the Nvidia GPU driver using DDU (display driver uninstaller)
    9) re-install the Nvidia GPU driver from the Nvidia website
    10) make sure that you check the clean install box and if available install the physx driver.


    Display Driver Uninstaller Download version 18.0.0.7 (or newer version if available)
    Display Driver Uninstaller: How to use - Windows 7 Help Forums
    NVIDIA
    Download Display Driver Uninstaller - MajorGeeks



    Code:
    Name	NVIDIA GeForce GTX 970
    PNP Device ID	PCI\VEN_10DE&DEV_13C2&SUBSYS_29743842&REV_A1\4&1286464&0&0008
    Adapter Type	GeForce GTX 970, NVIDIA compatible
    Adapter Description	NVIDIA GeForce GTX 970
    Adapter RAM	(1,048,576) bytes
    Installed Drivers	C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_95d88c9d04436846\nvldumdx.dll,C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_95d88c9d04436846\nvldumdx.dll,C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_95d88c9d04436846\nvldumdx.dll,C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_95d88c9d04436846\nvldumdx.dll
    Driver Version	23.21.13.9124
    INF File	oem1.inf (Section096 section)
    Color Planes	Not Available
    Color Table Entries	4294967296
    Resolution	1920 x 1080 x 60 hertz
    Bits/Pixel	32
    Memory Address	0xF6000000-0xF70FFFFF
    Memory Address	0xE0000000-0xF1FFFFFF
    Memory Address	0xF0000000-0xF1FFFFFF
    I/O Port	0x0000E000-0x0000EFFF
    IRQ Channel	IRQ 16
    I/O Port	0x000003B0-0x000003BB
    I/O Port	0x000003C0-0x000003DF
    Memory Address	0xA0000-0xBFFFF
    Driver	c:\windows\system32\driverstore\filerepository\nv_dispi.inf_amd64_95d88c9d04436846\nvlddmkm.sys (23.21.13.9124, 16.71 MB (17,526,688 bytes), 3/24/2018 11:57 AM)
    Code:
    nvlddmkm	nvlddmkm	c:\windows\system32\driverstore\filerepository\nv_dispi.inf_amd64_95d88c9d04436846\nvlddmkm.sys	Kernel Driver	Yes	Manual	Running	OK	Ignore	No	Yes
    Code:
    nvlddmkm.sys Thu Mar 15 15:30:24 2018 (5AAAF400)
    Last edited by zbook; 21 Jan 2019 at 11:58.
      My ComputerSystem Spec


  4. Posts : 58
    Windows 10 Pro 64 bit v1809
    Thread Starter
       #24

    As requested with BETA log + CMD log attached

    GPU driver uninstalled and re-installed as instructed
    BSOD at least twice a month - uncertain cause Attached Files
    Last edited by LeoBloom; 21 Jan 2019 at 16:42.
      My ComputerSystem Spec


  5. Posts : 25,509
    windows 10 professional version 1607 build 14393.969 64 bit
       #25

    The text data are fine.
    So far it appears that the bit flip was a misbehaving hardware driver.
    If there are no more BSOD this will complete the troubleshooting.
    If there are more BSOD and they are related to the GPU driver another driver version can be used.
    If there are recurrent BSOD with multiple driver versions then the hardware will need to be troubleshooted.
      My ComputerSystem Spec


  6. Posts : 58
    Windows 10 Pro 64 bit v1809
    Thread Starter
       #26

    Thanks zbook - to confirm, this BSOD was not related to the RAM (but rather GPU), correct?

    The majority of my BSOD were memory_management before.
      My ComputerSystem Spec


  7. Posts : 25,509
    windows 10 professional version 1607 build 14393.969 64 bit
       #27

    @philc43 had found the bit flip and asked that the RAM be tested over several weeks.
    Make sure that all of the RAM tests have been completed so that the problems related to RAM can be ruled in/out.

    It took a lot of time for the BSOD to display the misbehaving driver.
    At this moment in time a cause for the BSOD has been identified.

    Options include:

    a) continue to use the computer and report any BSOD
    and if there are any BSOD the dump files can be debugged to find a misbehaving driver or malfunctioning hardware

    versus

    b) using a tool which can immediately cause misbehaving drivers to BSOD
      My ComputerSystem Spec


  8. Posts : 58
    Windows 10 Pro 64 bit v1809
    Thread Starter
       #28

    OK - will proceed with option a) given that the GPU driver issue appears to be a one-off event. Will keep the current RAM configuration in the meantime. Thanks
      My ComputerSystem Spec


  9. Posts : 25,509
    windows 10 professional version 1607 build 14393.969 64 bit
       #29

    Please update the progress in the RAM testing.
      My ComputerSystem Spec


  10. Posts : 58
    Windows 10 Pro 64 bit v1809
    Thread Starter
       #30

    Just had another BSOD: DPC_WATCHDOG_VIOLATION

    Occurred while scrubbing through a video file

    See attached log

    Link to MEMORY.DMP: Dropbox - MEMORY.zip
    BSOD at least twice a month - uncertain cause Attached Files
      My ComputerSystem Spec


 
Page 3 of 8 FirstFirst 12345 ... LastLast

Related Threads
Random BSOD for the last month in BSOD Crashes and Debugging
Hey Guys, My PC keeps randomly BSODing mainly from DRIVER_IRQL_NOT_LESS_OR_EQUAL 00000000`00000000. Have tried different GPU & RAM. Have even done a fresh install to no avail any help would be much appreciated. Thanks in advance.
4 BSOD's on 2-month old PC in BSOD Crashes and Debugging
Recently built a new PC, and it works excellently well however over the last 3 weeks I've had 4 BSOD's all with the same bugcheck error code from Event Log I don't know how it starts or what triggers it. It simply runs into the issue every few...
3rd BSOD in a month in BSOD Crashes and Debugging
Hello. Last night I received my 3rd blue screen error in about a month. That one and the previous one said "system service exception (netio.sys)." I forget if the first time this happened the error listed the same. Anyway, here's my log file...
Multiple bsod's in last month in BSOD Crashes and Debugging
Hello, I have had multiple bsod's in the last month. they seem to occur when pc is not doing anything. When im working on it it bsod's sometimes, but when i walk away it will in a matter of minutes. 61517 i hope someone can tell me what is...
Keep getting BSOD for the pass 2 month in BSOD Crashes and Debugging
BlueScreenView says that its ntoskrnl.exe driver error.
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 14:20.
Find Us