BSOD at random times, no particular order

Alright, I've done a bugcheck analysis but don't see anything with the description of what you said. Just a bunch of txt after getting a detailed analysis.
Use !analyze -v to get detailed debugging information.

BugCheck 24, {1904fb, fffff88008f94c48, fffff88008f944a0, fffff80002ddde2e}

Probably caused by : ntkrnlmp.exe ( nt!FsRtlNotifyFilterReportChange+122 )

Followup: MachineOwner

EXCEPTION_RECORD: fffff88008f94c48 -- (.exr 0xfffff88008f94c48)
ExceptionAddress: fffff80002ddde2e (nt!FsRtlNotifyFilterReportChange+0x0000000000000122)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

CONTEXT: fffff88008f944a0 -- (.cxr 0xfffff88008f944a0;r)
rax=9cfff8a0028aa358 rbx=fffffa8003fc3060 rcx=0000000000000082
rdx=fffffa80030d76b0 rsi=fffff8a002df33e0 rdi=fffff8a002df3410
rip=fffff80002ddde2e rsp=fffff88008f94e80 rbp=0000000000000002
r8=fffff8a0038a56f0 r9=0000000000000000 r10=0000000000000060
r11=fffff88008f94fa8 r12=fffff88008f94f40 r13=fffff8a0038a56f0
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na po nc
cs=0010 ss=0000 ds=002b es=002b fs=0053 gs=002b efl=00010286
nt!FsRtlNotifyFilterReportChange+0x122:
fffff800`02ddde2e 66833800 cmp word ptr [rax],0 ds:002b:9cfff8a0`028aa358=????
Last set context:
rax=9cfff8a0028aa358 rbx=fffffa8003fc3060 rcx=0000000000000082
rdx=fffffa80030d76b0 rsi=fffff8a002df33e0 rdi=fffff8a002df3410
rip=fffff80002ddde2e rsp=fffff88008f94e80 rbp=0000000000000002
r8=fffff8a0038a56f0 r9=0000000000000000 r10=0000000000000060
r11=fffff88008f94fa8 r12=fffff88008f94f40 r13=fffff8a0038a56f0
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na po nc
cs=0010 ss=0000 ds=002b es=002b fs=0053 gs=002b efl=00010286
nt!FsRtlNotifyFilterReportChange+0x122:
fffff800`02ddde2e 66833800 cmp word ptr [rax],0 ds:002b:9cfff8a0`028aa358=????
Resetting default scope

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VERIFIER_ENABLED_VISTA_MINIDUMP

PROCESS_NAME: qw.exe

CURRENT_IRQL: 0

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

EXCEPTION_PARAMETER1: 0000000000000000

EXCEPTION_PARAMETER2: ffffffffffffffff

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002d00100
GetUlongFromAddress: unable to read from fffff80002d001c0
ffffffffffffffff

FOLLOWUP_IP:
nt!FsRtlNotifyFilterReportChange+122
fffff800`02ddde2e 66833800 cmp word ptr [rax],0

FAULTING_IP:
nt!FsRtlNotifyFilterReportChange+122
fffff800`02ddde2e 66833800 cmp word ptr [rax],0

BUGCHECK_STR: 0x24

ANALYSIS_VERSION: 6.3.9600.17336 (debuggers(dbg).150226-1500) amd64fre

LAST_CONTROL_TRANSFER: from fffff88001648a54 to fffff80002ddde2e

