HAL.dll BSOD

You are overclocking.

Code:

CPUID:        "Intel(R) Core(TM) i5-3570K CPU @ 3.40GHz"
MaxSpeed:     3400
CurrentSpeed: 3467

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)

Test your RAM modules for possible errors.
How to Test and Diagnose RAM Issues with Memtest86+
Run memtest for at least 8 passes, preferably overnight.

Stress test the Graphics Card using Furmark.
Video Card - Stress Test with Furmark

Stress test the CPU.
Hardware - Stress Test With Prime95

Check if the Power Supply Unit (PSU) supplying adequate power to the computer or not.
eXtreme Power Supply Calculator
At least 30% extra is safe. Also what is the wattage of the PSU?

Is the computer hot? Report us the heat of the computer after a couple of hours of your normal usage. Upload a screenshot of the summery tab of Speccy.

Uninstall Virtual Clone Drive.

No code has to be inserted here.

This SCSI Adapter may be problematic.

Make it sure that the OCZ-AGILITY3 SSD is running with the up-to-date firmware.
OCZ Technology

Let us know the results.
_____________________________________________________________________
BSOD ANALYSIS:

Code:

.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 9C, {0, fffff88002fdfb70, 0, 0}

Probably caused by : ntkrnlmp.exe ( nt!KxMcheckAbort+6c )

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

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

MACHINE_CHECK_EXCEPTION (9c)
A fatal Machine Check Exception has occurred.
KeBugCheckEx parameters;
    x86 Processors
        If the processor has ONLY MCE feature available (For example Intel
        Pentium), the parameters are:
        1 - Low  32 bits of P5_MC_TYPE MSR
        2 - Address of MCA_EXCEPTION structure
        3 - High 32 bits of P5_MC_ADDR MSR
        4 - Low  32 bits of P5_MC_ADDR MSR
        If the processor also has MCA feature available (For example Intel
        Pentium Pro), the parameters are:
        1 - Bank number
        2 - Address of MCA_EXCEPTION structure
        3 - High 32 bits of MCi_STATUS MSR for the MCA bank that had the error
        4 - Low  32 bits of MCi_STATUS MSR for the MCA bank that had the error
    IA64 Processors
        1 - Bugcheck Type
            1 - MCA_ASSERT
            2 - MCA_GET_STATEINFO
                SAL returned an error for SAL_GET_STATEINFO while processing MCA.
            3 - MCA_CLEAR_STATEINFO
                SAL returned an error for SAL_CLEAR_STATEINFO while processing MCA.
            4 - MCA_FATAL
                FW reported a fatal MCA.
            5 - MCA_NONFATAL
                SAL reported a recoverable MCA and we don't support currently
                support recovery or SAL generated an MCA and then couldn't
                produce an error record.
            0xB - INIT_ASSERT
            0xC - INIT_GET_STATEINFO
                  SAL returned an error for SAL_GET_STATEINFO while processing INIT event.
            0xD - INIT_CLEAR_STATEINFO
                  SAL returned an error for SAL_CLEAR_STATEINFO while processing INIT event.
            0xE - INIT_FATAL
                  Not used.
        2 - Address of log
        3 - Size of log
        4 - Error code in the case of x_GET_STATEINFO or x_CLEAR_STATEINFO
    AMD64 Processors
        1 - Bank number
        2 - Address of MCA_EXCEPTION structure
        3 - High 32 bits of MCi_STATUS MSR for the MCA bank that had the error
        4 - Low  32 bits of MCi_STATUS MSR for the MCA bank that had the error
Arguments:
Arg1: 0000000000000000
Arg2: fffff88002fdfb70
Arg3: 0000000000000000
Arg4: 0000000000000000

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


BUGCHECK_STR:  0x9C_GenuineIntel

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  f

LAST_CONTROL_TRANSFER:  from fffff80002c31818 to fffff80002cddc00

