Windows 7 Forums
Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: BSOD caused by tcpip.sys while gaming + streaming video


10 Jan 2012   #1

Windows 7 64-bit
 
 
BSOD while gaming + streaming video

The crash only seems to occur if I attempt to stream video and play a game simultaneously. Curiously, the crash is a bluescreen in name only, as visually it's actually a black screen followed by loss of signal to the monitor. Minidump suggests tcpip.sys is the cause.

Windows 7 64-bit OEM
Asus P8Z68-V LE
Intel Core i5 2500k 3.3ghz
8gb RAM
500gb Seagate (Windows install drive) + 2tb Western Digital (for extra storage)
AMD Sapphire Radeon HD6850

All parts are less than 1 year old, Windows 7 installed fresh 26 December with many documents restored from previous backup.

Attachment 192437
Attachment 192438

Despite perfmon.exe's insistence to the contrary, I'm running Bitdefender 2012 for anti-virus services.

My System SpecsSystem Spec
.

10 Jan 2012   #2

Windows 7 Home Premium 64 Bit
 
 

Code:
  1. Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\EffinCraig\Windows_NT6_BSOD_jcgriff2\011012-16442-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*c:\users\mike\documents\symbols*http://msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Personal Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506 Machine Name: Kernel base = 0xfffff800`02e62000 PsLoadedModuleList = 0xfffff800`030a7670 Debug session time: Tue Jan 10 06:56:20.599 2012 (UTC - 7:00) System Uptime: 0 days 2:17:08.003 Loading Kernel Symbols ............................................................... ................................................................ .......................... Loading User Symbols Loading unloaded module list ...... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck A, {ffffffffffffffff, 2, 0, fffff80002ee2bb6} Unable to load image \SystemRoot\system32\DRIVERS\atikmdag.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for atikmdag.sys *** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys Probably caused by : atikmdag.sys ( atikmdag+4da57 ) Followup: MachineOwner --------- 3: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* IRQL_NOT_LESS_OR_EQUAL (a) 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 a kernel debugger is available get the stack backtrace. Arguments: Arg1: ffffffffffffffff, memory referenced Arg2: 0000000000000002, IRQL Arg3: 0000000000000000, bitfield : bit 0 : value 0 = read operation, 1 = write operation bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status) Arg4: fffff80002ee2bb6, address which referenced memory Debugging Details: ------------------ READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80003111100 ffffffffffffffff CURRENT_IRQL: 2 FAULTING_IP: nt!KeSetEvent+16 fffff800`02ee2bb6 f6037f test byte ptr [rbx],7Fh CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0xA PROCESS_NAME: System TRAP_FRAME: fffff880009b0950 -- (.trap 0xfffff880009b0950) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=fffffa8007f20000 rbx=0000000000000000 rcx=0000000000000001 rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000 rip=fffff80002ee2bb6 rsp=fffff880009b0ae0 rbp=0000000000000004 r8=0000000000000000 r9=fffff880009b0c90 r10=fffffa8009ef4ef0 r11=fffff880009b0cf8 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei ng nz na pe nc nt!KeSetEvent+0x16: fffff800`02ee2bb6 f6037f test byte ptr [rbx],7Fh ds:0010:00000000`00000000=?? Resetting default scope LAST_CONTROL_TRANSFER: from fffff80002ede1e9 to fffff80002edec40 STACK_TEXT: fffff880`009b0808 fffff800`02ede1e9 : 00000000`0000000a ffffffff`ffffffff 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx fffff880`009b0810 fffff800`02edce60 : fffffa80`094d6df0 fffff880`00eff30f fffffa80`07321c01 ffffffff`ffffffff : nt!KiBugCheckDispatch+0x69 fffff880`009b0950 fffff800`02ee2bb6 : 00000000`000445a2 00000000`00000022 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x260 fffff880`009b0ae0 fffff880`04ad6a57 : 00000000`00000000 fffff880`00000000 fffffa80`09559400 fffffa80`09b5d9f0 : nt!KeSetEvent+0x16 fffff880`009b0b50 00000000`00000000 : fffff880`00000000 fffffa80`09559400 fffffa80`09b5d9f0 00000000`00000000 : atikmdag+0x4da57 STACK_COMMAND: kb FOLLOWUP_IP: atikmdag+4da57 fffff880`04ad6a57 ?? ??? SYMBOL_STACK_INDEX: 4 SYMBOL_NAME: atikmdag+4da57 FOLLOWUP_NAME: MachineOwner MODULE_NAME: atikmdag IMAGE_NAME: atikmdag.sys DEBUG_FLR_IMAGE_TIMESTAMP: 4ebb3c7e FAILURE_BUCKET_ID: X64_0xA_atikmdag+4da57 BUCKET_ID: X64_0xA_atikmdag+4da57 Followup: MachineOwner ---------
  2. Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\EffinCraig\Windows_NT6_BSOD_jcgriff2\011012-26286-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*c:\users\mike\documents\symbols*http://msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Personal Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506 Machine Name: Kernel base = 0xfffff800`02e1f000 PsLoadedModuleList = 0xfffff800`03064670 Debug session time: Tue Jan 10 07:48:27.085 2012 (UTC - 7:00) System Uptime: 0 days 0:29:53.100 Loading Kernel Symbols ............................................................... ................................................................ .......................... Loading User Symbols Loading unloaded module list ...... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck A, {ffffffffffffffff, 2, 0, fffff80002e9fbb6} Unable to load image \SystemRoot\system32\DRIVERS\atikmdag.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for atikmdag.sys *** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys Probably caused by : atikmdag.sys ( atikmdag+4da57 ) Followup: MachineOwner --------- 3: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* IRQL_NOT_LESS_OR_EQUAL (a) 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 a kernel debugger is available get the stack backtrace. Arguments: Arg1: ffffffffffffffff, memory referenced Arg2: 0000000000000002, IRQL Arg3: 0000000000000000, bitfield : bit 0 : value 0 = read operation, 1 = write operation bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status) Arg4: fffff80002e9fbb6, address which referenced memory Debugging Details: ------------------ READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800030ce100 ffffffffffffffff CURRENT_IRQL: 2 FAULTING_IP: nt!KeSetEvent+16 fffff800`02e9fbb6 f6037f test byte ptr [rbx],7Fh CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0xA PROCESS_NAME: System TRAP_FRAME: fffff880009b0950 -- (.trap 0xfffff880009b0950) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=fffffa8007e9b000 rbx=0000000000000000 rcx=0000000000000001 rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000 rip=fffff80002e9fbb6 rsp=fffff880009b0ae0 rbp=0000000000000004 r8=0000000000000000 r9=fffff880009b0c90 r10=fffffa800a103ef0 r11=fffff880009b0cf8 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei ng nz na pe nc nt!KeSetEvent+0x16: fffff800`02e9fbb6 f6037f test byte ptr [rbx],7Fh ds:e180:00000000`00000000=?? Resetting default scope LAST_CONTROL_TRANSFER: from fffff80002e9b1e9 to fffff80002e9bc40 STACK_TEXT: fffff880`009b0808 fffff800`02e9b1e9 : 00000000`0000000a ffffffff`ffffffff 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx fffff880`009b0810 fffff800`02e99e60 : fffffa80`0948cdf0 fffff880`00e9e30f 00000000`00000032 ffffffff`ffffffff : nt!KiBugCheckDispatch+0x69 fffff880`009b0950 fffff800`02e9fbb6 : 00000000`0000019c 00000000`00000022 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x260 fffff880`009b0ae0 fffff880`04aeea57 : 00000000`00000000 fffff880`00000000 fffffa80`09421000 00000000`00000000 : nt!KeSetEvent+0x16 fffff880`009b0b50 00000000`00000000 : fffff880`00000000 fffffa80`09421000 00000000`00000000 00000000`00000000 : atikmdag+0x4da57 STACK_COMMAND: kb FOLLOWUP_IP: atikmdag+4da57 fffff880`04aeea57 ?? ??? SYMBOL_STACK_INDEX: 4 SYMBOL_NAME: atikmdag+4da57 FOLLOWUP_NAME: MachineOwner MODULE_NAME: atikmdag IMAGE_NAME: atikmdag.sys DEBUG_FLR_IMAGE_TIMESTAMP: 4ebb3c7e FAILURE_BUCKET_ID: X64_0xA_atikmdag+4da57 BUCKET_ID: X64_0xA_atikmdag+4da57 Followup: MachineOwner ---------

