Windows 7 TCPIP.SYS mavi ekran hatası

İşletim sistemi
Windows 7

azafrak

Kilopat
Katılım
12 Mayıs 2015
Mesajlar
38
RAM
4GB
Anakart
LENOVO
Merhaba,

Cihaz durup dururken mavi ekrana düşüyor.
Ethernet kartı sürücüsü kaldırıldı, sıfırdan kuruldu.
Güncel ethernet kartı denendi.

Ramler silindi temizlendi.

Sorun devam ediyor.

Manufacturer LENOVO
Serial number INVALID
Version NOK
Chipset Intel H81 (Lynx Point)
Slots 4xPCI Express x1, 1xPCI Express x16
PCI Express version v2.0
USB version v3.0
USB port count 14
RAID capability Not Supported
Super-IO/LPC Chip Winbond/Nuvoton NCT6779D

[CODE title="Mavi Ekran"]
Microsoft (R) Windows Debugger Version 10.0.22549.1000 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\atifz\Desktop\041522-9297-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available


************* Path validation summary **************
Response Time (ms) Location
Deferred srv*
Symbol search path is: srv*
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Edition build lab: 7601.24384.amd64fre.win7sp1_ldr_escrow.190220-1800
Machine Name:
Kernel base = 0xfffff800`01e55000 PsLoadedModuleList = 0xfffff800`0208ec90
Debug session time: Fri Apr 15 17:13:04.837 2022 (UTC + 3:00)
System Uptime: 143 days 23:56:04.846
Loading Kernel Symbols
...............................................................
................................................................
.....................................
Loading User Symbols
Loading unloaded module list
..................................................
For analysis of this file, run !analyze -v
*** WARNING: Unable to verify timestamp for tcpip.sys
tcpip_fffff8800322d000+0x14e0:
fffff880`0322e4e0 488911 mov qword ptr [rcx],rdx ds:002b:00000000`00000000=????????????????
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
This is a very common BugCheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003. This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG. This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG. This will let us see why this breakpoint is
happening.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff8800322e4e0, The address that the exception occurred at
Arg3: fffff8801cf508f8, Exception Record Address
Arg4: fffff8801cf50160, Context Record Address

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

GetUlongPtrFromAddress: unable to read from fffff800020f2300

KEY_VALUES_STRING: 1

Key : AV.Dereference
Value: NullPtr

Key : AV.Fault
Value: Write

Key : Analysis.CPU.mSec
Value: 4499

Key : Analysis.DebugAnalysisManager
Value: Create

Key : Analysis.Elapsed.mSec
Value: 17537

Key : Analysis.Init.CPU.mSec
Value: 1561

Key : Analysis.Init.Elapsed.mSec
Value: 224736

Key : Analysis.Memory.CommitPeak.Mb
Value: 75

Key : WER.OS.Branch
Value: win7sp1_ldr_escrow

Key : WER.OS.Timestamp
Value: 2019-02-20T18:00:00Z

Key : WER.OS.Version
Value: 7.1.7601.24384


FILE_IN_CAB: 041522-9297-01.dmp

BUGCHECK_CODE: 7e

BUGCHECK_P1: ffffffffc0000005

BUGCHECK_P2: fffff8800322e4e0

BUGCHECK_P3: fffff8801cf508f8

BUGCHECK_P4: fffff8801cf50160

EXCEPTION_RECORD: fffff8801cf508f8 -- (.exr 0xfffff8801cf508f8)
ExceptionAddress: fffff8800322e4e0 (tcpip_fffff8800322d000+0x00000000000014e0)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000001
Parameter[1]: 0000000000000000
Attempt to write to address 0000000000000000

CONTEXT: fffff8801cf50160 -- (.cxr 0xfffff8801cf50160)
rax=0000000000000000 rbx=00000000001fffff rcx=0000000000000000
rdx=0000000000000000 rsi=0000000000000000 rdi=fffffa80bc7fd010
rip=fffff8800322e4e0 rsp=fffff8801cf50b38 rbp=fffff8801cf50c40
r8=0000000000000000 r9=0000000000000040 r10=0000000000000001
r11=fffff8801cf50880 r12=fffffa800559f028 r13=0000000000000000
r14=0000000000001000 r15=ffffffffffffffff
iopl=0 nv up ei ng nz na pe cy
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010283
tcpip_fffff8800322d000+0x14e0:
fffff880`0322e4e0 488911 mov qword ptr [rcx],rdx ds:002b:00000000`00000000=????????????????
Resetting default scope

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System

WRITE_ADDRESS: Unable to get MmSystemRangeStart
GetUlongPtrFromAddress: unable to read from fffff800020f22f0
GetUlongPtrFromAddress: unable to read from fffff800020f24a8
0000000000000000

ERROR_CODE: (NTSTATUS) 0xc0000005 - 0x%p adresindeki y nerge 0x%p adresindeki belle e ba vurdu. Bellek u olamaz %s.

