Var hocam. dmp sanırım Minidump dosyası. Yalnız yanında 4 tane daha klasör var ve bazısında 0, bazısında 4, bazısında 1 tane. dmp dosyası var. Hepsini güvenilir bir siteye upload edip yeni bir konu mu açayım? Bir de DVD slotunu kullanmıyoruz HDD'yi onun yerine taksak sorunum düzelir mi?

Normaldir aralarından 1 tanesi Memory Dump dosyası olduğundan. O büyük olan dosyayı paylaşmayın. Küçük boyutlu olanları paylaşın.

Veri aktarım hatalarının çözümü SATA kablosunu değiştirmek ama laptop olduğu için yapamazsınız. Bu hata dışında diskin bir sorunu yok.

HD Tune 5.75 ile Health sekmesinin fotoğrafını paylaşınız. Gezginler çöplüğünden indirmeyin. Sesin HDD ile alakası yok.

HDD ölmüş olmalı.

Herkese merhaba. Kardeşim EBA Canlı Ders'ten ders dinliyordu ve birden videodaki gibi ses çıkmaya başladı. Sesin HDD'den geldiğini tahmin ediyorum. Bataryayla olan bağlantıyı kestikten sonra ses durdu, ben de tekrar bilgisayarı tekrar açtım ve hemen HDD sağlığını test ettim. Grafik bayağı bir dalgalı gibi. Son bir aydır falan Word-Excel'i bile açmak işkence oluyordu, Daha 6 gün önce sağlık bölümünde bir sorun yokken şimdi 2 tane sorun bulmuş. Error scan bölümünde sorun yok. Bu sorunu bir daha yaşar mıyım, HDD çöp olmuş mu? Bu içeriği görüntülemek için üçüncü taraf çerezlerini yerleştirmek için izninize ihtiyacımız olacak. Daha detaylı bilgi için, çerezler sayfamıza bakınız. Üçüncü taraf çerezlerini kabul et

Hocam içini açıp yapabileceksem yaparım. Yani HDD'de sorun yok kabloda mı var? Eğer öyleyse sevindim açıkçası.

Siyah ekran ve ses sorununuz çözüldü mü?

RAM'e test yapmak aklıma gelmemişti, sağolun. Memtest ile bellekleri kontrol ediyorum.

Kaspersky'ı kaldırdım. Sistem geri yükleme noktası oluşturarak ve güvenli modda her iki ekran kartı sürücüsünü de DDU ile kaldırdım. Yalnız ekran kartı modelini hatırlamıyorum, aygıt yöneticisi ve dxdiag'da da gözükmüyor. Microsoft Temel Görüntü Bağdaştırıcısı gibi bir şey vardı sanırım. Driver'ı nasıl yükleyeceğim?

AMD'nin sitesinde olan sürücü güncelleştirme programını deneyin. Olmadı donanım kimliklerini paylaşınız.

Yukarıda paylaşmıştım. Orijinal sitesinden trial versiyonunun indirdim.

Sonucu bu mesajımdan sonra yazın. Üst üste mesaj atınca bildirim gelmiyor bana o yüzden.

Bir daha olmazsa anlayabilirsiniz sadece. Daha eskiden oluşan dosyalarda vardı attığınız dosyalardan sadece bugüne ait dosyalar yoktu. Daha önceden de böyle bir sorun yaşadığınızı düşünüyorum.

Bu eski sürümü olan 2.55. Yenisi 5.75 sürümü. Olmadı HDD Sentinel ile diskin sağlık durumunu paylaşınız. Trial versiyonu eski sürüm olandır. Pro yeni sürümü. Varsa Minidump dosyalarını paylaşınız. Minidump Dosyalarını Paylaşın Minidump dosyaları, bilgisayarınız mavi ekran verdiğinde belleğin ufak bir dökümünü barındıran dosyalardır. Bunları analiz ederek mavi ekran hatalarının nedenini öğrenebiliriz. Minidump dosyaları C:\Windows\Minidump klasöründe bulunur ve DMP uzantılıdır. Bu dosyaları sizden istediğimizde... www.technopat.net

İnternetten model adını -HP 250 G5- yazınca M330 ekran kartı olduğunu öğrendim ve şu an yine de sürücü güncelleştirme programını yüklüyorum. Intel'in de otomatik sürücü güncelleştirme programı varmış onu da yüklüyorum. İlginiz için teşekkürler.

Hocam sorunun duzeldigini nasıl anlayacagim? O siyah ekran canlı dersteyken bir kere geldi ondan sonra HDD hatası çıktı.

Daha önceden Windows güncellemesi 3 saati geçince ve hicbir işlem yapılamayinca gücü kesmiştim sinirden. O olabilir haklısınız. İlginiz için tekrardan teşekkürler, HD Tune'un bulduğu o iki hatanın çözümü için de HDD'nin DVD portuna takılması gerektigini söylediniz değil mi? Yanlış anlamadım umarım. Yarın onunla detaylıca ilgileneceğim, basarili olursam rehber bile yapabilirim

HDD'ler darbe ile bozulmaya müsait parçalar. Dükkandaki 3. sistemdeki HDD çok fazla darbeye maruz kaldı ve elektrik kesintileride dahil. O yüzden ses sorunlu bir HDD. Kasayla temassız şekilde süngerle monte ettiğim için ses bir nebze azaldı. Tabii laptop olduğu için öyle bir şey yapma şansınız yok maalesef.

