BSOD: Random - New CPU/Mobo/RAM

Hello all,

Last year I had a problem I could not figure out and someone here was able to help me. Once again it appears I am getting random blue screens and my skills in analyzing dumps seems to have declined.

For the most part I can't really tell what is causing it as I have gotten 2 so far (new build as of 4 hours ago).

New Rig Specs:
This Kit

Motherboard: MSI 760GM-P21 (FX)
CPU: AMD Phenom II X6 1045T 2.7GHz (OC'd to 3.36GHz via mobo 'OC Genie')
RAM: 4GB (1x) ADATA PC3-10600 (1333MHz)
PSU: Thermaltake 450w (can't find a model, came in the case).
GPU: ATI Radeon HD 5670
* Temperatures are staying 35c-40c

I am currently installing Win7 SP1 (64bit) to see if that alleviates the crashes.
Any input is highly appreciated!

Just an update here:
Installed SP1 as well as all the newest drivers I could find. No more BSOD's but I am seeing a lot of APPCRASH that seem to be random. Not sure if anyone can learn anything from my dumps / info. If not I suppose this is solved for the time being.

Another Update
Still crashing, running SP1 and all the latest drivers I could find. It also appears that navigating through Windows is quite sluggish. I have had blue screens with the CPU set to stock as well as with the "Auto OC" that came with the chip/mobo, same errors either way. Starting to get a bit irritating as I work from home professionally and rely on this desktop for work duties.

After doing my best to analyze the issue I came up with the following:

Code:

On Tue 7/31/2012 10:34:02 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\073112-18969-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x80640) 
Bugcheck code: 0x50 (0xFFFFF7FFF2DCE4E0, 0x8, 0xFFFFF7FFF2DCE4E0, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. 
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time. 


On Tue 7/31/2012 10:34:02 AM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0) 
Bugcheck code: 0x50 (0xFFFFF7FFF2DCE4E0, 0x8, 0xFFFFF7FFF2DCE4E0, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. 
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time. 


On Tue 7/31/2012 3:37:22 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\073012-20139-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x71F00) 
Bugcheck code: 0x50 (0xFFFFF9004422CC7C, 0x0, 0xFFFFF960000578A5, 0x5)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. 
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time. 


On Tue 7/31/2012 2:35:31 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\073012-19468-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x71F00) 
Bugcheck code: 0x1A (0x5003, 0xFFFFF780C0000000, 0x4CD5, 0xFFFFF9800EE00C09)
Error: MEMORY_MANAGEMENT
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules. 
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.

FINAL UPDATE:
This has been solved, I gave up trying to fix it and formatted. The issue appears to have been related to the motherboards auto overclock which needed a bare install to work correctly.

End result is a 6x 3.8ghz running smooth and stable!