BSOD While Running Ableton Live

Hi Folks, I'm a long time lurker and have been trying to diagnose this error I've been getting for the past two months. Essentially, I'm getting an Event 41 Kernel Power Problem, preceded by the lovely error below:

The computer has rebooted from a bugcheck. The bugcheck was: 0x00000124 (0x0000000000000000, 0xfffffa8008214028, 0x00000000b6004000, 0x00000000dc000135). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 100514-24148-01.

In addition to my system specs, I'm running a Focusrite 6i6 as a USB audio interface. I have gotten this error before outside of Ableton usage, while playing Guild Wars 2.

I downloaded BlueScreenView, which points to hal.dll and ntoskrnl.exe being the drivers associated with the errors. Beyond, that I'm not sure what that means. This appear to be deep level drivers unassociated with the recording process that seems to be causing the errors.

I also run Speccy, which points to no hardware issues.

Any help would be greatly appreciate, as this is derailing me recording my wedding proposal song.

This was my first post, am I missing anything?

It also might be worth noting, this error was experienced:

Event filter with query "SELECT * FROM __InstanceModificationEvent WITHIN 60 WHERE TargetInstance ISA "Win32_Processor" AND TargetInstance.LoadPercentage > 99" could not be reactivated in namespace "//./root/CIMV2" because of error 0x80041003. Events cannot be delivered through this filter until the problem is corrected.

I uploaded the files as instructed in the BSOD instruction, using method 1.

Just like you said,

Code:

Probably caused by :AuthenticAMD 
BugCheck 124, {0, fffffa8008134028, b6004000, e000135}

BugCheck 0x124

You have a 0x124 hardware bugcheck. If the system is still under warranty, I would recommend sending it in to have diagnostic tests done and any bad hardware replaced.

   Warning

Before you proceed with the following, answer these two questions: Are you still under warranty? Does your warranty allow you to open up the machine to check hardware? If you are unsure of the answers to these questions, contact your system manufacturer. WARNING: The steps that follow can void your warranty!!!

For your hardware stop 0x124 crash, read through Stop 0x124 - what it means and what to try and use the following hardware checks to supplement that link.

• If you are overclocking any hardware, please stop.
  
  
• If you have an SSD, make sure the following are up to date:
  • SSD firmware
  • BIOS Version
  • Chipset Drivers
  • Hard disk controller drivers/SATA drivers
  • If you have a Marvell IDE ATA/ATAPI device, make sure the drivers are up to date from the Intel site or Marvell site and not from your motherboard/vendor support site.
  
  
  
• Run all but the advanced tests with SeaTools for HDDs.
  SeaTools for Windows
  
  SeaTools for DOS
  
  
• Monitor temperatures during the following tests.
  
  Use the following programs to monitor the temperatures.
  • Real Temp is a good CPU temperature monitor.
  • Speccy - System Information - Free Download will monitor all hardware temperatures.
  • HWiNFO, HWiNFO32 & HWiNFO64 - Hardware Information and Analysis Tools can be inaccurate for CPU temperatures, but is a good program for GPU temperature monitoring.
  
  
  • Use FurMark: VGA Stress Test, Graphics Card and GPU Stability Test, Burn-in Test, OpenGL Benchmark and GPU Temperature | oZone3D.Net to test the graphics card GPU. Let it run until the GPU temperatures even out or until the GPU temperatures reach a dangerous level (you can find the max temperature for your card on either the nVidia or AMD sites; if you are not sure, ask us). The goal is to get a steady temperature, find out if the GPU is overheating, or to see if there are any artifacts present in the test itself: look for strange pixelated patterns on the screen or colors that do not look like they belong. Then use the |MG| Video Memory Stress Test 1.7.116 Download to test your graphics card memory. Let the memory test run for at least seven passes; the more the better.
    
    
  • Run Hardware - Stress Test With Prime95 to determine any hardware problems. Run all three tests for a few hours each. If you get errors, stop the test and post back here.
    
    
  • Follow the steps for doing CPU stress test using IntelBurnTest
  
  
• Run the boot version of Memtest86+ paying close attention to Parts 2 and 3 of the tutorial. Also, in case Memtest86+ misses anything and comes up with no errors, run the extended version of the Windows Memory Diagnostics Tool for at least five passes. These you may want to run overnight since they take a long time to complete (run them an hour before bed each of the next two nights and check before going to sleep that they are still running).
  
  For Part 3: If You Have Errors: If you swap any memory components, follow these steps for ESD safety:
  
  1. Shut down and turn off your computer.
  2. Unplug all power supplies to the computer (AC Power then battery for laptops, AC power for desktops)
  3. Hold down the power button for 30 seconds to close the circuit and ensure all power drains from components.
  4. Make sure you are grounded by using proper grounding techniques, i.e. work on an anti-static workbench, anti-static desk, or an anti-static pad. Hold something metallic while touching it to the anti-static surface, or use an anti-static wristband to attach to the anti-static material while working. If you do not have an anti-static workbench, desk, or pad, you can use your computer tower/case by finding a metal hold in it, such as a drive bay.
  
  Once these steps have been followed, it is safe to remove and replace components within your computer.

Remember to read closely through Stop 0x124 - what it means and what to try for the crash.

Coutesy of: writhziden

Post back results afterwards.

Hello,

Code:

AODDriver2.sys              Tue Feb 11 05:06:52 2014 (52FA044C)

Seems you have some Gigibyte crapware on your machine. Try uninstalling all the extra Gigibyte extra software that you have. Sometimes the programs alone can cause the BSODs.

If you are getting more BSODs, post up the new files.

Follow this tutorial to see if you can get rid of any left over drivers from Gibigyte,
Multiple BSODs pointing to many diferent drivers