bsod memory_management ntoskrnl.exe

System Information (local)
--------------------------------------------------------------------------------

Computer name: MARK-PC
Windows version: Windows 7 Service Pack 1, 6.1, build: 7601
Windows dir: C:\Windows
Hardware: MS-7977, MSI, Z170A GAMING M5 (MS-7977)
CPU: GenuineIntel Intel(R) Core(TM) i5-6600K CPU @ 3.50GHz Intel586, level: 6
4 logical processors, active mask: 15
RAM: 17137967104 bytes total




--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Tue 4/12/2016 3:10:11 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\041216-8486-01.dmp
This was probably caused by the following module: atikmpag.sys (atikmpag+0x745C)
Bugcheck code: 0x116 (0xFFFFFA8022022010, 0xFFFFF8800F0BB45C, 0x0, 0x2)
Error: VIDEO_TDR_ERROR
file path: C:\Windows\system32\drivers\atikmpag.sys
product: AMD driver
company: Advanced Micro Devices, Inc.
description: AMD multi-vendor Miniport Driver
Bug check description: This indicates that an attempt to reset the display driver and recover from a timeout failed.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: atikmpag.sys (AMD multi-vendor Miniport Driver, Advanced Micro Devices, Inc.).
Google query: Advanced Micro Devices, Inc. VIDEO_TDR_ERROR



On Tue 4/12/2016 3:10:11 PM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: atikmpag.sys (0xFFFFF8800F0BB45C)
Bugcheck code: 0x116 (0xFFFFFA8022022010, 0xFFFFF8800F0BB45C, 0x0, 0x2)
Error: VIDEO_TDR_ERROR
file path: C:\Windows\system32\drivers\atikmpag.sys
product: AMD driver
company: Advanced Micro Devices, Inc.
description: AMD multi-vendor Miniport Driver
Bug check description: This indicates that an attempt to reset the display driver and recover from a timeout failed.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: atikmpag.sys (AMD multi-vendor Miniport Driver, Advanced Micro Devices, Inc.).
Google query: Advanced Micro Devices, Inc. VIDEO_TDR_ERROR



On Tue 4/12/2016 3:00:30 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\041216-6661-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x74080)
Bugcheck code: 0x1A (0x403, 0xFFFFF680001A2628, 0xA48000000056E867, 0xFFFFF690001A2628)
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 Tue 4/12/2016 1:24:09 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\041116-7035-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x74080)
Bugcheck code: 0xA (0xFFFFFAB0000082F0, 0x2, 0x1, 0xFFFFF80002F006A0)
Error: IRQL_NOT_LESS_OR_EQUAL
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 Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.





--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------

4 crash dumps have been found and analyzed. A third party driver has been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers:

atikmpag.sys (AMD multi-vendor Miniport Driver, Advanced Micro Devices, Inc.)

Also some additional info. I have an MSI motherboard and had the one-click "game boost" on for a built-in overclock. I kept getting the Do you want to change the color scheme to improve performance?
Windows has detected your computer’s performance is slow. This could be because there are not enough resources to run the Windows Aero color scheme. To improve performance, try changing the color scheme to Windows 7 Basic. Any change you make will be in effect until the next time you log on to Windows.

I took off the overclock and haven't had that warning come up again. I also updated my ATi drivers as well to the most recent. I was running an older driver that I thought would help. But since I took off the game boost overclock and updated the ati driver this morning the only BSOD was the memory management one. I also just now ran Furmark for about 30 minutes to stress test the video card and it seems ok

I also ran memtest x86 this morning right after the memory bsod for an hour and no errors.

Ok I ran sfc/scannow and it found corrupt files but were unable to fix some of them. Is there anyway to upload the cbs lob cause its pretty huge ? Or should I just paste it ? I'm going to try a sfc repair here in a few.

Oh man...It wants to run it in safe mode. I had a major issue 2 days ago when I ran the avast anti-virus uninstaller, and it wanted to do it in safe mode. For some unknown reason, I couldn't get into safe-mode to save my life. So I let the program reboot me into safe mode, and it got stuck in a safe-mode loop. I had to reformat and re-do the whole system. I don't have fast boot enabled either. I have no idea why it got stuck in safe-mode. But now I'm super paranoid to even attempt it again.

SFC didn't want safe mode. It was the avast uninstaller that did, and that's what looped me. I'm a noob when it comes to overclocking. I just saw the one click game boost option in the new motherboard and thought....why not, should be relatively safe. At this point, it was half of my problems. Once I took off the overclock and updated the video drivers it's been BSOD free. Also did mem test and a video stress test. I researched the one thing SFC couldn't fix "iassdo.dll.mui" and am not to worried about it. Also, the "Windows has detected your computer’s performance is slow. This could be because there are not enough resources to run the Windows Aero color scheme." has stopped as well since I did the above. Using Avira for antivirus so far so good. PC has been behaving with no issues all day yesterday after the fixes. I'm going to run this bad boy for a few more days and hope not to see anymore BSOD's. Responding very well at this point. I will keep you posted, and wanted to thank you for your time and expertise on these issues. I really appreciate it, dude !!

Thank you...I hope so. Feeling pretty good about it. Told the PC "good morning" today and to please behave...lol... Time will tell. I will keep you updated, and hopefully, I can mark this case solved...wouldn't that be awesome.

Well, its been 2 days and no bsods. I'm going to mark this one solved !! The fix was updated ati drivers and no overclock, even though it was a safe "game boost" one click overclock. Thank you Colif for all your suggestions and help on this !

3 bsods today....just when I thought all was fine

On Mon 4/18/2016 11:23:25 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\041816-8424-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70380)
Bugcheck code: 0xA (0x38, 0x2, 0x0, 0xFFFFF80002EE9782)
Error: IRQL_NOT_LESS_OR_EQUAL
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 Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Mon 4/18/2016 11:23:25 PM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0xA (0x38, 0x2, 0x0, 0xFFFFF80002EE9782)
Error: IRQL_NOT_LESS_OR_EQUAL
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Mon 4/18/2016 9:37:01 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\041816-8642-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70380)
Bugcheck code: 0xDE (0x2, 0xFFFFF8A00F920038, 0xFFFFF8B20F920039, 0x5A88C0)
Error: POOL_CORRUPTION_IN_FILE_AREA
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 driver has corrupted pool memory that is used for holding pages destined for disk.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.





--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------

3 crash dumps have been found and analyzed. No offending third party drivers have been found. Connsider using WhoCrashed Professional which offers more detailed analysis using symbol resolution. Also configuring your system to produce a full memory dump may help you.