win7 mavi ekran hatası ve sonrasında olanlar

öncelikle merhaba...

siteyi incelediğimde benzer konular açılmış fakat daha farklı bir sorun yaşadığımdan yeni konu açma gereği duyuyorum..aynı konu daha önce açıldı ve gözümden kaçtıysa affola...

sorunuma gelince:

win7 ultimate 32bit işletim sistemi kullanıyorum..bilgisayarım mavi ekran hatası verip kapanıyor..açıldığında cd veya dvd den başlatmak için herhangi bir tuşa basın yazısı çıkıyor..tabi bastığımda cd falan olmadığından öylece kalıyor..bilgisayarı kapatıp tekrar açıyorum..bu defa hata denetimi çıkıyor..f8 e basıp güvenli mod da ya da başka türlü açmaya çalışıyorum yine de olmuyor...

hata denetimi bittiğinde bir hata bulamadığını söylüyor ve tekrar başlatıyor..yeniden açılışta tekrar hata denetimine geçiyor..f8 e basıp hata ayıklama modunu çalıştırdığımda bilgisayar açılıyor..ama işte sorun ondan sonra başlıyor :)

bilgisayar açılıyor fakat kurduğum programlar çalışmıyor ve kaldırdığım programlar ekle/kaldır da duruyor..silmeye çalışırsam dosya bulunamadı diyor ve kaldırmıyor...yani yeniden açıldığında bilgisayar sanki eski tarihli bir geri yükleme noktasına geçiş yapıyor..

bilgisayarı daha önceden aldığım image dosyası yardımıyla tekrar kuruyorum ve öyle hallediyorum sorunu..sorunu hallettikten sonra geri yükleme noktası oluşturuyorum fakat 2-3 gün sonra o oluşturduğum geri yükleme noktası nasıl oluyorsa yok oluyor..işim nedeniyle sürekli kullanmam gerekiyor ve uzun süreli bir tamir sürecine giremiyorum..virüs programı olarak microsoft security essentials-Malwarebytes Anti-Malware-CA Security Center-avg bulunmakta..virüs taramalarında bir şey bulamıyorlar..hepsi birlikte çalışmıyor ama,çakışma durumundan dolayı olduğunu sanmıyorum o yüzden..

dxdiag dosyası ile bilgisayarın tüm özellikleri aşşağıda...lütfen yardımcı olun..çok uzun oldu biliyorum..kusura bakmayın..saygılarımla hoşça kalasınız

DxDiag

System Information
------------------
Time of this report: 11/3/2013, 00:04:21
Machine name: ÖZDEMIR60
Operating System: Windows 7 Ultimate 32-bit (6.1, Build 7601) Service Pack 1 (7601.win7sp1_gdr.130828-1532)
Language: Turkish (Regional Setting: Turkish)
System Manufacturer: ASUSTeK Computer Inc.
System Model: K52JT
BIOS: BIOS Date: 10/30/09 15:13:23 Ver: 08.00.10
Processor: Intel(R) Core(TM) i5 CPU       M 480  @ 2.67GHz (4 CPUs), ~2.7GHz
Memory: 4096MB RAM
Available OS Memory: 3052MB RAM
Page File: 1558MB used, 4542MB available
Windows Dir: C:\Windows
DirectX Version: DirectX 1

Temiz kurulum yapıp. Antivirüs programları kurmayın. Sadece Kaspersky IS yükleyin. Güvenli mod vs gibi gelişmiş seçeneklerden girildiğinde çoğu programlar çalışmadığı için dediğiniz sorunların  oluşması normaldir.

Temiz format attıktan sonra gereksiz programları yüklemedikçe bir sorunla karşılaşmazsınız.

Mümkünse biosu da güncelleyin Leptop modelinizi doğru verdi iseniz;

teşekkürler ilginiz için..

dediğinizi daha önceden yaptım,temiz bir format attım,sonrasında image aldım,yine de değişmemişti durum..hatta formattan sonrada durum değişmeyince araştırma yaptım ve sality adlı virüs nedeniyle benzer sorunların olabileceğini öğrendim..bu virüsü anlatan bir yer de uzantısını ve yaptıkları anlatılmıştı..orada yazanlar doğrultusunda tarama yaptırdım ve gerçekten de o virüsün olduğu ortaya çıktı..çok sevindim,çünkü virüsü sildiğim de sorun düzelecekti..fakat, sırf o virüs için üretilmiş virüs programlarıyla defalarca kez taratma yapmama rağmen ve sonunda silmeme rağmen bu durum değişmedi..virüs silindikten sonra bilgisayarım çok daha iyi oldu fakat mavi ekran gelmesi ve ardından daha önceki bir zamana geri yükleme yapması değişmedi..

