Hi,
BugCheck F7, {220c0, cbca3bfc5f11, ffff3435c403a0ee, 0}
Probably caused by : amdppm.sys ( amdppm!ReadGenAddr+51 )
amdppm.sys is a Windows component which means something else drove it into Fault.
All the minidumps were similar - either no specific cause or a Windows component.
That with the fact that there were a lot of different Bug_Check points to a hardware
issue.
1. Run Driver Verifier to see if it can indicate a CAUSE (see methods below).
2. Check with MSI Support, their on-line documentation and drivers, and ask in their
forums about any known issues. Update the BIOS, low level chipset drivers, and the
major on-board and separate device drivers (see driver update methods below).
MSI Support
http://www.msi.com/index.php?func=service
MSI - Downloads (BIOS and Drivers)
http://www.msi.com/index.php?func=downloadindex
MSI - Forums
http://forum-en.msi.com/
MSI - Service
http://us.msi.com/index.php?func=service
MSI - Live Update On-Line
http://www.msi.com/index.php?func=downloadindex
MSI - Contacts - Set to North America - USA
http://www.msi.com/index.php?func=html&name=aboutus
3. Remove ALL power then reseat the cards memory and cables (on both ends when
possible) - actually remove and replace - do not just snug. Ensure the vents are clear
and that all the fans are working.
4. Check the memory (see methods below).
5. Check for malware (see methods in the next message).
6. As needed use ALL the methods in the troubleshooters below.
7. If nothing works consider re-installing Windows clean (requires you backup
all data off of the main drive where Windows resides).
======================
Troubleshoot blue screen errors
http://windows.microsoft.com/en-us/windows-10/troubleshoot-blue-screen-errors
========================================================
BCCode: F7 0x0000000F7
Check thoroughly for malware using the methods in the next message. Other possible causes include drivers, BIOS, low level chipset drivers, and errant software recently installed. Check the memory. If needed run Driver Verifier as indicated in the
troubleshooter below.
BCCode: F7 0x0000000F7
BCCode: F7 0x0000000F7 <-- read this link
http://www.faultwire.com/solutions-fatal_error/A-driver-has-overrun-a-stack-based-buffer-0x000000F7-*1244.html?order=votes
Bug Check 0xF7: DRIVER_OVERRAN_STACK_BUFFER <-- read this link
https://msdn.microsoft.com/en-us/library/ff560389(v=VS.85).aspx
=================================================
This utility makes it easy to see which versions are loaded :
Run DriverView - set VIEW to Hide Microsoft drivers - update those without
Dump in their names (and update BIOS and chipset).
DriverView - Free - utility displays the list of all device drivers currently loaded
on your system. For each driver in the list, additional useful information is
displayed: load address of the driver, description, version, product name,
company that created the driver, and more.
http://www.nirsoft.net/utils/driverview.html
For Drivers check System Maker as fallbacks and Device Maker's which are the
most current. Control Panel - Device Manager - Display Adapter - write down
the make and complete model of your video adapter - double click - Driver's
tab - write down the version info. Now click UPdate Driver (this may not do
anything as MS is far behind certifying drivers) - then Right Click - Uninstall -
REBOOT this will refresh the driver stack.
Repeat that for Network - Network Card (NIC), Wifi, Sound, Mouse and Keyboard
if 3rd party with their own software and drivers and any other major device drivers
you have.
Now go to System Maker's site (Dell, HP, Toshiba as examples) (as rollback) and
then Device Maker's site (Realtek, Intel, Nvidia, ATI as examples) and get their
latest versions. (Look for BIOS, Chipset, and software updates at System Maker's
site while there.)
Download - SAVE - go to where you put them - Right Click - RUN AD ADMIN -
REBOOT after each installation.
Always check in Device Manager - Drivers tab to be sure the version you are
installing actually shows up. This is because some drivers rollback before the
latest is installed (sound drivers particularly do this) so install a driver - reboot
- check to be sure it is installed and repeat as needed.
Repeat at Device Makers - BTW at Device Makers DO NOT RUN THEIR SCANNER -
heck manually by model.
Manually look at manufacturer's sites for drivers - and Device Maker's sites.
http://pcsupport.about.com/od/driverssupport/ht/driverdlmfgr.htm
====================================================
Memory tests do not catch all errors such as mismatched memory (possible even
for sticks that appear to be identical) and when faster memory is placed in system
behind slower memory. So it is best to also swap sticks in and out to check for
those even if all memory tests fail to show a problem.
To test RAM check here - let it run 4+ hours or so. <-- best method
www.memtest.org
MemTestX86 - Test RAM With
http://www.tenforums.com/tutorials/14201-memtest86-test-ram.html
For the Windows Memory Diagnostic Tool.
Type in Cortana's search box -> Windows Memory Diagnostics
at top of list - click it. in Windows 8/8.1/10 the name is "Windows Memory
Diagnostic".
======================================================
After doing ALL the updates you can, and if the issue continues, then run
DriverVerifier.
Driver Verifier can help find some BSOD issues :
Using Driver Verifier to identify issues with Windows drivers for advanced users
http://support.microsoft.com/kb/244617
How To Troubleshoot Driver Problems in Windows Vista or 7. (8/8.1 and 10
are essemtially the same).
http://www.winvistaclub.com/t79.html
Using Driver Verifier
http://msdn.microsoft.com/en-us/library/ff554113(v=VS.85).aspx
How to use Windows Driver Verifier Manager to Troubleshoot & Identify Driver
Issues
http://www.youtube.com/watch?v=_VwIDD9xngM
Driver Verifier
http://www.techsupportforum.com/2110308-post3.html
Using Driver Verifier
http://www.faultwire.com/solutions/using_driver_verifier.php
You can disable Driver Verifier
http://support.microsoft.com/kb/244617
WINKEY + X - RUN - type in -> verifier /reset hit enter to disable
Use BlueScreenView to see if there is a driver specified in the error message.
Also check with MyEventViewer at the time of the BlueScreen.
If DriverVerifier creates a minidump upload it and post the link here so we can
analyze it.
Hope this helps.
--------------------------------------------------------------------------------------------
Rob Brown -
Microsoft MVP <- profile - Windows Experience : Bicycle - Mark Twain said it right.