Jump to content

Welcome to Geeks to Go - Register now for FREE

Need help with your computer or device? Want to learn new tech skills? You're in the right place!
Geeks to Go is a friendly community of tech experts who can solve any problem you have. Just create a free account and post your question. Our volunteers will reply quickly and guide you through the steps. Don't let tech troubles stop you. Join Geeks to Go now and get the support you need!

How it Works Create Account
Photo

blue screen random shutdown (tcpip.sys problem)...help! keep getti

Started by fatkungfu , Mar 23 2014 12:19 PM

  • Please log in to reply

#1
fatkungfu
Posted 23 March 2014 - 12:19 PM

fatkungfu

    New Member

  • Member
  • Pip
  • 3 posts
i keep getting blue screen at random
here what WhoCrashed says
System Information (local)
--------------------------------------------------------------------------------

computer name: ERIC-PC
windows version: Windows 8 , 6.2, build: 9200
windows dir: C:\Windows
Hardware: ASUSTeK COMPUTER INC., P8Z77-V LK
CPU: GenuineIntel Intel® Core™ i7-3770K CPU @ 3.50GHz Intel586, level: 6
8 logical processors, active mask: 255
RAM: 17119883264 total
VM: 2147352576, free: 1934090240




--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Sun 3/23/2014 5:52:41 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\032314-11218-01.dmp
This was probably caused by the following module: tcpip.sys (0xFFFFF88001C03444)
Bugcheck code: 0x109 (0xA3A039D8A3441AD2, 0xB3B7465EF5C33C9A, 0xFFFFF88001C03444, 0x1)
Error: CRITICAL_STRUCTURE_CORRUPTION
file path: C:\Windows\system32\drivers\tcpip.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: TCP/IP Driver
Bug check description: This indicates that the kernel has detected critical kernel code or data corruption.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



On Sun 3/23/2014 5:52:41 PM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: tcpip.sys (0xFFFFF88001C03444)
Bugcheck code: 0x109 (0xA3A039D8A3441AD2, 0xB3B7465EF5C33C9A, 0xFFFFF88001C03444, 0x1)
Error: CRITICAL_STRUCTURE_CORRUPTION
file path: C:\Windows\system32\drivers\tcpip.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: TCP/IP Driver
Bug check description: This indicates that the kernel has detected critical kernel code or data corruption.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.

and here is the crash dump
https://mega.co.nz/#!Jl8XHbZD!ZZql9AEXuzAsezGn-0A07nyhmdQkBGqT3S4OxxtGT1I
  • 0

Advertisements

#2
Ztruker
Posted 23 March 2014 - 05:12 PM

Ztruker

    Member 5k

  • Technician
  • 7,091 posts
This is what windbg says:

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

CRITICAL_STRUCTURE_CORRUPTION (109)
This bugcheck is generated when the kernel detects that critical kernel code or
data have been corrupted. There are generally three causes for a corruption:
1) A driver has inadvertently or deliberately modified critical kernel code
or data. See http://www.microsoft...itPatching.mspx
2) A developer attempted to set a normal kernel breakpoint using a kernel
debugger that was not attached when the system was booted. Normal breakpoints,
"bp", can only be set if the debugger is attached at boot time. Hardware
breakpoints, "ba", can be set at any time.
3) A hardware corruption occurred, e.g. failing RAM holding kernel code or data.
Arguments:
Arg1: a3a039d8a3441ad2, Reserved
Arg2: b3b7465ef5c33c9a, Reserved
Arg3: fffff88001c03444, Failure type dependent information
Arg4: 0000000000000001, Type of corrupted region, can be
0 : A generic data region
1 : Modification of a function or .pdata
2 : A processor IDT
3 : A processor GDT
4 : Type 1 process list corruption
5 : Type 2 process list corruption
6 : Debug routine modification
7 : Critical MSR modification

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


PG_MISMATCH: 1000000

