BSOD For no apperent reason

Overclocking
If you are overclocking any hardware, STOP. Reset any changed values back to default.

Code:

Start Menu\Programs\ASUS\AI Suite II Public:Start Menu\Programs\ASUS\AI Suite II Public

   Warning

This is overclocking software and can lead to system instability and BSOD's. Please reset all components to their stock speeds and then remove the software.

SFC /scannow to check windows for corruption:

How to Repair Windows 7 System Files with System File Checker
1. Click Start
2. In the search box, type Command Prompt
3. In the list that appears, right-click on cmd.exe and choose Run as administrator
4. In the command window that opens, type

sfc /scannow

and hit enter.

Start up

Keep less stuff at the start-up. Only anti-virus, this helps avoid driver conflicts and improves time to log in to windows.
Troubleshoot a Problem by Performing a Clean Startup in Windows 7 or Vista
How to Change, Add, or Remove Startup Programs in Windows 7

Hard Drive/Storage

Post disk summary using CrystalDiskInfo software: CrystalDiskInfo Standard Edition

• For how to upload a screenshot or file, read here

Make a hard drive test from the hard drive manufacturers website: Hard Drive Diagnostic Procedure

For errors on your Hard drive(s): How to Run Disk Check in Windows 7

System Optimisers

Please remove the following software:

Code:

Start Menu\Programs\TuneUp Utilities 2012	Public:Start Menu\Programs\TuneUp Utilities 2012	Public
Start Menu\Programs\TuneUp Utilities 2012\All functions	Public:Start Menu\Programs\TuneUp Utilities 2012\All functions	Public

This software is a known cause of BSOD's. The windows 7 operating system does not require these registry cleaning software. They often tune-down rather than tune-up and can wreck the OS beyond repair. Microsoft have improved Windows 7 significantly and it is much better at organising and optimising itself than its predecessors. Check this, this and this thread for evidence.

If you feel the need to use a registry cleaning or optimisation software, most of us recommend the use of CCleaner - PC Optimization and Cleaning - Free Download but make sure you back up the registry before making letting ccleaner delete anything.10 Tips on How to Properly Maintain Your Computer

Daemon Tools/Alcohol %

Code:

Start Menu\Programs\DAEMON Tools Lite	Public:Start Menu\Programs\DAEMON Tools Lite	Public

Daemon Tools (and Alcohol % software) are known to cause BSOD's on some Win7 systems (mostly due to the sptd.sys driver, although we have seen dtsoftbus01.sys blamed on several occasions). Please uninstall the program, then use the following free tool to ensure that the troublesome sptd.sys driver is removed from your system (pick the 32 or 64 bit system depending on your system's configuration): DuplexSecure - FAQ

As an alternative, many people recommend the use of Total Mounter or Magic ISO

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, fffffa8010c2a028, be200000, 5110a}

Probably caused by : GenuineIntel

Followup: MachineOwner
---------

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

WHEA_UNCORRECTABLE_ERROR (124)
A fatal hardware error has occurred. Parameter 1 identifies the type of error
source that reported the error. Parameter 2 holds the address of the
WHEA_ERROR_RECORD structure that describes the error conditon.
Arguments:
Arg1: 0000000000000000, Machine Check Exception
Arg2: fffffa8010c2a028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000be200000, High order 32-bits of the MCi_STATUS value.
Arg4: 000000000005110a, Low order 32-bits of the MCi_STATUS value.

Debugging Details:
------------------


BUGCHECK_STR:  0x124_GenuineIntel

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  f

