BSOD about 3-4 times a week. Not specific to any particular action

Good news, and you're welcome.

68°C is within limits, but with your cooler it should be no more than 60°C.
Make sure the cooler is tight, but not too tight, as too loose or too tight can decrease performance.
You shouldn't be able to twist the cooler, with a light pressure turn, don't use full force.

Looks like you've been stable for a couple weeks, and now passed Prime and memtest86+, you can mark this thread 'Solved'.

Let us know if you have any more questions.

Those temps are much better.

You're welcome.

Sorry to hear that.

Do you still have these settings:
Dram 1.550V
VCCSA 1.070V

Your last crash:

Code:

STOP 0x0000004E: PFN_LIST_CORRUPT
Usual causes:  Device driver, ?memory
Probably caused by : memory_corruption ( nt!MiBadShareCount+4c )
FAILURE_BUCKET_ID:  X64_0x4E_99_nt!MiBadShareCount+4c

The usual causes are a bad driver and, of coarse, bad RAM.

Run Driver Verifier as per this tutorial:
Driver Verifier - Enable and Disable
First make a Restore Point.
Driver Verifier will slow down your system, run for a minimum of 24 hours, it will need several hours to cause a crash. A couple crashes will be needed to evaluate the cause, upload the full BSoD report when you get a couple crashes.

It may be due to the RAM causing these problems, getting new RAM may be necessary. To be sure run Driver Verifier first.

If there is no crash by now, the drivers are good, you can turn off Driver Verifier.
Were you using the computer normally?

Let us know if you get another crash.

Windows had a problem which indicated the hard drive and ran diskcheck.

Just to be sure run WD Lifguard.
Run the WD Lifeguard test on your WD HDD(s). Quick Test first, if it passes then run the Extended Test.
Data Lifeguard Diagnostic for Windows

What Anti-virus are you using?
Run a full scan.

Are all Windows updates installed?

Your crash:

Code:

STOP 0x0000001A: MEMORY_MANAGEMENT
Usual causes:  Device driver, memory, kernel
A PTE or the working set list is corrupt.
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
PROCESS_NAME:  chrome.exe
LAST_CONTROL_TRANSFER:  from fffff800032cf7e7 to fffff80003278c40
FAILURE_BUCKET_ID:  X64_0x1a_41284_VRF_nt!_??_::FNODOBFM::_string_+4ad3

This usually indicates hardware but can be caused by a driver.
Since it's blaming Chrome, you should un-install it for testing.
You can install it again later, when the cause is found.

From your App Events Log:

Code:

Event[10469]:
  Log Name: Application
  Source: Microsoft-Windows-Wininit
  Date: 2013-02-23T14:08:04.000
  Event ID: 1001
  Task: N/A
  Level: Information
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: JFB-PC
  Description: 


Checking file system on C:
The type of the file system is NTFS.


One of your disks needs to be checked for consistency. You
may cancel the disk check, but it is strongly recommended
that you continue.
Windows will now check the disk.                         

CHKDSK is verifying files (stage 1 of 3)...
  192256 file records processed.                                         

File verification completed.
  432 large file records processed.                                   

  0 bad file records processed.                                     

  2 EA records processed.                                           

  60 reparse records processed.                                      

CHKDSK is verifying indexes (stage 2 of 3)...
The index root $I30 is missing in file 0x7183.
Correcting error in index $I30 for file 29059.
  244412 index entries processed.                                        

Index verification completed.
CHKDSK is scanning unindexed files for reconnect to their original directory.
  28 unindexed files scanned.                                        

CHKDSK is recovering remaining unindexed files.
  28 unindexed files recovered.                                      

CHKDSK is verifying security descriptors (stage 3 of 3)...
  192256 file SDs/SIDs processed.                                        

Cleaning up 201 unused index entries from index $SII of file 0x9.
Cleaning up 201 unused index entries from index $SDH of file 0x9.
Cleaning up 201 unused security descriptors.
Security descriptor verification completed.
  26078 data files processed.                                           

CHKDSK is verifying Usn Journal...
  34645728 USN bytes processed.                                            

Usn Journal verification completed.
Correcting errors in the master file table's (MFT) BITMAP attribute.
Correcting errors in the Volume Bitmap.
Windows has made corrections to the file system.

 976759807 KB total disk space.
 101350668 KB in 96075 files.
     65228 KB in 26081 indexes.
         0 KB in bad sectors.
    323447 KB in use by the system.
     65536 KB occupied by the log file.
 875020464 KB available on disk.

      4096 bytes in each allocation unit.
 244189951 total allocation units on disk.
 218755116 allocation units available on disk.

Internal Info:
00 ef 02 00 35 dd 01 00 02 8a 03 00 00 00 00 00  ....5...........
50 01 00 00 3c 00 00 00 00 00 00 00 00 00 00 00  P...<...........
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................

Windows has finished checking your disk.
Please wait while your computer restarts.

This shows there were problems found on your hard drive, and they were fixed.
Run the Lifeguard test linked above.