Windows 7 Random, stumped

[cowlud]

Link RemovedLink Removed

I'm lost keep getting random Bsods. I can go a whole day without getting them and then sometimes I get 5 or more.

Things I've tried:
Reinstalled windows (WIPED HD AND STARTED FROM SCRATCH)
Different wireless USB card (the usb card I used did the same thing tho)
Fully updated drivers and all things from motherboard support site, INCLUDING BIOS.
I should add that this seems to only happen when web surfing and other online activities like gaming.

My verdict:
The WUSB600N is not compatible with windows 7 or there are current windows security updates that are conflicting with its driver. I don't have any firewalls running, infact the only thing that is running is microsoft security essentials.
The USBport.sys bluescreen bothers me though so I figured I'd better seek out some extra help here.

 

[cowlud]

heres more info incase it may help find a solution.

I forgot to add that I'm using WUSB600N v2 which is on the approved for windows 7 compatability list.

Also forgot to say that I've checked my ram and video ram extensively with testing apps and even windows memory diagnostics. Yes, my computer is OC'd. Yes, these bluescreens still occur at stock settings. I've tested the OC without a connection to the internet and it works fine.

I'm hoping to figure this out cause I dont want to spend more $ trying another wireless usb nic, especially since the one I'm using is listed for compatability already.

 

[kaos]

