BSOD when streaming to Roku 2 - ntoskrnl and tcpip.sys

[writhziden]

Daemon Tools Lite isn't listed in the program list... Should I be able to just delete spdt.sys from drivers directory and be good?

Use that uninstall utility I linked. That should do the trick.

 

[tpattgeek]

Done. I'll let you know how it goes. Thanks.

 

[writhziden]

Best wishes!

 

[tpattgeek]

I have streamed several movies to the Roku now and have not had any issues. I removed Daemon Tools the same time I removed Avast, but I think Avast was the underlying problem. Thanks for the help!

 

[writhziden]

I have streamed several movies to the Roku now and have not had any issues. I removed Daemon Tools the same time I removed Avast, but I think Avast was the underlying problem. Thanks for the help!

Thanks for posting back. Glad things seem to be sorted. Let us know if you have any questions, comments, or concerns in the future.

 

[tpattgeek]

OK, we have streamed several movies using the Roku, but it happened again last night. Attached is my dump file. It appears ffmpeg.exe is at fault... I use bsplayer for video playback on the PC, and I know the PC's codecs are used when streaming to Roku... So, was that a codec installed with bsplayer? Is that something that can be updated? Should I get rid of bsplayer altogether? Seems like it's one thing after another...

 

[writhziden]

Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [H:\BSODDmpFiles\tpattgeek\012412-15943-01\012412-15943-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
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`03053000 PsLoadedModuleList = 0xfffff800`03298670
Debug session time: Tue Jan 24 17:40:46.751 2012 (UTC - 7:00)
System Uptime: 1 days 4:30:14.421
Loading Kernel Symbols
...............................................................
................................................................
...........................................
Loading User Symbols
Loading unloaded module list
..........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {fffffa80077a6000, 0, fffff8800154ef1a, 0}


Could not read faulting driver name
Probably caused by : NETIO.SYS ( NETIO!memmove+ca )

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

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

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced.  This cannot be protected by try-except,
it must be protected by a Probe.  Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: fffffa80077a6000, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff8800154ef1a, If non-zero, the instruction address which referenced the bad memory
	address.
Arg4: 0000000000000000, (reserved)

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


Could not read faulting driver name

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80003302100
 fffffa80077a6000 

FAULTING_IP: 
NETIO!memmove+ca
fffff880`0154ef1a 4c8b540af8      mov     r10,qword ptr [rdx+rcx-8]

MM_INTERNAL_CODE:  0

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x50

PROCESS_NAME:  ffmpeg.exe

CURRENT_IRQL:  0

TRAP_FRAME:  fffff88009baf1f0 -- (.trap 0xfffff88009baf1f0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=000000000359d268
rdx=fffffa8004208d9c rsi=0000000000000000 rdi=0000000000000000
rip=fffff8800154ef1a rsp=fffff88009baf388 rbp=000000000000013c
 r8=000000000000013c  r9=001ffffffffffb80 r10=0000000000000000
r11=0000000003594128 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na pe nc
NETIO!memmove+0xca:
fffff880`0154ef1a 4c8b540af8      mov     r10,qword ptr [rdx+rcx-8] ds:fffffa80`077a5ffc=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff8000307b9fc to fffff800030cfc40

STACK_TEXT:  
fffff880`09baf088 fffff800`0307b9fc : 00000000`00000050 fffffa80`077a6000 00000000`00000000 fffff880`09baf1f0 : nt!KeBugCheckEx
fffff880`09baf090 fffff800`030cdd6e : 00000000`00000000 fffffa80`077a6000 00000000`00000000 00000000`0000013c : nt! ?? ::FNODOBFM::`string'+0x4611f
fffff880`09baf1f0 fffff880`0154ef1a : fffff880`0155008f fffffa80`03b3f320 00000000`00000000 fffffa80`065dfcf0 : nt!KiPageFault+0x16e
fffff880`09baf388 fffff880`0155008f : fffffa80`03b3f320 00000000`00000000 fffffa80`065dfcf0 fffffa80`065dfe50 : NETIO!memmove+0xca
fffff880`09baf390 fffff880`04076845 : 00000000`0000013c 00000000`0000013c 00000000`0000013c 00000000`00000000 : NETIO!RtlCopyMdlToBuffer+0x8f
fffff880`09baf3f0 fffff880`0408d790 : fffff880`09baf970 fffff880`09baf790 fffff880`09baf790 fffffa80`03ff5a10 : afd!AfdCopyMdlChainToBufferArray+0x115
fffff880`09baf480 fffff880`040757bb : 00000000`00000001 00000000`000007ff 00000000`00006904 fffff880`09baf7d0 : afd!AfdFastConnectionReceive+0x7c0
fffff880`09baf6a0 fffff800`033ea803 : 00000000`00004000 fffffa80`06ef0f20 00000000`0028dda0 fffffa80`041fbe01 : afd!AfdFastIoDeviceControl+0x7ab
fffff880`09bafa10 fffff800`033eb2f6 : fffff880`09bafbf8 00000000`000000b8 00000000`00000001 00000000`00000000 : nt!IopXxxControlFile+0x373
fffff880`09bafb40 fffff800`030ceed3 : fffff880`09bafca0 fffffa80`0460cd00 fffff880`09bafbf8 00000000`00000001 : nt!NtDeviceIoControlFile+0x56
fffff880`09bafbb0 00000000`751f2e09 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0008ec08 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x751f2e09


STACK_COMMAND:  kb

FOLLOWUP_IP: 
NETIO!memmove+ca
fffff880`0154ef1a 4c8b540af8      mov     r10,qword ptr [rdx+rcx-8]

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  NETIO!memmove+ca

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: NETIO

IMAGE_NAME:  NETIO.SYS

DEBUG_FLR_IMAGE_TIMESTAMP:  4ce79381

FAILURE_BUCKET_ID:  X64_0x50_NETIO!memmove+ca

BUCKET_ID:  X64_0x50_NETIO!memmove+ca

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

NETIO.SYS is usually blamed when the antivirus or network adapter is at fault. What antivirus are you currently using? Is your network adapter driver up to date?

You may also try uninstalling/updating/disabling LogMeIn and seeing if you continue to have the problem.

 

[tpattgeek]

I'd hate to have to remove all of my software just to stream to my Roku. I'm using Avira for AV but will try MSE to prove it's not a cause. And yes, my NIC driver is up to date.

 

[tpattgeek]

Does NETIO.SYS prove it's a driver fault? What are the chances of it being some other software?

 

[writhziden]

Does NETIO.SYS prove it's a driver fault? What are the chances of it being some other software?

Anything is possible. If you want to rule out software, proceed with the steps to http://www.sevenforums.com/tutorial...ation-conflicts-performing-clean-startup.html.



What were the results of clean startup?