BSOD every time PC wakes from sleep mode

Page 2 of 2 FirstFirst 12

  1. Posts : 9
    Windows 10 Pro 64 bit
    Thread Starter
       #11

    zbook, thank you got the advice. Re the BIOS I was on 3003 already, but then developed the problem so I tried the beta 3503 to see if it helped. I have now restored it to 3003. I had already tried downclocking the RAM but the issue still happened hence i put the overclock back on. I had it non-overclocked while following your steps. Please see the results below:

    Microsoft Windows [Version 10.0.18363.657]
    (c) 2019 Microsoft Corporation. All rights reserved.

    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.18362.1

    Image Version: 10.0.18363.657

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

    Image Version: 10.0.18363.657

    [==========================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 Samsung 840 Pro.

    Stage 1: Examining basic file system structure ...
    634624 file records processed.
    File verification completed.
    33751 large file records processed.
    0 bad file records processed.

    Stage 2: Examining file name linkage ...
    55855 reparse records processed.
    770798 index entries processed.
    Index verification completed.
    0 unindexed files scanned.
    0 unindexed files recovered to lost and found.
    55855 reparse records processed.

    Stage 3: Examining security descriptors ...
    Security descriptor verification completed.
    68088 data files processed.
    CHKDSK is verifying Usn Journal...
    36391688 USN bytes processed.
    Usn Journal verification completed.

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

    249555687 KB total disk space.
    96853228 KB in 272701 files.
    178544 KB in 68089 indexes.
    0 KB in bad sectors.
    772323 KB in use by the system.
    65536 KB occupied by the log file.
    151751592 KB available on disk.

    4096 bytes in each allocation unit.
    62388921 total allocation units on disk.
    37937898 allocation units available on disk.

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

    C:\WINDOWS\system32>wmic recoveros set DebugInfoType = 7
    Updating property(s) of '\\DESKTOP-EKCD2F4\ROOT\CIMV2:Win32_OSRecoveryConfiguration.Name="Microsoft Windows 10 Pro|C:\\WINDOWS|\\Device\\Harddisk0\\Partition1"'
    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>bcdedit /enum {badmemory}

    RAM Defects
    -----------
    identifier {badmemory}

    C:\WINDOWS\system32>


    Attachment 267451

    Attachment 267452

    I cannot recall for certain, but I do feel the virtual memory figure used to be different, I am not sure if this has significance?

    Thank you again for all the help
      My Computer


  2. Posts : 38,342
    windows 10 professional version 1607 build 14393.969 64 bit
       #12

    Overclocking is a common cause of BSOD and unexpected shutdowns and restarts.

    It it very difficult to troubleshoot while there is an overclock.

    Confounding factors need to be reduced or eliminated to find misbehaving drivers or malfunctioning hardware.

    Make sure that all components are returned to stock.
      My Computer


  3. Posts : 9
    Windows 10 Pro 64 bit
    Thread Starter
       #13

    I appreciate that and can confirm I have disabled the overclock. The above tests were run with it off. I just had another and still can't see any memory dumps even after following your suggested steps.
      My Computer


  4. Posts : 38,342
    windows 10 professional version 1607 build 14393.969 64 bit
       #14

    For any BSOD:

    a) run the V2 log collector to collect new log files

    b) open file explorer> this PC > C: > in the right upper corner search for: C:\Windows\memory.dmp
    > if the file size is < 1.5 GB then zip > post a separate share link into the thread using one drive, drop box, or google drive
      My Computer


  5. Posts : 9
    Windows 10 Pro 64 bit
    Thread Starter
       #15

    latest log:

    Attachment 267482

    I am perplexed as I still can't locate any memory dumps having looked through system folders and using the searches as you recommend.
      My Computer


  6. Posts : 38,342
    windows 10 professional version 1607 build 14393.969 64 bit
       #16

    The RAM is overclocked at 2400.
    Make sure the speeds are < or = 1600

    The RAM modules appear to be different from those on the Qualified Vendor List (QVL).

    RAM not on the QVL can cause unexpected shutdowns and restarts.
      My Computer


  7. Posts : 9
    Windows 10 Pro 64 bit
    Thread Starter
       #17

    I have disabled the memory overclock in the bios and did so days ago. All suggestions have been followed with it at 1600. Please see images.
    Attachment 267556
    Attachment 267557

    Re: the compatibilty of hardware. I have had the system for over 5 years with all the same components apart from the GPU which was swapped 3 years ago. I have never had any issues until this problem started a several weeks ago.
      My Computer


  8. Posts : 38,342
    windows 10 professional version 1607 build 14393.969 64 bit
       #18

    Please upload a new V2.
      My Computer


  9. Posts : 9
    Windows 10 Pro 64 bit
    Thread Starter
       #19

    I just wanted to provide an update incase anyone else has a similar issue. Despite all of the helpful suggestions I was stuck in the same loop. I eventually reinstalled windows as a clean install yet again and the exact same problem remained.

    It would appear tentatively that I have found the solution however. After much searching I found a few people having the same issues on the samsung forums. It would appear that after a certain build of windows 10 there was an issue with the NVME drivers causing the exact same problem for people with Samsung SSDs. I tried the autoupdate on device manager and it stated I had the latest driver, but I then manually downloaded and installed "Samsung NVM Express Driver 3.3" and fingers crossed since then I have not had a single BSOD (48 hours later).

    Thank you for all your time and suggestions and I hope this may prove useful for someone else.
      My Computer


  10. Posts : 38,342
    windows 10 professional version 1607 build 14393.969 64 bit
       #20

    End users reading this thread may benefit from your reply.

    Thank you for the follow up.

    I'm glad that things are sorted.

    You are welcome.

    If not already making images consider making free backup images:

    Macrium Software | Your Image is Everything
    Backup and Restore with Macrium Reflect
      My Computer


 
Page 2 of 2 FirstFirst 12

  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 19:37.
Find Us




Windows 10 Forums