Silent random BSOD occurring in the background

Page 1 of 3 123 LastLast

  1. Posts : 428
    Windows 10 Pro x64 Version 1803
       #1

    Silent random BSOD occurring in the background


    Hello,

    Out of nowhere, I noticed a hardware error in the Reliability History without noticing anything weird around that time when using my PC; there were no freezes, black screens, BSOD's or reboots. I recall watching YouTube videos at that time. Nothing is overclocked, it's a fresh install of Windows 10 Pro x64 October Update. PC is 10 months old.

    - I have attached the V2 Log Collector as requested and the WER file. Please see the attachments.
    - Here is the link to the dump file (large size, around 1.1GB)

    What is causing this error and how to fix it?
    Silent random BSOD occurring in the background Attached Files
    Last edited by JohnnyGui; 13 May 2019 at 18:23.
      My Computer

  2. Ztruker's Avatar
    Posts : 10,229
    Windows 10 Pro X64 1909 18363.815
       #2

    Follow the instructions at the link in the yellow box at the top of your thread and at the top of the forum.

    For the MEMORY.DMP file, copy it to another location ASAP as it may be deleted. Zip it then upload to a file sharing site like OneDrive or Dropbox. Post a share link here.
      My Computers


  3. Posts : 428
    Windows 10 Pro x64 Version 1803
    Thread Starter
       #3

    Ztruker said:
    Follow the instructions at the link in the yellow box at the top of your thread and at the top of the forum.

    For the MEMORY.DMP file, copy it to another location ASAP as it may be deleted. Zip it then upload to a file sharing site like OneDrive or Dropbox. Post a share link here.
    I have edited my OP accordingly. Waiting for anyone's help.
      My Computer

  4. Ztruker's Avatar
    Posts : 10,229
    Windows 10 Pro X64 1909 18363.815
       #4

    Looked a the full dump:
    Code:
    BugCheck AB, {3, 200, 0, 5}
    Probably caused by : win32kfull.sys ( win32kfull!CheckSessionPoolAllocations+8caae )
    0: kd> !analyze -v
    
    SESSION_HAS_VALID_POOL_ON_EXIT (ab)
    Caused by a session driver not freeing its pool allocations prior to a
    session unload.  This indicates a bug in win32k.sys, atmfd.dll,
    rdpdd.dll or a video driver.
    Arguments:
    Arg1: 0000000000000003, session ID
    Arg2: 0000000000000200, number of paged pool bytes that are leaking
    Arg3: 0000000000000000, number of nonpaged pool bytes that are leaking
    Arg4: 0000000000000005, total number of paged and nonpaged allocations that are leaking.
        nonpaged allocations are in the upper half of this word,
        paged allocations are in the lower half of this word.
    Look at rdpdd.dll which belongs to something called RDP Service from what I've been able to find out via Google searches. I don't have it on any of my systems (all Win 10 Pro X64) so it must be Enterprise or Business use software.

    Also try completely uninstalling your Nvidia driver using DDU then download and install the latest available:

    Remove and install latest Nvidia drivers:

    Get the latest driver for your Nvidia card here: NVIDIA Driver Downloads
    Completely uninstall the current Nvidia display drivers using Display Driver Uninstaller (DDU) from WagnardMobile here: Official Download Here. Do this in Safe Mode.

    Then do a custom install of only the Nvidia Graphics and PhysX driver.

    See if that gets rid of the problem.

    The log files are in a foreign (non-English) language and some can not be analyzed. Please change the system language to English and post a new V2 log collector zip.

    Add, Remove, and Change Display Language in Windows 10
    How To Change Language In Windows 10 Operating System - YouTube

    You can put the language back to normal once done though you may have to do this multiple times if I need you to run the log collector script again in the future. Won't help with data that's already collected as far as I can tell but newly generated data will be in English which can help.

    Thanks
      My Computers


  5. Posts : 428
    Windows 10 Pro x64 Version 1803
    Thread Starter
       #5

    Ztruker said:
    Looked a the full dump:
    Code:
    BugCheck AB, {3, 200, 0, 5}
    Probably caused by : win32kfull.sys ( win32kfull!CheckSessionPoolAllocations+8caae )
    0: kd> !analyze -v
    
    SESSION_HAS_VALID_POOL_ON_EXIT (ab)
    Caused by a session driver not freeing its pool allocations prior to a
    session unload.  This indicates a bug in win32k.sys, atmfd.dll,
    rdpdd.dll or a video driver.
    Arguments:
    Arg1: 0000000000000003, session ID
    Arg2: 0000000000000200, number of paged pool bytes that are leaking
    Arg3: 0000000000000000, number of nonpaged pool bytes that are leaking
    Arg4: 0000000000000005, total number of paged and nonpaged allocations that are leaking.
        nonpaged allocations are in the upper half of this word,
        paged allocations are in the lower half of this word.
    Look at rdpdd.dll which belongs to something called RDP Service from what I've been able to find out via Google searches. I don't have it on any of my systems (all Win 10 Pro X64) so it must be Enterprise or Business use software.

    Also try completely uninstalling your Nvidia driver using DDU then download and install the latest available:

    Remove and install latest Nvidia drivers:

    Get the latest driver for your Nvidia card here: NVIDIA Driver Downloads
    Completely uninstall the current Nvidia display drivers using Display Driver Uninstaller (DDU) from WagnardMobile here: Official Download Here. Do this in Safe Mode.

    Then do a custom install of only the Nvidia Graphics and PhysX driver.

    See if that gets rid of the problem.

    The log files are in a foreign (non-English) language and some can not be analyzed. Please change the system language to English and post a new V2 log collector zip.

    Add, Remove, and Change Display Language in Windows 10
    How To Change Language In Windows 10 Operating System - YouTube

    You can put the language back to normal once done though you may have to do this multiple times if I need you to run the log collector script again in the future. Won't help with data that's already collected as far as I can tell but newly generated data will be in English which can help.

    Thanks
    Thanks for the info. Does this report rule out a hardware fault?
      My Computer

  6. Ztruker's Avatar
    Posts : 10,229
    Windows 10 Pro X64 1909 18363.815
       #6

    No, doesn't rule it out but there is no indication yet of a hardware cause for your problem.

    Do you overclock, over/undervolt?
      My Computers



  7. Posts : 428
    Windows 10 Pro x64 Version 1803
    Thread Starter
       #7

    Ztruker said:
    No, doesn't rule it out but there is no indication yet of a hardware cause for your problem.

    Do you overclock, over/undervolt?
    No, never did.

    I do recall the power plug falling out of the socket making the PC shut down unexpectedly while being on the Windows Login screen. That was around 12 days before this silent BSOD. Other than that my PC has been working great, even under heavy gaming. Not sure if this could have caused this error. Checkdisk and SFC /scannow did not find any errors.
      My Computer

  8. philc43's Avatar
    Posts : 4,353
    64bit Win 10 Pro ver 1909 Build 18363.535 and W10 Insider Ver 2004 Build 19536
       #8

    Since this was a live kernel event and was handled by the OS without the need for a BSOD I think you can safely assume that it is not a serious concern. I would only start to think more investigation is needed if it keeps appearing. So far you have only had one instance of this.
      My Computers


  9. Posts : 428
    Windows 10 Pro x64 Version 1803
    Thread Starter
       #9

    philc43 said:
    Since this was a live kernel event and was handled by the OS without the need for a BSOD I think you can safely assume that it is not a serious concern. I would only start to think more investigation is needed if it keeps appearing. So far you have only had one instance of this.
    Thanks for the reassuring answer. So a silent (questionable) hardware error that only happens once could be a random occurrence without a definite underlying problem?
      My Computer

  10. philc43's Avatar
    Posts : 4,353
    64bit Win 10 Pro ver 1909 Build 18363.535 and W10 Insider Ver 2004 Build 19536
       #10

    JohnnyGui said:
    Thanks for the reassuring answer. So a silent (questionable) hardware error that only happens once could be a random occurrence without a definite underlying problem?
    Agreed!
      My Computers


 
Page 1 of 3 123 LastLast

Related Threads
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 04:19.
Find Us




Windows 10 Forums