A few things:
First off, we're dealing with various different bugchecks here, varying from NTFS_FILE_SYSTEM (24) to SYSTEM_SERVICE_EXCEPTION (3b) to IRQL_NOT_LESS_OR_EQUAL (a), etc. Generally, I am going to assume for the moment we are dealing with a driver issue due to a few of the bugchecks and some memory corruption, as well as taking a look at the modules list. However, something interesting, in a few of these dumps CCC.exe is the process that faulted. Generally you don't pay too much attention to that, however I would like to note that's interesting considering you mentioned your friend has recently upgraded GPU's. Just something to note of.
1. ASACPI.sys is listed. This is a driver linked to various different Asus utilities. Asus utilities for the most part are huge causes of BSOD's on W7 based systems, and I would recommend your friend removes any and all Asus systems bundled onto his system that he may have installed from the disk, etc. These utilities don't offer too much of importance anyway, and given that one or more utilities can monitor and even change BIOS settings on the fly, there is a link between the EFI and OS... which to me, that's a little unsettling, and that's why issues I would imagine occur with these utilities. Also maybe just because they're coded horribly, who knows.
2. Make sure you friend is on the latest GPU drivers via AMD's website. If he is, ensure he is not on a BETA driver version. If he is not on a BETA driver version, but is on the latest, ask him to roll back a version or two to ensure it's not a driver related issue.
3. If still having problems after #1-2, I'd recommend enabling Driver Verifier to see if we can catch any software issues going on:
What is Driver Verifier?
Driver Verifier is included in Windows 7, Windows Server 2008 R2, Windows Vista, Windows Server 2008, Windows 2000, Windows XP, and Windows Server 2003 to promote stability and reliability; you can use this tool to troubleshoot driver issues. Windows kernel-mode components can cause system corruption or system failures as a result of an improperly written driver, such as an earlier version of a Windows Driver Model (WDM) driver.
Essentially, if there's a 3rd party driver believed to be at issue, enabling Driver Verifier will help flush out the rogue driver by flagging it and causing your system to BSOD.
Before enabling Driver Verifier, it is recommended to create a System Restore Point:
Vista - START | type rstrui - create a restore point
Windows 7 - START | type create | select "Create a Restore Point"
How to enable Driver Verifier:
Start > type "verifier" without the quotes > Select the following options -
1. Select - "Create custom settings (for code developers)"
2. Select - "Select individual settings from a full list"
3. Check the following boxes -
- Special Pool
- Pool Tracking
- Force IRQL Checking
- Deadlock Detection
- Security Checks (Windows 7)
- Concurrentcy Stress Test (Windows 8)
- DDI compliance checking (Windows 8)
- Miscellaneous Checks
4. Select - "Select driver names from a list"
5. Click on the "Provider" tab. This will sort all of the drivers by the provider.
6. Check EVERY box that is NOT provided by Microsoft / Microsoft Corporation.
7. Click on Finish.
Important information regarding Driver Verifier:
- If Driver Verifier finds a violation, the system will BSOD.
- After enabling Driver Verifier and restarting the system, depending on the culprit, if for example the driver is on start-up, you may not be able to get back into normal Windows because Driver Verifier will flag it, and as stated above, that will cause / force a BSOD.
If this happens, do not panic, do the following:
- Boot into Safe Mode by repeatedly tapping the F8 key during boot-up.
- Once in Safe Mode - Start > type "system restore" without the quotes.
- Choose the restore point you created earlier.
If you did not set up a restore point, do not worry, you can still disable Driver Verifier to get back into normal Windows:
- Start > Search > type "cmd" without the quotes.
- To turn off Driver Verifier, type in cmd "verifier /reset" without the quotes.
- Restart and boot into normal Windows.
How long should I keep Driver Verifier enabled for?
It varies, many experts and analysts have different recommendations. Personally, I recommend keeping it enabled for at least 36-48 hours. If you don't BSOD by then, disable Driver Verifier.
My system BSOD'd, where can I find the crash dumps?
They will be located in C:\Windows\Minidump
Any other questions can most likely be answered by this article:
4. Your friend has UltraMon's multi-monitor utility installed. If after every other test related thing we do, we are still having problems, I would tell your friend to uninstall this utility. It very may well be causing issues here given all of the CCC related crashes, general video problems, etc. Just a flag raiser for me, personally.
I think that's a good start!!! I am also sure many other BSOD analysts will pass through and chime in on anything I missed or add something of their own : )