.NET framework error, computer freezes then BsOD 0x000000F4

On startup, I get a .NET error (see photo). Immediately after the .NET error shows up, the computer freezes and produces a BSoD (see photo). I tried to download a dump file, but nothing shows up in the report, except for a report dated 18 months ago. In the BSoD screen, "the collecting data for crash dump" line doesn't load any data.

So now, after I do a hard power off and restart the computer, I get BSoD 0x0000007E. I can't get to the startup anymore.

I did a startup repair at one of the start ups, I did a chkdsk, but everything was good.

So, I'm stuck now on the startup repair window everytime.

Sorry, but i can't produce a dumpfile, as the computer doesn't produce one. And I can't get into the configurations since my computer freezes.

Update. I removed old .NET and installed a newer one. By installing a newer .NET and 3 startup repairs, I managed to finally get to the desktop.

Once I got to the desk top, I downloaded Debugging kit, installed it and found a Symantec file causing the problem. Removed Symantec, reinstalled and all is well. Then...I opened Quickbooks and BOOM!!!

BSOD. So, now the minidump isn't working again, so no minidump report. The BSOD code is 0xF4. The code adjacent the minidump is 0xc0000010

Any ideas?

I have 80% of available space. Yes, there is a mini dump file from this morning, but i can't open it with Windows Debugger (I set it up via SevenForums tutorial) WhoCrashed doesn't even see it.

And I did notice a lock symbol on the mini dump folder.

I moved it to a new folder on the desktop. I also did the "Take Ownership" tutorial on this forum so when i open it i have the option to take ownership. Not sure if it's correct. See screen shots.

Here's the mini dump file. I just did a chkdsk f r

3 sectors were damaged and repaired.