BSOD playing RIFT/Youtube/Stream Watching

Vico696 · 04 Oct 2013

Ok recently i started have that BSOD issue too so i decided to take my pc to the local pc technician.After checking my pc for 8 days the guy told me he couldnt Trigger the BSOD after watching streams playing videos Benchmarks etc the only thing he didnt done is gaming.The only thing he informed me is that he thinks this comes from my GPU after checking prolly my Crash dump or something.Now from what i noticed my pc sometimes when i play RIFT it mini crashes like (example of word "bad" and i listen even the sound as "Bababad"
and after comes back againi dont know if this is from game lag or from the problem i just mention it.As far i remember the same sound was coming when i had also the blue screens like 1-2 seconds before they apear and today that i had also my last BSOD i had some minutes ago a similar crash but the BSOD happend when i was afk and the pc was playing only a Youtube video.I need your help guys cause its rly hard to affort money for now to take pc to a new tech shop or Change blindly my GPU like that.

here is the complete problem code of last BSOD and the colect data from the tool

Arc · 04 Oct 2013

Your crash dumps are not showing any finite probable cause. In such a situation, it is better to enable Driver Verifier to monitor the drivers.
Driver Verifier - Enable and Disable
Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.

Information

Why Driver Verifier:
It puts a stress on the drivers, ans so it makes the unstable drivers crash. Hopefully the driver that crashes is recorded in the memory dump.

How Can we know that DV is enabled:
It will make the system bit of slow, laggy.

Warning

Before enabling DV, make it sure that you have earlier System restore points made in your computer. You can check it easily by using CCleaner looking at Tools > System Restore.

If there is no points, make a System Restore Point manually before enabling DV.

Tip

If you fail to get on the Desktop because of DV, Boot into Advanced Boot Options > Safe mode. Disable DV there. Now boot normally again, and try following the instruction of enabling DV again.
If you cannot boot in Safe mode too, do a System Restore to a point you made earlier.

Let us know the results, with the subsequent crash dumps, if any. Post it following the Blue Screen of Death (BSOD) Posting Instructions.
______________________________________________________________________

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {fffff88002a61990, 2, 8, fffff88002a61990}

Probably caused by : tcpip.sys ( tcpip!IppLoopbackTransmit+11a )

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

1: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: fffff88002a61990, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000008, value 0 = read operation, 1 = write operation
Arg4: fffff88002a61990, address which referenced memory

Debugging Details:
------------------


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800032bf100
GetUlongFromAddress: unable to read from fffff800032bf1c0
 fffff88002a61990 Nonpaged pool

CURRENT_IRQL:  2

FAULTING_IP: 
+0
fffff880`02a61990 ??              ???

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0xD1

PROCESS_NAME:  SDFSSvc.exe

TRAP_FRAME:  fffff880083cd6a0 -- (.trap 0xfffff880083cd6a0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff88001b480c0 rbx=0000000000000000 rcx=fffffa80092fd900
rdx=fffffa800b1926c0 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88002a61990 rsp=fffff880083cd838 rbp=0000000000000000
 r8=0000000000000001  r9=0000000000000000 r10=0000000000000028
r11=fffff880083cd8f0 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na pe nc
fffff880`02a61990 ??              ???
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80003087129 to fffff80003087b80

FAILED_INSTRUCTION_ADDRESS: 
+0
fffff880`02a61990 ??              ???

STACK_TEXT:  
fffff880`083cd558 fffff800`03087129 : 00000000`0000000a fffff880`02a61990 00000000`00000002 00000000`00000008 : nt!KeBugCheckEx
fffff880`083cd560 fffff800`03085da0 : ffff0300`00000000 fffffa80`0b724060 00000000`00000000 00000000`00000001 : nt!KiBugCheckDispatch+0x69
fffff880`083cd6a0 fffff880`02a61990 : fffff880`01a3e2ba fffff880`01b6e906 00000000`00000001 fffff880`083cd860 : nt!KiPageFault+0x260
fffff880`083cd838 fffff880`01a3e2ba : fffff880`01b6e906 00000000`00000001 fffff880`083cd860 fffff880`083cd8f8 : 0xfffff880`02a61990
fffff880`083cd840 fffff800`03093878 : fffff880`01b6e9a0 fffff800`0339b006 00000000`00000000 00000000`00000004 : tcpip!IppLoopbackTransmit+0x11a
fffff880`083cd8f0 fffff880`01a3ebcf : fffff880`01a8e4b4 fffff800`0339b33b fffff880`083cdb02 00000000`00000000 : nt!KeExpandKernelStackAndCalloutEx+0xd8
fffff880`083cd9d0 fffff880`01a60357 : fffffa80`0bbb0450 00000000`00000004 fffff880`083cde01 00000000`00000000 : tcpip!IppLoopbackEnqueue+0x22f
fffff880`083cda80 fffff880`01a66a85 : fffffa80`092fe820 00000000`00000001 fffffa80`00000001 00000000`00000080 : tcpip!IpNlpFastSendDatagram+0xb77
fffff880`083cde30 fffff880`01a7bd74 : 00000000`00000000 fffffa80`0a7187f0 00000000`0032a64f 00000000`00000001 : tcpip!TcpTcbSend+0x495
fffff880`083ce0b0 fffff880`01a78e2e : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : tcpip!TcpDisconnectTcb+0x1c4
fffff880`083ce200 fffff800`03093878 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : tcpip!TcpTlConnectionDisconnectCalloutRoutine+0x1e
fffff880`083ce230 fffff880`01a795a0 : fffff880`01a78e10 fffff800`03378eba 00000000`00000000 00000000`00000001 : nt!KeExpandKernelStackAndCalloutEx+0xd8
fffff880`083ce310 fffff880`02ede819 : fffffa80`06aabf00 00000000`00000000 fffff880`083ce4a0 fffffa80`0b3ab6f0 : tcpip!TcpTlConnectionDisconnect+0x70
fffff880`083ce380 fffff880`02edeef6 : fffff880`083ceb60 00000000`00000000 00000000`00000000 00000000`00000000 : afd!AfdBeginDisconnect+0x119
fffff880`083ce440 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : afd!AfdPartialDisconnect+0x1a6


STACK_COMMAND:  kb

FOLLOWUP_IP: 
tcpip!IppLoopbackTransmit+11a
fffff880`01a3e2ba 85db            test    ebx,ebx

SYMBOL_STACK_INDEX:  4

SYMBOL_NAME:  tcpip!IppLoopbackTransmit+11a

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: tcpip

IMAGE_NAME:  tcpip.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  51d78b2c

FAILURE_BUCKET_ID:  X64_0xD1_CODE_AV_BAD_IP_tcpip!IppLoopbackTransmit+11a

BUCKET_ID:  X64_0xD1_CODE_AV_BAD_IP_tcpip!IppLoopbackTransmit+11a

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