Zawieszanie sie ssytemu

[x0marko0x]

witam

Mam problem z laptopem. dell xps l502x i7 6gb ramu windows 7 64bit

Problem wystepuja od dosc dawna, robilem rozmaite testy w tym 32 bitowy ktory trwal ponad7h, mialem wymieniana plyte glowna, wczoraj wrocil z serwisu i problem nadal wystepuje.

Podczas wlaczenia gry mija ok 2-6h i zawiesza sie, ostatio po 30 minutach nawet. Jest to irytujace poniewaz problem

wystepuja od 3 miesiecy, a objawy nasilily sie i sa czestsze. Wczoraj laptop wrocil z serwisu - usuneli wszystko,

zainstalowali system i ponoc usuneli wirusa (ktory powodoal zawieszanie sie ?) - instaluje woczraj gre wlaczam, mija 15-20 min i to samo (3x wczoraj sie zawiesil).

Nie wiem co zrobic teraz, chcialem dac tutaj logi z Memory.dmp lecz takiego pliku nie towrzy po tym jak sie zawiesza. Przed wyslaniem laptopa do serwisu zapisalem archiwum z pliku memory.dmp i chcialem porowac z tymi co beda po "naprawie"

 

 

http://imageshack.us/photo/my-images/694/20110601085.jpg/

Uploaded with ImageShack.us

 

historia pliku przed wyslaniem do serwisu:

 

Microsoft ® Windows Debugger Version 6.12.0002.633 AMD64

Copyright © Microsoft Corporation. All rights reserved.

 

 

Loading Dump File [C:\Windows\MEMORY.DMP]

Kernel Summary Dump File: Only kernel address space is available

 

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols

Executable search path is:

Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64

Product: WinNt, suite: TerminalServer SingleUserTS Personal

Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631

Machine Name:

Kernel base = 0xfffff800`02e54000 PsLoadedModuleList = 0xfffff800`03099650

Debug session time: Sat Aug 6 09:14:57.594 2011 (UTC + 2:00)

System Uptime: 0 days 0:04:11.436

Loading Kernel Symbols

...............................................................

................................................................

..................................

Loading User Symbols

