Windows 10: 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

:)

 

MEMORY_MANAGEMENT,PFN_LIST_CORRUPT,BAD_POOL_HEADER BSODs on Windows 10 while gaming or just using my PC.

Any news on this?

I am still getting MEMORY_MANAGEMENT BSODs

 

Lots of BSOD's

PS: after my previous/last replie i had 3 more BSOD's:

seems like there are a lot of random once...

MEMORY_MANAGEMENT win32kbase.sys

MEMORY_MANAGEMENT ntoskrnl.exe

ntoskrnl.exe

 

Hi JRHNBR,

Welcome to the 10forums.

Please read 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'.

 

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.

 

I used windows memory diagnostic tool in control panel.

The resource protection program didn't find anything

 

Good.

What memory test have you performed?

 

The windows memory diagnostic program

 

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+ - Test RAM - Windows 10 Forums



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.

 

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?

 

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.

 

I did the memory test and it came up with no issues

 

Alright,
Please try the following





Diagnostic Test

DRIVER VERIFIER


Warning Please make a backup of your important files and get your rescue media or create one.
Please create a restore point.
Please follow this tutorial to run driver verifier.

Driver verifier stresses your drivers and will crash your pc if any driver fails due to a violation.

Driver verifier should be performed for a max of 48 hours, or when you have a bluescreen, whatever comes first.

If driver verifier has found a violation and you can't get back into windows normally, try to boot into safe mode and reset in safe mode driver verifier, or in the troubleshooting options open command prompt and type verifier /reset.



Note Your system will act very sluggishly while driver verifier is enabled, this is normal as your drivers will be being subjected to heavy testing in order to make them crash.

 

I actually tried that and it crashed before windows could boot.

 

Do you know where the boot process was?