MINI DUMPS

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000007E, {ffffffffc0000005, fffff80002ca9c15, fffff88002fcb578, fffff88002fcade0}
Probably caused by : discache.sys ( discache!DispModifyObjectLru+144 )
Followup: MachineOwner
---------
2: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003.  This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG.  This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG.  This will let us see why this breakpoint is
happening.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff80002ca9c15, The address that the exception occurred at
Arg3: fffff88002fcb578, Exception Record Address
Arg4: fffff88002fcade0, Context Record Address
Debugging Details:
------------------

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
FAULTING_IP: 
nt!MiRemoveNode+205
fffff800`02ca9c15 49395808        cmp     qword ptr [r8+8],rbx
EXCEPTION_RECORD:  fffff88002fcb578 -- (.exr 0xfffff88002fcb578)
ExceptionAddress: fffff80002ca9c15 (nt!MiRemoveNode+0x0000000000000205)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff
CONTEXT:  fffff88002fcade0 -- (.cxr 0xfffff88002fcade0)
rax=fffff8a004c69258 rbx=fffff8a00bd51770 rcx=fffff8a004c69258
rdx=fffff80002e465ff rsi=fffff8a00bd51770 rdi=fffff8a00bd51770
rip=fffff80002ca9c15 rsp=fffff88002fcb7b0 rbp=fffff80002e465c0
 r8=005c00296b793030  r9=0000000000003be0 r10=0000000000003be0
r11=fffff88002fcb878 r12=0000000000000001 r13=fffffa80039d3040
r14=00000000ffffffff r15=fffff8a000001990
iopl=0         nv up ei pl nz na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010206
nt!MiRemoveNode+0x205:
fffff800`02ca9c15 49395808        cmp     qword ptr [r8+8],rbx ds:002b:005c0029`6b793038=????????????????
Resetting default scope
CUSTOMER_CRASH_COUNT:  1
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
CURRENT_IRQL:  0
ERROR_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 fffff80002eb00e0
 ffffffffffffffff 
FOLLOWUP_IP: 
discache!DispModifyObjectLru+144
fffff880`03de6308 ba444c7275      mov     edx,75724C44h
BUGCHECK_STR:  0x7E
LAST_CONTROL_TRANSFER:  from fffff80002f0aa7b to fffff80002ca9c15
STACK_TEXT:  
fffff880`02fcb7b0 fffff800`02f0aa7b : fffff8a0`0bd51790 fffffa80`039e4b60 00000000`00000000 fffff8a0`0bd51770 : nt!MiRemoveNode+0x205
fffff880`02fcb7e0 fffff800`02c7d8b4 : 00000000`00000000 fffffa80`039d3040 fffffa80`039eb660 00000000`00000000 : nt! ?? ::NNGAKEGL::`string'+0x324ad
fffff880`02fcb820 fffff800`02f8d264 : fffffa80`039d3040 00000000`00000000 fffffa80`039e4b60 00000000`00000000 : nt!ObfDereferenceObject+0xd4
fffff880`02fcb880 fffff800`02f8d164 : 00000000`00003be0 fffffa80`039d3040 fffff8a0`00001990 00000000`00003be0 : nt!ObpCloseHandleTableEntry+0xc4
fffff880`02fcb910 fffff800`02c77953 : fffffa80`039e4b60 fffff880`02fcb9e0 fffff8a0`0be60180 000f003f`00000000 : nt!ObpCloseHandle+0x94
fffff880`02fcb960 fffff800`02c73ef0 : fffff880`03de6308 fffff880`03deb2c0 00000000`0016d907 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
fffff880`02fcbaf8 fffff880`03de6308 : fffff880`03deb2c0 00000000`0016d907 00000000`00000000 00000000`0016d907 : nt!KiServiceLinkage
fffff880`02fcbb00 fffff880`03de6663 : ffffffff`ffffffff ffffffff`ffffffff fffff800`02e1d500 00000000`00000000 : discache!DispModifyObjectLru+0x144
fffff880`02fcbc20 fffff880`03de66c7 : fffff880`03de66bc fffff800`02e1d5f8 fffffa80`039e4b60 00000000`00000000 : discache!DispFlushLru+0x19b
fffff880`02fcbc80 fffff800`02c85961 : fffff800`02e1d500 fffff800`02f73820 fffffa80`039e4b60 fffff800`02e1d5f8 : discache!DispLruWorkerRoutine+0xb
fffff880`02fcbcb0 fffff800`02f1bbc6 : 00000000`00000000 fffffa80`039e4b60 00000000`00000080 fffffa80`039d3040 : nt!ExpWorkerThread+0x111
fffff880`02fcbd40 fffff800`02c56bc6 : fffff880`02d63180 fffffa80`039e4b60 fffff880`02d6dfc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`02fcbd80 00000000`00000000 : fffff880`02fcc000 fffff880`02fc6000 fffff880`02fcb110 00000000`00000000 : nt!KiStartSystemThread+0x16

SYMBOL_STACK_INDEX:  7
SYMBOL_NAME:  discache!DispModifyObjectLru+144
FOLLOWUP_NAME:  MachineOwner
MODULE_NAME: discache
IMAGE_NAME:  discache.sys
DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc52e
STACK_COMMAND:  .cxr 0xfffff88002fcade0 ; kb
FAILURE_BUCKET_ID:  X64_0x7E_discache!DispModifyObjectLru+144
BUCKET_ID:  X64_0x7E_discache!DispModifyObjectLru+144
Followup: MachineOwner
---------

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000007E, {ffffffffc0000005, fffff80002ca9c15, fffff88002fcb578, fffff88002fcade0}
Probably caused by : discache.sys ( discache!DispModifyObjectLru+144 )
Followup: MachineOwner
---------
2: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003.  This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG.  This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG.  This will let us see why this breakpoint is
happening.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff80002ca9c15, The address that the exception occurred at
Arg3: fffff88002fcb578, Exception Record Address
Arg4: fffff88002fcade0, Context Record Address
Debugging Details:
------------------

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
FAULTING_IP: 
nt!MiRemoveNode+205
fffff800`02ca9c15 49395808        cmp     qword ptr [r8+8],rbx
EXCEPTION_RECORD:  fffff88002fcb578 -- (.exr 0xfffff88002fcb578)
ExceptionAddress: fffff80002ca9c15 (nt!MiRemoveNode+0x0000000000000205)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff
CONTEXT:  fffff88002fcade0 -- (.cxr 0xfffff88002fcade0)
rax=fffff8a004c69258 rbx=fffff8a00bd51770 rcx=fffff8a004c69258
rdx=fffff80002e465ff rsi=fffff8a00bd51770 rdi=fffff8a00bd51770
rip=fffff80002ca9c15 rsp=fffff88002fcb7b0 rbp=fffff80002e465c0
 r8=005c00296b793030  r9=0000000000003be0 r10=0000000000003be0
r11=fffff88002fcb878 r12=0000000000000001 r13=fffffa80039d3040
r14=00000000ffffffff r15=fffff8a000001990
iopl=0         nv up ei pl nz na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010206
nt!MiRemoveNode+0x205:
fffff800`02ca9c15 49395808        cmp     qword ptr [r8+8],rbx ds:002b:005c0029`6b793038=????????????????
Resetting default scope
CUSTOMER_CRASH_COUNT:  1
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
CURRENT_IRQL:  0
ERROR_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 fffff80002eb00e0
 ffffffffffffffff 