FAULTING_IP:
tcpip!IPSecInitializeTaskOffloadModule+117b0
fffff880`01c03444 f7412c00000200 test dword ptr [rcx+2Ch],20000h

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: CODE_CORRUPTION

BUGCHECK_STR: 0x109

PROCESS_NAME: System

CURRENT_IRQL: 2

STACK_TEXT:
fffff880`02f68328 00000000`00000000 : 00000000`00000109 a3a039d8`a3441ad2 b3b7465e`f5c33c9a fffff880`01c03444 : nt!KeBugCheckEx


STACK_COMMAND: kb

CHKIMG_EXTENSION: !chkimg -lo 50 -db !tcpip
3 errors : !tcpip (fffff88001c03383-fffff88001c03603)
fffff88001c03380 04 0f 84 *17 b6 fe ff 83 f9 02 0f 84 0c b6 fe ff ................
...
fffff88001c034a0 48 8b cb *ea 88 ef e1 ff 90 e9 4c e8 fe ff cc 48 H.........L....H
...
fffff88001c03600 d8 e9 2c *e0 fe ff 48 8d 15 63 d6 fe ff 48 8b cb ..,...H..c...H..

MODULE_NAME: memory_corruption

IMAGE_NAME: memory_corruption

FOLLOWUP_NAME: memory_corruption

DEBUG_FLR_IMAGE_TIMESTAMP: 0

MEMORY_CORRUPTOR: STRIDE

FAILURE_BUCKET_ID: MEMORY_CORRUPTION_STRIDE

BUCKET_ID: MEMORY_CORRUPTION_STRIDE

Followup: memory_corruption


I would suggest running memory diagnostic to see if you have a hardware problem.

Download Memtest86+ (you want the 2nd one Download - Pre-Compiled Bootable ISO (.zip)). Unzip it then create a CD from the iso file using your CD burning software. There is a good freeware burner called ImgBurn which will do this easily.

DO NOT burn the .iso file directly to CD. It must be used as input to a program that knows what to do with it, like the one I mentioned above.

You can do this on any computer that has a working CD Burner.

You can also use a Flash drive instead of a CD.

Download - Auto-installer for USB Key (Win 9x/2k/xp/7) *NEW!*.
Unzip and run Memtest86+ USB Installer.exe.
It will format the flash drive if you tell it to. I used a small, 16MB flash drive and it had 8.5GB left when done.

Boot the CD or Flash drive and run Memtes
  • 0

#3
jcgriff2
Posted 24 March 2014 - 10:54 PM

jcgriff2

    Member

  • Expert
  • 92 posts
  • MVP

If memtest86+ comes back clean, run Driver Verifier -

 

http://www.sysnative...dows-vista.html

 

Regards. . .

 

jcgriff2


  • 0

#4
fatkungfu
Posted 28 March 2014 - 03:07 PM

fatkungfu

    New Member

  • Topic Starter
  • Member
  • Pip
  • 3 posts

This is what windbg says:
 

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

CRITICAL_STRUCTURE_CORRUPTION (109)
This bugcheck is generated when the kernel detects that critical kernel code or
data have been corrupted. There are generally three causes for a corruption:
1) A driver has inadvertently or deliberately modified critical kernel code
or data. See http://www.microsoft...itPatching.mspx
2) A developer attempted to set a normal kernel breakpoint using a kernel
debugger that was not attached when the system was booted. Normal breakpoints,
"bp", can only be set if the debugger is attached at boot time. Hardware
breakpoints, "ba", can be set at any time.
3) A hardware corruption occurred, e.g. failing RAM holding kernel code or data.
Arguments:
Arg1: a3a039d8a3441ad2, Reserved
Arg2: b3b7465ef5c33c9a, Reserved
Arg3: fffff88001c03444, Failure type dependent information
Arg4: 0000000000000001, Type of corrupted region, can be
0 : A generic data region
1 : Modification of a function or .pdata
2 : A processor IDT
3 : A processor GDT
4 : Type 1 process list corruption
5 : Type 2 process list corruption
6 : Debug routine modification
7 : Critical MSR modification

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


PG_MISMATCH: 1000000

FAULTING_IP:
tcpip!IPSecInitializeTaskOffloadModule+117b0
fffff880`01c03444 f7412c00000200 test dword ptr [rcx+2Ch],20000h

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: CODE_CORRUPTION

