Windows 7 crashes when using any type of movie maker

I have MP4 videos that I am trying to make into a movie. I have tried numerous software movie makers including “Windows live movie maker “, but every program that I have tried gives the BSOD and reboots my computer. I am presently using Movie Plus 5, but it too gives the BSOD within 10 minutes of use. The system will boot back up and run with everything else as normal but as soon as I start the movie software the system goes down again. I have ran software for checking all drivers, for sure the NVIDIA Video drivers and they show that they are all up to date. I have ran malware and spyware, cleaned the registers, checked the heat on the CPU’s and ran error checking on the drives. I have been hunting this squirrel for 2 weeks now and I think it’s time to bring the big dogs in.
Hope you can help
the system info is too big to list so I attached it.

As to registry cleaning... Many of us on the forums actually do not recommend automated optimization tools for Windows 7. Windows 7 does a much better job of handling its own optimization than its predecessors did. We especially do not recommend registry cleaning as an "optimization" step because automated registry cleaning causes more harm to the registry than it actually repairs.

In the future, if you need help optimizing Windows 7, please post a thread in Performance & Maintenance - Windows 7 Forums or follow the tutorial enclosed in that forum to Optimize Windows 7.

Code:

Loading Dump File [D:\Kingston\BSODDmpFiles\oldsage\Windows_NT6_BSOD_jcgriff2\031212-25053-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 (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`02c06000 PsLoadedModuleList = 0xfffff800`02e4b670
Debug session time: Mon Mar 12 19:32:38.384 2012 (UTC - 6:00)
System Uptime: 0 days 4:26:51.163
Loading Kernel Symbols
...............................................................
................................................................
...................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1E, {ffffffffc0000005, fffff80002cce5ab, 5, 20}

Probably caused by : hardware ( nt! ?? ::FNODOBFM::`string'+497a0 )

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

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

KMODE_EXCEPTION_NOT_HANDLED (1e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff80002cce5ab, The address that the exception occurred at
Arg3: 0000000000000005, Parameter 0 of the exception
Arg4: 0000000000000020, Parameter 1 of the exception

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! ?? ::FNODOBFM::`string'+497a0
fffff800`02cce5ab 0000            add     byte ptr [rax],al

EXCEPTION_PARAMETER1:  0000000000000005

EXCEPTION_PARAMETER2:  0000000000000020

WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002eb5100
 0000000000000020 

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

BUGCHECK_STR:  0x1E_c0000005

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  MoviePlus.exe

CURRENT_IRQL:  0

TRAP_FRAME:  fffff88005b136e0 -- (.trap 0xfffff88005b136e0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=000000000018d988
rdx=00000000048b0bec rsi=0000000000000000 rdi=0000000000000000
rip=0000000074f94e84 rsp=000000000018d920 rbp=000000000018d9b2
 r8=000000000000002b  r9=0000000074987db9 r10=0000000000000000
r11=0000000000000246 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na po nc
0023:74f94e84 ??              ???
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002cce588 to fffff80002c82c40

MISALIGNED_IP: 
nt! ?? ::FNODOBFM::`string'+497a0
fffff800`02cce5ab 0000            add     byte ptr [rax],al

STACK_TEXT:  
fffff880`05b12448 fffff800`02cce588 : 00000000`0000001e ffffffff`c0000005 fffff800`02cce5ab 00000000`00000001 : nt!KeBugCheckEx
fffff880`05b12450 fffff800`02c822c2 : fffff880`05b12c28 fffff880`05b13638 fffff880`05b12cd0 fffff880`05b136e0 : nt! ?? ::FNODOBFM::`string'+0x4977d
fffff880`05b12af0 fffff800`02c80e3a : 00000000`00000001 00000000`00000020 00000000`00000000 fffff880`05b13638 : nt!KiExceptionDispatch+0xc2
fffff880`05b12cd0 fffff800`02cce5ab : fffff880`05b13638 fffff880`05b136e0 fffff880`05b136e0 00000000`00000000 : nt!KiPageFault+0x23a
fffff880`05b12e60 fffff800`02c822c2 : fffff880`05b13638 00000000`0018da10 fffff880`05b136e0 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x497a0
fffff880`05b13500 fffff800`02c80e3a : 00000000`00000000 00000000`00000000 00000000`00000001 00000000`0018da10 : nt!KiExceptionDispatch+0xc2
fffff880`05b136e0 00000000`74f94e84 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x23a
00000000`0018d920 fffff800`02c7a210 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x74f94e84
fffff880`05b13af0 fffff880`05b13b28 : 00000000`7404aecc fffff900`00000000 fffff880`05b13bb0 00000000`00000000 : nt!KiCallUserMode
fffff880`05b13af8 00000000`7404aecc : fffff900`00000000 fffff880`05b13bb0 00000000`00000000 fffff880`05b14470 : 0xfffff880`05b13b28
fffff880`05b13b00 fffff900`00000000 : fffff880`05b13bb0 00000000`00000000 fffff880`05b14470 3e418df4`d5b892bf : 0x7404aecc
fffff880`05b13b08 fffff880`05b13bb0 : 00000000`00000000 fffff880`05b14470 3e418df4`d5b892bf 3e418df4`d5b892bf : 0xfffff900`00000000
fffff880`05b13b10 00000000`00000000 : fffff880`05b14470 3e418df4`d5b892bf 3e418df4`d5b892bf bfaeb733`a3618000 : 0xfffff880`05b13bb0


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt! ?? ::FNODOBFM::`string'+497a0
fffff800`02cce5ab 0000            add     byte ptr [rax],al

SYMBOL_STACK_INDEX:  4

SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+497a0

FOLLOWUP_NAME:  MachineOwner

IMAGE_NAME:  hardware

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MODULE_NAME: hardware

FAILURE_BUCKET_ID:  X64_IP_MISALIGNED

BUCKET_ID:  X64_IP_MISALIGNED

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

• If you are overclocking any hardware, please stop.
  
  
• 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.
  
  
• 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.

The information provided about your system does not seem to be accurate. I was trying to find where you would update your drivers, but when I search for your system, HP just lists every single Pavilion desktop they have available. Please post the results of CTRL+ALT+S to get HP specs.