FOLLOWUP_IP: 
discache!DispModifyObjectLru+144
fffff880`03de6308 ba444c7275      mov     edx,75724C44h
BUGCHECK_STR:  0x7E
LAST_CONTROL_TRANSFER:  from fffff80002f0aa7b to fffff80002ca9c15
STACK_TEXT:  
fffff880`02fcb7b0 fffff800`02f0aa7b : fffff8a0`0bd51790 fffffa80`039e4b60 00000000`00000000 fffff8a0`0bd51770 : nt!MiRemoveNode+0x205
fffff880`02fcb7e0 fffff800`02c7d8b4 : 00000000`00000000 fffffa80`039d3040 fffffa80`039eb660 00000000`00000000 : nt! ?? ::NNGAKEGL::`string'+0x324ad
fffff880`02fcb820 fffff800`02f8d264 : fffffa80`039d3040 00000000`00000000 fffffa80`039e4b60 00000000`00000000 : nt!ObfDereferenceObject+0xd4
fffff880`02fcb880 fffff800`02f8d164 : 00000000`00003be0 fffffa80`039d3040 fffff8a0`00001990 00000000`00003be0 : nt!ObpCloseHandleTableEntry+0xc4
fffff880`02fcb910 fffff800`02c77953 : fffffa80`039e4b60 fffff880`02fcb9e0 fffff8a0`0be60180 000f003f`00000000 : nt!ObpCloseHandle+0x94
fffff880`02fcb960 fffff800`02c73ef0 : fffff880`03de6308 fffff880`03deb2c0 00000000`0016d907 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
fffff880`02fcbaf8 fffff880`03de6308 : fffff880`03deb2c0 00000000`0016d907 00000000`00000000 00000000`0016d907 : nt!KiServiceLinkage
fffff880`02fcbb00 fffff880`03de6663 : ffffffff`ffffffff ffffffff`ffffffff fffff800`02e1d500 00000000`00000000 : discache!DispModifyObjectLru+0x144
fffff880`02fcbc20 fffff880`03de66c7 : fffff880`03de66bc fffff800`02e1d5f8 fffffa80`039e4b60 00000000`00000000 : discache!DispFlushLru+0x19b
fffff880`02fcbc80 fffff800`02c85961 : fffff800`02e1d500 fffff800`02f73820 fffffa80`039e4b60 fffff800`02e1d5f8 : discache!DispLruWorkerRoutine+0xb
fffff880`02fcbcb0 fffff800`02f1bbc6 : 00000000`00000000 fffffa80`039e4b60 00000000`00000080 fffffa80`039d3040 : nt!ExpWorkerThread+0x111
fffff880`02fcbd40 fffff800`02c56bc6 : fffff880`02d63180 fffffa80`039e4b60 fffff880`02d6dfc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`02fcbd80 00000000`00000000 : fffff880`02fcc000 fffff880`02fc6000 fffff880`02fcb110 00000000`00000000 : nt!KiStartSystemThread+0x16

SYMBOL_STACK_INDEX:  7
SYMBOL_NAME:  discache!DispModifyObjectLru+144
FOLLOWUP_NAME:  MachineOwner
MODULE_NAME: discache
IMAGE_NAME:  discache.sys
DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc52e
STACK_COMMAND:  .cxr 0xfffff88002fcade0 ; kb
FAILURE_BUCKET_ID:  X64_0x7E_discache!DispModifyObjectLru+144
BUCKET_ID:  X64_0x7E_discache!DispModifyObjectLru+144
Followup: MachineOwner
---------

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 3B, {c0000005, fffff80002c8d486, fffff88009837d20, 0}
Probably caused by : ntkrnlmp.exe ( nt!RtlpCoalesceFreeBlocks+ae )
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff80002c8d486, Address of the instruction which caused the bugcheck
Arg3: fffff88009837d20, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.
Debugging Details:
------------------

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
FAULTING_IP: 
nt!RtlpCoalesceFreeBlocks+ae
fffff800`02c8d486 498b06          mov     rax,qword ptr [r14]
CONTEXT:  fffff88009837d20 -- (.cxr 0xfffff88009837d20)
rax=0000000000000000 rbx=fffff900c0903210 rcx=0000000000000000
rdx=fffff900c09031f0 rsi=fffff900c0800000 rdi=fffff900c09031f0
rip=fffff80002c8d486 rsp=fffff880098386f0 rbp=fffff900c09031f0
 r8=fffff900c0903220  r9=0000000000000020 r10=00000000000003a4
r11=fffff900c076c770 r12=fffff900c040a500 r13=00000000000206cf
r14=0000000000000000 r15=fffff880098387d0
iopl=0         nv up ei pl zr na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010246
nt!RtlpCoalesceFreeBlocks+0xae:
fffff800`02c8d486 498b06          mov     rax,qword ptr [r14] ds:002b:00000000`00000000=????????????????
Resetting default scope
CUSTOMER_CRASH_COUNT:  1
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x3B
PROCESS_NAME:  taskhost.exe
CURRENT_IRQL:  0
LAST_CONTROL_TRANSFER:  from 0000000000000000 to fffff80002c8d486
STACK_TEXT:  
fffff880`098386f0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!RtlpCoalesceFreeBlocks+0xae