STACK_TEXT:
fffff880`08f94e80 fffff880`01648a54 : fffffa80`02ea6980 fffffa80`030d76b0 fffff8a0`038a56f0 01ceb348`37570060 : nt!FsRtlNotifyFilterReportChange+0x122
fffff880`08f94fb0 fffff880`016ce9bd : 00000000`00000000 fffff8a0`02c635c0 fffff8a0`02c636f0 fffff8a0`038a56f0 : Ntfs!NtfsReportDirNotify+0x104
fffff880`08f95070 fffff880`0163f639 : 00000000`00000098 fffff800`02dbf576 fffff880`08f955d0 00000000`00006000 : Ntfs!NtfsCommonCleanup+0xe9d
fffff880`08f95490 fffff800`02ad4878 : fffff880`08f955d0 fffff8a0`019db3a0 fffffa80`018fb550 fffff880`08f95650 : Ntfs!NtfsCommonCleanupCallout+0x19
fffff880`08f954c0 fffff880`0163f6b2 : fffff880`0163f620 00000002`0008002c 00000000`00000000 00000000`00000000 : nt!KeExpandKernelStackAndCalloutEx+0xd8
fffff880`08f955a0 fffff880`016dcba4 : fffff880`08f95670 fffff880`08f95670 fffff880`08f95670 00000000`00000000 : Ntfs!NtfsCommonCleanupOnNewStack+0x42
fffff880`08f95610 fffff800`02f71d26 : fffff880`08f95670 fffffa80`02c45460 fffffa80`02c45460 fffffa80`030d7030 : Ntfs!NtfsFsdCleanup+0x144
fffff880`08f95880 fffff880`01143bcf : fffffa80`02c45800 fffff880`08f95920 fffffa80`02c95350 fffffa80`02c54010 : nt!IovCallDriver+0x566
fffff880`08f958e0 fffff880`011426df : fffffa80`02ef69e0 fffffa80`02ef69e0 fffffa80`02d43000 fffffa80`02c45460 : fltmgr!FltpLegacyProcessingAfterPreCallbacksCompleted+0x24f
fffff880`08f95970 fffff800`02f71d26 : fffffa80`02c45460 00000000`00000002 fffffa80`02ef69e0 00000000`00000000 : fltmgr!FltpDispatch+0xcf
fffff880`08f959d0 fffff800`02dd196f : fffffa80`02c45460 fffffa80`03df8950 00000000`00000000 fffffa80`02548420 : nt!IovCallDriver+0x566
fffff880`08f95a30 fffff800`02dbf964 : 00000000`00000000 fffffa80`03df8950 fffff880`01160101 fffffa80`02530f01 : nt!IopCloseFile+0x11f
fffff880`08f95ac0 fffff800`02dbf721 : fffffa80`03df8950 fffffa80`00000001 fffff8a0`02f50500 00000000`00000002 : nt!ObpDecrementHandleCount+0xb4
fffff880`08f95b40 fffff800`02dbfce4 : 00000000`00000418 fffffa80`03df8950 fffff8a0`02f50500 00000000`00000418 : nt!ObpCloseHandleTableEntry+0xb1
fffff880`08f95bd0 fffff800`02ac7e53 : fffffa80`03fc3060 fffff880`08f95ca0 00000000`7efdb000 00000000`7efdb000 : nt!ObpCloseHandle+0x94
fffff880`08f95c20 00000000`76df13aa : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`001ae088 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x76df13aa


SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: nt!FsRtlNotifyFilterReportChange+122

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 521ea035

IMAGE_VERSION: 6.1.7601.18247

STACK_COMMAND: .cxr 0xfffff88008f944a0 ; kb

FAILURE_BUCKET_ID: X64_0x24_VRF_nt!FsRtlNotifyFilterReportChange+122

BUCKET_ID: X64_0x24_VRF_nt!FsRtlNotifyFilterReportChange+122

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:x64_0x24_vrf_nt!fsrtlnotifyfilterreportchange+122

FAILURE_ID_HASH: {13ccbb6f-9ab6-8211-c685-1556472c30e3}

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

Hmm, run SeaTools. SeaTools for DOS and Windows - How to Use

I'm getting a pass

Have you run all the tests?

yeah, just ran all of them again and got a pass on all

@Layback Bear That's the process running when the BSOD occured. The culprit is always in the IMAGE_NAME.

Anyways i hate to say this but wipe your drive and re-install Windows. This is probably the NTFS being corrupt as it is an 0x24(NTFS_FILE_SYSTEM) bugcheck.

EDIT: Before re-installing go into an elevated command prompt and type in chkdsk /f /r and see if that works.

Didn't end up doing anything for me, i'm just gonna format. Oh well, thanks for all the help

No problem! It's my duty to help!