Kaspersky güncelleyin güncelse kaldırın. Intel ve AMD ekran kartı sorun çıkarmış DDU ile sürücülerini kaldırıp güncelini yükleyiniz ikisi için. USB ile ilgili hatalarda görünüyor USB girişi bozuk olabilir. Rehber: DDU ile Sürücü Kaldırma Rehberi Display Driver Uninstaller , zamanla bilgisayara takılan farklı monitörler, üst üste güncellenen sürücüler ve Windows güncellemeleri sonrası biriken kayıt defteri ve sürücü dosyalarını silerek temiz bir sürücü kurulumunun yolunu açan kullanışlı bir araçtır. Adım adım sürücü temizliği... www.technopat.net Sürprizbozan: Hata kodu Kod:Panoya kopyala Bugcheck Analysis VIDEO_ENGINE_TIMEOUT_DETECTED (141) One of the the display engines failed to respond in timely fashion. Arguments: Arg1: ffffb105f1292460, Optional pointer to internal TDR recovery context . Arg2: fffff80641cba550, The pointer into responsible device driver module . Arg3: 0000000000000000, The secondary driver specific bucketing key. Arg4: 00000000000007b4, Optional internal context dependent data. Debugging Details: Unable to load image igdkmd64. sys, Win32 error 0n2 WARNING: Unable to verify timestamp for igdkmd64. sys KEY_VALUES_STRING: 1 Key : Analysis. CPU. mSec Value: 3390 Key : Analysis. DebugAnalysisProvider. CPP Value: Create: 8007007e on DESKTOP-J7A11VA Key : Analysis. DebugData Value: CreateObject Key : Analysis. DebugModel Value: CreateObject Key : Analysis. Elapsed. mSec Value: 5444 Key : Analysis. Memory. CommitPeak. Mb Value: 85 Key : Analysis. System Value: CreateObject ADDITIONAL_XML: 1 OS_BUILD_LAYERS: 1 DUMP_FILE_ATTRIBUTES: 0x18 Kernel Generated Triage Dump Live Generated Dump BUGCHECK_CODE: 141 BUGCHECK_P1: ffffb105f1292460 BUGCHECK_P2: fffff80641cba550 BUGCHECK_P3: 0 BUGCHECK_P4: 7b4 TAG_NOT_DEFINED_202b: Unknown TAG in analysis list 202b PROCESS_NAME: System STACK_TEXT: ffffc180`b734f510 fffff806`3d2f0ea0 : ffffb105`f1292460 ffffc180`b734f780 ffffb105`f1292460 ffffb105`e81ec770 : watchdog! WdpDbgCaptureTriageDump+0x64a ffffc180`b734f5c0 fffff806`3d190fe9 : 00000000`00000004 ffffb105`e4888000 ffffb105`e488f8f0 ffffb105`e48bb000 : watchdog! WdDbgReportRecreate+0xd0 ffffc180`b734f620 fffff806`47c312a9 : ffffb105`00000000 ffffb105`ea55b030 ffffb105`f1292460 ffffb105`e48bb000 : dxgkrnl! TdrUpdateDbgReport+0x119 ffffc180`b734f680 fffff806`47cd17a5 : ffffb105`e48bb000 00000000`00000000 ffffb105`e4888000 ffffb105`e48bb001 : dxgmms2! VidSchiResetEngine+0x709 ffffc180`b734f830 fffff806`47ca53db : ffffb105`e4888000 00000000`00000001 00000000`00000000 00000000`00000000 : dxgmms2! VidSchiResetEngines+0xb1 ffffc180`b734f880 fffff806`47c7d252 : ffffc180`b734f901 00000000`01383116 00000000`00989680 00000000`00000001 : dxgmms2! VidSchiCheckHwProgress+0x2815b ffffc180`b734f8f0 fffff806`47c0b9ca : ffffb105`e9b0cbb0 ffffb105`e4888000 ffffc180`b734fa19 00000000`00989680 : dxgmms2! VidSchiWaitForSchedulerEvents+0x372 ffffc180`b734f9c0 fffff806`47c8ad45 : ffffb105`eb3b2900 ffffb105`e4888000 ffffb105`eb3b2920 ffffb105`e0541920 : dxgmms2! VidSchiScheduleCommandToRun+0x2ca ffffc180`b734fa80 fffff806`47c8acfa : ffffb105`e4888400 fffff806`47c8ac30 ffffb105`e4888000 fffff806`20d5f100 : dxgmms2! VidSchiRun_PriorityTable+0x35 ffffc180`b734fad0 fffff806`25ea2ae5 : ffffb105`e3dec280 fffff806`00000001 ffffb105`e4888000 000fa4ef`b59bbfff : dxgmms2! VidSchiWorkerThread+0xca ffffc180`b734fb10 fffff806`25ffbbf8 : fffff806`20d5f180 ffffb105`e3dec280 fffff806`25ea2a90 00000000`00000000 : nt! PspSystemThreadStartup+0x55 ffffc180`b734fb60 00000000`00000000 : ffffc180`b7350000 ffffc180`b7349000 00000000`00000000 00000000`00000000 : nt! KiStartSystemThread+0x28 SYMBOL_NAME: igdkmd64+3a550 MODULE_NAME: igdkmd64 IMAGE_NAME: igdkmd64. sys STACK_COMMAND: . thread ; . cxr ; kb FAILURE_BUCKET_ID: LKD_0x141_IMAGE_igdkmd64. sys OSPLATFORM_TYPE: x64 OSNAME: Windows 10 FAILURE_ID_HASH: Followup: MachineOwner Bugcheck Analysis VIDEO_ENGINE_TIMEOUT_DETECTED (141) One of the the display engines failed to respond in timely fashion. Arguments: Arg1: ffffca0fc1260010, Optional pointer to internal TDR recovery context . Arg2: fffff8037edda7b0, The pointer into responsible device driver module . Arg3: 0000000000000000, The secondary driver specific bucketing key. Arg4: 0000000000000a54, Optional internal context dependent data. Debugging Details: Unable to load image amdkmdag. sys, Win32 error 0n2 WARNING: Unable to verify timestamp for amdkmdag. sys KEY_VALUES_STRING: 1 Key : Analysis. CPU. mSec Value: 3327 Key : Analysis. DebugAnalysisProvider. CPP Value: Create: 8007007e on DESKTOP-J7A11VA Key : Analysis. DebugData Value: CreateObject Key : Analysis. DebugModel Value: CreateObject Key : Analysis. Elapsed. mSec Value: 5559 Key : Analysis. Memory. CommitPeak. Mb Value: 85 Key : Analysis. System Value: CreateObject ADDITIONAL_XML: 1 OS_BUILD_LAYERS: 1 DUMP_FILE_ATTRIBUTES: 0x18 Kernel Generated Triage Dump Live Generated Dump BUGCHECK_CODE: 141 BUGCHECK_P1: ffffca0fc1260010 BUGCHECK_P2: fffff8037edda7b0 BUGCHECK_P3: 0 BUGCHECK_P4: a54 TAG_NOT_DEFINED_202b: Unknown TAG in analysis list 202b PROCESS_NAME: System STACK_TEXT: fffff502`7e83f510 fffff803`75240ea0 : ffffca0f`c1260010 fffff502`7e83f780 ffffca0f`c1260010 ffffca0f`c25b1260 : watchdog! WdpDbgCaptureTriageDump+0x64a fffff502`7e83f5c0 fffff803`750e0db9 : 00000000`00000005 ffffca0f`bffe0000 ffffca0f`c002d540 ffffca0f`c0029000 : watchdog! WdDbgReportRecreate+0xd0 fffff502`7e83f620 fffff803`79ec1369 : ffffca0f`00000000 ffffca0f`c66ea030 ffffca0f`c1260010 ffffca0f`c0029000 : dxgkrnl! TdrUpdateDbgReport+0x119 fffff502`7e83f680 fffff803`79f61615 : ffffca0f`c0029000 00000000`00000000 ffffca0f`bffe0000 ffffca0f`c0029001 : dxgmms2! VidSchiResetEngine+0x709 fffff502`7e83f830 fffff803`79f3524b : ffffca0f`bffe0000 00000000`00000001 00000000`00000000 00000000`00000000 : dxgmms2! VidSchiResetEngines+0xb1 fffff502`7e83f880 fffff803`79f0d0c2 : fffff502`7e83f901 00000000`00031c4a 00000000`00989680 00000000`00000010 : dxgmms2! VidSchiCheckHwProgress+0x2815b fffff502`7e83f8f0 fffff803`79e9b9ca : ffffca0f`bff804e0 ffffca0f`bffe0000 fffff502`7e83fa19 00000000`00989680 : dxgmms2! VidSchiWaitForSchedulerEvents+0x372 fffff502`7e83f9c0 fffff803`79f1abb5 : ffffca0f`c9dee700 ffffca0f`bffe0000 ffffca0f`c9dee740 ffffca0f`c502b920 : dxgmms2! VidSchiScheduleCommandToRun+0x2ca fffff502`7e83fa80 fffff803`79f1ab6a : ffffca0f`bffe0400 fffff803`79f1aaa0 ffffca0f`bffe0000 ffff9d01`9eda8100 : dxgmms2! VidSchiRun_PriorityTable+0x35 fffff502`7e83fad0 fffff803`5ce66dd5 : ffffca0f`bff75500 fffff803`00000001 ffffca0f`bffe0000 000fa4ef`b59bbfff : dxgmms2! VidSchiWorkerThread+0xca fffff502`7e83fb10 fffff803`5cffb4f8 : ffff9d01`9eda8180 ffffca0f`bff75500 fffff803`5ce66d80 00000000`00000000 : nt! PspSystemThreadStartup+0x55 fffff502`7e83fb60 00000000`00000000 : fffff502`7e840000 fffff502`7e839000 00000000`00000000 00000000`00000000 : nt! KiStartSystemThread+0x28 SYMBOL_NAME: amdkmdag+aa7b0 MODULE_NAME: amdkmdag IMAGE_NAME: amdkmdag. sys STACK_COMMAND: . thread ; . cxr ; kb FAILURE_BUCKET_ID: LKD_0x141_IMAGE_amdkmdag. sys OSPLATFORM_TYPE: x64 OSNAME: Windows 10 FAILURE_ID_HASH: Followup: MachineOwner Bugcheck Analysis VIDEO_DXGKRNL_LIVEDUMP (193) Livedumps triggered by dxgkrnl Arguments: Arg1: 0000000000000810, Reason Code. 100 Internal Arg2: ffffb583dec24000, Reserved. Arg3: ffffb583da135040, Reserved. Arg4: 000000000000023c, Reserved. Debugging Details: WARNING: Unable to verify timestamp for win32k. sys KEY_VALUES_STRING: 1 Key : Analysis. CPU. mSec Value: 10577 Key : Analysis. DebugAnalysisProvider. CPP Value: Create: 8007007e on DESKTOP-J7A11VA Key : Analysis. DebugData Value: CreateObject Key : Analysis. DebugModel Value: CreateObject Key : Analysis. Elapsed. mSec Value: 49399 Key : Analysis. Memory. CommitPeak. Mb Value: 85 Key : Analysis. System Value: CreateObject Key : WER. OS. Branch Value: vb_release Key : WER. OS. Timestamp Value: 2019-12-06T14:06:00Z Key : WER. OS. Version Value: 10.0.19041.1 ADDITIONAL_XML: 1 OS_BUILD_LAYERS: 1 DUMP_FILE_ATTRIBUTES: 0x10 Live Generated Dump BUGCHECK_CODE: 193 BUGCHECK_P1: 810 BUGCHECK_P2: ffffb583dec24000 BUGCHECK_P3: ffffb583da135040 BUGCHECK_P4: 23c PROCESS_NAME: System STACK_TEXT: fffffe08`80994fc0 fffff804`29b8da6a : ffffffff`ffffffff fffffe08`80995060 00000000`00000000 00000000`00000000 : nt! IopLiveDumpEndMirroringCallback+0xb4 fffffe08`80995010 fffff804`29ba8dc3 : 00000000`00000000 00000000`00000000 ffffb583`dd50f700 ffffb583`dd50f700 : nt! MmDuplicateMemory+0x2be fffffe08`809950a0 fffff804`29a9393f : ffffb583`dd50f700 ffffb583`dd50f700 00000000`00000000 00000000`00000000 : nt! IopLiveDumpCaptureMemoryPages+0x9f fffffe08`809951f0 fffff804`296e8b07 : 00000000`00000000 ffffdd0e`fbb7c6d0 00000000`00000000 7fffb583`e4479d60 : nt! IoCaptureLiveDump+0x3e7 fffffe08`809953d0 fffff804`29a5e6dc : ffffb583`00000022 ffffffff`80002d64 00000000`00000000 ffffb583`e4479ce0 : nt! DbgkCaptureLiveKernelDump+0x2ef fffffe08`80995460 fffff804`296058b5 : 00000000`00000025 fffffe08`809957b0 ffffffff`00000040 00000000`00000000 : nt! NtSystemDebugControl+0xacf4c fffffe08`80995570 fffff804`295f7d00 : fffff804`437a54af ffffb583`e50f4ce0 fffff804`437b213a ffffffff`800043a0 : nt! KiSystemServiceCopyEnd+0x25 fffffe08`80995778 fffff804`437a54af : ffffb583`e50f4ce0 fffff804`437b213a ffffffff`800043a0 ffffb583`e50f4a30 : nt! KiServiceLinkage fffffe08`80995780 fffff804`437b0ebf : ffffb583`dec24000 fffffe08`80995a60 ffffb583`d2ae6cf0 fffffe08`80995a60 : watchdog! WdpDbgCaptureKernelDump+0x73 fffffe08`80995800 fffff804`437b0d7d : 00000000`00000000 00000000`00000000 ffffb583`e2031040 00000000`00000000 : watchdog! WdDbgReportRecreate+0xef fffffe08`80995860 fffff804`4360bf8f : 00000000`00000000 fffffe08`80995a60 00000000`00000010 fffff804`4360bf50 : watchdog! WdDbgReportCreate+0x3d fffffe08`809958c0 fffff804`435f98fe : ffffb583`dec24000 fffffe08`80995a60 ffffb583`d2ae6cf0 00000000`00000018 : dxgkrnl! DxgCreateLiveDumpWithWdLogs+0x3f fffffe08`80995910 fffff804`294c1f15 : ffffb583`e2031040 fffff804`2e8a2c60 ffffb583`d2ae6cf0 fffff804`00000000 : dxgkrnl! ProcessDeadlockThread+0x4e fffffe08`80995a70 fffff804`29466dd5 : ffffb583`e2031040 00000000`00000080 ffffb583`d2b02080 00000000`00000000 : nt! ExpWorkerThread+0x105 fffffe08`80995b10 fffff804`295fb4f8 : ffffc900`85fc0180 ffffb583`e2031040 fffff804`29466d80 00000000`00000246 : nt! PspSystemThreadStartup+0x55 fffffe08`80995b60 00000000`00000000 : fffffe08`80996000 fffffe08`8098f000 00000000`00000000 00000000`00000000 : nt! KiStartSystemThread+0x28 SYMBOL_NAME: dxgkrnl! DxgCreateLiveDumpWithWdLogs+3f MODULE_NAME: dxgkrnl IMAGE_NAME: dxgkrnl. sys IMAGE_VERSION: 10.0.19041.508 STACK_COMMAND: . thread ; . cxr ; kb BUCKET_ID_FUNC_OFFSET: 3f FAILURE_BUCKET_ID: LKD_0x193_dxgkrnl! DxgCreateLiveDumpWithWdLogs OS_VERSION: 10.0.19041.1 BUILDLAB_STR: vb_release OSPLATFORM_TYPE: x64 OSNAME: Windows 10 FAILURE_ID_HASH: Followup: MachineOwner Bugcheck Analysis PDC_LOCK_WATCHDOG_LIVEDUMP (17c) A thread has been holding the PDC lock for too long Arguments: Arg1: ffff868836797040, The thread holding the PDC lock. Arg2: 0000000000007530, Lock watchdog timeout in milliseconds. Arg3: 0000000000000000, Reserved. Arg4: 0000000000000000, Reserved. Debugging Details: WARNING: Unable to verify timestamp for win32k. sys KEY_VALUES_STRING: 1 Key : Analysis. CPU. mSec Value: 6046 Key : Analysis. DebugAnalysisProvider. CPP Value: Create: 8007007e on DESKTOP-J7A11VA Key : Analysis. DebugData Value: CreateObject Key : Analysis. DebugModel Value: CreateObject Key : Analysis. Elapsed. mSec Value: 31241 Key : Analysis. Memory. CommitPeak. Mb Value: 79 Key : Analysis. System Value: CreateObject Key : WER. OS. Branch Value: vb_release Key : WER. OS. Timestamp Value: 2019-12-06T14:06:00Z Key : WER. OS. Version Value: 10.0.19041.1 ADDITIONAL_XML: 1 OS_BUILD_LAYERS: 1 DUMP_FILE_ATTRIBUTES: 0x10 Live Generated Dump BUGCHECK_CODE: 17c BUGCHECK_P1: ffff868836797040 BUGCHECK_P2: 7530 BUGCHECK_P3: 0 BUGCHECK_P4: 0 PROCESS_NAME: System STACK_TEXT: ffffd78b`d82b7510 fffff801`6d7a1cdd : ffffffff`ffffffff ffffd78b`d82b75b0 00000000`00000000 ffffd78b`d82b7658 : nt! IopLiveDumpEndMirroringCallback+0xb4 ffffd78b`d82b7560 fffff801`6d7b8f23 : 00000000`00000000 00000000`00000000 ffff8688`45e332e0 ffff8688`45e332e0 : nt! MmDuplicateMemory+0x261 ffffd78b`d82b75f0 fffff801`6d6a2b0f : ffff8688`45e332e0 ffff8688`45e332e0 ffffd78b`d82b7988 00000000`00000000 : nt! IopLiveDumpCaptureMemoryPages+0x9f ffffd78b`d82b7740 fffff801`6d6954ec : 00000000`00000000 ffffc70d`af7f1970 ffffc70d`af88c850 ffffc70d`af7f1970 : nt! IoCaptureLiveDump+0x3e7 ffffd78b`d82b7920 fffff801`6d695d1c : ffffffff`80001a34 00000000`00000000 00000000`00000000 00000000`0000017c : nt! DbgkpWerCaptureLiveFullDump+0x14c ffffd78b`d82b7980 fffff801`6d69532d : 00000000`00000002 00000000`00000000 fffff801`6fc687e8 ffff8688`00000000 : nt! DbgkpWerProcessPolicyResult+0x30 ffffd78b`d82b79b0 fffff801`6fc79eab : ffff8688`44a24040 fffff801`6fc79e60 ffff8688`367cd560 fffff801`6d0df08c : nt! DbgkWerCaptureLiveKernelDump+0x1dd ffffd78b`d82b7a10 fffff801`6d033f45 : ffff8688`44a24040 fffff801`6d0def90 ffff8688`367cd560 ffff8688`00000000 : pdc! PdcpLockWatchdogWorkerRoutine+0x4b ffffd78b`d82b7a70 fffff801`6d146745 : ffff8688`44a24040 00000000`00000080 ffff8688`366b20c0 00000000`00000001 : nt! ExpWorkerThread+0x105 ffffd78b`d82b7b10 fffff801`6d1e5598 : ffffab81`9dfb6180 ffff8688`44a24040 fffff801`6d1466f0 00000000`00000246 : nt! PspSystemThreadStartup+0x55 ffffd78b`d82b7b60 00000000`00000000 : ffffd78b`d82b8000 ffffd78b`d82b1000 00000000`00000000 00000000`00000000 : nt! KiStartSystemThread+0x28 SYMBOL_NAME: pdc! PdcpLockWatchdogWorkerRoutine+4b MODULE_NAME: pdc IMAGE_NAME: pdc. sys IMAGE_VERSION: 10.0.19041.329 STACK_COMMAND: . thread ; . cxr ; kb BUCKET_ID_FUNC_OFFSET: 4b FAILURE_BUCKET_ID: LKD_0x17C_pdc! PdcpLockWatchdogWorkerRoutine OS_VERSION: 10.0.19041.1 BUILDLAB_STR: vb_release OSPLATFORM_TYPE: x64 OSNAME: Windows 10 FAILURE_ID_HASH: Followup: MachineOwner Bugcheck Analysis BUGCODE_USB3_DRIVER (144) This bugcheck usually happens when the USB3 core stack detects an invalid operation being performed by a USB client. This bugcheck may also occur due to hardware failure on a USB Boot Device. Arguments: Arg1: 0000000000003003, USB3_WER_BUGCODE_USBHUB3_DEVICE_ENUMERATION_FAILURE A USB device failed enumeration. Arg2: ffffef0d9e7075b0, USBHUB3_LIVEDUMP_CONTEXT Arg3: 0000000040010000, 0 Arg4: 0000000000000000, 0 Debugging Details: KEY_VALUES_STRING: 1 Key : Analysis. CPU. mSec Value: 5093 Key : Analysis. DebugAnalysisProvider. CPP Value: Create: 8007007e on DESKTOP-J7A11VA Key : Analysis. DebugData Value: CreateObject Key : Analysis. DebugModel Value: CreateObject Key : Analysis. Elapsed. mSec Value: 5488 Key : Analysis. Memory. CommitPeak. Mb Value: 81 Key : Analysis. System Value: CreateObject ADDITIONAL_XML: 1 OS_BUILD_LAYERS: 1 DUMP_FILE_ATTRIBUTES: 0x18 Kernel Generated Triage Dump Live Generated Dump BUGCHECK_CODE: 144 BUGCHECK_P1: 3003 BUGCHECK_P2: ffffef0d9e7075b0 BUGCHECK_P3: 40010000 BUGCHECK_P4: 0 PROCESS_NAME: System STACK_TEXT: ffffef0d`9e707030 fffff802`2954ccf9 : 00000000`00000013 00000000`00000000 fffff802`2956e9dc 00000000`00000000 : UsbHub3! TelemetryData_CreateReport+0xcc ffffef0d`9e707560 fffff802`29540eb9 : 00000000`00000000 00000000`00000001 fffff802`29524760 00000000`00000000 : UsbHub3! WER_CreateReport+0x279 ffffef0d`9e707630 fffff802`29529a09 : ffffb406`bfe9b350 ffffb406`c22a20d0 00000000`000003e8 00000000`00000000 : UsbHub3! HUBMISC_CreateWerReport+0x179 ffffef0d`9e7076d0 fffff802`29530de0 : 00000000`00000004 ffffef0d`9e707888 00000000`00000fed ffffef0d`9e707890 : UsbHub3! HUBPDO_ReportDeviceFailure+0x209 ffffef0d`9e707810 fffff802`2951a737 : 00000000`00000fed fffff802`2951a596 00000000`000011cf fffff802`29535a07 : UsbHub3! HUBDSM_MarkingUnknownDeviceAsFailed+0x10 ffffef0d`9e707840 fffff802`2951bafe : ffffb406`00000fa0 00000000`00000fed ffffef0d`00000fa0 fffff802`29576b80 : UsbHub3! HUBSM_ExecuteEntryFunctionsAndPushPopStateMachinesForCurrentState+0x87 ffffef0d`9e7078e0 fffff802`2951af59 : 00000000`00000fed 00000000`00000f00 00000000`00000fa0 fffff802`29576b01 : UsbHub3! HUBSM_RunStateMachine+0x5f2 ffffef0d`9e707960 fffff802`28aaa770 : ffffb406`c770e310 fffff802`2951ae00 ffffb406`bfee8760 fffff802`2951aeb0 : UsbHub3! HUBSM_EvtSmWorkItem+0xa9 ffffef0d`9e7079a0 fffff802`28aaa6f9 : ffffb406`cd187b50 ffffb406`bfee8760 ffffb406`cd58f040 fffff802`28aaa6f0 : ucx01000! Controller_ForwardProgressWorkItemCallback+0x60 ffffef0d`9e7079d0 fffff802`0a8d9cd3 : 00000000`00000000 ffffb406`cd187b50 ffffb406`bfee8760 fffff802`246e53c0 : ucx01000! Controller_ForwardProgressWorkItemWdmCallback+0x9 ffffef0d`9e707a00 fffff802`0a833f45 : ffffb406`ce365040 ffffb406`ce365040 fffff802`0a8d9c40 00020001`00000000 : nt! IopProcessWorkItem+0x93 ffffef0d`9e707a70 fffff802`0a946745 : ffffb406`ce365040 00000000`00000080 ffffb406`b770b100 ef0d9ce2`9000ffff : nt! ExpWorkerThread+0x105 ffffef0d`9e707b10 fffff802`0a9e5598 : ffffda81`dba9c180 ffffb406`ce365040 fffff802`0a9466f0 7ffcac7f`cea00000 : nt! PspSystemThreadStartup+0x55 ffffef0d`9e707b60 00000000`00000000 : ffffef0d`9e708000 ffffef0d`9e701000 00000000`00000000 00000000`00000000 : nt! KiStartSystemThread+0x28 SYMBOL_NAME: UsbHub3! TelemetryData_CreateReport+cc MODULE_NAME: UsbHub3 IMAGE_NAME: UsbHub3. sys IMAGE_VERSION: 10.0.19041.264 STACK_COMMAND: . thread ; . cxr ; kb BUCKET_ID_FUNC_OFFSET: cc FAILURE_BUCKET_ID: LKD_0x144_USBHUB3_DEVICE_ENUMERATION_FAILURE_UsbHub3! TelemetryData_CreateReport OSPLATFORM_TYPE: x64 OSNAME: Windows 10 FAILURE_ID_HASH: Followup: MachineOwner Bugcheck Analysis BUGCODE_USB3_DRIVER (144) This bugcheck usually happens when the USB3 core stack detects an invalid operation being performed by a USB client. This bugcheck may also occur due to hardware failure on a USB Boot Device. Arguments: Arg1: 0000000000003003, USB3_WER_BUGCODE_USBHUB3_DEVICE_ENUMERATION_FAILURE A USB device failed enumeration. Arg2: ffff8c070fa325b0, USBHUB3_LIVEDUMP_CONTEXT Arg3: 0000000040010000, 0 Arg4: 0000000000000000, 0 Debugging Details: KEY_VALUES_STRING: 1 Key : Analysis. CPU. mSec Value: 5171 Key : Analysis. DebugAnalysisProvider. CPP Value: Create: 8007007e on DESKTOP-J7A11VA Key : Analysis. DebugData Value: CreateObject Key : Analysis. DebugModel Value: CreateObject Key : Analysis. Elapsed. mSec Value: 6189 Key : Analysis. Memory. CommitPeak. Mb Value: 81 Key : Analysis. System Value: CreateObject ADDITIONAL_XML: 1 OS_BUILD_LAYERS: 1 DUMP_FILE_ATTRIBUTES: 0x18 Kernel Generated Triage Dump Live Generated Dump BUGCHECK_CODE: 144 BUGCHECK_P1: 3003 BUGCHECK_P2: ffff8c070fa325b0 BUGCHECK_P3: 40010000 BUGCHECK_P4: 0 PROCESS_NAME: System STACK_TEXT: ffff8c07`0fa32030 fffff805`448eccf9 : 00000000`00000013 00000000`00000000 fffff805`4490e9dc 00000000`00000000 : UsbHub3! TelemetryData_CreateReport+0xcc ffff8c07`0fa32560 fffff805`448e0eb9 : 00000000`00000000 00000000`00000001 fffff805`448c4760 00000000`00000000 : UsbHub3! WER_CreateReport+0x279 ffff8c07`0fa32630 fffff805`448c9a09 : ffffc287`d5235350 ffffc287`de0110d0 00000000`000003e8 00000000`00000000 : UsbHub3! HUBMISC_CreateWerReport+0x179 ffff8c07`0fa326d0 fffff805`448d0de0 : 00000000`00000004 ffff8c07`0fa32888 00000000`00000fed ffff8c07`0fa32890 : UsbHub3! HUBPDO_ReportDeviceFailure+0x209 ffff8c07`0fa32810 fffff805`448ba737 : 00000000`00000fed fffff805`448ba596 00000000`000011cf fffff805`448d5a07 : UsbHub3! HUBDSM_MarkingUnknownDeviceAsFailed+0x10 ffff8c07`0fa32840 fffff805`448bbafe : ffffc287`00000fa0 00000000`00000fed ffff8c07`00000fa0 fffff805`44916b80 : UsbHub3! HUBSM_ExecuteEntryFunctionsAndPushPopStateMachinesForCurrentState+0x87 ffff8c07`0fa328e0 fffff805`448baf59 : 00000000`00000fed 00000000`00000f00 ffffc287`00000fa0 fffff805`44916b01 : UsbHub3! HUBSM_RunStateMachine+0x5f2 ffff8c07`0fa32960 fffff805`426aa770 : ffffc287`ddae2f90 fffff805`448bae00 ffffc287`d5428cd0 fffff805`448baeb0 : UsbHub3! HUBSM_EvtSmWorkItem+0xa9 ffff8c07`0fa329a0 fffff805`426aa6f9 : ffffc287`de3a0f70 ffffc287`d5428cd0 ffffc287`cd14f080 fffff805`426aa6f0 : ucx01000! Controller_ForwardProgressWorkItemCallback+0x60 ffff8c07`0fa329d0 fffff805`24a1aa33 : 00000000`00000000 ffffc287`de3a0f70 ffffc287`d5428cd0 fffff805`295ac5c0 : ucx01000! Controller_ForwardProgressWorkItemWdmCallback+0x9 ffff8c07`0fa32a00 fffff805`24b035f5 : ffffc287`cdb29080 ffffc287`cdb29080 fffff805`24a1a9a0 00000000`00000000 : nt! IopProcessWorkItem+0x93 ffff8c07`0fa32a70 fffff805`24aa2ae5 : ffffc287`cdb29080 00000000`00000080 ffffc287`cd102080 000fa4ef`b59bbfff : nt! ExpWorkerThread+0x105 ffff8c07`0fa32b10 fffff805`24bfbbf8 : ffff8d81`197b6180 ffffc287`cdb29080 fffff805`24aa2a90 00000000`00000000 : nt! PspSystemThreadStartup+0x55 ffff8c07`0fa32b60 00000000`00000000 : ffff8c07`0fa33000 ffff8c07`0fa2c000 00000000`00000000 00000000`00000000 : nt! KiStartSystemThread+0x28 SYMBOL_NAME: UsbHub3! TelemetryData_CreateReport+cc MODULE_NAME: UsbHub3 IMAGE_NAME: UsbHub3. sys IMAGE_VERSION: 10.0.19041.264 STACK_COMMAND: . thread ; . cxr ; kb BUCKET_ID_FUNC_OFFSET: cc FAILURE_BUCKET_ID: LKD_0x144_USBHUB3_DEVICE_ENUMERATION_FAILURE_UsbHub3! TelemetryData_CreateReport OSPLATFORM_TYPE: x64 OSNAME: Windows 10 FAILURE_ID_HASH: Followup: MachineOwner Bugcheck Analysis BUGCODE_USB3_DRIVER (144) This bugcheck usually happens when the USB3 core stack detects an invalid operation being performed by a USB client. This bugcheck may also occur due to hardware failure on a USB Boot Device. Arguments: Arg1: 0000000000003003, USB3_WER_BUGCODE_USBHUB3_DEVICE_ENUMERATION_FAILURE A USB device failed enumeration. Arg2: fffffb0dbe0c25b0, USBHUB3_LIVEDUMP_CONTEXT Arg3: 0000000040010000, 0 Arg4: 0000000000000000, 0 Debugging Details: KEY_VALUES_STRING: 1 Key : Analysis. CPU. mSec Value: 4843 Key : Analysis. DebugAnalysisProvider. CPP Value: Create: 8007007e on DESKTOP-J7A11VA Key : Analysis. DebugData Value: CreateObject Key : Analysis. DebugModel Value: CreateObject Key : Analysis. Elapsed. mSec Value: 6131 Key : Analysis. Memory. CommitPeak. Mb Value: 79 Key : Analysis. System Value: CreateObject ADDITIONAL_XML: 1 OS_BUILD_LAYERS: 1 DUMP_FILE_ATTRIBUTES: 0x18 Kernel Generated Triage Dump Live Generated Dump BUGCHECK_CODE: 144 BUGCHECK_P1: 3003 BUGCHECK_P2: fffffb0dbe0c25b0 BUGCHECK_P3: 40010000 BUGCHECK_P4: 0 PROCESS_NAME: System STACK_TEXT: fffffb0d`be0c2030 fffff802`7d53ccf9 : 00000000`00000013 00000000`00000000 fffff802`7d55e9dc 00000000`00000000 : UsbHub3! TelemetryData_CreateReport+0xcc fffffb0d`be0c2560 fffff802`7d530eb9 : 00000000`00000000 00000000`00000001 fffff802`7d514760 00000000`00000000 : UsbHub3! WER_CreateReport+0x279 fffffb0d`be0c2630 fffff802`7d519a09 : ffff928b`630203f0 ffff928b`632b1110 00000000`000003e8 00000000`00000000 : UsbHub3! HUBMISC_CreateWerReport+0x179 fffffb0d`be0c26d0 fffff802`7d520de0 : 00000000`00000004 fffffb0d`be0c2888 00000000`00000fed fffffb0d`be0c2890 : UsbHub3! HUBPDO_ReportDeviceFailure+0x209 fffffb0d`be0c2810 fffff802`7d50a737 : 00000000`00000fed fffff802`7d50a596 00000000`000011cf fffff802`7d525a07 : UsbHub3! HUBDSM_MarkingUnknownDeviceAsFailed+0x10 fffffb0d`be0c2840 fffff802`7d50bafe : ffff928b`00000fa0 00000000`00000fed fffffb0d`00000fa0 fffff802`7d566b80 : UsbHub3! HUBSM_ExecuteEntryFunctionsAndPushPopStateMachinesForCurrentState+0x87 fffffb0d`be0c28e0 fffff802`7d50af59 : 00000000`00000fed 00000000`00000f00 00000000`00000fa0 fffff802`7d566b01 : UsbHub3! HUBSM_RunStateMachine+0x5f2 fffffb0d`be0c2960 fffff802`83b4a770 : ffff928b`62adab10 fffff802`7d50ae00 ffff928b`62e11c60 fffff802`7d50aeb0 : UsbHub3! HUBSM_EvtSmWorkItem+0xa9 fffffb0d`be0c29a0 fffff802`83b4a6f9 : ffff928b`626c5e20 ffff928b`62e11c60 ffff928b`5c770080 fffff802`83b4a6f0 : ucx01000! Controller_ForwardProgressWorkItemCallback+0x60 fffffb0d`be0c29d0 fffff802`65e1aa33 : 00000000`00000000 ffff928b`626c5e20 ffff928b`62e11c60 fffff802`675ac5c0 : ucx01000! Controller_ForwardProgressWorkItemWdmCallback+0x9 fffffb0d`be0c2a00 fffff802`65f035f5 : ffff928b`5ad6b5c0 ffff928b`5ad6b5c0 fffff802`65e1a9a0 ffff3e0b`00000000 : nt! IopProcessWorkItem+0x93 fffffb0d`be0c2a70 fffff802`65ea2ae5 : ffff928b`5ad6b5c0 00000000`00000080 ffff928b`5ad02080 5049110f`504a100f : nt! ExpWorkerThread+0x105 fffffb0d`be0c2b10 fffff802`65ffbbf8 : ffffd981`2109f180 ffff928b`5ad6b5c0 fffff802`65ea2a90 889a8948`00000580 : nt! PspSystemThreadStartup+0x55 fffffb0d`be0c2b60 00000000`00000000 : fffffb0d`be0c3000 fffffb0d`be0bc000 00000000`00000000 00000000`00000000 : nt! KiStartSystemThread+0x28 SYMBOL_NAME: UsbHub3! TelemetryData_CreateReport+cc MODULE_NAME: UsbHub3 IMAGE_NAME: UsbHub3. sys IMAGE_VERSION: 10.0.19041.264 STACK_COMMAND: . thread ; . cxr ; kb BUCKET_ID_FUNC_OFFSET: cc FAILURE_BUCKET_ID: LKD_0x144_USBHUB3_DEVICE_ENUMERATION_FAILURE_UsbHub3! TelemetryData_CreateReport OSPLATFORM_TYPE: x64 OSNAME: Windows 10 FAILURE_ID_HASH: Followup: MachineOwner Bugcheck Analysis BUGCODE_USB3_DRIVER (144) This bugcheck usually happens when the USB3 core stack detects an invalid operation being performed by a USB client. This bugcheck may also occur due to hardware failure on a USB Boot Device. Arguments: Arg1: 0000000000003003, USB3_WER_BUGCODE_USBHUB3_DEVICE_ENUMERATION_FAILURE A USB device failed enumeration. Arg2: ffffb98182f9a5b0, USBHUB3_LIVEDUMP_CONTEXT Arg3: 0000000040010000, 0 Arg4: 0000000000000000, 0 Debugging Details: KEY_VALUES_STRING: 1 Key : Analysis. CPU. mSec Value: 5124 Key : Analysis. DebugAnalysisProvider. CPP Value: Create: 8007007e on DESKTOP-J7A11VA Key : Analysis. DebugData Value: CreateObject Key : Analysis. DebugModel Value: CreateObject Key : Analysis. Elapsed. mSec Value: 5719 Key : Analysis. Memory. CommitPeak. Mb Value: 81 Key : Analysis. System Value: CreateObject ADDITIONAL_XML: 1 OS_BUILD_LAYERS: 1 DUMP_FILE_ATTRIBUTES: 0x18 Kernel Generated Triage Dump Live Generated Dump BUGCHECK_CODE: 144 BUGCHECK_P1: 3003 BUGCHECK_P2: ffffb98182f9a5b0 BUGCHECK_P3: 40010000 BUGCHECK_P4: 0 PROCESS_NAME: System STACK_TEXT: ffffb981`82f9a030 fffff802`6cd0ccf9 : 00000000`00000013 00000000`00000000 fffff802`6cd2e9dc 00000000`00000000 : UsbHub3! TelemetryData_CreateReport+0xcc ffffb981`82f9a560 fffff802`6cd00eb9 : 00000000`00000000 00000000`00000001 fffff802`6cce4760 00000000`00000000 : UsbHub3! WER_CreateReport+0x279 ffffb981`82f9a630 fffff802`6cce9a09 : ffffbc0f`54742310 ffffbc0f`5a9b50d0 00000000`000003e8 00000000`00000000 : UsbHub3! HUBMISC_CreateWerReport+0x179 ffffb981`82f9a6d0 fffff802`6ccf0de0 : 00000000`00000004 ffffb981`82f9a888 00000000`00000fed ffffb981`82f9a890 : UsbHub3! HUBPDO_ReportDeviceFailure+0x209 ffffb981`82f9a810 fffff802`6ccda737 : 00000000`00000fed fffff802`6ccda596 00000000`000011cf fffff802`6ccf5a07 : UsbHub3! HUBDSM_MarkingUnknownDeviceAsFailed+0x10 ffffb981`82f9a840 fffff802`6ccdbafe : ffffbc0f`00000fa0 00000000`00000fed ffffb981`00000fa0 fffff802`6cd36b80 : UsbHub3! HUBSM_ExecuteEntryFunctionsAndPushPopStateMachinesForCurrentState+0x87 ffffb981`82f9a8e0 fffff802`6ccdaf59 : 00000000`00000fed 00000000`00000f00 ffffbc0f`00000fa0 fffff802`6cd36b01 : UsbHub3! HUBSM_RunStateMachine+0x5f2 ffffb981`82f9a960 fffff802`6caaa770 : ffffbc0f`63d29710 fffff802`6ccdae00 ffffbc0f`4e6f3040 fffff802`6ccdaeb0 : UsbHub3! HUBSM_EvtSmWorkItem+0xa9 ffffb981`82f9a9a0 fffff802`6caaa6f9 : ffffbc0f`5ab4fc60 ffffbc0f`4e6f3040 ffffbc0f`4e735080 fffff802`6caaa6f0 : ucx01000! Controller_ForwardProgressWorkItemCallback+0x60 ffffb981`82f9a9d0 fffff802`514d9cd3 : 00000000`00000000 ffffbc0f`5ab4fc60 ffffbc0f`4e6f3040 fffff802`53633d60 : ucx01000! Controller_ForwardProgressWorkItemWdmCallback+0x9 ffffb981`82f9aa00 fffff802`51433f45 : ffffbc0f`54635040 ffffbc0f`54635040 fffff802`514d9c40 00000000`00000000 : nt! IopProcessWorkItem+0x93 ffffb981`82f9aa70 fffff802`51546745 : ffffbc0f`54635040 00000000`00000080 ffffbc0f`4ccd5100 fffff802`515e6ae0 : nt! ExpWorkerThread+0x105 ffffb981`82f9ab10 fffff802`515e5598 : fffff802`4c4f9180 ffffbc0f`54635040 fffff802`515466f0 00000000`00000000 : nt! PspSystemThreadStartup+0x55 ffffb981`82f9ab60 00000000`00000000 : ffffb981`82f9b000 ffffb981`82f94000 00000000`00000000 00000000`00000000 : nt! KiStartSystemThread+0x28 SYMBOL_NAME: UsbHub3! TelemetryData_CreateReport+cc MODULE_NAME: UsbHub3 IMAGE_NAME: UsbHub3. sys IMAGE_VERSION: 10.0.19041.264 STACK_COMMAND: . thread ; . cxr ; kb BUCKET_ID_FUNC_OFFSET: cc FAILURE_BUCKET_ID: LKD_0x144_USBHUB3_DEVICE_ENUMERATION_FAILURE_UsbHub3! TelemetryData_CreateReport OSPLATFORM_TYPE: x64 OSNAME: Windows 10 FAILURE_ID_HASH: Followup: MachineOwner

