Toshiba notebook mavi ekran ve pil sorunu

Zimand

Kilopat
Katılım
23 Nisan 2018
Mesajlar
63
Çözümler
2
Birkaç yıllık i5 4200U işlemcili Toshiba notebookta pil değişikliği yapıldıktan sonra sorunlar çıkmaya başladı. Pilin performanssızlığı bir yana şarja takıldığında %15'in altındayken sürekli şarj alımı kesiliyor. %10'un altındayken bu sorun Windows'un "düşük pil" uyarısı vermesi ve uyarının kendiliğinden kaybolması şeklinde kendini gösteriyor. %10'un üzerine çıkana kadar çıkıp kaybolmalar kendini tekrarlıyor.
Bu sorun yaşanırken mavi ekran verdiği oluyor.

Minidump dosyalarını ekliyorum. Sorunun nereden kaynaklandığını bulabilir miyiz?
Pil kaynaklı olması sürpriz olmaz.

Teşekkürler.
Ek:
 
Son düzenleyen: Moderatör:
Kod:
VIDEO_MEMORY_MANAGEMENT_INTERNAL (10e)
The video memory manager encountered a condition that it can't recover from. By crashing,
the video memory manager is attempting to get enough information into the minidump such that
somebody can pinpoint what lead to this condition.
Arguments:
Arg1: 000000000000002d, The subtype of the bugcheck:
Arg2: ffffe380bee67920
Arg3: ffffe380b2349b30
Arg4: ffff840ce59fa0c0

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

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

KEY_VALUES_STRING: 1


PROCESSES_ANALYSIS: 1

SERVICE_ANALYSIS: 1

STACKHASH_ANALYSIS: 1

TIMELINE_ANALYSIS: 1


DUMP_CLASS: 1

DUMP_QUALIFIER: 400

BUILD_VERSION_STRING:  18362.1.amd64fre.19h1_release.190318-1202

SYSTEM_MANUFACTURER:  TOSHIBA

SYSTEM_PRODUCT_NAME:  SATELLITE M50-A

SYSTEM_SKU:  PSKPNE

SYSTEM_VERSION:  PSKPNE-01101GTE

BIOS_VENDOR:  TOSHIBA

BIOS_VERSION:  1.50

BIOS_DATE:  12/02/2013

BASEBOARD_MANUFACTURER:  TOSHIBA

BASEBOARD_PRODUCT:  ZEMAA

BASEBOARD_VERSION:  1.00

DUMP_TYPE:  2

BUGCHECK_P1: 2d

BUGCHECK_P2: ffffe380bee67920

BUGCHECK_P3: ffffe380b2349b30

BUGCHECK_P4: ffff840ce59fa0c0

BUGCHECK_STR:  0x10e_2d

CPU_COUNT: 4

CPU_MHZ: 8f7

CPU_VENDOR:  GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 45

CPU_STEPPING: 1

CPU_MICROCODE: 6,45,1,0 (F,M,S,R)  SIG: 24'00000000 (cache) 24'00000000 (init)

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  0

ANALYSIS_SESSION_HOST:  DESKTOP-VJAA6DJ

ANALYSIS_SESSION_TIME:  02-15-2020 16:09:02.0506

ANALYSIS_VERSION: 10.0.18362.1 amd64fre

LAST_CONTROL_TRANSFER:  from fffff8016dcb41a0 to fffff801673c14e0

