Windows 10: BSOD MEMORY_MANAGEMENT randomly throughout day

Ran the verifier over the weekend (I computer was idle since I was at home) and didn't get any blue screens. I turned off the verifer since the link you provided says not to run more than 48 hours and the dump file I previously posted is the most up to date.

 

Use your pc as you normally would and let me know if any BSOD occurs.

 

So I don't want to jinx this but I think I found the error because I haven't BSOD in a week now. I had my two sticks of ram ram in slots a2, b2 and not a1,b1. Googling seems to suggest that that could cause problems, so hopefully this is my issue. Thanks for all your help

 

Thought I was in the clear, but I BSOD a couple times this past week. One time I got an AMD drivers error from "whocrashed" program so I un/reinstalled all my AMD drivers, however I just BSOD again today.

 

Please uninstall everything of AMD using Display Driver Uninstaller and install new drivers from AMD. Be sure to install as less as possible software using custom/advanced options, you can use this tutorial for the installation part *Arrow AMD Graphics Drivers - Install Without Catalyst Install Manager - Windows 7 Help Forums
Attachment 111745
Code: 5: kd> lmvm atikmpag Browse full module list start end module name fffff805`e6c30000 fffff805`e6cb2000 atikmpag T (no symbols) Loaded symbol image file: atikmpag.sys Image path: \SystemRoot\System32\DriverStore\FileRepository\c0307329.inf_amd64_55b6bd3e40065979\atikmpag.sys Image name: atikmpag.sys Browse all global symbols functions data Timestamp: Fri Sep 16 20:50:37 2016 (57DC3EFD) CheckSum: 0008AD31 ImageSize: 00082000 Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4[/quote]

 

Used that program to the uninstall graphic drivers and then I installed the minimum drivers necessary according the AMDs site. BSOD's twice in the past week, but the errors showing up in "whocrashed" seem to be different than the previous ones. Upload the new dump files below. Thanks for your help again.

 

Diagnostics Test

HDD TEST
*Arrow Run HDTune to

• check the health,
• scan for errors, no quick scan but full scan
• run a benchmark.

It may take some time, but please take the time you need to perform it properly.
When above is done please make screenshots of the following

• the health,
• the error scan,
• the benchmark incl. following
  • transfer rate,
  • access time,
  • burst rate,
  • cpu usage.

*Arrow Run SeaTools DOS to check the integrity of your HDD. SeaTools for DOS and Windows - How to Use - Windows 7 Help Forums
Run the long test.
*Arrow Check Disk (chkdsk) - Read Event Viewer Log - Windows 7 Help Forums

 

hdtune
Attachment 114177Attachment 114178Attachment 114179
seagate
Attachment 114180

chkdsk results

Attachment 114181Attachment 114182

 

Follow the instructions carefully. Run the same command on each partition/drive.

 

Hopefully these are the right ones now

 

Looks good, a correction to the file system on the SSD was made *Smile
Code: CHKDSK discovered free space marked as allocated in the volume bitmap.Windows has made corrections to the file system.[/quote] Let us know how it goes.

 

Hello,
The problem has persisted, but no as frequent. I was getting an error after I did the chkdsk which, when I googled it, suggested doing an in place repair for Windows 10. I did that which but still get an occasional BSOD. I guess the in place repair deletes old dump files, so the attached only has files from after the repair

Thanks again for your help

 

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.

 

Hello,
I ran driver verifier Friday and over the weekend. Didn't get any BSOD in that time frame. From what I remember, it seems most of the BSOD happen when I am not using the computer and it is sitting idle, if this info helps at all. I am really not running that many programs on the computer, mostly Matlab, Chrome, and google drive. Could it be a networking thing with drive trying to sync?

 

If it would, your network drivers would be caught by driver verifier.


Please fill in your system specsPlease follow this tutorial and download the tool. The tool will give you detailed information about your system specs, please fill in your system specs more completely including PSU, cooling and other used stuff like mouse, keyboard, monitor, case, etc.
The PSU, cooling and other stuff are NOT mentioned in the tool.
In the left corner below in your post you find 'My System Specs'. After clicking it you can find a link a little below that says 'Update your System Spec', click on this link to get to the page where you can fill in your system specs.