PEB is paged out (Peb.Ldr = 000007ff`fffdf018). Type ".hh dbgerr001" for details

Loading unloaded module list

........

*******************************************************************************

* *

* Bugcheck Analysis *

* *

*******************************************************************************

 

Use !analyze -v to get detailed debugging information.

 

BugCheck D1, {100000017, 2, 0, fffff8800186f060}

 

Probably caused by : tcpip.sys ( tcpip!UdpSendMessages+2f0 )

 

Followup: MachineOwner

---------

 

6: 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: 0000000100000017, memory referenced

Arg2: 0000000000000002, IRQL

Arg3: 0000000000000000, value 0 = read operation, 1 = write operation

Arg4: fffff8800186f060, address which referenced memory

 

Debugging Details:

------------------

 

 

READ_ADDRESS: 0000000100000017

 

CURRENT_IRQL: 2

 

FAULTING_IP:

tcpip!UdpSendMessages+2f0

fffff880`0186f060 837a1801 cmp dword ptr [rdx+18h],1

 

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

 

BUGCHECK_STR: 0xD1

 

PROCESS_NAME: svchost.exe

 

TRAP_FRAME: fffff8800bd1ccb0 -- (.trap 0xfffff8800bd1ccb0)

NOTE: The trap frame does not contain all registers.

Some register values may be zeroed or incorrect.

rax=fffffa8008afc280 rbx=0000000000000000 rcx=fffffa8008d49790

rdx=00000000ffffffff rsi=0000000000000000 rdi=0000000000000000

rip=fffff8800186f060 rsp=fffff8800bd1ce40 rbp=fffff8800bd1d400

r8=0000000000004800 r9=0000000000000001 r10=06004000a7f7d946

r11=fffff8800bd1d458 r12=0000000000000000 r13=0000000000000000

r14=0000000000000000 r15=0000000000000000

iopl=0 nv up ei pl nz na po nc

tcpip!UdpSendMessages+0x2f0:

fffff880`0186f060 837a1801 cmp dword ptr [rdx+18h],1 ds:092c:0017=????????

Resetting default scope

 

LAST_CONTROL_TRANSFER: from fffff80002ed32a9 to fffff80002ed3d00

 

STACK_TEXT:

fffff880`0bd1cb68 fffff800`02ed32a9 : 00000000`0000000a 00000001`00000017 00000000`00000002 00000000`00000000 : nt!

 

KeBugCheckEx

fffff880`0bd1cb70 fffff800`02ed1f20 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`0000000e : nt!

 

KiBugCheckDispatch+0x69

fffff880`0bd1ccb0 fffff880`0186f060 : 00000000`00000000 fffff880`0bd1d3d0 00000000`00000000 fffff880`0bd1d818 : nt!

 

KiPageFault+0x260

fffff880`0bd1ce40 fffff880`0186f495 : fffff880`0bd1d370 64536553`08d2d40d fffff8a0`00000000 fffff880`0bd1d310 : tcpip!

 

UdpSendMessages+0x2f0

fffff880`0bd1d230 fffff800`02ee0668 : 00000201`00000000 a0798000`00000010 00010101`011fffff fffff8a0`00000003 : tcpip!

 

UdpTlProviderSendMessagesCalloutRoutine+0x15

fffff880`0bd1d260 fffff880`0186f528 : fffff880`0186f480 fffff8a0`053ebca0 fffff880`69634d00 fffff8a0`00000001 : nt!

 

KeExpandKernelStackAndCalloutEx+0xd8

fffff880`0bd1d340 fffff880`03eedcbe : fffffa80`063c3db0 fffffa80`091577e0 00000000`00000000 fffffa80`06f6c3f0 : tcpip!

 

UdpTlProviderSendMessages+0x78

fffff880`0bd1d3c0 fffff880`03eed8f3 : 00000000`0000004c fffff880`0bd1db60 fffff880`0bd1d690 00000000`0000004c : afd!

 

AfdTLFastDgramSend+0xbe

fffff880`0bd1d460 fffff880`03ed104c : fffffa80`091577e0 fffff880`0bd1d690 00000000`0000004c 00000000`00010000 : afd!

 

AfdFastDatagramSend+0x2e3

fffff880`0bd1d560 fffff800`031ede93 : 00000000`00000000 fffffa80`08d49940 00000000`0660fd88 fffffa80`0745df01 : afd!

 

AfdFastIoDeviceControl+0x103c

fffff880`0bd1d8d0 fffff800`031ee986 : fffff683`ff7eae70 00000000`00000000 00000000`00000000 00000000`0660fd88 : nt!

 

IopXxxControlFile+0x373

fffff880`0bd1da00 fffff800`02ed2f93 : 00000000`00000001 0000007f`ffffffff 00000000`00000000 00000980`00000000 : nt!

 

NtDeviceIoControlFile+0x56

fffff880`0bd1da70 00000000`7798138a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!

 

KiSystemServiceCopyEnd+0x13

00000000`0061d9c8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7798138a

 

 

STACK_COMMAND: kb

 

FOLLOWUP_IP:

tcpip!UdpSendMessages+2f0

fffff880`0186f060 837a1801 cmp dword ptr [rdx+18h],1

 

SYMBOL_STACK_INDEX: 3

 

SYMBOL_NAME: tcpip!UdpSendMessages+2f0

 

FOLLOWUP_NAME: MachineOwner

 

MODULE_NAME: tcpip

 

IMAGE_NAME: tcpip.sys

 

DEBUG_FLR_IMAGE_TIMESTAMP: 4db4de6a

 

FAILURE_BUCKET_ID: X64_0xD1_tcpip!UdpSendMessages+2f0

 

BUCKET_ID: X64_0xD1_tcpip!UdpSendMessages+2f0

 

Followup: MachineOwner

---------

 

 

 

 

Nie wiem czemu teraz mam poblokowane kilka narzedzi (tak jakbym nie byl administratorem) nie moge zapisac m.in. pliku tekstowego na partycji dysku.

 

Ustawienia z uruchamianie i odzyskiwanie

 

http://imageshack.us/photo/my-images/27/memory12.jpg/

Uploaded with ImageShack.us

 

 

Prosilbym o rade jak wlaczyc zapis do pliku memory.dmp - chcialbym przedstawic tutaj i mam nadzieje ze mi pomozecie z problemem ktory nie potrafi rozwiazac serwis. W poniedzialek dzwonie do serwisu ze g.... zrobili i byc moze chcialbym

przedstawic argumenty odnosnie tego pliku .dmp

 

Prosze o pomoc

Pozdrawiam

 

edit:

znalazlem ustawienia przywracania sytemu wszedzie mialem wylaczone, jak biore wlacz to pojawia sie komunikat o bledzie:

 

http://imageshack.us/photo/my-images/225/bladl.jpg/

Uploaded with ImageShack.us

 

edit2:

teraz z samego laptopa korzystalem (bez zewnetrznego monitora) i udalo mi sie wejsc procesy podczas zawieszenia sie:

 

http://imageshack.us/photo/my-images/716/12538038.jpg/

http://imageshack.us/photo/my-images/705/72478771.jpg/

http://imageshack.us/photo/my-images/143/60364685.jpg/

 

jak widac wiele procesow jest zatrzymana, co moze powodowac takie problemy? udalo mi sie szybko zapisac zrzuty i po chwili nie mozna bylo nic robic, po podlaczeniu monitora i wystapieniu bledu (jak na screnia na samej gorze) nie moge wejsc w menadrzera zadan, tylko reset zostaje.

 

edit3:

wkoncu zapisal sie plik .dmp i byl teraz widocnzy bluescrean

http://imageshack.us/photo/my-images/833/20110813118.jpg/

 

logi:

 

Microsoft ® Windows Debugger Version 6.12.0002.633 AMD64

Copyright © Microsoft Corporation. All rights reserved.

 

 

Loading Dump File [C:\Windows\Minidump\081311-21652-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

Executable search path is:

Windows 7 Kernel Version 7600 MP (8 procs) Free x64

Product: WinNt, suite: TerminalServer SingleUserTS Personal

Built by: 7600.16385.amd64fre.win7_rtm.090713-1255

Machine Name:

Kernel base = 0xfffff800`03067000 PsLoadedModuleList = 0xfffff800`032a4e50

Debug session time: Sat Aug 13 14:30:21.048 2011 (UTC + 2:00)

System Uptime: 0 days 0:09:36.110

Loading Kernel Symbols

...............................................................

................................................................

.....................................

Loading User Symbols

Loading unloaded module list

.....

*******************************************************************************

* *

* Bugcheck Analysis *

* *

*******************************************************************************

 

Use !analyze -v to get detailed debugging information.

 

BugCheck D1, {fffff880d1049af0, 2, 1, fffff8800ff89cfa}

 

Unable to load image nvlddmkm.sys, Win32 error 0n2

*** WARNING: Unable to verify timestamp for nvlddmkm.sys

*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys

Probably caused by : nvlddmkm.sys ( nvlddmkm+118cfa )

 

Followup: MachineOwner

---------

 

4: 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: fffff880d1049af0, memory referenced

Arg2: 0000000000000002, IRQL

Arg3: 0000000000000001, value 0 = read operation, 1 = write operation

Arg4: fffff8800ff89cfa, address which referenced memory

 

Debugging Details:

------------------

 

 

WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff8000330f0e0

fffff880d1049af0

 

CURRENT_IRQL: 2

 

FAULTING_IP:

nvlddmkm+118cfa

fffff880`0ff89cfa 4c891cd0 mov qword ptr [rax+rdx*8],r11

 

CUSTOMER_CRASH_COUNT: 1

 

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

 

BUGCHECK_STR: 0xD1

 

PROCESS_NAME: System

 

TRAP_FRAME: fffff88006dacf10 -- (.trap 0xfffff88006dacf10)

NOTE: The trap frame does not contain all registers.

Some register values may be zeroed or incorrect.

rax=fffff88008c4a000 rbx=0000000000000000 rcx=fffffa8005f16b38

rdx=000000001907ff5e rsi=0000000000000000 rdi=0000000000000000

rip=fffff8800ff89cfa rsp=fffff88006dad0a0 rbp=0000000000000000

r8=0000580f7002259c r9=000000000000000f r10=0000000000000000

r11=0000580f7002259c r12=0000000000000000 r13=0000000000000000

r14=0000000000000000 r15=0000000000000000

iopl=0 nv up ei pl nz na pe nc

nvlddmkm+0x118cfa:

fffff880`0ff89cfa 4c891cd0 mov qword ptr [rax+rdx*8],r11 ds:1010:fffff880`d1049af0=????????????????

Resetting default scope

 

LAST_CONTROL_TRANSFER: from fffff800030d8469 to fffff800030d8f00

 

STACK_TEXT:

fffff880`06dacdc8 fffff800`030d8469 : 00000000`0000000a fffff880`d1049af0 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx

fffff880`06dacdd0 fffff800`030d70e0 : fffffa80`0608a010 0000000f`700225f4 00000000`60ba0000 00000000`000e0000 : nt!KiBugCheckDispatch+0x69

fffff880`06dacf10 fffff880`0ff89cfa : 00000000`00001c5d fffffa80`08ee1010 00000000`00000000 fffffa80`08c876e8 : nt!KiPageFault+0x260

fffff880`06dad0a0 00000000`00001c5d : fffffa80`08ee1010 00000000`00000000 fffffa80`08c876e8 fffffa80`05f16b38 : nvlddmkm+0x118cfa

fffff880`06dad0a8 fffffa80`08ee1010 : 00000000`00000000 fffffa80`08c876e8 fffffa80`05f16b38 fffff880`0ff89d76 : 0x1c5d

fffff880`06dad0b0 00000000`00000000 : fffffa80`08c876e8 fffffa80`05f16b38 fffff880`0ff89d76 fffffa80`05f16b38 : 0xfffffa80`08ee1010

 

 

STACK_COMMAND: kb

 

FOLLOWUP_IP:

nvlddmkm+118cfa

fffff880`0ff89cfa 4c891cd0 mov qword ptr [rax+rdx*8],r11

 

SYMBOL_STACK_INDEX: 3

 

SYMBOL_NAME: nvlddmkm+118cfa

 

FOLLOWUP_NAME: MachineOwner

 

MODULE_NAME: nvlddmkm

 

IMAGE_NAME: nvlddmkm.sys

 

DEBUG_FLR_IMAGE_TIMESTAMP: 4d5eb1fc

 

FAILURE_BUCKET_ID: X64_0xD1_nvlddmkm+118cfa

 

BUCKET_ID: X64_0xD1_nvlddmkm+118cfa

 

Followup: MachineOwner

---------

Edytowane 13 Sierpnia 2011 przez x0marko0x

[donald]

Zgraj na pendrav programy ,i formatuj dysk ,jak masz płytkeod producentaz systemem to wgraj ustawienia fabryczne.Powini ci dac Recovery Menager z systemem Windows.

[x0marko0x]

Zgraj na pendrav programy ,i formatuj dysk ,jak masz płytkeod producentaz systemem to wgraj ustawienia fabryczne.Powini ci dac Recovery Menager z systemem Windows.

 

Jezeli chodzi o sterowniki, mialem rozne ze strony della, ze strony nvidi, roze wersje. System byl 3 x instalowany, z oprogramowaniem della (tuz po zakupie laptopa), pozniej z dysku recovery, za trzecim razem dostalem system (wykluczenie mozliwosci ingerencji oprogramowania della?), ktory zainstalowalem i te same problemy wystepowaly. w Poniedzialek laptop trafil do serwisu della, w piatek wrocil w dokumencie ktory przyszedl wraz z laptopem wykryto? wirusa ktory usunieto, sformatowano system i zainstalowano system, lecz nie pozbyli sie glownego problemu ktory mam 3 miesiace.

Robilem testy ktore zalecil konsultant:

Preboot System Assessment (PSA), oraz 32 BIT TEST. Pierwszy trwal ok 30-40 min drugi ponad 7h, oba testy nic nie wykryly, zamienialem rowniez slotami pamieci kazda pojeydnczo w kazdym ze slotow, zawieszal sie.

[bierek]

Dump tworzy się dopiero po restarcie systemu. Dolny problem to coś związanego z kartą graficzną (google tak zidentyfikowało plik), sprawdz czy się nie przegrzewa.