HDD çok ısındı mı? Laptop darbe aldı mı?

Ekran kartı sürücülerini sorunsuz bir şekilde kurdum. Şimdi Kaspersky'ı kuramaz mıyım? Bir de DVD'yi iptal edip HDD'yi oraya mı takacağım? Böyle yaparsam sorunum düzelecek mi?

Hocam HD Tune PRO hiçbir şekilde açılmıyor. Crack dahi indirdim ama görünmez pencere açılıyor. Bu arada Memtest86 hata vermedi, şimdi Hard Disk Sentinel Pro'yu kuruyorum paylaşırım birazdan. Minidump dosyası yok. Sağlık durumu bu şekilde. 131 veri aktarımı sırasında hata oluşmuş.

Laptoplarda HDD için bir tane slot olur sadece onun dışında olmaz. DVD yeri varsa oraya takmayı deneyebilirsiniz. Takma yerinde kablo olmaz slot gibidir. Aldığınız hata mavi ekrana benziyor mavi ekranda da görüntü gider ses kalır normalde mavi ekranın gelmesi gerekir ama siyah ekranda kalabilir. Bu ekran kartı ile ilgili bir sorunu gösteriyor olabilir. Windows'un konumunda olan LiveKernelReports adlı klasörde dosya var mı?

Buraya Upload edebilirsiniz. Yeni bir konu açmanıza gerek yok. Düzelebilir takmayı deneyin.

HDD Ölmüş Gibi Duruyor gidip Yeni Bir HDD Yerine Oyun Oynuyorsan 480 oynamıyorsan 240 GB'lik SSD alırsan çok tatlı olur Kardeşin yumruk atmış anladım büyük ihtimalle HDD ya da RAM zarar görmüş eğer pimler sıkıntılıysa Geçmiş olsun

HDD çok ısınmadı. Ancak 2 ay önce falan kardeşim klavyeye "yumruk" atmıştı. O günden beri PC'de bir sorun var ve yavaşlığın sebebini benim "format atmama" bağlıyorlar...

Dediklerimi doğru bie şekilde yaptıysanız sorununuzun düzelmesi lazım. Tekrardan mavi ekran alırsanız dosyaları paylaşırsınız. Kaspersky'ı kurabilirsiniz.

Desktop MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere. www.mediafire.com Hocam kusura bakmayın hata aldığım PC'de çalışan USB kendi PC'mde çalışmayınca biraz uğraştım.

Dosyalardan bir tanesi 312 MB. Normal mi? Fazla geldi biraz.