BSOD Apparent related to IPOD Touch and/or related services

[sut]

My PC has recently started erratic BSOD crashes after a year of bliss. I installed UBUNTU as second boot option and it seems to work normally. Would rather not just give up on Windows 7 - particularly as this is x64 version and UBUNTU is only x86 version; I also have some windows-only software that has run very well on this system.

So I used msconfig.exe to stop loading some software and services and in doing so returned to crash free desktop with most functionality. However reactivating my APPLE IPod related services caused the BSOD to return (with STOP: 0x000000D1 ... with ) indicating IPOD is somehow at fault here??!

I checked some available hotfixes but was not convinced my case was presented.

had been happy with iTunes/Ipod on this PC over last year so surprised to see change.

I wonder what happened.

 

[zigzag3143]

My PC has recently started erratic BSOD crashes after a year of bliss. I installed UBUNTU as second boot option and it seems to work normally. Would rather not just give up on Windows 7 - particularly as this is x64 version and UBUNTU is only x86 version; I also have some windows-only software that has run very well on this system.

So I used msconfig.exe to stop loading some software and services and in doing so returned to crash free desktop with most functionality. However reactivating my APPLE IPod related services caused the BSOD to return (with STOP: 0x000000D1 ... with ) indicating IPOD is somehow at fault here??!

I checked some available hotfixes but was not convinced my case was presented.

had been happy with iTunes/Ipod on this PC over last year so surprised to see change.

I wonder what happened.

These were virtually identical and all related to tcpip.sys so your Ipod may be somewhat at fault. I would suspect the driver first and would run driver verifier to find if it is in fact the problem.

I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).

In Windows 7 you can make a Startup Repair disk by going to Start....All Programs...Maintenance...Create a System Repair Disc - with Windows Vista you'll have to use your installation disk or the "Repair your computer" option at the top of the Safe Mode menu .

Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.

Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).

If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.

Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\K\Desktop\Windows_NT6_BSOD_jcgriff2\051611-16957-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\Symbols*http://msdl.microsoft.com/download/symbols;srv*e:\symbols
*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16792.amd64fre.win7_gdr.110408-1633
Machine Name:
Kernel base = 0xfffff800`03204000 PsLoadedModuleList = 0xfffff800`03441e50
Debug session time: Mon May 16 21:49:19.618 2011 (GMT-4)
System Uptime: 0 days 0:11:48.789
Loading Kernel Symbols
...............................................................
................................................................
............................
Loading User Symbols
Loading unloaded module list
.......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {1c, 2, 1, fffff8800187c3ba}

Probably caused by : tcpip.sys ( tcpip!TcpBeginTcbSend+32a )

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

0: 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: 000000000000001c, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, value 0 = read operation, 1 = write operation
Arg4: fffff8800187c3ba, address which referenced memory

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


WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff800034ac0e0
 000000000000001c 

CURRENT_IRQL:  2

FAULTING_IP: 
tcpip!TcpBeginTcbSend+32a
fffff880`0187c3ba f083401c01      lock add dword ptr [rax+1Ch],1

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xD1

PROCESS_NAME:  SearchFilterHo

TRAP_FRAME:  fffff80000ba1590 -- (.trap 0xfffff80000ba1590)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=fffffa8005774710
rdx=fffffa8005774700 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8800187c3ba rsp=fffff80000ba1720 rbp=fffff80000ba1828
 r8=fffffa8005774510  r9=fffff80000ba17c0 r10=fffffa8005774640
r11=0000000000000020 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na pe nc
tcpip!TcpBeginTcbSend+0x32a:
fffff880`0187c3ba f083401c01      lock add dword ptr [rax+1Ch],1 ds:17c0:00000000`0000001c=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80003273c69 to fffff80003274700

STACK_TEXT:  
fffff800`00ba1448 fffff800`03273c69 : 00000000`0000000a 00000000`0000001c 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff800`00ba1450 fffff800`032728e0 : fffffa80`0a3fb350 00000000`00000001 fffffa80`46786d4b fffffa80`08d1c030 : nt!KiBugCheckDispatch+0x69
fffff800`00ba1590 fffff880`0187c3ba : 00000000`00000001 fffffa80`05732a90 fffffa80`05734240 fffff880`01807dff : nt!KiPageFault+0x260
fffff800`00ba1720 fffff880`0187abc9 : ffff0080`012c99eb ffff0080`012c99fb fffffa80`08dd2080 00000000`00000001 : tcpip!TcpBeginTcbSend+0x32a
fffff800`00ba19a0 fffff880`01876a56 : 00000000`00000000 00000000`00000001 fffff880`01968128 00000000`00000000 : tcpip!TcpTcbSend+0x1d9
fffff800`00ba1c20 fffff880`0187e44c : fffffa80`08d73e00 00000000`00000000 00000000`00000000 fffff880`01861700 : tcpip!TcpFlushDelay+0x316
fffff800`00ba1d00 fffff880`018606c7 : fffffa80`0672f000 fffffa80`06606860 fffffa80`06740104 00000000`00000000 : tcpip!TcpPreValidatedReceive+0x20c
fffff800`00ba1db0 fffff880`01860799 : fffff800`00ba1f30 fffff880`0196e9a0 fffff800`00ba1f40 fffff800`00ba1e90 : tcpip!IppDeliverListToProtocol+0x97
fffff800`00ba1e70 fffff880`01860c90 : 00000000`00000000 00000000`00000000 fffffa80`0a115c40 fffff800`00ba1f30 : tcpip!IppProcessDeliverList+0x59
fffff800`00ba1ee0 fffff880`0185fb21 : fffffa80`46786d4b fffffa80`0672f000 fffff880`0196e9a0 00000000`08dd3801 : tcpip!IppReceiveHeaderBatch+0x231
fffff800`00ba1fc0 fffff880`0185e592 : fffffa80`08dd7600 00000000`00000000 fffffa80`08dd3801 00000000`00000001 : tcpip!IpFlcReceivePackets+0x651
fffff800`00ba21c0 fffff880`01877e5a : fffffa80`08dd3800 fffff800`00ba22f0 fffffa80`08dd3800 00000000`00000000 : tcpip!FlpReceiveNonPreValidatedNetBufferListChain+0x2b2
fffff800`00ba22a0 fffff800`03283e5a : fffffa80`08d1c030 fffff800`00b9d000 00000000`00004800 00000000`00000000 : tcpip!FlReceiveNetBufferListChainCalloutRoutine+0xda
fffff800`00ba22f0 fffff880`01877882 : fffff880`01877d80 fffff800`00ba2400 fffffa80`08a84102 00000000`00005000 : nt!KeExpandKernelStackAndCalloutEx+0xda
fffff800`00ba23d0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : tcpip!FlReceiveNetBufferListChain+0xb2


STACK_COMMAND:  kb

FOLLOWUP_IP: 
tcpip!TcpBeginTcbSend+32a
fffff880`0187c3ba f083401c01      lock add dword ptr [rax+1Ch],1

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  tcpip!TcpBeginTcbSend+32a

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: tcpip

IMAGE_NAME:  tcpip.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4c15a458

FAILURE_BUCKET_ID:  X64_0xD1_tcpip!TcpBeginTcbSend+32a

BUCKET_ID:  X64_0xD1_tcpip!TcpBeginTcbSend+32a

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