BSOD on new build

Your crash was caused by Catalyst Control Center, part of your ATI video card driver package.

Code:

 
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff80002ecb4fe, Address of the instruction which caused the bugcheck
Arg3: fffff880083fee20, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.
Debugging Details:
------------------
 
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
FAULTING_IP: 
nt!KiSwapContext+9e
fffff800`02ecb4fe 440f285980      movaps  xmm11,xmmword ptr [rcx-80h]
CONTEXT:  fffff880083fee20 -- (.cxr 0xfffff880083fee20)
rax=000007ffffedc000 rbx=fffff8000303be80 rcx=00000000c0000102
rdx=00000000000007ff rsi=fffffa8006939060 rdi=fffff80003049cc0
rip=fffff80002ecb4fe rsp=fffff880083ff800 rbp=fffffa8006939060
 r8=fffffa8005dc9bb8  r9=0000000000000000 r10=fffffffffffffffe
r11=00000000000156df r12=0000000000000000 r13=0000000000000000
r14=fffffa8005dc9b30 r15=fffff80000b96080
iopl=0         nv up ei pl nz ac pe cy
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010213
nt!KiSwapContext+0x9e:
fffff800`02ecb4fe 440f285980      movaps  xmm11,xmmword ptr [rcx-80h] ds:002b:00000000`c0000082=????????????????????????????????
Resetting default scope
CUSTOMER_CRASH_COUNT:  1
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x3B
PROCESS_NAME:  CCC.exe
CURRENT_IRQL:  2
LAST_CONTROL_TRANSFER:  from 0000000000000000 to fffff80002ecb4fe
STACK_TEXT:  
fffff880`083ff800 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSwapContext+0x9e
 
FOLLOWUP_IP: 
nt!KiSwapContext+9e
fffff800`02ecb4fe 440f285980      movaps  xmm11,xmmword ptr [rcx-80h]
SYMBOL_STACK_INDEX:  0
SYMBOL_NAME:  nt!KiSwapContext+9e
FOLLOWUP_NAME:  MachineOwner
MODULE_NAME: nt
IMAGE_NAME:  ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP:  4d9fdd5b
STACK_COMMAND:  .cxr 0xfffff880083fee20 ; kb
FAILURE_BUCKET_ID:  X64_0x3B_nt!KiSwapContext+9e
BUCKET_ID:  X64_0x3B_nt!KiSwapContext+9e
Followup: MachineOwner
---------

Uninstall your ATI graphics drivers, and install new ones.

Drivers - Clean Left over Files after Uninstalling
You might consider just loading the drivers and not CCC.

You can use MSI Afterburner it's a good GPU control program.

Latest AMD Catalyst Video Driver for Windows 7


Do you have the latest version of Avast installed?
Latest version of Avast Antivirus

Code:

 
Event[391]:
  Log Name: System
  Source: Service Control Manager
  Date: 2011-05-25T22:47:14.405
  Event ID: 7026
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: DaveQuadcore-PC
  Description: 
The following boot-start or system-start driver(s) failed to load: 
aswSnx - This is an Avast driver
 
Event[4316]:
  Log Name: System
  Source: Service Control Manager
  Date: 2011-05-24T09:50:23.321
  Event ID: 7022
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: DaveQuadcore-PC
  Description: 
The avast! Antivirus service hung on starting.

Have you been having problems with your CD-ROM?
A lot of these errors.

Code:

 
Event[1261]:
  Log Name: System
  Source: cdrom
  Date: 2011-05-25T10:21:25.517
  Event ID: 15
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: DaveQuadcore-PC
  Description: 
The device, \Device\CdRom0, is not ready for access yet.

D/L and run Western Digital Lifeguard– Quick Test and Extended Test

Code:

Event[5754]:
  Log Name: System
  Source: Disk
  Date: 2011-05-22T21:12:06.221
  Event ID: 7
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: DaveQuadcore-PC
  Description: 
The device, \Device\Harddisk0\DR2, has a bad block.
 
 
Event[6160]:
  Log Name: System
  Source: Ntfs
  Date: 2011-05-22T19:09:19.219
  Event ID: 55
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: DaveQuadcore-PC
  Description: 
The file system structure on the disk is corrupt and unusable. Please run the chkdsk utility on the volume E:.

Your welcome.

Let us know if you get any more BSoDs.

Personally, I would stay with Avast, but it's your choice.

To check the HDD status and repair the bad blocks run Western Digital Lifeguard– Quick Test and Extended Test.
Let us know what the tests report.

Did you get dump files?
Post them here if you did.

If it is more stable after you deleted Avast, then D/L Microsoft Security Essentials for testing. IF everything is stable, then you can change to something else.

Did you install the same ATI drivers?
Which ones?
Are you still using CCC?
CCC has been known to cause crashes.
MSI Afterburner is good, have been using it with no issues, it's more stable and easier to adjust/monitor your ATI card.
Sometimes you might need to install an older version of the ATI drivers, they seem to be having a lot of bugs now and a lot of fixes, so you might have to try a few different ones.

As far as the CPU core settings, these are usually set by the program that you have running.