BSOD while rendering in sony vegas, 0x00000124

Security Software: ??? Recommend either of these two:

• Microsoft Security Essentials - Free Antivirus for Windows
  
  
• Good and Free system security combination.

Possible out of date drivers:

Code:

lirsgt	fffff880`06c72000	fffff880`06c7f000	Sat Mar 06 12:53:01 2004 (404a2c1d)	0001a199		lirsgt.sys
atksgt	fffff880`07e2a000	fffff880`07e79000	Sun May 17 07:36:34 2009 (4a1012e2)	0004fc56		atksgt.sys

lirsgt.sys
atksgt.sys
Neither look too serious, so don't worry about these yet.

Code:

Loading Dump File [D:\Kingston\BSODDmpFiles\Tombo\Windows_NT6_BSOD_jcgriff2\032412-31153-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17727.amd64fre.win7sp1_gdr.111118-2330
Machine Name:
Kernel base = 0xfffff800`02e65000 PsLoadedModuleList = 0xfffff800`030a9650
Debug session time: Sat Mar 24 12:08:05.996 2012 (UTC - 6:00)
System Uptime: 0 days 8:03:12.777
Loading Kernel Symbols
...............................................................
................................................................
.................................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

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

Probably caused by : hardware

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

2: 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: fffffa800f3a3028, 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:  VISTA_DRIVER_FAULT

PROCESS_NAME:  FileIOSurrogat

CURRENT_IRQL:  f

STACK_TEXT:  
fffff880`0396db58 fffff800`02e2ea3b : 00000000`00000124 00000000`00000000 fffffa80`0f3a3028 00000000`be200000 : nt!KeBugCheckEx
fffff880`0396db60 fffff800`02ff1c43 : 00000000`00000001 fffffa80`0f3a6aa0 00000000`00000000 fffffa80`0f3a6af0 : hal!HalBugCheckSystem+0x1e3
fffff880`0396dba0 fffff800`02e2e700 : 00000000`00000728 fffffa80`0f3a6aa0 fffff880`0396df30 fffff880`0396df00 : nt!WheaReportHwError+0x263
fffff880`0396dc00 fffff800`02e2e052 : fffffa80`0f3a6aa0 fffff880`0396df30 fffffa80`0f3a6aa0 00000000`00000000 : hal!HalpMcaReportError+0x4c
fffff880`0396dd50 fffff800`02e2df0d : 00000000`00000008 00000000`00000001 fffff880`0396dfb0 00000000`00000000 : hal!HalpMceHandler+0x9e
fffff880`0396dd90 fffff800`02e21e88 : 00000000`0444abc0 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0x55
fffff880`0396ddc0 fffff800`02ee062c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40
fffff880`0396ddf0 fffff800`02ee0493 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x6c
fffff880`0396df30 00000000`6b25e669 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x153
00000000`07839968 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x6b25e669


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: hardware

IMAGE_NAME:  hardware

DEBUG_FLR_IMAGE_TIMESTAMP:  0

FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_CACHE

BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_CACHE

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

Read through Stop 0x124 - what it means and what to try and use the following to supplement that thread:

• 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. 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 a 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).
  
  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.
  
  Once these steps have been followed, it is safe to remove and replace components within your computer.

Thanks for the fast reply! I think the security thing is because I disabled UAC, I have kaspersky internet security installed. I will try everything else you have posted.