STACK_TEXT:  
ffff840c`e59fa048 fffff801`6dcb41a0 : 00000000`0000010e 00000000`0000002d ffffe380`bee67920 ffffe380`b2349b30 : nt!KeBugCheckEx
ffff840c`e59fa050 fffff801`6c593717 : ffffe380`b2349b30 00000000`00000002 00000000`00000002 ffffe380`bcf8ef50 : watchdog!WdLogEvent5_WdCriticalError+0xe0
ffff840c`e59fa090 fffff801`6c61aa0d : ffffe380`ba9c0250 ffffe380`b2349b30 ffffe380`bee67920 00000000`00000000 : dxgmms2!VIDMM_CPU_HOST_APERTURE::MapRange+0xca23
ffff840c`e59fa120 fffff801`6c60c8f8 : ffffe380`bef73140 ffff840c`e59fa230 00000000`00000000 ffff840c`e59fa308 : dxgmms2!VIDMM_GLOBAL::BuildMdlForAllocInCpuHostAperture+0xe5
ffff840c`e59fa160 fffff801`6c5dfbd7 : 00000000`00000000 00000000`00000002 ffffa10c`1b09b000 ffffe380`bef73140 : dxgmms2!VIDMM_PAGE_TABLE_BASE::GetCpuVisibleAddress+0x2cd00
ffff840c`e59fa1a0 fffff801`6c5dd8ff : 00000000`00000000 00000000`00000000 00000000`00000002 00000000`00000000 : dxgmms2!VIDMM_PAGE_TABLE_BASE::GetDriverUpdateAddress+0xb7
ffff840c`e59fa230 fffff801`6c60ce3f : 00000000`00000000 ffffa10c`1b6a3c10 00000000`00000002 00000000`00000002 : dxgmms2!VIDMM_PAGE_TABLE::UpdatePageTableInvalidate+0x3b
ffff840c`e59fa300 fffff801`6c5deb38 : 00000000`00000002 ffffe380`bf250ad0 00000000`00000000 00000000`00000000 : dxgmms2!VIDMM_PAGE_TABLE::CommitVirtualAddressRange+0x2d18f
ffff840c`e59fa3e0 fffff801`6c5ddd13 : ffffe380`bf250ad0 ffffe380`bf2c6470 ffff840c`e59fa640 00000000`00000000 : dxgmms2!VIDMM_PAGE_DIRECTORY::CommitVirtualAddressRange+0x9c8
ffff840c`e59fa580 fffff801`6c6199b7 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : dxgmms2!CVirtualAddressAllocator::CommitVirtualAddressRange+0x2e3
ffff840c`e59fa6f0 fffff801`6c6094b2 : 00000000`00000000 00000000`00000000 00000000`00000076 ffffa10c`1b09b000 : dxgmms2!VIDMM_GLOBAL::InitPagingProcessVaSpace+0x19e23
ffff840c`e59fa870 fffff801`6c5f81a7 : ffffe380`bbd24a10 ffffe380`00000000 00000000`00000001 ffffe380`bbd24a70 : dxgmms2!VIDMM_GLOBAL::ProcessSystemCommand+0x2dd12
ffff840c`e59fa9e0 fffff801`6c5f6ee9 : ffffe380`bbd24a10 ffffa10c`16752601 ffff8b80`eb220100 00000000`00000100 : dxgmms2!VIDMM_WORKER_THREAD::Run+0x12a7
ffff840c`e59fabe0 fffff801`6732a7a5 : ffffa10c`1ad11040 fffff801`6c5f6ee0 ffffe380`bbd24a10 ffff8210`00000001 : dxgmms2!VidMmWorkerThreadProc+0x9
ffff840c`e59fac10 fffff801`673c8b2a : ffff8b80`eb220180 ffffa10c`1ad11040 fffff801`6732a750 00000000`00000001 : nt!PspSystemThreadStartup+0x55
ffff840c`e59fac60 00000000`00000000 : ffff840c`e59fb000 ffff840c`e59f5000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x2a


THREAD_SHA1_HASH_MOD_FUNC:  e7dd2df4591209d881d183b020669f087e8fb7e5

THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  f109470de2885ed6b34239eb609d00e8b143d789

THREAD_SHA1_HASH_MOD:  9cbcc28a597f647d4e07e10f1de1721c7ca63ba2

FOLLOWUP_IP: 
dxgmms2!VIDMM_CPU_HOST_APERTURE::MapRange+ca23
fffff801`6c593717 90              nop

FAULT_INSTR_CODE:  377ae990

SYMBOL_STACK_INDEX:  2

SYMBOL_NAME:  dxgmms2!VIDMM_CPU_HOST_APERTURE::MapRange+ca23

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: dxgmms2

IMAGE_NAME:  dxgmms2.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  0

IMAGE_VERSION:  10.0.18362.476

STACK_COMMAND:  .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET:  ca23

FAILURE_BUCKET_ID:  0x10e_2d_dxgmms2!VIDMM_CPU_HOST_APERTURE::MapRange

BUCKET_ID:  0x10e_2d_dxgmms2!VIDMM_CPU_HOST_APERTURE::MapRange

PRIMARY_PROBLEM_CLASS:  0x10e_2d_dxgmms2!VIDMM_CPU_HOST_APERTURE::MapRange

TARGET_TIME:  2020-02-13T12:31:14.000Z

OSBUILD:  18362

OSSERVICEPACK:  592

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK:  272

PRODUCT_TYPE:  1

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

OSEDITION:  Windows 10 WinNt TerminalServer SingleUserTS

OS_LOCALE:  

USER_LCID:  0

OSBUILD_TIMESTAMP:  1972-08-22 03:24:00

BUILDDATESTAMP_STR:  190318-1202

BUILDLAB_STR:  19h1_release

BUILDOSVER_STR:  10.0.18362.1.amd64fre.19h1_release.190318-1202

ANALYSIS_SESSION_ELAPSED_TIME:  b3ad

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:0x10e_2d_dxgmms2!vidmm_cpu_host_aperture::maprange

FAILURE_ID_HASH:  {e24407bd-c019-66cd-5bed-5339a6b0e6f7}

Followup:     MachineOwner

Siz bu sistemde hiç sürücü güncellemediniz mi🙂
Gelelim yapmanız gerekenlere;
DDU ile Intel ve Nvidia kaldırıp sistemi yeniden başlattıktan sonra güncel sürücüleri sırası ile yükleyin.
Kablolu ve kablosuz güncelle. Chipset güncelle. Bataryanın orijinalliğini kontrol et.
Hotkey kaldır. Avast geçiçi olarak kaldır.
 
Uyarı! Bu konu 6 yıl önce açıldı.
Muhtemelen daha fazla tartışma gerekli değildir ki bu durumda yeni bir konu başlatmayı öneririz. Eğer yine de cevabınızın gerekli olduğunu düşünüyorsanız buna rağmen cevap verebilirsiniz.

Technopat Haberler

Yeni konular

Geri
Yukarı