STACK_TEXT:  
fffff800`00ba8a98 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: GenuineIntel

IMAGE_NAME:  GenuineIntel

DEBUG_FLR_IMAGE_TIMESTAMP:  0

FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_CACHE

BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_CACHE

Followup: MachineOwner
---------

0: kd> !errrec fffffa8010c2a028
===============================================================================
Common Platform Error Record @ fffffa8010c2a028
-------------------------------------------------------------------------------
Record Id     : 01ce701a02a8da24
Severity      : Fatal (1)
Length        : 928
Creator       : Microsoft
Notify Type   : Machine Check Exception
Timestamp     : 6/23/2013 14:47:45 (UTC)
Flags         : 0x00000000

===============================================================================
Section 0     : Processor Generic
-------------------------------------------------------------------------------
Descriptor    @ fffffa8010c2a0a8
Section       @ fffffa8010c2a180
Offset        : 344
Length        : 192
Flags         : 0x00000001 Primary
Severity      : Fatal

Proc. Type    : x86/x64
Instr. Set    : x64
Error Type    : Cache error
Operation     : Generic
Flags         : 0x00
Level         : 2
CPU Version   : 0x00000000000306a9
Processor ID  : 0x0000000000000000

===============================================================================
Section 1     : x86/x64 Processor Specific
-------------------------------------------------------------------------------
Descriptor    @ fffffa8010c2a0f0
Section       @ fffffa8010c2a240
Offset        : 536
Length        : 128
Flags         : 0x00000000
Severity      : Fatal

Local APIC Id : 0x0000000000000000
CPU Id        : a9 06 03 00 00 08 10 00 - bf e3 9a 7f ff fb eb bf
                00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00
                00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00

Proc. Info 0  @ fffffa8010c2a240

===============================================================================
Section 2     : x86/x64 MCA
-------------------------------------------------------------------------------
Descriptor    @ fffffa8010c2a138
Section       @ fffffa8010c2a2c0
Offset        : 664
Length        : 264
Flags         : 0x00000000
Severity      : Fatal

Error         : GCACHEL2_ERR_ERR (Proc 0 Bank 8)
  Status      : 0xbe2000000005110a
  Address     : 0x000000041e4d3780
  Misc.       : 0x0000001080000086

A "stop 0x124" is fundamentally different to many other types of bluescreens because it stems from a hardware complaint.

   Tip

Stop 0x124 minidumps contain very little practical information, and it is therefore necessary to approach the problem as a case of hardware in an unknown state of distress.

You can read more on this error and what to try here... Stop 0x124 - what it means and what to try: Stop 124 Troubleshooting Strategy

Take your time. No rush, good luck.

It appears a error occurred within the Level 2 Cache, in such a case, I suggest running Hardware - Stress Test With Prime95, and then selecting the Small FFTs test, the test will need to least run for two hours.

Do you have any CPU temperature monitoring programs? If you don't then I would recommend:

• Core Temp
• HWMonitor CPUID - System & hardware benchmark, monitoring, reporting

Also from the raw call stack for the thread (thanks to Arc), there's a few drivers which could be possible causes:

Code:

0: kd> lmvm nvlddmkm
start             end                 module name
fffff880`0a0e1000 fffff880`0abc2000   nvlddmkm T (no symbols)           
    Loaded symbol image file: nvlddmkm.sys
    Image path: nvlddmkm.sys
    Image name: nvlddmkm.sys
    Timestamp:        Sun May 12 20:09:45 2013 (518FE8F9)
    CheckSum:         00AB6DED
    ImageSize:        00AE1000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Ensure the version within the Device Manager matches the latest WHQL version:

Version: 320.18
Release Date for Desktops and Notebooks : May 23rd 2013
In Device Manager: 9.18.13.2018

Code:

0: kd> lmvm ndisrd
start             end                 module name
fffff880`077c2000 fffff880`077cc000   ndisrd   T (no symbols)           
    Loaded symbol image file: ndisrd.sys
    Image path: ndisrd.sys
    Image name: ndisrd.sys
    Timestamp:        Thu May 31 04:03:33 2012 (4FC6DF85)
    CheckSum:         0000A7D8
    ImageSize:        0000A000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Your Mionet driver/WinpkFilter high performance packet filtering framework seems to be a possible cause, and is possibly outdated, please check for updates from here: MioNet| Your personal private network for PC remote access, webcam access software, backup, and file sharing

Code:

0: kd> lmvm Rt64win7
start             end                 module name
fffff880`072c1000 fffff880`07374000   Rt64win7 T (no symbols)           
    Loaded symbol image file: Rt64win7.sys
    Image path: Rt64win7.sys
    Image name: Rt64win7.sys
    Timestamp:        Tue Jun 12 15:00:29 2012 (4FD74B7D)
    CheckSum:         000B8CFC
    ImageSize:        000B3000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Your Realtek RTL8168D/8111D Family PCI-E Gigabit Ethernet NIC driver seems to be a possible cause, and is potientally outdated, please check for any updates from here: Realtek

I want to add some points more with koolkat77 and x BlueRobot .... as it is one of the most extensive number of causes I have ever noticed.

Uninstall WinpkFilter LightWeight Filters.

Disable the webcam, at least for the time being till you are running without BSODs.

Daemon Tools, Alcohol 120% and Power Archiver Pro uses SCSI Pass Through Direct (SPTD), which is a well known BSOD causer. Uninstall Daemon Tools at first. Then download SPTD standalone installer from Disk-Tools.com, and execute the downloaded file as guided below :

• Double click to open it.
• Click this button only:
• 
• If it is grayed out, as in the picture, there is no more SPTD in your system, and you just close the window.

Get rid of intel rapid storage. First uninstall it from Control Panel > Programs and Features. Then Uninstall the driver from device manager.

1. Right click on "my computer" icon and click "manage" on the context menu.
2. It will open the "computer management" window.
3. Select "Device Manager" in the left pane, It will list all the existing devices up.
4. Expand "IDE ATA/ATAPI controllers" by clicking on the triangle in front of it.
5. Select one Intel device item under it, right click, uninstall.
6. Continue the process for all Intel items under "IDE ATA/ATAPI controllers"
7. Now restart the computer. At restart, windows will auto configure the appropriate native system driver.

Intel XHCI drivers needs to be updated.

Code:

fffff880`0a000000 fffff880`0a0c5000   iusb3xhc   (deferred)             
    Image path: iusb3xhc.sys
    Image name: iusb3xhc.sys
    Timestamp:        Mon May 21 12:51:40 2012 (4FB9ED04)
    CheckSum:         000CA061
    ImageSize:        000C5000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Search for updates in https://downloadcenter.intel.com/default.aspx.

As you are getting BSODs, you should stop overclocking and run all the hardware components like CPU, GPU and RAM to their default settings. Also set the BIOS to default, too.
How To Clear CMOS (Reset BIOS)

Take these two hardware tests .....

• How to Test and Diagnose RAM Issues with Memtest86+
• Video Card - Stress Test with Furmark

Let us know the results. The motherboard is brand new I guess?