BSOD before and after fresh Windows install. Has ran good since 2008..

Only 27 updates since SP1 - most systems have 70 or more. Please visit Windows Update and get all available updates (it may take checking multiple times).

Nice clean system - and with the reinstall of Windows it's most likely a hardware problem.
BUT, let's try this stuff first:

NCREMOTEPCI.SYS dates from 2006
Please update this driver, it most likely belongs to the software for your Satellite TV receiver.
More info on the driver here: Driver Reference Table

nvm62x64.sys dates from 2008
Please update this driver, it is the networking driver for your motherboard and comes packed with the nVidia chipset drivers at Drivers - Download NVIDIA Drivers
More info on the driver here: Driver Reference Table

atinavrr.sys dates from 2008
Please update this driver, it most likely belongs to the ATI drivers on your system. I have no idea of what ATI device it could be associated with as there is no dxdiag report in the uploaded files.
If unable to update it, please uninstall the ATI software from your system.
If still unable to remove the driver, post back and we'll give instructions on how to safely remove it.
More info on the driver here: Driver Reference Table

If these don't fix it, then start with the free hardware diagnostics here: Hardware Diags I'd start with the hard drive test as the BSOD blames the NTFS file system (and that's on the hard drive).

Further info on BSOD error messages available at: http://www.carrona.org/bsodindx.html

The following info is just FYI, I've already addressed the issues that I saw in the above paragraphs:
3RD PARTY DRIVERS PRESENT IN THE DUMP FILES
- Create a System Restore Point prior to doing any of this. DO NOT mess with the drivers themselves - leave the Windows\System32\drivers directory alone unless we specifically direct you to it!
- Please either update the older drivers from the device manufacturer's website - or uninstall them from your system. Reference links are included below.
- DO NOT use Windows Update or the Update Drivers function of Device Manager.
- Please feel free to post back about any drivers that you are having difficulty locating.
- Windows Update exceptions may be noted below for Windows drivers.

Code:

nvraid.sys      Fri Mar 19 16:59:20 2010 (4BA3E5A8)
nvstor.sys      Fri Mar 19 16:45:11 2010 (4BA3E257)
amdxata.sys     Fri Mar 19 12:18:18 2010 (4BA3A3CA)
dump_nvstor.sys Fri Mar 19 16:45:11 2010 (4BA3E257)
nvm62x64.sys    Fri Oct 17 17:01:06 2008 (48F8FD12)
nvlddmkm.sys    Thu May 14 16:48:07 2009 (4A0C8387)
atinavrr.sys    Wed May 14 21:16:11 2008 (482B8EDB)
NCREMOTEPCI.SYS Mon Sep 11 16:47:50 2006 (4505CB76)

http://www.carrona.org/drivers/driver.php?id=nvraid.sys
http://www.carrona.org/drivers/driver.php?id=nvstor.sys
http://www.carrona.org/drivers/driver.php?id=amdxata.sys
http://www.carrona.org/drivers/driver.php?id=dump_nvstor.sys
http://www.carrona.org/drivers/driver.php?id=nvm62x64.sys
http://www.carrona.org/drivers/driver.php?id=nvlddmkm.sys
http://www.carrona.org/drivers/driver.php?id=atinavrr.sys
http://www.carrona.org/drivers/driver.php?id=NCREMOTEPCI.SYS

BSOD BUGCHECK SUMMARY

Code:

Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\021812-21871-01.dmp]
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Debug session time: Sat Feb 18 19:59:46.163 2012 (UTC - 5:00)
System Uptime: 0 days 0:16:14.209
Probably caused by : Ntfs.sys ( Ntfs! ?? ::FNODOBFM::`string'+2b49 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  svchost.exe
BUGCHECK_STR:  0x24
FAILURE_BUCKET_ID:  X64_0x24_Ntfs!_??_::FNODOBFM::_string_+2b49
Bugcheck code 00000024
Arguments 00000000`001904fb fffff880`06d65ea8 fffff880`06d65700 fffff800`029d3b87
BiosVersion = 6.00 PG
BiosReleaseDate = 11/24/2009
CPUID:        "Intel(R) Core(TM)2 Quad  CPU   Q9450  @ 2.66GHz"
MaxSpeed:     2660
CurrentSpeed: 2666
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
  
  

Start with the free hardware diagnostics here: Hardware Diags I'd start with the hard drive test as the BSOD blames the NTFS file system (and that's on the hard drive).