bir de format atmak benim için çok büyük bir problem..çünkü elimde ki orijinal windows cd sini kaybettim..işim nedeniyle kullandığım ve her yerde bulunamayacak bir çok program kurulu..onları tekrar bulup kurmak çok zaman alır..patronlar da ne virüsten anlar,ne de programları kuramadım dan.. o yüzden format haricinde yapılabilecek bir şeyler varsa öğrenmek isterim.

tekrar çok teşekkür ederim ilginize..hoşça kalasınız

Sality virüsünü çok iyi bilirim. Format atıp Usb bellek takmadı isen bulaşmamıştır. Eğer taktı isen Dediğim antivirüsü kurup sistemi ve bütün bellek ve diskleri tarat. Mavi ekran için C:windows minidump altında ki dosyalar gerekli bunları burda paylaş v bu durum formattan önce oldu ise ve usb bellek gibi aygıtlar takmadı isen çözüm sağlanabilir.

formatt attmadan önce bir çok harici hard disk ve usb bellek takıldı bilgisayarıma..formattan sonra durum değişmeyince araştırdım ve sality virüsünden haberdar oldum..sonrasında sality virüsünü temizledim..yani öyle umuyorum.."sality killer-win32.sality-ca-avg remover sality " programlarıyla tek tek yaptım taratma işlemini..kendisini gizlediği kayıt defteri uzantısını bu taratmalardan sonra bulamadım ve bilgisayarım oldukça hızlandı ve kasma sorunu ortadan kalktı..ben de silindiğini düşünüyorum açıkcası..

bu arada geçtiğimiz gece, bilgisayarımda daha önceden sildiğim ama program ekle kaldırda durduğunu söylediğim programları silmek için "your uninstaller" adlı programı kurdum..bu program sayesinde bir şeyi farkettim..program ekle kaldırda görünmeyen ama your uninstaller da programlar arasında görünen pc_recovery_.... (noktalı yerlerde sembollerden oluşan bir ismi olduğu için yazamıyorum) bir program mevcut görünüyordu..o programı sildim..sildikten sonra internet explorer hata verdi ve "intalled microsoft fix it" programıyla explorer ı düzelttim..bu işlemden sonra bilgisayarımda geri yükleme noktası oluştu ve herşey normal görünmeye başladı..acaba bu pc_recovery_ adlı programdan dolayı mı bu hatayı alıyordum anlayamadım..

istediğiniz dosyayı buraya koyalıyorum..benim bilgisayar bilgim yeterli değil...umarım siz bir sonuca varabilirsiniz..ilginiz için tekrar çok teşekkür ederim..çok uzun oldu yine kusura bakmayın

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