First, make sure Catalyst Control Center/Vision Engine Control Center is not overclocking your display card. If it is, turn off overclocking.

If the above does not stop your blue screen crashes, uninstall your display card and re-install using the following steps.

1. Download and install Driver Sweeper
2. Download the latest driver for your display card
3. Click Start Menu
4. Right Click My Computer
5. Click Manage
6. Click Device Manager from the list on the left
7. Click the + next to Display adapter
8. Right click your display/graphics card device
9. Click Uninstall
10. Check the box to Delete driver software for the device
11. Click OK
12. Restart your computer in safe mode
13. Run Driver Sweeper, select display card manufacturer's drivers, analyze, clean
14. Restart your computer
15. Install the latest drivers
My System SpecsSystem Spec
10 Jan 2012   #3

Windows 7 64-bit
 
 

Hi there, thanks for the quick reply. I tried the steps you listed and it doesn't seem to have helped. I created a fresh BSOD dump in case anything changed:

Attachment 192477
Attachment 192478

The performance monitor found some errors with the HD audio device this time around, which seems odd since the audio service seems to be running normally.
My System SpecsSystem Spec
.


10 Jan 2012   #4

Windows 7 Home Premium 64 Bit
 
 

Code:
  1. Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\EffinCraig\Windows_NT6_BSOD_jcgriff2\011012-26707-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*c:\users\mike\documents\symbols*http://msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Personal Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506 Machine Name: Kernel base = 0xfffff800`02e06000 PsLoadedModuleList = 0xfffff800`0304b670 Debug session time: Tue Jan 10 12:03:53.096 2012 (UTC - 7:00) System Uptime: 0 days 4:13:17.501 Loading Kernel Symbols ............................................................... ................................................................ .......................... Loading User Symbols Loading unloaded module list ........ ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck A, {ffffffffffffffff, 2, 0, fffff80002e86bb6} Unable to load image \SystemRoot\system32\DRIVERS\atikmdag.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for atikmdag.sys *** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys Probably caused by : atikmdag.sys ( atikmdag+4da57 ) Followup: MachineOwner --------- 3: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* IRQL_NOT_LESS_OR_EQUAL (a) 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 a kernel debugger is available get the stack backtrace. Arguments: Arg1: ffffffffffffffff, memory referenced Arg2: 0000000000000002, IRQL Arg3: 0000000000000000, bitfield : bit 0 : value 0 = read operation, 1 = write operation bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status) Arg4: fffff80002e86bb6, address which referenced memory Debugging Details: ------------------ READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800030b5100 ffffffffffffffff CURRENT_IRQL: 2 FAULTING_IP: nt!KeSetEvent+16 fffff800`02e86bb6 f6037f test byte ptr [rbx],7Fh CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0xA PROCESS_NAME: System TRAP_FRAME: fffff880009b0950 -- (.trap 0xfffff880009b0950) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=fffffa8007e9e000 rbx=0000000000000000 rcx=0000000000000001 rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000 rip=fffff80002e86bb6 rsp=fffff880009b0ae0 rbp=0000000000000004 r8=0000000000000000 r9=fffff880009b0c90 r10=fffffa800a12bef0 r11=fffff880009b0cf8 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei ng nz na pe nc nt!KeSetEvent+0x16: fffff800`02e86bb6 f6037f test byte ptr [rbx],7Fh ds:4930:00000000`00000000=?? Resetting default scope LAST_CONTROL_TRANSFER: from fffff80002e821e9 to fffff80002e82c40 STACK_TEXT: fffff880`009b0808 fffff800`02e821e9 : 00000000`0000000a ffffffff`ffffffff 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx fffff880`009b0810 fffff800`02e80e60 : fffffa80`094a9a30 fffff880`00ea930f 00000000`0000001e ffffffff`ffffffff : nt!KiBugCheckDispatch+0x69 fffff880`009b0950 fffff800`02e86bb6 : 00000000`000096e7 00000000`00000022 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x260 fffff880`009b0ae0 fffff880`04b40a57 : 00000000`00000000 fffff880`00000000 fffffa80`09460400 fffffa80`06d14930 : nt!KeSetEvent+0x16 fffff880`009b0b50 00000000`00000000 : fffff880`00000000 fffffa80`09460400 fffffa80`06d14930 00000000`00000000 : atikmdag+0x4da57 STACK_COMMAND: kb FOLLOWUP_IP: atikmdag+4da57 fffff880`04b40a57 ?? ??? SYMBOL_STACK_INDEX: 4 SYMBOL_NAME: atikmdag+4da57 FOLLOWUP_NAME: MachineOwner MODULE_NAME: atikmdag IMAGE_NAME: atikmdag.sys DEBUG_FLR_IMAGE_TIMESTAMP: 4ebb3c7e FAILURE_BUCKET_ID: X64_0xA_atikmdag+4da57 BUCKET_ID: X64_0xA_atikmdag+4da57 Followup: MachineOwner ---------
  2. Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\EffinCraig\Windows_NT6_BSOD_jcgriff2\011012-35490-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*c:\users\mike\documents\symbols*http://msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Personal Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506 Machine Name: Kernel base = 0xfffff800`02e1e000 PsLoadedModuleList = 0xfffff800`03063670 Debug session time: Tue Jan 10 12:38:30.642 2012 (UTC - 7:00) System Uptime: 0 days 0:17:40.657 Loading Kernel Symbols ............................................................... ................................................................ .......................... Loading User Symbols Loading unloaded module list ...... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck A, {ffffffffffffffff, 2, 0, fffff80002e9ebb6} Unable to load image \SystemRoot\system32\DRIVERS\atikmdag.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for atikmdag.sys *** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys Probably caused by : atikmdag.sys ( atikmdag+4da57 ) Followup: MachineOwner --------- 3: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* IRQL_NOT_LESS_OR_EQUAL (a) 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 a kernel debugger is available get the stack backtrace. Arguments: Arg1: ffffffffffffffff, memory referenced Arg2: 0000000000000002, IRQL Arg3: 0000000000000000, bitfield : bit 0 : value 0 = read operation, 1 = write operation bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status) Arg4: fffff80002e9ebb6, address which referenced memory Debugging Details: ------------------ READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800030cd100 ffffffffffffffff CURRENT_IRQL: 2 FAULTING_IP: nt!KeSetEvent+16 fffff800`02e9ebb6 f6037f test byte ptr [rbx],7Fh CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0xA PROCESS_NAME: System TRAP_FRAME: fffff880009b0950 -- (.trap 0xfffff880009b0950) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=fffffa8007e9b000 rbx=0000000000000000 rcx=0000000000000001 rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000 rip=fffff80002e9ebb6 rsp=fffff880009b0ae0 rbp=0000000000000004 r8=0000000000000000 r9=fffff880009b0c90 r10=fffffa8009ee5ef0 r11=fffff880009b0cf8 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei ng nz na pe nc nt!KeSetEvent+0x16: fffff800`02e9ebb6 f6037f test byte ptr [rbx],7Fh ds:d6b0:00000000`00000000=?? Resetting default scope LAST_CONTROL_TRANSFER: from fffff80002e9a1e9 to fffff80002e9ac40 STACK_TEXT: fffff880`009b0808 fffff800`02e9a1e9 : 00000000`0000000a ffffffff`ffffffff 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx fffff880`009b0810 fffff800`02e98e60 : fffffa80`094a6d10 fffff880`00ed330f fffffa80`07c12bc8 ffffffff`ffffffff : nt!KiBugCheckDispatch+0x69 fffff880`009b0950 fffff800`02e9ebb6 : 00000000`0000df96 00000000`00000022 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x260 fffff880`009b0ae0 fffff880`04a84a57 : 00000000`00000000 fffff880`00000000 fffffa80`09446000 fffffa80`06cad6b0 : nt!KeSetEvent+0x16 fffff880`009b0b50 00000000`00000000 : fffff880`00000000 fffffa80`09446000 fffffa80`06cad6b0 00000000`00000000 : atikmdag+0x4da57 STACK_COMMAND: kb FOLLOWUP_IP: atikmdag+4da57 fffff880`04a84a57 ?? ??? SYMBOL_STACK_INDEX: 4 SYMBOL_NAME: atikmdag+4da57 FOLLOWUP_NAME: MachineOwner MODULE_NAME: atikmdag IMAGE_NAME: atikmdag.sys DEBUG_FLR_IMAGE_TIMESTAMP: 4ebb3c7e FAILURE_BUCKET_ID: X64_0xA_atikmdag+4da57 BUCKET_ID: X64_0xA_atikmdag+4da57 Followup: MachineOwner ---------
