Getting MEMORY_MANAGEMENT BSOD after upgrading to Windows 10

Darragh0081 · Mar 25, 2017

Hello,

I just got the BSOD MEMORY_MANAGEMENT when playing Battlefield: Hardline. I've had this BSoD twice now usually when playing Intense games.

I've had no computer issues before but I got a BSoD after the first week of Installation

Specs:
CPU: Intel(R) Core(TM) i5-6500 CPU @ 3.20GHz
Video Card: AMD Radeon R9 200 Series
Memory: 8.0 GB
Motherboard: Asrock H110m-plus
OS: Microsoft Windows 10 (build 14393), 64-bit

Minidump File: https://www.dropbox.com/s/x6d5lb4clvstlqq/032517-23281-01.dmp?dl=0
Dump: https://www.dropbox.com/s/5fit43cz60y4456/MEMORY.DMP?dl=0

I ran bluescreen view and got this MEMORY_MANAGEMENT 0x0000001a, Caused by: ntoskrnl.exe Caused by Address: ntoskrnl.exe+14a510.

I have ran Windows Memory Diagnostic with no errors, I have also ran /sfc scannow and had no integrity violations.

My operating system prior to this was Windows 7 and I decided to upgrade but I feel like it was a huge regret after upgrading.

Looking for some help/insight.

johnbl · Mar 25, 2017

first bugcheck was due to a corruption of a data structure that maps data in memory to locations in your pagefile.sys.

I would go into windows control panel and disable the pagefile (virtual memory) and create a new one incase this was caused by a bad spot in the pagefile.

good chance a bios update and USB driver update will help. Often using usb audio with out of date bios and usb drivers can cause "random" corruptions.

it looks like microsoft memory compression was trying to prefetch something from the hard drive page file when it hit the error.

I would update the BIOS if there is a newer version, update the chipset driver and sata drivers for your motherboard. If you have two sata controllers you might put the drive data cable on a different port or different sata controller.

I would run crystaldiskinfo.exe to read the SMART info from the drive to see if it is generating any hardware errors.

I would go to https://live.sysinternals.com/ and download and run rammap, then go to the menu item EMPTY and select each option, this will clear your working set and reduce the amount of programs that windows will attempt to load into standby memory. This will reduce the chance of you hitting this particular bugcheck.

I would also run memtest to check your RAM for timing problems since this occurred while memory decompression was running.

- you might also want to scan using malwarebytes
- you might also want to remove hacking programs that are installed. (activation key server)

machine info:
BIOS Version P1.20
BIOS Release Date 01/25/2016
Manufacturer ASRock
Product B150M-HDS
Processor Version Intel(R) Core(TM) i5-6500 CPU @ 3.20GHz
Processor Voltage 8ah - 1.0V
External Clock 100MHz
Max Speed 5000MHz
Current Speed 3200MHz

Darragh0081 · Mar 25, 2017

I disabled the pagefile and I may sound like a complete muppet but I am wondering just how to create a new pagefile. I used the disc that came a long with my motherboard to install Audio Drivers. I upgraded my BIOS regardless of hating the fact I might break my pc. There are no new updates for the Chipset. I ran CDI and I got Current Pending Sector Count - Current: 100 Worst: 100. I also got uncorrectable sector count, current: 100, worst: 100. I hope you're able to make sense of those two pieces of information. This is an upload link for all the information from CrystalDiskInfo - https://drive.google.com/open?id=0B7DsndCzXZ5qa0doUFR0cTJfZ1U

I hope this can help you get a better understanding.

Update: After doing 95% of the above beside creating a new pagefile I am going to test on my intensive game report to see whether or not I get another BSOD.

johnbl · Mar 25, 2017

your drive has about 14000 hour on it (1.6 years full time spinning)
it reported 386 Reported Uncorrectable Errors and three pending bad sectors. These are the type of errors that will crash windows. if the bad sector was in the pagefile.sys, (which is a hidden file on c:\) when you turn off the virtual memory reboot, the pagefile.sys should be deleted. when you turn the virtual memory back on it should create a new file.

normally failure rates for this type of drive are about 28% the first year, then 16% for each year after that until the drive just dies. Generally by 5 years all of the drives will have died for that manufacture run.

you are running windows 10, it does data integrity checking on the drive which helps to relocate data off of bad sectors and then marks the sectors as bad. this means that windows is helping you as much as it can by moving your date from bad sectors, it will do this until the drive just fails to read the data.
The drive retails for $48 now. I would look into migrating your system to a solid state drive. When they fail the generally still can be read from. you can still use the HDD as a data drive if you want to. You may find that clearing the standby list and making the new pagefile will have fixed the bugheck problem. The pagefile gets a lot of use, failure reading the data will result in a inpage error and a bluescreen. The standby list is harder to predict, windows keeps a list of every program you have run and tries to preload the program into memory before you actually attempt to run it. The more memory you system has, the more programs it will load into standby. if one of your programs you ran months ago is on a bad sector then when windows tries to prefetch it into memory the system will get this bugcheck and you will not know why unless you dig into windows and look at what it was trying to preload. This is why you would want to empty the standby memory list. You could also look at the list you might find games that you have not run for 6 months being loaded into standby memory.

also, windows can run without a page file but it will partition a part of your physical ram and use it as a pagefile. Works fine if you have plenty of RAM and is useful when you want to make sure you don't have a problem involving hard drive problems and the pagefile.sys

Darragh0081 · Mar 25, 2017

You're correct, I believe the pagefile was causing the issue and after installing the new BIOS and emptying all of the data seems to have shifted the issue and I have not ran into an issue since. I cannot thank you enough and will for future reference look into purchasing an SSD to store an OS on.

Paul NZ · Mar 25, 2017

If you want to test the ram. test it with memtest not the windows programs. It's too short and does nothing

Search

Getting MEMORY_MANAGEMENT BSOD after upgrading to Windows 10

Darragh0081

Prominent

johnbl

johnbl

Polypheme

Darragh0081

Prominent

johnbl

Polypheme

Darragh0081

Prominent

Paul NZ

Polypheme

TRENDING THREADS

Latest posts

Moderators online

Share this page