EXCEPTION_CODE_STR: c0000005

EXCEPTION_PARAMETER1: 0000000000000001

EXCEPTION_PARAMETER2: 0000000000000000

EXCEPTION_STR: 0xc0000005

STACK_TEXT:
fffff880`1cf50b38 fffff880`0323b5be : 01d850e3`b0056c35 00000000`001fffff fffffa80`4c4c4cb4 00000000`000007ff : tcpip_fffff8800322d000+0x14e0
fffff880`1cf50b40 01d850e3`b0056c35 : 00000000`001fffff fffffa80`4c4c4cb4 00000000`000007ff fffff880`1cf50b80 : tcpip_fffff8800322d000+0xe5be
fffff880`1cf50b48 00000000`001fffff : fffffa80`4c4c4cb4 00000000`000007ff fffff880`1cf50b80 00000000`00000000 : 0x01d850e3`b0056c35
fffff880`1cf50b50 fffffa80`4c4c4cb4 : 00000000`000007ff fffff880`1cf50b80 00000000`00000000 fffff880`1cf50b98 : 0x1fffff
fffff880`1cf50b58 00000000`000007ff : fffff880`1cf50b80 00000000`00000000 fffff880`1cf50b98 00000000`00100000 : 0xfffffa80`4c4c4cb4
fffff880`1cf50b60 fffff880`1cf50b80 : 00000000`00000000 fffff880`1cf50b98 00000000`00100000 fffffa80`056761d0 : 0x7ff
fffff880`1cf50b68 00000000`00000000 : fffff880`1cf50b98 00000000`00100000 fffffa80`056761d0 ffffffff`800f4994 : 0xfffff880`1cf50b80


SYMBOL_NAME: tcpip_fffff8800322d000+14e0

MODULE_NAME: tcpip_fffff8800322d000

IMAGE_NAME: tcpip.sys

STACK_COMMAND: .cxr 0xfffff8801cf50160 ; kb

FAILURE_BUCKET_ID: 0x7E_tcpip_fffff8800322d000+14e0

OS_VERSION: 7.1.7601.24384

BUILDLAB_STR: win7sp1_ldr_escrow

OSPLATFORM_TYPE: x64

OSNAME: Windows 7

FAILURE_ID_HASH: {1ff02d18-0176-d2f5-3bb3-5e24c9b59f10}

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

[/CODE]
@KojiroHyuga04
 
Son düzenleme:
Okuldaydım, müsait değildim o zaman. Şimdi ilgilenebilirim.

Dökümü atmışsınız, bize dosyanın kendisi lazım.

Rehbere göre paylaşın.
 
Merhaba,

Cihaz durup dururken mavi ekrana düşüyor.
Ethernet kartı sürücüsü kaldırıldı, sıfırdan kuruldu.
Güncel ethernet kartı denendi.

Ramler silindi temizlendi.

Sorun devam ediyor.

Manufacturer LENOVO
Serial number INVALID
Version NOK
Chipset Intel H81 (Lynx Point)
Slots 4xPCI Express x1, 1xPCI Express x16
PCI Express version v2.0
USB version v3.0
USB port count 14
RAID capability Not Supported
Super-IO/LPC Chip Winbond/Nuvoton NCT6779D

[CODE title="Mavi Ekran"]
Microsoft (R) Windows Debugger Version 10.0.22549.1000 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\atifz\Desktop\041522-9297-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available


************* Path validation summary **************
Response Time (ms) Location
Deferred srv*
Symbol search path is: srv*
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Edition build lab: 7601.24384.amd64fre.win7sp1_ldr_escrow.190220-1800
Machine Name:
Kernel base = 0xfffff800`01e55000 PsLoadedModuleList = 0xfffff800`0208ec90
Debug session time: Fri Apr 15 17:13:04.837 2022 (UTC + 3:00)
System Uptime: 143 days 23:56:04.846
Loading Kernel Symbols
...............................................................
................................................................
.....................................
Loading User Symbols
Loading unloaded module list
..................................................
For analysis of this file, run !analyze -v
*** WARNING: Unable to verify timestamp for tcpip.sys
tcpip_fffff8800322d000+0x14e0:
fffff880`0322e4e0 488911 mov qword ptr [rcx],rdx ds:002b:00000000`00000000=????????????????
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
This is a very common BugCheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003. This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG. This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG. This will let us see why this breakpoint is
happening.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff8800322e4e0, The address that the exception occurred at
Arg3: fffff8801cf508f8, Exception Record Address
Arg4: fffff8801cf50160, Context Record Address

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

GetUlongPtrFromAddress: unable to read from fffff800020f2300

KEY_VALUES_STRING: 1

Key : AV.Dereference
Value: NullPtr

Key : AV.Fault
Value: Write

Key : Analysis.CPU.mSec
Value: 4499

Key : Analysis.DebugAnalysisManager
Value: Create

Key : Analysis.Elapsed.mSec
Value: 17537

Key : Analysis.Init.CPU.mSec
Value: 1561

Key : Analysis.Init.Elapsed.mSec
Value: 224736

Key : Analysis.Memory.CommitPeak.Mb
Value: 75

Key : WER.OS.Branch
Value: win7sp1_ldr_escrow

Key : WER.OS.Timestamp
Value: 2019-02-20T18:00:00Z

Key : WER.OS.Version
Value: 7.1.7601.24384


FILE_IN_CAB: 041522-9297-01.dmp

BUGCHECK_CODE: 7e

BUGCHECK_P1: ffffffffc0000005

BUGCHECK_P2: fffff8800322e4e0

BUGCHECK_P3: fffff8801cf508f8

BUGCHECK_P4: fffff8801cf50160

EXCEPTION_RECORD: fffff8801cf508f8 -- (.exr 0xfffff8801cf508f8)
ExceptionAddress: fffff8800322e4e0 (tcpip_fffff8800322d000+0x00000000000014e0)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000001
Parameter[1]: 0000000000000000
Attempt to write to address 0000000000000000

CONTEXT: fffff8801cf50160 -- (.cxr 0xfffff8801cf50160)
rax=0000000000000000 rbx=00000000001fffff rcx=0000000000000000
rdx=0000000000000000 rsi=0000000000000000 rdi=fffffa80bc7fd010
rip=fffff8800322e4e0 rsp=fffff8801cf50b38 rbp=fffff8801cf50c40
r8=0000000000000000 r9=0000000000000040 r10=0000000000000001
r11=fffff8801cf50880 r12=fffffa800559f028 r13=0000000000000000
r14=0000000000001000 r15=ffffffffffffffff
iopl=0 nv up ei ng nz na pe cy
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010283
tcpip_fffff8800322d000+0x14e0:
fffff880`0322e4e0 488911 mov qword ptr [rcx],rdx ds:002b:00000000`00000000=????????????????
Resetting default scope

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System

WRITE_ADDRESS: Unable to get MmSystemRangeStart
GetUlongPtrFromAddress: unable to read from fffff800020f22f0
GetUlongPtrFromAddress: unable to read from fffff800020f24a8
0000000000000000

ERROR_CODE: (NTSTATUS) 0xc0000005 - 0x%p adresindeki y nerge 0x%p adresindeki belle e ba vurdu. Bellek u olamaz %s.

EXCEPTION_CODE_STR: c0000005

EXCEPTION_PARAMETER1: 0000000000000001

EXCEPTION_PARAMETER2: 0000000000000000

EXCEPTION_STR: 0xc0000005

STACK_TEXT:
fffff880`1cf50b38 fffff880`0323b5be : 01d850e3`b0056c35 00000000`001fffff fffffa80`4c4c4cb4 00000000`000007ff : tcpip_fffff8800322d000+0x14e0
fffff880`1cf50b40 01d850e3`b0056c35 : 00000000`001fffff fffffa80`4c4c4cb4 00000000`000007ff fffff880`1cf50b80 : tcpip_fffff8800322d000+0xe5be
fffff880`1cf50b48 00000000`001fffff : fffffa80`4c4c4cb4 00000000`000007ff fffff880`1cf50b80 00000000`00000000 : 0x01d850e3`b0056c35
fffff880`1cf50b50 fffffa80`4c4c4cb4 : 00000000`000007ff fffff880`1cf50b80 00000000`00000000 fffff880`1cf50b98 : 0x1fffff
fffff880`1cf50b58 00000000`000007ff : fffff880`1cf50b80 00000000`00000000 fffff880`1cf50b98 00000000`00100000 : 0xfffffa80`4c4c4cb4
fffff880`1cf50b60 fffff880`1cf50b80 : 00000000`00000000 fffff880`1cf50b98 00000000`00100000 fffffa80`056761d0 : 0x7ff
fffff880`1cf50b68 00000000`00000000 : fffff880`1cf50b98 00000000`00100000 fffffa80`056761d0 ffffffff`800f4994 : 0xfffff880`1cf50b80


SYMBOL_NAME: tcpip_fffff8800322d000+14e0

MODULE_NAME: tcpip_fffff8800322d000

IMAGE_NAME: tcpip.sys

STACK_COMMAND: .cxr 0xfffff8801cf50160 ; kb

FAILURE_BUCKET_ID: 0x7E_tcpip_fffff8800322d000+14e0

OS_VERSION: 7.1.7601.24384

BUILDLAB_STR: win7sp1_ldr_escrow

OSPLATFORM_TYPE: x64

OSNAME: Windows 7

FAILURE_ID_HASH: {1ff02d18-0176-d2f5-3bb3-5e24c9b59f10}

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

[/CODE]
@KojiroHyuga04
Hocam kusura bakmazsan .NET DLL Dosyası Düzenleme şu konumdaki son soruma bakabilir misin?
 

Geri
Yukarı