BUGCHECK_STR: 0x109

PROCESS_NAME: System

CURRENT_IRQL: 2

STACK_TEXT:
fffff880`02f68328 00000000`00000000 : 00000000`00000109 a3a039d8`a3441ad2 b3b7465e`f5c33c9a fffff880`01c03444 : nt!KeBugCheckEx


STACK_COMMAND: kb

CHKIMG_EXTENSION: !chkimg -lo 50 -db !tcpip
3 errors : !tcpip (fffff88001c03383-fffff88001c03603)
fffff88001c03380 04 0f 84 *17 b6 fe ff 83 f9 02 0f 84 0c b6 fe ff ................
...
fffff88001c034a0 48 8b cb *ea 88 ef e1 ff 90 e9 4c e8 fe ff cc 48 H.........L....H
...
fffff88001c03600 d8 e9 2c *e0 fe ff 48 8d 15 63 d6 fe ff 48 8b cb ..,...H..c...H..

MODULE_NAME: memory_corruption

IMAGE_NAME: memory_corruption

FOLLOWUP_NAME: memory_corruption

DEBUG_FLR_IMAGE_TIMESTAMP: 0

MEMORY_CORRUPTOR: STRIDE

FAILURE_BUCKET_ID: MEMORY_CORRUPTION_STRIDE

BUCKET_ID: MEMORY_CORRUPTION_STRIDE

Followup: memory_corruption


I would suggest running memory diagnostic to see if you have a hardware problem.

Download Memtest86+ (you want the 2nd one Download - Pre-Compiled Bootable ISO (.zip)). Unzip it then create a CD from the iso file using your CD burning software. There is a good freeware burner called ImgBurn which will do this easily.

DO NOT burn the .iso file directly to CD. It must be used as input to a program that knows what to do with it, like the one I mentioned above.

You can do this on any computer that has a working CD Burner.

You can also use a Flash drive instead of a CD.

Download - Auto-installer for USB Key (Win 9x/2k/xp/7) *NEW!*.
Unzip and run Memtest86+ USB Installer.exe.
It will format the flash drive if you tell it to. I used a small, 16MB flash drive and it had 8.5GB left when done.

Boot the CD or Flash drive and run Memtes

 

Memtest86 it not working i try to boot in to it but it just go to windows 8 and not to the Memtest86

here my blue screen dump https://mega.co.nz/#...XO-kP8lLOJzD4Bw


Edited by fatkungfu, 28 March 2014 - 03:11 PM.

  • 0

#5
SleepyDude
Posted 28 March 2014 - 05:28 PM

SleepyDude

    Trusted Helper

  • Malware Removal
  • 4,978 posts

Memtest86 it not working i try to boot in to it but it just go to windows 8 and not to the Memtest86

 

Hi,

 

If you have the UEFI Bios with Secure Boot enable it will not allow you to boot other OS besides Windows 8.

 

If this is the case it's probably easier to use the Windows Memory Diagnostic included on Windows.

 How to Identify RAM Problems with Windows Memory Diagnostic


  • 0

#6
fatkungfu
Posted 28 March 2014 - 07:20 PM

fatkungfu

    New Member

  • Topic Starter
  • Member
  • Pip
  • 3 posts

Windows Memory Diagnostic say that my ram it working and there are no error so what can do to fix blue screening 


Edited by fatkungfu, 28 March 2014 - 07:21 PM.

  • 0

#7
Ztruker
Posted 28 March 2014 - 08:24 PM

Ztruker

    Member 5k

  • Technician
  • 7,091 posts