FOLLOWUP_IP: 
nt!RtlpCoalesceFreeBlocks+ae
fffff800`02c8d486 498b06          mov     rax,qword ptr [r14]
SYMBOL_STACK_INDEX:  0
SYMBOL_NAME:  nt!RtlpCoalesceFreeBlocks+ae
FOLLOWUP_NAME:  MachineOwner
MODULE_NAME: nt
IMAGE_NAME:  ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP:  4d9fdd34
STACK_COMMAND:  .cxr 0xfffff88009837d20 ; kb
FAILURE_BUCKET_ID:  X64_0x3B_nt!RtlpCoalesceFreeBlocks+ae
BUCKET_ID:  X64_0x3B_nt!RtlpCoalesceFreeBlocks+ae
Followup: MachineOwner
---------

2: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
NTFS_FILE_SYSTEM (24)
    If you see NtfsExceptionFilter on the stack then the 2nd and 3rd
    parameters are the exception record and context record. Do a .cxr
    on the 3rd parameter and then kb to obtain a more informative stack
    trace.
Arguments:
Arg1: 00000000001904fb
Arg2: fffff88002f7e688
Arg3: fffff88002f7def0
Arg4: fffff80002cf56ab
Debugging Details:
------------------

EXCEPTION_RECORD:  fffff88002f7e688 -- (.exr 0xfffff88002f7e688)
ExceptionAddress: fffff80002cf56ab (nt!RebalanceNode+0x000000000000001b)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: 0000000000000018
Attempt to read from address 0000000000000018
CONTEXT:  fffff88002f7def0 -- (.cxr 0xfffff88002f7def0)
rax=fffff8a00cea66ff rbx=fffff8a00b3c4570 rcx=fffff8a00cea66c0
rdx=fffff8a00b3c4501 rsi=fffff8a00cea66c0 rdi=fffff8a00b3c4570
rip=fffff80002cf56ab rsp=fffff88002f7e8c0 rbp=fffffa80049ae648
 r8=0000000000003ffc  r9=0000ffffffffffff r10=0000000000000000
r11=fffff8a00cea66c0 r12=0000000000000001 r13=fffffa80049ae180
r14=fffff88002f7e9ff r15=0000000000000000
iopl=0         nv up ei ng nz na pe nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010282
nt!RebalanceNode+0x1b:
fffff800`02cf56ab 45384a18        cmp     byte ptr [r10+18h],r9b ds:002b:00000000`00000018=??
Resetting default scope
CUSTOMER_CRASH_COUNT:  1
PROCESS_NAME:  System
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:  0000000000000018
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002f070e0
 0000000000000018 
FOLLOWUP_IP: 
Ntfs!NtfsDeleteFcb+179
fffff880`010e3079 4c8b1b          mov     r11,qword ptr [rbx]
FAULTING_IP: 
nt!RebalanceNode+1b
fffff800`02cf56ab 45384a18        cmp     byte ptr [r10+18h],r9b
BUGCHECK_STR:  0x24
DEFAULT_BUCKET_ID:  NULL_CLASS_PTR_DEREFERENCE
LAST_CONTROL_TRANSFER:  from fffff80002ca090e to fffff80002cf56ab
STACK_TEXT:  
fffff880`02f7e8c0 fffff800`02ca090e : fffff8a0`0b3c4570 fffff800`02cf454d 00000000`00000006 fffff8a0`0cb536f0 : nt!RebalanceNode+0x1b
fffff880`02f7e8f0 fffff800`02ca0989 : fffffa80`049ae648 fffff800`02e745a0 fffffa80`04749950 fffffa80`049ae180 : nt!DeleteNodeFromTree+0x15e
fffff880`02f7e930 fffff880`010e3079 : fffff880`02f7e9f0 fffff800`02e745a0 fffff8a0`0b3c4570 fffffa80`0583cad0 : nt!RtlDeleteElementGenericTableAvl+0x39
fffff880`02f7e960 fffff880`01058cfa : fffff800`02e745a0 fffff880`02f7eb01 fffff880`02f7e9e1 fffff8a0`0bd57b40 : Ntfs!NtfsDeleteFcb+0x179
fffff880`02f7e9c0 fffff880`010e03dc : fffffa80`0583cad0 fffffa80`049ae180 fffff8a0`0bd57b40 fffff8a0`0bd57ed8 : Ntfs!NtfsTeardownFromLcb+0x1ea
fffff880`02f7ea50 fffff880`01061602 : fffffa80`0583cad0 fffffa80`0583cad0 fffff8a0`0bd57b40 00000000`00000000 : Ntfs!NtfsTeardownStructures+0xcc
fffff880`02f7ead0 fffff880`010f78f3 : fffffa80`0583cad0 fffff800`02e745a0 fffff8a0`0bd57b40 00000000`00000009 : Ntfs!NtfsDecrementCloseCounts+0xa2
fffff880`02f7eb10 fffff880`010d1c9f : fffffa80`0583cad0 fffff8a0`0bd57c70 fffff8a0`0bd57b40 fffffa80`049ae180 : Ntfs!NtfsCommonClose+0x353
fffff880`02f7ebe0 fffff800`02cdc961 : 00000000`00000000 fffff880`010d1b00 fffffa80`039e8b01 fffffa80`00000002 : Ntfs!NtfsFspClose+0x15f
fffff880`02f7ecb0 fffff800`02f72bc6 : 000004f4`00000000 fffffa80`039e8b60 00000000`00000080 fffffa80`039d3040 : nt!ExpWorkerThread+0x111
fffff880`02f7ed40 fffff800`02cadbc6 : fffff880`02d63180 fffffa80`039e8b60 fffff880`02d6dfc0 000004f4`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`02f7ed80 00000000`00000000 : fffff880`02f7f000 fffff880`02f79000 fffff880`02f7e9f0 00000000`00000000 : nt!KiStartSystemThread+0x16

SYMBOL_STACK_INDEX:  3
SYMBOL_NAME:  Ntfs!NtfsDeleteFcb+179
FOLLOWUP_NAME:  MachineOwner
MODULE_NAME: Ntfs
IMAGE_NAME:  Ntfs.sys
DEBUG_FLR_IMAGE_TIMESTAMP:  4d79996d
STACK_COMMAND:  .cxr 0xfffff88002f7def0 ; kb
FAILURE_BUCKET_ID:  X64_0x24_Ntfs!NtfsDeleteFcb+179
BUCKET_ID:  X64_0x24_Ntfs!NtfsDeleteFcb+179
Followup: MachineOwner
---------

an idea for u for some bugcheck codes

how did u test your hardwre>

 

[cowlud]

I tested it by encoding a video file for an hour since encoding is the most processor intensive task I do on this computer. Never got a bluescreen.

I just tried prime95 and ran into a bluescreen after about 5 minutes.

I'm going to run the computer at factory specs again. It's strange that the bluescreen only happen when using the internet though. If I get another bluescreen on factory specs, I'll upload it for a bugcheck.

 

[kemical]

I'd also try running this app: Memtest86+ - Advanced Memory Diagnostic Tool

Check only one stick at a time so if one errors out you know which one it is.. Windows memory diagnostic just isn't good enough.

 

[cowlud]

All the bluescreens have stopped except for one. I get a page fault bsod very rarely so I'm gonna just guess that I have a bad ram stick somewhere. I tried both memtest and windows memory diagnostic but i didnt test them individually last time. Going to try that now. OC is fixed atleast, ran prime95 stable for an hour.

Still not sure why I only had problems when connected to the internet but atleast its for the most part fixed. Just need to find which ram or ram slot on the mobo might be failing/faulty.