STACK_TEXT:  
fffff880`02fdfb38 fffff800`02c31818 : 00000000`0000009c 00000000`00000000 fffff880`02fdfb70 00000000`00000000 : nt!KeBugCheckEx
fffff880`02fdfb40 fffff800`02c30f57 : 00000000`00000004 00000000`00000000 00000000`00000004 00000000`00000000 : hal!HalpMcaReportError+0x164
fffff880`02fdfc90 fffff800`02c24e88 : 00000000`1e8d9229 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0x9f
fffff880`02fdfcc0 fffff800`02cdc4ec : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40
fffff880`02fdfcf0 fffff800`02cdc353 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x6c
fffff880`02fdfe30 fffff800`02d13483 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x153
fffff880`009a9980 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxFlushEntireTb+0x93


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!KxMcheckAbort+6c
fffff800`02cdc4ec 488d8c2400010000 lea     rcx,[rsp+100h]

SYMBOL_STACK_INDEX:  4

SYMBOL_NAME:  nt!KxMcheckAbort+6c

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  5147d9c6

FAILURE_BUCKET_ID:  X64_0x9C_GenuineIntel_nt!KxMcheckAbort+6c

BUCKET_ID:  X64_0x9C_GenuineIntel_nt!KxMcheckAbort+6c

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

Good till time :)
If any further problem, let us know :)

Update asmedia XHCI driver.

Code:

fffff880`04800000 fffff880`04864000   asmtxhci   (deferred)             
    Image path: \SystemRoot\system32\DRIVERS\asmtxhci.sys
    Image name: asmtxhci.sys
    Timestamp:        Thu Nov 03 08:30:22 2011 (4EB203C6)
    CheckSum:         0006C541
    ImageSize:        00064000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Get the Version 1.14.3.0dated 2012.03.27 from P8Z77-V PRO - Motherboards - ASUS

Update Intel(R) USB 3.0 eXtensible Host Controller Driver too.

Code:

fffff880`03e00000 fffff880`03ec4000   iusb3xhc   (deferred)             
    Image path: \SystemRoot\system32\DRIVERS\iusb3xhc.sys
    Image name: iusb3xhc.sys
    Timestamp:        Thu Jan 05 17:24:45 2012 (4F058F85)
    CheckSum:         000C5CCE
    ImageSize:        000C4000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Get the Version 1.0.5.235 dated 2012.07.09 from P8Z77-V PRO - Motherboards - ASUS

The CPU may be factory overclocked, but bring it back to default. Same for the GPU.

Stress test the Graphics Card using Furmark.
Video Card - Stress Test with Furmark
Post a screenshot of the furmark window before closing the program.

Is the computer hot? Report us the heat of the computer after a couple of hours of your normal usage. Upload a screenshot of the summery tab of Speccy. We need the screenshot to see.

Test your RAM modules for possible errors.
How to Test and Diagnose RAM Issues with Memtest86+
Run memtest for at least 8 passes, preferably overnight.

If the logitech gaming devices are not in use, does it provide a BSOD? Observe and let us know.

Hope you will take all the suggestions and post us the feedback accordingly.
______________________________________________________________________________
BSOD ANALYSIS:

Code:

BugCheck 50, {fffff80006f504a1, 8, fffff80006f504a1, 2}


Could not read faulting driver name
Probably caused by : win32k.sys ( win32k!DrvGetRegistryHandleFromDeviceMap+791 )

Followup: MachineOwner
-----------------------------------------------------------------------------------
BugCheck D1, {ffffffff, 2, 0, fffff8800417df2f}

Probably caused by : hardware ( USBPORT!USBPORT_Xdpc_Worker+17f )

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

talon03 said:

That's great, thanks. I've updated the drivers as suggested.

The logitech gaming device is my mouse... so it's pretty much always in use!

Updated all the drivers within 3 minutes? Even cool.

If possible, try another alternative mouse.

Do the following steps.

• Download USBDeview. Execute it.
• Edit > Select all.
• File > Save Selected Items.
• Give a file name in the save dialog and save it on desktop.
• Zip the file. Upload the zip here.