BSOD 0x109 because of clfs.sys

I've attached my minidump here, but the general idea is that my computer has been blue screen free for a while now, but all of a sudden this one driver has started causing blue screen. any help would be appreciated.

Hello ComicCajun,
Can you run a file check, (tutorial link below).

http://www.vistax64.com/tutorials/66978-system-files-sfc-command.html

If that shows that no repairs were made, then you need to start hardware diagnostics, i would remove all but one stick of ram and try it, if that is OK, then remove that stick and try another one, and so on.
Also, you may want to eliminate the HDD, this page should help. (courtesy of usasma)

http://www.carrona.org/hddiag.html

The Minidump log shows a Bugcheck string 0x109,

CRITICAL_STRUCTURE_CORRUPTION (109)
This bugcheck is generated when the kernel detects that critical kernel code or
data have been corrupted. There are generally three causes for a corruption:
1) A driver has inadvertently or deliberately modified critical kernel code
or data. SeePatching Policy for x64-Based Systems: Changes in policy that are related to patching the kernel for the x64-based versions of Microsoft Windows Server 2003 and Microsoft Windows XP Professional x64 Edition operating systems
2) A developer attempted to set a normal kernel breakpoint using a kernel
debugger that was not attached when the system was booted. Normal breakpoints,
"bp", can only be set if the debugger is attached at boot time. Hardware
breakpoints, "ba", can be set at any time.
3) A hardware corruption occurred, e.g. failing RAM holding kernel code or data.

I can see that all your drivers are up to date, so, if the file check is clear, i think we can assume that its a hardware issue.
All we have to do is to narrow it down, easier said than done though.
Hope this helps, good luck and post your results.

There is also a hotfix for that here Error message when you start a Windows Vista-based computer: "STOP: 0x00000050 PAGE_FAULT_IN_NONPAGED_AREA"

Ken J+

I just did the ram test. Keep in mind that last time I did this dell had to send me a new mobo because we found out that one of the ram slots was defunct. Well, this time there were 3 ram slots that gave me that ever so annoying beep. I'll be calling Dell soon to get a new one, but is this a common problem with the i7 920 mother board? And is there anything I can do right now?
Also out of curiosity, I leave my computer on all night and I was wondering if this is possibly causing my system to overheat and damaging my ram slots OR is this a newbie assumption and the problem is entirely from the mother board itself?

Leaving the PC on all the time does not harm it at all, the PC's in the place i work have not been turned off for, well, it must be years.
What beep did you get off the ram slots, was this on boot up or when you took out the memory sticks, the PC was switched off when you removed the ram, please tell me it was, lol.
As for the MB, I'm not sure if you have just been incredibly unlucky or there is an inherent fault with that series MB, early days really.

Okay...just an update. The dell technician just left, and once he did, I decided to quickly test out each slot yet again to make sure that the ram slots are not broken again. I again got the beeps on the black labeled ram slots and no beeps on the white ones. However, all six gigs are appearing on the F2 start up and on the control panel. I am so confused now because I thought the beeping was caused by an inability to detect the ram but is perhaps that the blacks wont work without being paired with a white?

I would look in the MB manual, just to see if it mentions anything in there.