New build some random bsod's need help with plz

[spyfox]

Hello,
I just finished a new build and have been getting a few random BSOD's.
BSOD #1irql_not_less_or_equal ntoskrnl.exe
BSOD #2 memory_management ntoskrnl.exe

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.

Thank you in advance,

Mark

 

[spyfox]

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.)

 

[spyfox]

Does anybody care to take a look at the dump files ? I sure could use some input.... Thx

 

[axe0]

In case you've gotten more BSODs since the last upload :ar: http://www.sevenforums.com/bsod-help-support/96879-blue-screen-death-bsod-posting-instructions.html

 

[spyfox]

File has been uploaded

 

[axe0]

You are running an HP Product ID (PID) on a MSI board.
This makes your installation counterfeit.
Troubleshooting a counterfeit installation is useless as it is not known what has been modified to your system.
A counterfeit installation contains heavily modified code which causes the system to behave in unexpected ways.
For this reason, analyzing counterfeit systems is unreliable and most analysts won't try it.

OS Configuration:          Standalone Workstation
OS Build Type:             Multiprocessor Free
Registered Owner:          Mark
Registered Organization:   
Product ID:                [COLOR="Red"]00426-OEM-8992662-00010[/COLOR] <-- HP PID on MSI board
Original Install Date:     4/10/2016, 6:16:04 AM
System Boot Time:          4/28/2016, 11:11:34 AM
System Manufacturer:       MSI

I recommend to install a genuine copy of Windows.
If, after you have installed a genuine copy of Windows, you still get BSOD's we'll be happy to assist you.