Yeni Kayıt
Konudaki Resimler
|
Hızlı 
Bildirim
mavi ekran hatası minidump dosyası mevcut
Sıcak Fırsatlarda Tıklananlar
Editörün Seçtiği Fırsatlar
Daha Fazla 
Bu Konudaki Kullanıcılar:
Daha Az 
3 Misafir - 3 Masaüstü
Giriş
Mesaj
-
-
EDIT: Neyse, cahilliğime vermek lazım galiba durumu. Ehil arkadaşlar duruma el atmışlar, bende cahilce yazdıklarımı silip ortadan kayboluyorum. Geçmiş olsun, kolay gelsin.
< Bu mesaj bu kişi tarafından değiştirildi dopac34 -- 5 Haziran 2014; 19:31:58 > -
quote:
Orijinalden alıntı: dopac34
Kullanmış olduğunuz Bitlocker programına ait bir hata iletisi ancak zaten windows u yeni baştan kurmuşsunuz bu durumda hata iletisinin de düzeldiğini varsaymak gerekiyor.
yok kardeş format attıktan sonra verdi bu mavi ekranı bitlocker nedir yararı yoksa sileyim mi -
myo_1433
M
kullanıcısına yanıt
Son zamanlarda yeni bir parça taktın mı?
Bu mavi ekran hatası genelde bozuk veya yerine düzgün oturmamış RAM'lerden kaynaklanır.
Kolay gelsin.. -
quote:
Orijinalden alıntı: Mesafesiz
Son zamanlarda yeni bir parça taktın mı?
Bu mavi ekran hatası genelde bozuk veya yerine düzgün oturmamış RAM'lerden kaynaklanır.
Kolay gelsin..
ram değilde hard disc değişti bayadır yapmıyordu -
myo_1433
M
kullanıcısına yanıt
RAMlar tam oturmamış olabilir kontrol et!
==================================================
Dump File : 060514-21699-01.dmp
Crash Time : 05.06.2014 17:02:53
Bug Check String : PFN_LIST_CORRUPT
Bug Check Code : 0x0000004e
Parameter 1 : 00000000`00000099
Parameter 2 : 00000000`000c317e
Parameter 3 : 00000000`00000002
Parameter 4 : 00000000`000c316b
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+75bc0
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7601.18409 (win7sp1_gdr.140303-2144)
Processor : x64
Crash Address : ntoskrnl.exe+75bc0
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\060514-21699-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7601
Dump File Size : 302.227
Dump File Time : 05.06.2014 17:04:03
==================================================
-
quote:
Orijinalden alıntı: Mesafesiz
RAMlar tam oturmamış olabilir kontrol et!
==================================================
Dump File : 060514-21699-01.dmp
Crash Time : 05.06.2014 17:02:53
Bug Check String : PFN_LIST_CORRUPT
Bug Check Code : 0x0000004e
Parameter 1 : 00000000`00000099
Parameter 2 : 00000000`000c317e
Parameter 3 : 00000000`00000002
Parameter 4 : 00000000`000c316b
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+75bc0
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7601.18409 (win7sp1_gdr.140303-2144)
Processor : x64
Crash Address : ntoskrnl.exe+75bc0
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\060514-21699-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7601
Dump File Size : 302.227
Dump File Time : 05.06.2014 17:04:03
==================================================
kontrol ettim şimdi oturmuşlar sorun yok orada
-
quote:
Orijinalden alıntı: dopac34
Bitlocker programı bir hdd bilgi şifreleme programıdır. Windows 7 ultimate ve enterprase sürümleri ile birlikte gelir ve öyle program ekle kaldır ile kaldırılacak basit bir program değildir. cmd ekranında "scannow/ sfc" yazıp arızalı olduğu varsayılan dosyayı onarmayı deneyin. İşe yaramaz ve ileride yine mavi ekran hataları alırsanız programı kaldırmayı deneyebiliriz ki anladığım kadarı ile aktif hale getirmemişsiniz.
kardeş güzel diyorsunda bende home premıum 64 bit yüklü bu sürümde bitlocker yok zaten olmayan program nasıl mavi ekran hatası verebilir ki ? -
myo_1433
M
kullanıcısına yanıt
Hata vermeye devam ediyorsa RAMları çıkar sil ve yine tak!
Çıkarmışken RAM yuvalarına bir elektrik süpürgesi tututu ver !
Daha ne yapayım
-
quote:
Orijinalden alıntı: Mesafesiz
Hata vermeye devam ediyorsa RAMları çıkar sil ve yine tak!
Çıkarmışken RAM yuvalarına bir elektrik süpürgesi tututu ver !
Daha ne yapayım
tamam dediklerini yaparım bir daha vermedi zaten donanımsal olduğunu düşünmüyorum teşekkürler ilgin için
< Bu mesaj bu kişi tarafından değiştirildi myo_1433 -- 5 Haziran 2014; 18:54:27 > -
quote:
Orijinalden alıntı: dopac34
Windows 7 ile gelen bir uygulama. Burada ayrıntısı mevcut
Ancak windows XP ve Vista ilede kullanımı oluyormuş. Burada ayrıntılı bilgi mevcut. Buda demek oluyor ki ya update yapmışsınız veya orjinal olmayan bir windows kurulum paketi kullanmaktasınız.
Birde anlamadığım nokta acaba bendeki dump dosyasımı arızalı, @Mesafesiz arkadaşımın koyduğu dump analizi ile bendekinin hiç bir alakası yok, crash dump zamanları bile farklı, siz dosyayı nereden bulup indirdiniz?
Microsoft (R) Windows Debugger Version 6.3.9600.17029 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\ARS\Downloads\060514-29016-01 (2).dmp]
Mini Kernel Dump File: Only registers and stack trace are available
************* Symbol Path validation summary **************
Response Time (ms) Location
Deferred SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols
Symbol search path is: SRV*c:\websymbols*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.18409.amd64fre.win7sp1_gdr.140303-2144
Machine Name:
Kernel base = 0xfffff800`02e02000 PsLoadedModuleList = 0xfffff800`03045890
Debug session time: Thu Jun 5 16:54:08.635 2014 (UTC + 3:00)
System Uptime: 0 days 0:20:19.525
Loading Kernel Symbols
.
Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading symbols.
..............................................................
................................................................
......................................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000007E, {ffffffffc0000005, fffff80002e80b80, fffff88003793dc8, fffff88003793620}
Probably caused by : fvevol.sys ( fvevol!FveFilterDeviceControl+1d0 )
Followup: MachineOwner
---------
2: 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: fffff80002e80b80, The address that the exception occurred at
Arg3: fffff88003793dc8, Exception Record Address
Arg4: fffff88003793620, Context Record Address
Debugging Details:
------------------
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - 0x%08lx adresindeki y nerge, 0x%08lx bellek adresine ba
FAULTING_IP:
nt!IofCallDriver+50
fffff800`02e80b80 49ff64c070 jmp qword ptr [r8+rax*8+70h]
EXCEPTION_RECORD: fffff88003793dc8 -- (.exr 0xfffff88003793dc8)
ExceptionAddress: fffff80002e80b80 (nt!IofCallDriver+0x0000000000000050)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff
CONTEXT: fffff88003793620 -- (.cxr 0xfffff88003793620;r)
rax=000000000000000e rbx=fffff88001c3a3b0 rcx=fffffa800b6549d0
rdx=fffffa800d1ff310 rsi=fffffa800d1ff310 rdi=fffffa800b672a90
rip=fffff80002e80b80 rsp=fffff88003794008 rbp=0000000000000001
r8=0063005c00320001 r9=000000000000000e r10=fffff80003007588
r11=fffffa800700b040 r12=fffffa800b672940 r13=fffffa800c3df6a0
r14=0000000000000002 r15=0000000000000001
iopl=0 nv up ei ng nz na pe nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010282
nt!IofCallDriver+0x50:
fffff800`02e80b80 49ff64c070 jmp qword ptr [r8+rax*8+70h] ds:002b:0063005c`003200e1=????????????????
Last set context:
rax=000000000000000e rbx=fffff88001c3a3b0 rcx=fffffa800b6549d0
rdx=fffffa800d1ff310 rsi=fffffa800d1ff310 rdi=fffffa800b672a90
rip=fffff80002e80b80 rsp=fffff88003794008 rbp=0000000000000001
r8=0063005c00320001 r9=000000000000000e r10=fffff80003007588
r11=fffffa800700b040 r12=fffffa800b672940 r13=fffffa800c3df6a0
r14=0000000000000002 r15=0000000000000001
iopl=0 nv up ei ng nz na pe nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010282
nt!IofCallDriver+0x50:
fffff800`02e80b80 49ff64c070 jmp qword ptr [r8+rax*8+70h] ds:002b:0063005c`003200e1=????????????????
Resetting default scope
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
PROCESS_NAME: System
CURRENT_IRQL: 0
ERROR_CODE: (NTSTATUS) 0xc0000005 - 0x%08lx adresindeki y nerge, 0x%08lx bellek adresine ba
EXCEPTION_PARAMETER1: 0000000000000000
EXCEPTION_PARAMETER2: ffffffffffffffff
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800030af100
GetUlongFromAddress: unable to read from fffff800030af1c0
ffffffffffffffff
FOLLOWUP_IP:
fvevol!FveFilterDeviceControl+1d0
fffff880`01c0b808 8bd8 mov ebx,eax
BUGCHECK_STR: 0x7E
ANALYSIS_VERSION: 6.3.9600.17029 (debuggers(dbg).140219-1702) amd64fre
LAST_CONTROL_TRANSFER: from fffff88001c0b808 to fffff80002e80b80
STACK_TEXT:
fffff880`03794008 fffff880`01c0b808 : 00000000`00000000 fffff800`02e88b91 fffff880`03794100 00000000`00000000 : nt!IofCallDriver+0x50
fffff880`03794010 fffff880`01482082 : fffffa80`0d1ff310 00000000`00000000 fffffa80`0d1ff668 fffffa80`0b871190 : fvevol!FveFilterDeviceControl+0x1d0
fffff880`03794080 fffff800`031336da : fffffa80`0b871040 fffffa80`0b871040 00000000`00000000 fffff880`037949f0 : volsnap!VolSnapDeviceControl+0x72
fffff880`037940f0 fffff880`014782c5 : fffffa80`0769aaf0 fffff880`01477cf0 fffffa80`0cfef110 fffffa80`0b871190 : nt!IoVolumeDeviceToDosName+0x92
fffff880`037949c0 fffff880`01477d1c : 00000000`00000001 fffff880`01477cf0 fffffa80`0a436b38 fffffa80`0700b040 : volsnap!VspLogErrorWorker+0x85
fffff880`03794b40 fffff800`02e81261 : fffff880`01477cf0 fffff800`0301d2d8 fffffa80`0700b040 00000000`00000000 : volsnap!VspMediumPriorityWorkItem+0x2c
fffff880`03794b70 fffff800`0311373a : 00000000`00000000 fffffa80`0700b040 00000000`00000080 fffffa80`06f94b30 : nt!ExpWorkerThread+0x111
fffff880`03794c00 fffff800`02e688e6 : fffff880`03589180 fffffa80`0700b040 fffff880`035940c0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`03794c40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: fvevol!FveFilterDeviceControl+1d0
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: fvevol
IMAGE_NAME: fvevol.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 5100a65c
IMAGE_VERSION: 6.1.7601.18062
STACK_COMMAND: .cxr 0xfffff88003793620 ; kb
FAILURE_BUCKET_ID: X64_0x7E_fvevol!FveFilterDeviceControl+1d0
BUCKET_ID: X64_0x7E_fvevol!FveFilterDeviceControl+1d0
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:x64_0x7e_fvevol!fvefilterdevicecontrol+1d0
FAILURE_ID_HASH: {feccb655-e0d9-1e56-b193-28672f9f8c83}
Followup: MachineOwner
---------
2: kd> .time
Debug session time: Thu Jun 5 16:54:08.635 2014 (UTC + 3:00)
System Uptime: 0 days 0:20:19.525
c windows dan bulup yükledim
-
quote:
Orijinalden alıntı: myo_1433
quote:
Orijinalden alıntı: dopac34
Windows 7 ile gelen bir uygulama. Burada ayrıntısı mevcut
Ancak windows XP ve Vista ilede kullanımı oluyormuş. Burada ayrıntılı bilgi mevcut. Buda demek oluyor ki ya update yapmışsınız veya orjinal olmayan bir windows kurulum paketi kullanmaktasınız.
Birde anlamadığım nokta acaba bendeki dump dosyasımı arızalı, @Mesafesiz arkadaşımın koyduğu dump analizi ile bendekinin hiç bir alakası yok, crash dump zamanları bile farklı, siz dosyayı nereden bulup indirdiniz?
Microsoft (R) Windows Debugger Version 6.3.9600.17029 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\ARS\Downloads\060514-29016-01 (2).dmp]
Mini Kernel Dump File: Only registers and stack trace are available
************* Symbol Path validation summary **************
Response Time (ms) Location
Deferred SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols
Symbol search path is: SRV*c:\websymbols*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.18409.amd64fre.win7sp1_gdr.140303-2144
Machine Name:
Kernel base = 0xfffff800`02e02000 PsLoadedModuleList = 0xfffff800`03045890
Debug session time: Thu Jun 5 16:54:08.635 2014 (UTC + 3:00)
System Uptime: 0 days 0:20:19.525
Loading Kernel Symbols
.
Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading symbols.
..............................................................
................................................................
......................................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000007E, {ffffffffc0000005, fffff80002e80b80, fffff88003793dc8, fffff88003793620}
Probably caused by : fvevol.sys ( fvevol!FveFilterDeviceControl+1d0 )
Followup: MachineOwner
---------
2: 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: fffff80002e80b80, The address that the exception occurred at
Arg3: fffff88003793dc8, Exception Record Address
Arg4: fffff88003793620, Context Record Address
Debugging Details:
------------------
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - 0x%08lx adresindeki y nerge, 0x%08lx bellek adresine ba
FAULTING_IP:
nt!IofCallDriver+50
fffff800`02e80b80 49ff64c070 jmp qword ptr [r8+rax*8+70h]
EXCEPTION_RECORD: fffff88003793dc8 -- (.exr 0xfffff88003793dc8)
ExceptionAddress: fffff80002e80b80 (nt!IofCallDriver+0x0000000000000050)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff
CONTEXT: fffff88003793620 -- (.cxr 0xfffff88003793620;r)
rax=000000000000000e rbx=fffff88001c3a3b0 rcx=fffffa800b6549d0
rdx=fffffa800d1ff310 rsi=fffffa800d1ff310 rdi=fffffa800b672a90
rip=fffff80002e80b80 rsp=fffff88003794008 rbp=0000000000000001
r8=0063005c00320001 r9=000000000000000e r10=fffff80003007588
r11=fffffa800700b040 r12=fffffa800b672940 r13=fffffa800c3df6a0
r14=0000000000000002 r15=0000000000000001
iopl=0 nv up ei ng nz na pe nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010282
nt!IofCallDriver+0x50:
fffff800`02e80b80 49ff64c070 jmp qword ptr [r8+rax*8+70h] ds:002b:0063005c`003200e1=????????????????
Last set context:
rax=000000000000000e rbx=fffff88001c3a3b0 rcx=fffffa800b6549d0
rdx=fffffa800d1ff310 rsi=fffffa800d1ff310 rdi=fffffa800b672a90
rip=fffff80002e80b80 rsp=fffff88003794008 rbp=0000000000000001
r8=0063005c00320001 r9=000000000000000e r10=fffff80003007588
r11=fffffa800700b040 r12=fffffa800b672940 r13=fffffa800c3df6a0
r14=0000000000000002 r15=0000000000000001
iopl=0 nv up ei ng nz na pe nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010282
nt!IofCallDriver+0x50:
fffff800`02e80b80 49ff64c070 jmp qword ptr [r8+rax*8+70h] ds:002b:0063005c`003200e1=????????????????
Resetting default scope
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
PROCESS_NAME: System
CURRENT_IRQL: 0
ERROR_CODE: (NTSTATUS) 0xc0000005 - 0x%08lx adresindeki y nerge, 0x%08lx bellek adresine ba
EXCEPTION_PARAMETER1: 0000000000000000
EXCEPTION_PARAMETER2: ffffffffffffffff
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800030af100
GetUlongFromAddress: unable to read from fffff800030af1c0
ffffffffffffffff
FOLLOWUP_IP:
fvevol!FveFilterDeviceControl+1d0
fffff880`01c0b808 8bd8 mov ebx,eax
BUGCHECK_STR: 0x7E
ANALYSIS_VERSION: 6.3.9600.17029 (debuggers(dbg).140219-1702) amd64fre
LAST_CONTROL_TRANSFER: from fffff88001c0b808 to fffff80002e80b80
STACK_TEXT:
fffff880`03794008 fffff880`01c0b808 : 00000000`00000000 fffff800`02e88b91 fffff880`03794100 00000000`00000000 : nt!IofCallDriver+0x50
fffff880`03794010 fffff880`01482082 : fffffa80`0d1ff310 00000000`00000000 fffffa80`0d1ff668 fffffa80`0b871190 : fvevol!FveFilterDeviceControl+0x1d0
fffff880`03794080 fffff800`031336da : fffffa80`0b871040 fffffa80`0b871040 00000000`00000000 fffff880`037949f0 : volsnap!VolSnapDeviceControl+0x72
fffff880`037940f0 fffff880`014782c5 : fffffa80`0769aaf0 fffff880`01477cf0 fffffa80`0cfef110 fffffa80`0b871190 : nt!IoVolumeDeviceToDosName+0x92
fffff880`037949c0 fffff880`01477d1c : 00000000`00000001 fffff880`01477cf0 fffffa80`0a436b38 fffffa80`0700b040 : volsnap!VspLogErrorWorker+0x85
fffff880`03794b40 fffff800`02e81261 : fffff880`01477cf0 fffff800`0301d2d8 fffffa80`0700b040 00000000`00000000 : volsnap!VspMediumPriorityWorkItem+0x2c
fffff880`03794b70 fffff800`0311373a : 00000000`00000000 fffffa80`0700b040 00000000`00000080 fffffa80`06f94b30 : nt!ExpWorkerThread+0x111
fffff880`03794c00 fffff800`02e688e6 : fffff880`03589180 fffffa80`0700b040 fffff880`035940c0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`03794c40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: fvevol!FveFilterDeviceControl+1d0
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: fvevol
IMAGE_NAME: fvevol.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 5100a65c
IMAGE_VERSION: 6.1.7601.18062
STACK_COMMAND: .cxr 0xfffff88003793620 ; kb
FAILURE_BUCKET_ID: X64_0x7E_fvevol!FveFilterDeviceControl+1d0
BUCKET_ID: X64_0x7E_fvevol!FveFilterDeviceControl+1d0
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:x64_0x7e_fvevol!fvefilterdevicecontrol+1d0
FAILURE_ID_HASH: {feccb655-e0d9-1e56-b193-28672f9f8c83}
Followup: MachineOwner
---------
2: kd> .time
Debug session time: Thu Jun 5 16:54:08.635 2014 (UTC + 3:00)
System Uptime: 0 days 0:20:19.525
c windows dan bulup yükledim
ARKADAŞIM SENİN DERDİN NE? SORUN ÇÖZÜLDÜ!
Sayfa:
1
Ip işlemleri
Bu mesaj IP'si ile atılan mesajları ara Bu kullanıcının son IP'si ile atılan mesajları ara Bu mesaj IP'si ile kullanıcı ara Bu kullanıcının son IP'si ile kullanıcı ara
KAPAT X
Bu mesaj IP'si ile atılan mesajları ara Bu kullanıcının son IP'si ile atılan mesajları ara Bu mesaj IP'si ile kullanıcı ara Bu kullanıcının son IP'si ile kullanıcı ara
KAPAT X
