Driver_power_state_failure and memory_management BSOD

Page 1 of 3 123 LastLast

  1. Posts : 20
    Windows 10
       #1

    Driver_power_state_failure and memory_management BSOD


    I got a new laptop and after about a week I started to get the BSOD driver_power_state_failure. Sometimes it wouldn't happen for days and sometimes I'd get it 2-3 times a day. I ran whocrashed and the program said it was caused by the ntoskrnl.exe (nt+0x14E240) module. So I performed a memory test and it came up with no errors. Then today I got the driver_power_state_failure and as I was restarting my computer I got the memory_management BSOD. I'm assuming they're both caused by the same driver/program. Any way I can keep these crashes from happening?

    Specs:
    Chassis manufacturer: Acer
    CPU: Intel Core i5 5200U 2.2 GHz
    GPU: Nvidia GeForce 940m 2048mb
    Memory: x1 8gb DDR3
    Storage: 1tb hybrid drive
    OS: Windows 10 Home 64bit


    Crash dump directory: C:\WINDOWS\Minidump



    On Fri 9/11/2015 5:40:23 PM GMT your computer crashed
    crash dump file: C:\WINDOWS\Minidump\091115-17406-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x14E240)
    Bugcheck code: 0x1A (0x5100, 0xFFFFF6E800B6B410, 0x1E, 0x1000000028164)
    Error: MEMORY_MANAGEMENT
    file path: C:\WINDOWS\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    Bug check description: This indicates that a severe memory management error occurred.
    This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.






    On Fri 9/11/2015 5:40:23 PM GMT your computer crashed
    crash dump file: C:\WINDOWS\memory.dmp
    This was probably caused by the following module: rdyboost.sys (rdyboost+0x2845)
    Bugcheck code: 0x1A (0x5100, 0xFFFFF6E800B6B410, 0x1E, 0x1000000028164)
    Error: MEMORY_MANAGEMENT
    file path: C:\WINDOWS\system32\drivers\rdyboost.sys
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: ReadyBoost Driver
    Bug check description: This indicates that a severe memory management error occurred.
    This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
    The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.


    Dump file:
    091115-17406-01.dmp 9/11/2015 1:40:23 PM MEMORY_MANAGEMENT 0x0000001a 00000000`00005100 fffff6e8`00b6b410 00000000`0000001e 00010000`00028164 ntoskrnl.exe ntoskrnl.exe+14e240 NT Kernel & System Microsoft® Windows® Operating System Microsoft Corporation 10.0.10240.16463 (th1.150819-1946) x64 ntoskrnl.exe+14e240 C:\WINDOWS\Minidump\091115-17406-01.dmp 4 15 10240 276,376 9/11/2015 1:41:08 PM
    Last edited by JRHNBR; 11 Sep 2015 at 15:09.
      My Computer


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

    Hi JRHNBR,

    Welcome to the 10forums.

    Please read BSOD Posting Instructions & How to upload files

    Ntoskrnl.exe isn't the cause, without this file you cannot start your computer because this file is needed in the boot process.
    Windows files are usually blamed when 3rd party's are 'hiding'.
      My Computers


  3. Posts : 20
    Windows 10
    Thread Starter
       #3
      My Computer


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

    What memory test did you do exactly? The built-in feature?

    Please do the following:

    • Open an admin command prompt
    • Copy/paste "sfc/scannow" (without quotes) and press enter
    • When it finished reboot your system
    • Open again an admin command prompt
    • Enter sfc/scannow again



    If sfc/scannow doesn't say "Windows Resource Protection did not find any integrity violation", please upload the cbs.log file located at {windows partition}\Windows\Logs\CBS\, if the file is too large try a 3rd party uploader like dropbox, onedrive, google drive, mediafire etc.
    System File Check(SFC a.k.a. Windows Resource Protection) needs to have your system rebooted in order for sfc to try to fix the problems that it finds.
      My Computers


  5. Posts : 20
    Windows 10
    Thread Starter
       #5

    I used windows memory diagnostic tool in control panel.

    The resource protection program didn't find anything
      My Computer


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

    Good.

    What memory test have you performed?
      My Computers


  7. Posts : 20
    Windows 10
    Thread Starter
       #7

    The windows memory diagnostic program
      My Computer


  8. Posts : 14,901
    Windows 10 Pro
       #8

    Sorry, I didn't see you previous answer.

    Please run the diagnostic, this memory test is proven better then the built-in feature.




    Diagnostic Test

     RAM TEST


    Run MemTest86+ to analyse your RAM. MemTest86+ - Test RAM - Windows 10 Forums

    Note   Note


    MemTest86+ needs to be run for at least 8 passes for conclusive results. Set it running before you go to bed and leave it overnight. We're looking for zero errors here. Even a single error will indicate RAM failure.
      My Computers


  9. Posts : 20
    Windows 10
    Thread Starter
       #9

    Ok I'll try this tonight. Also one of the blue screens was said to be caused by rdyboost.sys. Is this the source of the issues?
      My Computer


  10. Posts : 14,901
    Windows 10 Pro
       #10

    That is a windows file, if it would be the source of the problem then it would mean your windows is corrupted.
    The solution for a corrupted windows would be the System File Check (Sfc a.k.a. Windows Resource Protection) or a reinstallation of windows if the corruption is too bad.
    Since you don't have any corruption, missing files or other problems, this file isn't the real cause.
      My Computers


 

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




Windows 10 Forums