BSOD and computer freezes

Hi all,
I built my own PC and have a mid level of tech knowledge (I can get around on Windows, but don't do much with the command prompt or in the bios). Ever since I built my computer, I have been experiencing two issues: BSOD and computer freezes accompanied by a weird machine-like noise. These can happen when browsing teh internet, watching movies, or even when I am not around. I have changed the BSOD timeout to wait for me to come back before restarting, so usually I just take note of the error message and then force restart. I have WhoCrashed running and also have saved my dump files as per the instructions on the forums. I have Hard Disk Sentinel running and it has not detected any bad sectors or hot temperatures (usually runs between 34-36 dg C). I have already updated my drivers (I suspected my video card at first) and am currently halfway through a 24-hr run using verifier.exe. Basically on verifier, I unchecked all of the non-Microsoft drivers and did a restart. So far, no freezes. However, these freezes occur irregularly, so I am not surprised. Sometimes the freeze occurs once a month or as often as twice a week. I have noticed that it also tends to happen more often (or maybe I am unlucky) when I wake up my computer from sleep or a restart. I basically log on, open up a few tabs, and *POOF* - freeze. Any help would be appreciated. I have the dump files attached to this post. Let me know if any further information is required.

Here is the information about my PC build:


OS: Windows 7 Professional 64bit
CPU: Intel Core 2 Quad Q6600 @ 2.40 GHz
MOBO: Gigabyte EP45-UD3R
RAM: 8 GB DDR2 (4 x 2GB) [OCZ sticks: OCZ2P10662G]
GPU: NVIDIA GeForce GTX 550 Ti
HDD: Seagate Barracuda Green 1.5TB 5900RPM (ST1500DL003-9VT16L)
AV: Microsoft Security Essentials
PSU: ModX Stream Pro 600W

ok so I let verifier run over night but apparently I forgot to change the computer's sleep settings. But I did get a blue screen when I woke the computer. I have attached the dumps and associated files with this post.

=== delete ===

Arc said:

Unfortunately it is not a verifier enabled BSOD.

Code:

0: kd> !verifier
fffff80003296b20: Unable to get verifier list.

Though it is pointing to some HDD /file system misbehavior.

Do some Disc checks.

1. Reseat the sata and power.
   
2. Run chkdsk /f/r, following the option two of the tutorial Disk Check
3. Seatool for dos: SeaTools | Seagate download
   Burn it in a blank cd. boot from the CD, click on "Accept", wait for it to finish detecting the drives, then in the upper left corner select "Basic Tests", then select "Long Test" and let it run.

About DV, you need to run the computer at its normal use within DV enabled. Not to leave it idle without any action. Hopefully it gives the output very soon, it it has to.

On another note, 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 it start showing errors/red lines, stop testing. A single error is enough to determine that something is going bad there.
_________________________________________________________

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 24, {1904fb, fffff88008658d78, fffff880086585d0, fffff800030dba1f}

Probably caused by : ntkrnlmp.exe ( nt!FsRtlAcquireFileForCcFlushEx+3c )

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

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

NTFS_FILE_SYSTEM (24)
    If you see NtfsExceptionFilter on the stack then the 2nd and 3rd
    parameters are the exception record and context record. Do a .cxr
    on the 3rd parameter and then kb to obtain a more informative stack
    trace.
Arguments:
Arg1: 00000000001904fb
Arg2: fffff88008658d78
Arg3: fffff880086585d0
Arg4: fffff800030dba1f

so you think it is hardware related, and not software?