BSOD W7 64 bits

[MyPcSucks]

Hello, I'd hope someone can help me with this. My PC has alot of BSOD and games and aplications crash alot, normally when I'm using the internet. I'll attach some crash dumps maybe someone can find out the problem. Thanks for the help.

 

[zigzag3143]

Hello, I'd hope someone can help me with this. My PC has alot of BSOD and games and aplications crash alot, normally when I'm using the internet. I'll attach some crash dumps maybe someone can find out the problem. Thanks for the help.

Hi and welcome

this crash was caused by tcpip.sys.

I would run a system file check to erify and repair your system files to do that
type cmd in search>right click and run as admin>sfc /scannow
I would also check for updatednetwork driver.

Ken

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


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

Symbol search path is: SRV*d:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
[B]Built by: 7600.16385.amd64fre.win7_rtm.090713-1255[/B]
Machine Name:
Kernel base = 0xfffff800`02a1f000 PsLoadedModuleList = 0xfffff800`02c5ce50
Debug session time: Mon Dec 28 15:25:47.047 2009 (GMT-5)
System Uptime: 0 days 5:03:31.154
Loading Kernel Symbols
...............................................................
................................................................
....................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {80000000000, 2, 0, fffff88001862d3e}
[B]
Probably caused by : tcpip.sys [/B]( tcpip!IppFragmentPackets+8e )

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

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

[B]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.[/B]
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: 0000080000000000, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff88001862d3e, address which referenced memory

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


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002cc70e0
 0000080000000000 

CURRENT_IRQL:  2

FAULTING_IP: 
tcpip!IppFragmentPackets+8e
fffff880`01862d3e 4d8b6d00        mov     r13,qword ptr [r13]

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xD1

PROCESS_NAME:  System

TRAP_FRAME:  fffff880051b2000 -- (.trap 0xfffff880051b2000)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff880051b2210 rbx=0000000000000000 rcx=fffff8800196b9a0
rdx=0000080000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88001862d3e rsp=fffff880051b2190 rbp=fffff8800196b9a0
 r8=fffffa800296e040  r9=fffffa8002de9160 r10=0000000000000004
r11=fffff880051b22a8 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
tcpip!IppFragmentPackets+0x8e:
fffff880`01862d3e 4d8b6d00        mov     r13,qword ptr [r13] ds:1f60:00000000`00000000=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002a90469 to fffff80002a90f00

STACK_TEXT:  
fffff880`051b1eb8 fffff800`02a90469 : 00000000`0000000a 00000800`00000000 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`051b1ec0 fffff800`02a8f0e0 : fffffa80`02228240 00000000`00000004 00000000`000054c6 fffffa80`0222686d : nt!KiBugCheckDispatch+0x69
fffff880`051b2000 fffff880`01862d3e : fffffa80`027dde00 00000000`00000001 fffffa80`027ef000 00000000`00000000 : nt!KiPageFault+0x260
fffff880`051b2190 fffff880`018bf0a8 : fffff880`0196b9a0 fffffa80`027ef000 fffff880`01960004 00000000`02e44901 : tcpip!IppFragmentPackets+0x8e
fffff880`051b22b0 fffff880`01859272 : fffffa80`028d2130 00000000`00000000 fffffa80`02e44901 00000000`00000001 : tcpip! ?? ::FNODOBFM::`string'+0x43f39
fffff880`051b24b0 fffff880`018726ba : fffffa80`02e44990 fffff880`051b25e0 fffffa80`02e44990 00000000`00000000 : tcpip!FlpReceiveNonPreValidatedNetBufferListChain+0x2b2
fffff880`051b2590 fffff800`02aa064a : fffffa80`02228240 fffff880`051ad000 00000000`00004800 00000000`00000000 : tcpip!FlReceiveNetBufferListChainCalloutRoutine+0xda
fffff880`051b25e0 fffff880`018720e2 : fffff880`018725e0 fffff880`051b26f0 00000000`00000002 00000000`00000000 : nt!KeExpandKernelStackAndCalloutEx+0xda
fffff880`051b26c0 fffff880`0178d0eb : fffffa80`02e48010 00000000`00000000 fffffa80`02c3e1a0 00000000`0000000f : tcpip!FlReceiveNetBufferListChain+0xb2
fffff880`051b2730 fffff880`01756fc6 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ndis!ndisMIndicateNetBufferListsToOpen+0xdb
fffff880`051b27a0 fffff880`0171f27e : fffffa80`02c3e1a0 00000000`00000000 00000000`00000000 00000000`00000000 : ndis!ndisMDispatchReceiveNetBufferLists+0x1d6
fffff880`051b2c20 fffff880`0171f573 : fffffa80`02c3e1a0 fffffa80`02c3e1a0 00000000`00000080 fffffa80`0279f200 : ndis!ndisDoPeriodicReceivesIndication+0x14e
fffff880`051b2c80 fffff880`01708b0c : 00000000`00010300 fffffa80`02c3f388 00000000`00000080 fffffa80`0279f2e0 : ndis!ndisPeriodicReceivesWorker+0x63
fffff880`051b2cb0 fffff800`02d34166 : 00000000`0b76b032 fffffa80`03a1f4b0 00000000`00000080 fffffa80`03a1f4b0 : ndis!ndisReceiveWorkerThread+0x12c
fffff880`051b2d40 fffff800`02a6f486 : fffff880`009e6180 fffffa80`03a1f4b0 fffff880`009f0f40 00000000`00000246 : nt!PspSystemThreadStartup+0x5a
fffff880`051b2d80 00000000`00000000 : fffff880`051b3000 fffff880`051ad000 fffff880`051b2a00 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  kb

FOLLOWUP_IP: 
tcpip!IppFragmentPackets+8e
fffff880`01862d3e 4d8b6d00        mov     r13,qword ptr [r13]

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  tcpip!IppFragmentPackets+8e

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: tcpip

IMAGE_NAME:  tcpip.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc26e

FAILURE_BUCKET_ID:  X64_0xD1_tcpip!IppFragmentPackets+8e

BUCKET_ID:  X64_0xD1_tcpip!IppFragmentPackets+8e

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

 

[MyPcSucks]

Hello and thank you for your reply. I've done the system file check and updated network drivers but the problem still persists. Is there any other thing I can try?

 

[zigzag3143]

Hello and thank you for your reply. I've done the system file check and updated network drivers but the problem still persists. Is there any other thing I can try?

yes. if the problem is persistent and chronic.

Using Driver Verifier is an iffy proposition. Most times it'll  crash and it'll tell you what the driver is. But sometimes it'll crash  and won't tell you the driver. Other times it'll crash before you can  log in to Windows. If you can't get to Safe Mode, then you'll have to  resort to offline editing of the registry to disable Driver Verifier.

So, 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).

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 [B]EXCEPT FOR[/B] "Low Resource Simulation" and  click "Next"
- Select "Select driver names from a list" and click "Next"
Then select all drivers [B]NOT[/B] provided by Microsoft and click  "Next"
- Select "Finish" on the next page.

Reboot the system and [B][U]wait for it to crash to the Blue Screen[/U][/B].  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.

Reboot into Windows (after the crash) and [B][U]turn off Driver Verifier[/U][/B]  by going back in and selecting "Delete existing settings" on the first  page, then locate and zip up the memory dump file and upload it with  your next post.

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.
If that doesn't work, post back and we'll have to see about fixing the  registry entry off-line.

Excepts by our wizard John

make sure you back up


KJ