How did you get tcpip.sys? These are all related to your display card. It could be a memory problem. Run the boot version of Memtest86+ paying close attention to Parts 2 and 3 of the tutorial. Also, in case Memtest86+ misses anything and comes up with no errors, run the extended version of the Windows Memory Diagnostics Tool for at least five passes. These you may want to run overnight since they take a long time to complete.
My System SpecsSystem Spec
10 Jan 2012   #5

Windows 7 Ultimate 64bit SP1
 
 

Hi.

Just my 2 cents:

In addition to writhziden advice,remove Bitdefender from your system for testing purposes.


For now download and install Microsoft Security Essentials with windows firewall enable.
My System SpecsSystem Spec
10 Jan 2012   #6

Windows 7 Home Premium 64 Bit
 
 

Quote   Quote: Originally Posted by panais View Post
Hi.

Just my 2 cents:

In addition to writhziden advice,remove Bitdefender from your system for testing purposes.


For now download and install Microsoft Security Essentials with windows firewall enable.
Use the second method in How to uninstall BitDefender to uninstall bitdefender. It is always better to remove antivirus software using the developer's uninstall tools.

Thanks panais for the input.
My System SpecsSystem Spec
10 Jan 2012   #7

Windows 7 64-bit
 
 

I got the tcpip.sys thing by viewing the minidumps in BlueScreenView; it keeps appearing under the "Caused By Driver" column in the top pane. I'm no expert on these things so I guess I just assumed it was accurate.

