BSOD immediately after sleep/hibernate

Page 1 of 2 12 LastLast

  1. Posts : 30
    Windows 10
       #1

    BSOD immediately after sleep/hibernate


    I sometimes get a failure from either Corrupt Page or Memory Management after returning from either sleep mode or hibernate. Always caused by ntoskrnl.exe+142940. I wonder if it might be caused by my trying to log in too soon and the different threads running before memory has completed it's refresh.

    Please note I really don't believe that there is a problem with the ram in my PC because Linux Mint has never reported a problem.

    Rob.
      My Computer


  2. Posts : 14,903
    Windows 10 Pro
       #2

    Hi rhogg4859,

    Could you try to increase the memory frequency to 1866MHz, this may be done by changing the XMP profile.
      My Computers


  3. Posts : 30
    Windows 10
    Thread Starter
       #3

    axe0 said:
    Hi rhogg4859,

    Could you try to increase the memory frequency to 1866MHz, this may be done by changing the XMP profile.
    Sorry what is XMP and how do I change it?

    And how is changing the frequency going to help, why is it a problem? As I said before Linux does not find it a problem. I would like to understand more of what is going on.

    Thanks
    Rob.
      My Computer


  4. Posts : 14,903
    Windows 10 Pro
       #4

    XMP = eXteme Memory Profile, changing the profile allows to change the frequency, timing and voltage of the memory to different values.

    Why it may be a problem is compatibility with your CPU. So far I have checked at AMD (scroll down the page) the CPU support 1866MHz frequency from DDR3 memory. Provided that per the dump your memory frequency is 1333MHz I would suggest that you increase it by enabling/changing XMP in the BIOS.
      My Computers


  5. Posts : 30
    Windows 10
    Thread Starter
       #5

    Ok. The XMP settings in bios were Profile1/Auto and is showing System memory Multiplier of 18.67 and Memory Frequency of 1866Mhz. I am not surprised at that because the memory is 1866 but this does not answer why Microsoft is reporting 1333.
      My Computer


  6. Posts : 14,903
    Windows 10 Pro
       #6

    It's something I can't answer either, here is what the dump shows.
    Code:
    [Memory Device (Type 17) - Length 34 - Handle 0027h]
      Physical Memory Array Handle  0023h
      Memory Error Info Handle      [Not Provided]
      Total Width                   64 bits
      Data Width                    64 bits
      Size                          4096MB
      Form Factor                   09h - DIMM
      Device Set                    [None]
      Device Locator                Node0_Dimm1
      Bank Locator                  Node0_Bank0
      Memory Type                   18h - Specification Reserved
      Type Detail                   4080h - Synchronous
      Speed                         1333MHz
      Manufacturer                  Corsair           
      Serial Number                             
      Asset Tag Number                            
      Part Number                   CMZ8GX3M2A186
    
    [Memory Device (Type 17) - Length 34 - Handle 002bh]
      Physical Memory Array Handle  0023h
      Memory Error Info Handle      [Not Provided]
      Total Width                   64 bits
      Data Width                    64 bits
      Size                          4096MB
      Form Factor                   09h - DIMM
      Device Set                    [None]
      Device Locator                Node0_Dimm3
      Bank Locator                  Node0_Bank0
      Memory Type                   18h - Specification Reserved
      Type Detail                   4080h - Synchronous
      Speed                         1333MHz
      Manufacturer                  Corsair
      Serial Number                             
      Asset Tag Number                            
      Part Number                   CMZ8GX3M2A186
      My Computers


  7. Posts : 30
    Windows 10
    Thread Starter
       #7

    Yes that is what is reported in Task Manager. I was just searching the internet to see what others have found.
      My Computer


  8. Posts : 30
    Windows 10
    Thread Starter
       #8

    I think this reported speed is a red herring.

    See Microsoft Community

    So others have reported it as a problem with Task Manager not reading the XMP properly. I think CPU-z does show the correct speed but I am not sure how to interpret CPU-z.

    So we are back with the problem of why the BSOD?
      My Computer


  9. Posts : 14,903
    Windows 10 Pro
       #9

    A thing that should be noted, the information provided is from the dump.
    The dump is from the RAM, the RAM reserves a small amount of memory to register the hardware into volatile register so the system knows what it works with everytime it starts up.

    Simply speaking, it is impossible that any software is conflicting with it or misreading, because the information is from Windows itself.
    Please don't interpret this in a way like that there is a bug or something, because if that would be the case then you wouldn't be able to boot.
      My Computers


  10. Posts : 30
    Windows 10
    Thread Starter
       #10

    Here is CPU-z
    Dropbox - Screenshot 2016-09-14 15.36.32.png
    Dropbox - Screenshot 2016-09-14 15.38.41.png
    Dropbox - Screenshot 2016-09-14 15.43.09.png

    I don't know what it all means but I believe it shows XMP as 1864 and Task Manager shows 1333 so who's right?

    Now with my motherboard there is shared ram with the screen/video could this be why MS has chosen the lower of the possible speeds for ram so as to match the Radeon on board video chip?
    Dropbox - Screenshot 2016-09-14 15.46.40.png
      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 11:38.
Find Us




Windows 10 Forums