Loading Dump File [C:\Windows\Minidump\102713-104598-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: *** Invalid ***
****************************************************************************
* Symbol loading may be unreliable without a symbol search path.           *
* Use .symfix to have the debugger choose a symbol path.                   *
* After setting your symbol path, use .reload to refresh symbol locations. *
****************************************************************************
Executable search path is:
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
*                                                                   *
* The Symbol Path can be set by:                                    *
*   using the _NT_SYMBOL_PATH environment variable.                 *
*   using the -y <symbol_path> argument when starting the debugger. *
*   using .sympath and .sympath+                                    *
*********************************************************************
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Kernel base = 0x83045000 PsLoadedModuleList = 0x83185230
Debug session time: Sun Oct 27 01:49:37.102 2013 (GMT+2)
System Uptime: 0 days 0:49:11.132
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
*                                                                   *
* The Symbol Path can be set by:                                    *
*   using the _NT_SYMBOL_PATH environment variable.                 *
*   using the -y <symbol_path> argument when starting the debugger. *
*   using .sympath and .sympath+                                    *
*********************************************************************
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Loading Kernel Symbols
............................................................................................................................................................................................
Loading User Symbols
Loading unloaded module list
.................
Unable to load image AVGIDSFilter.Sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for AVGIDSFilter.Sys
*** ERROR: Module load completed but symbols could not be loaded for AVGIDSFilter.Sys
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000008E, {c0000005, 0, a8b4cb74, 0}

***** Kernel symbols are WRONG. Please fix symbols to do analysis.

*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!KPRCB                                      ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!KPRCB                                      ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
*                                                                   *
* The Symbol Path can be set by:                                    *
*   using the _NT_SYMBOL_PATH environment variable.                 *
*   using the -y <symbol_path> argument when starting the debugger. *
*   using .sympath and .sympath+                                    *
*********************************************************************
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
*                                                                   *
* The Symbol Path can be set by:                                    *
*   using the _NT_SYMBOL_PATH environment variable.                 *
*   using the -y <symbol_path> argument when starting the debugger. *
*   using .sympath and .sympath+                                    *
*********************************************************************
Probably caused by : AVGIDSFilter.Sys ( AVGIDSFilter+2086 )

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

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

KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
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: c0000005, The exception code that was not handled
Arg2: 00000000, The address that the exception occurred at
Arg3: a8b4cb74, Trap Frame
Arg4: 00000000

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

***** Kernel symbols are WRONG. Please fix symbols to do analysis.

*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!KPRCB                                      ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!KPRCB                                      ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
*                                                                   *
* The Symbol Path can be set by:                                    *
*   using the _NT_SYMBOL_PATH environment variable.                 *
*   using the -y <symbol_path> argument when starting the debugger. *
*   using .sympath and .sympath+                                    *
*********************************************************************
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
*                                                                   *
* The Symbol Path can be set by:                                    *
*   using the _NT_SYMBOL_PATH environment variable.                 *
*   using the -y <symbol_path> argument when starting the debugger. *
*   using .sympath and .sympath+                                    *
*********************************************************************

FAULTING_MODULE: 83045000 nt

DEBUG_FLR_IMAGE_TIMESTAMP:  4d53709b

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - 0x%08lx adresindeki y nerge, 0x%08lx bellek adresine ba

FAULTING_IP:
+0
00000000 ??              ???

TRAP_FRAME:  a8b4cb74 -- (.trap 0xffffffffa8b4cb74)
ErrCode = 00000000
eax=a8b4cc00 ebx=00000000 ecx=04871788 edx=0487178c esi=8af3bb50 edi=8b6d1170
eip=00000000 esp=a8b4cbe8 ebp=a8b4cc34 iopl=0         nv up ei ng nz na pe nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010286
00000000 ??              ???
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WRONG_SYMBOLS

BUGCHECK_STR:  0x8E

LAST_CONTROL_TRANSFER:  from a2c17086 to 00000000

STACK_TEXT:  
WARNING: Frame IP not in any known module. Following frames may be wrong.
a8b4cbe4 a2c17086 00000002 a8b4cc00 a9825100 0x0
a8b4cc34 8307402a 8b6d1170 8af3bb50 8af3bb50 AVGIDSFilter+0x2086
a8b4cc4c 83249b9c a9825100 8af3bb50 8af3bdb8 nt+0x2f02a
a8b4cc6c 8325f6f2 8b6d1170 a9825100 00000001 nt+0x204b9c
a8b4cd08 8307a856 8b6d1170 00000000 00000000 nt+0x21a6f2
a8b4cd34 77ae70f4 badb0d00 0224f428 00000000 nt+0x35856
a8b4cd38 badb0d00 0224f428 00000000 00000000 0x77ae70f4
a8b4cd3c 0224f428 00000000 00000000 00000000 0xbadb0d00
a8b4cd40 00000000 00000000 00000000 00000000 0x224f428

STACK_COMMAND:  kb

FOLLOWUP_IP:
AVGIDSFilter+2086
a2c17086 ??              ???

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  AVGIDSFilter+2086

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: AVGIDSFilter

IMAGE_NAME:  AVGIDSFilter.Sys

BUCKET_ID:  WRONG_SYMBOLS

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

1: kd> g
       ^ No runnable debuggees error in 'g'

AVG antivirüsü kaldır. Windows 8.1 format at temiz ve hiçbir usb bellek takma Kaspersky IS yükle tüm bellekleri tal ve tarama yap. Sonra sürücüleri güncelle ve ne yapacaksan yaparsın.

teşekkür ederim..bir çözüm yolu yoksa dediğiniz gibi format atmamız gerekecek sanırım..
ilginiz ve zaman ayırdığınız için sağolun