I've re-tried the removal and re-installing of my video drivers after removing Bitdefender and installing MSE. The crash still occurs so I'll run the memory tests this evening and post again in the morning.

Thanks for your help so far, 'tis much appreciated.
My System SpecsSystem Spec
11 Jan 2012   #8

Windows 7 64-bit
 
 

Memtest86+ and Memory Diagnostic Tool revealed no errors.
My System SpecsSystem Spec
11 Jan 2012   #9

Windows 7 Home Premium 64 Bit
 
 

These problems sometimes occur due to file corruption. Run Disk Check with both boxes checked for all HDDs and with Automatically fix file system errors checked for all SSDs.
My System SpecsSystem Spec
12 Jan 2012   #10

Windows 7 64-bit
 
 

Finished error checking the drives, still getting the crash.

I didn't start getting this crash until I started using this mobo and video card together; previously I had been using this same video card with an old Asus P5K without any issues. I'm not sure if that provides any extra clues.
My System SpecsSystem Spec
Reply

 BSOD caused by tcpip.sys while gaming + streaming video




Thread Tools



Similar help and support threads for2: BSOD caused by tcpip.sys while gaming + streaming video
Thread Forum
BSOD after Gaming/Streaming BSOD Help and Support
Slow and choppy video playback in streaming and gaming Music, Pictures & Video
BSOD at random times during gaming, some video streaming. BSOD Help and Support
BSOD Randomly Gaming,Streaming,Video Encoding BSOD Help and Support
Computer Stutters While Playing/Streaming Video or Gaming Graphic Cards
Erratic BSOD, usually while gaming; STOP screen says tcpip.sys BSOD Help and Support
BSOD when streaming to Roku 2 - ntoskrnl and tcpip.sys BSOD Help and Support

Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd

All times are GMT -5. The time now is 08:27 PM.
Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App
  

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33