The latest dump indicates your Nvidia driver:

 

 

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

SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION (c1)
Special pool has detected memory corruption.  Typically the current thread's
stack backtrace will reveal the guilty party.
Arguments:
Arg1: fffff980215e6f80, address trying to free
Arg2: fffff980215e6163, address where bits are corrupted
Arg3: 0000000000554080, (reserved)
Arg4: 0000000000000023, caller is freeing an address where nearby bytes within the same page have been corrupted

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

BUGCHECK_STR:  0xC1_23

SPECIAL_POOL_CORRUPTION_TYPE:  23

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP

PROCESS_NAME:  chrome.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff80299205581 to fffff802990d2440

STACK_TEXT:  
fffff880`0ceaed08 fffff802`99205581 : 00000000`000000c1 fffff980`215e6f80 fffff980`215e6163 00000000`00554080 : nt!KeBugCheckEx
fffff880`0ceaed10 fffff802`99204a94 : 00000000`00000000 fffffa80`0ecab000 00000000`00000003 00000000`00000010 : nt!MiCheckSpecialPoolSlop+0xa1
fffff880`0ceaed50 fffff802`992ea7e9 : 00000000`00012cf8 00000000`00000000 00000000`614c764e 00000000`00000000 : nt!MmFreeSpecialPool+0x178
fffff880`0ceaee80 fffff802`996b9587 : fffff980`215e6f80 fffff980`215e6f80 fffffa80`0ecab000 00000000`00000000 : nt!ExFreePool+0x6d8
fffff880`0ceaef60 fffff880`0438f24b : fffff880`0ceaf1d8 fffff980`215e6f80 fffff880`0ceaf089 00000000`00000000 : nt!VerifierExFreePoolWithTag+0x47
fffff880`0ceaef90 fffff880`0ceaf1d8 : fffff980`215e6f80 fffff880`0ceaf089 00000000`00000000 00000000`00000000 : nvlddmkm+0xd324b
fffff880`0ceaef98 fffff980`215e6f80 : fffff880`0ceaf089 00000000`00000000 00000000`00000000 fffff880`0432d7b3 : 0xfffff880`0ceaf1d8
fffff880`0ceaefa0 fffff880`0ceaf089 : 00000000`00000000 00000000`00000000 fffff880`0432d7b3 fffff880`0ceaf1d8 : 0xfffff980`215e6f80
fffff880`0ceaefa8 00000000`00000000 : 00000000`00000000 fffff880`0432d7b3 fffff880`0ceaf1d8 fffff880`0ceaf1d8 : 0xfffff880`0ceaf089

STACK_COMMAND:  kb

FOLLOWUP_IP:
nvlddmkm+d324b
fffff880`0438f24b ??              ???

SYMBOL_STACK_INDEX:  5
SYMBOL_NAME:  nvlddmkm+d324b
FOLLOWUP_NAME:  MachineOwner
MODULE_NAME: nvlddmkm
IMAGE_NAME:  nvlddmkm.sys
DEBUG_FLR_IMAGE_TIMESTAMP:  5315b408
FAILURE_BUCKET_ID:  0xC1_23_VRF_nvlddmkm+d324b
BUCKET_ID:  0xC1_23_VRF_nvlddmkm+d324b
 


  • 0

#8
jcgriff2
Posted 29 March 2014 - 10:26 PM

jcgriff2

    Member

  • Expert
  • 92 posts
  • MVP

It may be a false positive by Driver Verifier.

 

NVIDIA drivers have been showing up only in VERIFIER_ENABLED dumps lately (Windows 8/8.1)

 

Be sure NVIDIA video drivers are updated anyway.


  • 0
Back to Windows 8 and 8.1 · Next Unread Topic →




Similar Topics

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users

  1. Geeks to Go Community
  2. → Operating Systems
  3. → Windows 8 and 8.1

As Featured On:

Microsoft Yahoo BBC MSN PC Magazine Washington Post HP