BSOD multiple times on new computer

i just finished building my own custom desktop today and i had installed windows 7 64bit home , while doing windows updates i kept on getting several different BSOD's


021812-29530-01.dmp 2/18/2012 7:13:59 PM SYSTEM_SERVICE_EXCEPTION 0x0000003b 00000000`c0000005 fffff880`012caf28 fffff880`0375ddb0 00000000`00000000 Ntfs.sys Ntfs.sys+72f28 x64 ntoskrnl.exe+705c0 C:\Windows\Minidump\021812-29530-01.dmp 4 15 7600 276,272




021812-26254-01.dmp 2/18/2012 6:51:19 PM MEMORY_MANAGEMENT 0x0000001a 00000000`00000031 fffffa80`08ce9f60 fffff880`07d86000 fffff8a0`07be00e3 ntoskrnl.exe ntoskrnl.exe+705c0 NT Kernel & System Microsoft® Windows® Operating System Microsoft Corporation 6.1.7600.16841 (win7_gdr.110622-1503) x64 ntoskrnl.exe+705c0 C:\Windows\Minidump\021812-26254-01.dmp 4 15 7600 276,272




021812-31574-01.dmp 2/18/2012 6:15:40 PM MEMORY_MANAGEMENT 0x0000001a 00000000`00000783 fffff880`06f4a480 fffff980`0a280000 fffff8a0`07609920 Ntfs.sys Ntfs.sys+5cd80 x64 ntoskrnl.exe+705c0 C:\Windows\Minidump\021812-31574-01.dmp 4 15 7600 276,272



021812-25038-01.dmp 2/18/2012 5:49:32 PM SYSTEM_THREAD_EXCEPTION_NOT_HANDLED 0x1000007e ffffffff`c0000005 fffff800`0317e61f fffff880`02fa1a48 fffff880`02fa12b0 ntoskrnl.exe ntoskrnl.exe+36061f NT Kernel & System Microsoft® Windows® Operating System Microsoft Corporation 6.1.7600.16841 (win7_gdr.110622-1503) x64 ntoskrnl.exe+36061f C:\Windows\Minidump\021812-25038-01.dmp 4 15 7600 276,272




021812-28470-01.dmp 2/18/2012 4:28:05 PM BAD_POOL_HEADER 0x00000019 00000000`00000003 fffff880`02c14b40 fffff880`02c16840 fffff880`02c14b40 win32k.sys win32k.sys+1b1d59 x64 ntoskrnl.exe+71f00 C:\Windows\Minidump\021812-28470-01.dmp 4 15 7600 272,200

have you checked your bios settings?
cpu voltage/memory voltage/ memory timming /cpu temp

scrooge

Windows x64 Ultimate
Motherboard - GIGABYTE GA-970A-UD3 AM3+ AMD 970 SATA 6Gb/s USB 3.0 ATX AMD Motherboard

Video Card - XFX HD-677X-ZNLC Radeon HD 6770 1GB 128-bit GDDR5 PCI Express 2.1 x16 HDCP Ready CrossFireX Support Video Card

Processor - AMD Athlon II X4 645 Propus 3.1GHz Socket AM3 95W Quad-Core Desktop Processor ADX645WFGMBOX

Hard Drive - Seagate Barracuda ST500DM002 500GB 7200 RPM SATA 6.0Gb/s 3.5" Internal Hard Drive -Bare Drive

RAM - G.SKILL Ripjaws Series 8GB (2 x 4GB) 240-Pin DDR3 SDRAM DDR3 1333 (PC3 10666) Desktop Memory Model F3-10666CL9D-8GBRL

On Wed 2/22/2012 10:36:40 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\022212-26925-01.dmp
uptime: 00:30:29
This was probably caused by the following module: fltmgr.sys (fltmgr+0x323F)
Bugcheck code: 0x1A (0x411, 0xFFFFF68000026310, 0x4D00, 0xFFFFF68000000003)
Error: MEMORY_MANAGEMENT
file path: C:\Windows\system32\drivers\fltmgr.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Microsoft Filesystem Filter Manager
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 a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.


On Wed 2/22/2012 10:36:40 PM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
uptime: 00:30:29
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x1A (0x411, 0xFFFFF68000026310, 0x4D00, 0xFFFFF68000000003)
Error: MEMORY_MANAGEMENT
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.


On Wed 2/22/2012 9:41:17 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\022212-17191-01.dmp
uptime: 00:35:48
This was probably caused by the following module: ntoskrnl.exe (nt+0x71F00)
Bugcheck code: 0x1A (0x5003, 0xFFFFF70001080000, 0xDBBE, 0xDBC00001EF7C)
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.


On Wed 2/22/2012 9:04:42 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\022212-16114-01.dmp
uptime: 00:13:06
This was probably caused by the following module: ntoskrnl.exe (nt+0x71F00)
Bugcheck code: 0x1A (0x41790, 0xFFFFFA8004127490, 0xFFFF, 0x0)
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.

scrooge said:

have you checked your bios settings?
cpu voltage/memory voltage/ memory timming /cpu temp

scrooge

no i have not, what should i be looking for exactly?

heres the attachment for the system health report

download cpuz at CPUID - System & hardware benchmark, monitoring, reporting
then upload a screen shot of cpu / spd and memory so we can see what your settings are.

http://imageshack.us/f/818/cpuzw.png/

try boosting your cpu voltage up to 1.15 and see if the system becomes more stable.