Çözüldü Windows XP mavi ekran hatası

Bu konu çözüldü olarak işaretlenmiştir. Çözülmediğini düşünüyorsanız konuyu rapor edebilirsiniz.
İşletim sistemi
Windows XP

Berkomino

Hectopat
Katılım
21 Kasım 2020
Mesajlar
18
Daha fazla  
Cinsiyet
Erkek
Windows XP bilgisayarımda bazı uygulamaları açtığımda 2 saniye sonra bu ekran geliyor. Nedeni ne olabilir?
 

Dosya Ekleri

  • 20201128_114927.jpg
    20201128_114927.jpg
    246,8 KB · Görüntüleme: 280
Çözüm
Bütün mavi ekranlarınız GPU'nuz kaynaklı görünüyor.
Hata dökümlerini mobilde olduğum için psylaşamıyorum. Sonra güncelleyeceğim.
Ekran kartı sürücüsünü kaldırıp güncel bir sürümünü kurunuz. Sisteminizi de yazınız.
 
Hâlâ Windows XP kullanan bir bilgisayardan daha fazla hayır gelmez bence. Zaten bu işletim sisteminden kalma birçok bilgisayar bileşeni ömrünü çoktan tamamladı.

Sistemi komple değiştirmeniz güzel bir çözüm denemesi olacaktır. Yok, ben değiştiremem derseniz en azından DDU ile (Windows XP desteği var mı, bilmiyorum) GPU sürücünüzü kaldırıp yeniden kurmayı deneyebilirsiniz ama çözüleceğini zannetmiyorum.

Döküm dosyalarınızı ve sistem özelliklerinizi paylaşın.
 
Son düzenleme:
Hâlâ Windows XP kullanan bir bilgisayardan daha fazla hayır gelmez bence. Zaten bu işletim sisteminden kalma birçok bilgisayar bileşeni ömrünü çoktan tamamladı.

Sistemi komple değiştirmeniz güzel bir çözüm denemesi olacaktır. Yok, ben değiştiremem derseniz en azından DDU ile (Windows XP desteği var mı, bilmiyorum) GPU sürücünüzü kaldırıp yeniden kurmayı deneyebilirsiniz ama çözüleceğini zannetmiyorum.

Döküm dosyalarınızı ve sistem özelliklerinizi paylaşın.

Her insanın bütçesi olmuyor mecbur kullanıyor. Bırakın da hayır gelip gelmiyeceğini arkadaş kendi karar versin.
 
Artı -1 Eksi
İşlemci: İntel Pentium 4, 631 (Cedar Mill)
Anakart: MSI p4m900m2 (MS-7255 V2)
RAM: 2024+512 MB DDR2 667MGz
ROM: 250GB HDD
Ekran Kartı: Geforce 7100 GS
Monitör: Casper 776K

Döküm dosyalarını nasıl paylaşacağımı söyler misiniz?


Böylemi
 
Son düzenleme:
Daha Windows XP ihtiyar delikanlısını kullanan var mı derken bu konu çok iyi geldi. Minidump dosyasını atın. Minidump dosyası olmadan elimizden bir şey gelmez. Bu dosyalar C\Windows\Minidump klasoründe bulunur. Paylaşma konusuna gelince Google Drive'a yükleyip herkese açık seçeneğini açmak gerekiyor. Sonra da dosyayı Drive'dan açıp linki buraya yapıştıracaksınız.
İşlemci: İntel Pentium 4, 631 (Cedar Mill)
Anakart: MSI p4m900m2 (MS-7255 V2)
RAM: 2024+512 MB DDR2 667MGz
ROM: 250GB HDD
Ekran Kartı: Geforce 7100 GS
Monitör: Casper 776K

Döküm dosyalarını nasıl paylaşacağımı söyler misiniz?


Böylemi
Çabuk öğreniyorsunuz 😀 😁
Bayağı bir mavi belaya uğramış sisteminiz.
 
Bütün mavi ekranlarınız GPU'nuz kaynaklı görünüyor.
Hata dökümlerini mobilde olduğum için psylaşamıyorum. Sonra güncelleyeceğim.
 
Çözüm
Bütün mavi ekranlarınız GPU'nuz kaynaklı görünüyor.
Hata dökümlerini mobilde olduğum için psylaşamıyorum. Sonra güncelleyeceğim.
DDU ile dediklerinizi yaptım ve mavi ekran hatası çözüldü. Teşekkürler. Şimdi de Bios güncellemesini indirip kuracağım. Bu arada izninizle bir soru daha sormak istiyorum. Bu sistem Windows 10 kaldırır mı? Sorunsuz, kasmadan çalıştırmasına gerek yok. Sadece kurmam gerekiyor da.
 
Döküm dosyaları:
Kod:
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: bd29696b, The address that the exception occurred at
Arg3: b1d9f88c, Trap Frame
Arg4: 00000000

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


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 453

    Key  : Analysis.DebugAnalysisProvider.CPP
    Value: Create: 8007007e on DESKTOP-62N06FT

    Key  : Analysis.DebugData
    Value: CreateObject

    Key  : Analysis.DebugModel
    Value: CreateObject

    Key  : Analysis.Elapsed.mSec
    Value: 6169

    Key  : Analysis.Memory.CommitPeak.Mb
    Value: 55

    Key  : Analysis.System
    Value: CreateObject


ADDITIONAL_XML: 1

OS_BUILD_LAYERS: 1

BUGCHECK_CODE:  8e

BUGCHECK_P1: ffffffffc0000005

BUGCHECK_P2: ffffffffbd29696b

BUGCHECK_P3: ffffffffb1d9f88c

BUGCHECK_P4: 0

TRAP_FRAME:  b1d9f88c -- (.trap 0xffffffffb1d9f88c)
ErrCode = 00000000
eax=e2247b80 ebx=00000000 ecx=e2226ad4 edx=bd3e43a8 esi=bd3dcab0 edi=bd3e4e70
eip=bd29696b esp=b1d9f900 ebp=e2226ad4 iopl=0         nv up ei pl zr na pe nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010246
nv4_disp+0x28496b:
bd29696b 8b03            mov     eax,dword ptr [ebx]  ds:0023:00000000=????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  RTSS.exe

STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
b1d9f9b0 80505f97     00001000 00400000 00000a0a nv4_disp+0x28496b
b1d9f9b4 00000000     00400000 00000a0a 00000400 nt!MiLocateAndReserveWsle+0xb1


SYMBOL_NAME:  nv4_disp+28496b

MODULE_NAME: nv4_disp

IMAGE_NAME:  nv4_disp.dll

STACK_COMMAND:  .thread ; .cxr ; kb

FAILURE_BUCKET_ID:  0x8E_nv4_disp+28496b

OSPLATFORM_TYPE:  x86

OSNAME:  Windows XP

FAILURE_ID_HASH:  {13c3f280-b89d-6b4a-341a-5643c66be5cb}

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

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: bd29696b, The address that the exception occurred at
Arg3: b146a50c, Trap Frame
Arg4: 00000000

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


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 468

    Key  : Analysis.DebugAnalysisProvider.CPP
    Value: Create: 8007007e on DESKTOP-62N06FT

    Key  : Analysis.DebugData
    Value: CreateObject

    Key  : Analysis.DebugModel
    Value: CreateObject

    Key  : Analysis.Elapsed.mSec
    Value: 6502

    Key  : Analysis.Memory.CommitPeak.Mb
    Value: 54

    Key  : Analysis.System
    Value: CreateObject


ADDITIONAL_XML: 1

OS_BUILD_LAYERS: 1

BUGCHECK_CODE:  8e

BUGCHECK_P1: ffffffffc0000005

BUGCHECK_P2: ffffffffbd29696b

BUGCHECK_P3: ffffffffb146a50c

BUGCHECK_P4: 0

TRAP_FRAME:  b146a50c -- (.trap 0xffffffffb146a50c)
ErrCode = 00000000
eax=e2447b80 ebx=00000000 ecx=e2426ad4 edx=bd3e43a8 esi=bd3dcab0 edi=bd3e4e70
eip=bd29696b esp=b146a580 ebp=e2426ad4 iopl=0         nv up ei pl zr na pe nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010246
nv4_disp+0x28496b:
bd29696b 8b03            mov     eax,dword ptr [ebx]  ds:0023:00000000=????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  3

PROCESS_NAME:  gta-vc.exe

STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
b146a57c bd3e4e70     00000006 e2425c70 00000001 nv4_disp+0x28496b
b146a580 00000000     e2425c70 00000001 e2426ad4 nv4_disp+0x3d2e70


SYMBOL_NAME:  nv4_disp+28496b

MODULE_NAME: nv4_disp

IMAGE_NAME:  nv4_disp.dll

STACK_COMMAND:  .thread ; .cxr ; kb

FAILURE_BUCKET_ID:  0x8E_nv4_disp+28496b

OSPLATFORM_TYPE:  x86

OSNAME:  Windows XP

FAILURE_ID_HASH:  {13c3f280-b89d-6b4a-341a-5643c66be5cb}

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

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: bd29696b, The address that the exception occurred at
Arg3: b22d088c, Trap Frame
Arg4: 00000000

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


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 468

    Key  : Analysis.DebugAnalysisProvider.CPP
    Value: Create: 8007007e on DESKTOP-62N06FT

    Key  : Analysis.DebugData
    Value: CreateObject

    Key  : Analysis.DebugModel
    Value: CreateObject

    Key  : Analysis.Elapsed.mSec
    Value: 2093

    Key  : Analysis.Memory.CommitPeak.Mb
    Value: 55

    Key  : Analysis.System
    Value: CreateObject


ADDITIONAL_XML: 1

OS_BUILD_LAYERS: 1

BUGCHECK_CODE:  8e

BUGCHECK_P1: ffffffffc0000005

BUGCHECK_P2: ffffffffbd29696b

BUGCHECK_P3: ffffffffb22d088c

BUGCHECK_P4: 0

TRAP_FRAME:  b22d088c -- (.trap 0xffffffffb22d088c)
ErrCode = 00000000
eax=e2247b80 ebx=00000000 ecx=e2226ad4 edx=bd3e43a8 esi=bd3dcab0 edi=bd3e4e70
eip=bd29696b esp=b22d0900 ebp=e2226ad4 iopl=0         nv up ei pl zr na pe nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010246
nv4_disp+0x28496b:
bd29696b 8b03            mov     eax,dword ptr [ebx]  ds:0023:00000000=????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  2

PROCESS_NAME:  RTSS.exe

STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
b22d09b0 80505f97     00001000 00400000 00000a0a nv4_disp+0x28496b
b22d09b4 00000000     00400000 00000a0a 00000400 nt!MiLocateAndReserveWsle+0xb1


SYMBOL_NAME:  nv4_disp+28496b

MODULE_NAME: nv4_disp

IMAGE_NAME:  nv4_disp.dll

STACK_COMMAND:  .thread ; .cxr ; kb

FAILURE_BUCKET_ID:  0x8E_nv4_disp+28496b

OSPLATFORM_TYPE:  x86

OSNAME:  Windows XP

FAILURE_ID_HASH:  {13c3f280-b89d-6b4a-341a-5643c66be5cb}

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

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: bd29696b, The address that the exception occurred at
Arg3: b168288c, Trap Frame
Arg4: 00000000

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


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 421

    Key  : Analysis.DebugAnalysisProvider.CPP
    Value: Create: 8007007e on DESKTOP-62N06FT

    Key  : Analysis.DebugData
    Value: CreateObject

    Key  : Analysis.DebugModel
    Value: CreateObject

    Key  : Analysis.Elapsed.mSec
    Value: 2047

    Key  : Analysis.Memory.CommitPeak.Mb
    Value: 55

    Key  : Analysis.System
    Value: CreateObject


ADDITIONAL_XML: 1

OS_BUILD_LAYERS: 1

BUGCHECK_CODE:  8e

BUGCHECK_P1: ffffffffc0000005

BUGCHECK_P2: ffffffffbd29696b

BUGCHECK_P3: ffffffffb168288c

BUGCHECK_P4: 0

TRAP_FRAME:  b168288c -- (.trap 0xffffffffb168288c)
ErrCode = 00000000
eax=e2247b80 ebx=00000000 ecx=e2226ad4 edx=bd3e43a8 esi=bd3dcab0 edi=bd3e4e70
eip=bd29696b esp=b1682900 ebp=e2226ad4 iopl=0         nv up ei pl zr na pe nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010246
nv4_disp+0x28496b:
bd29696b 8b03            mov     eax,dword ptr [ebx]  ds:0023:00000000=????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  3

PROCESS_NAME:  RTSS.exe

STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
b16829b0 80505f97     00001000 00400000 00000a0a nv4_disp+0x28496b
b16829b4 00000000     00400000 00000a0a 00000400 nt!MiLocateAndReserveWsle+0xb1


SYMBOL_NAME:  nv4_disp+28496b

MODULE_NAME: nv4_disp

IMAGE_NAME:  nv4_disp.dll

STACK_COMMAND:  .thread ; .cxr ; kb

FAILURE_BUCKET_ID:  0x8E_nv4_disp+28496b

OSPLATFORM_TYPE:  x86

OSNAME:  Windows XP

FAILURE_ID_HASH:  {13c3f280-b89d-6b4a-341a-5643c66be5cb}

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

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: bd29696b, The address that the exception occurred at
Arg3: b1d9750c, Trap Frame
Arg4: 00000000

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


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 499

    Key  : Analysis.DebugAnalysisProvider.CPP
    Value: Create: 8007007e on DESKTOP-62N06FT

    Key  : Analysis.DebugData
    Value: CreateObject

    Key  : Analysis.DebugModel
    Value: CreateObject

    Key  : Analysis.Elapsed.mSec
    Value: 2064

    Key  : Analysis.Memory.CommitPeak.Mb
    Value: 54

    Key  : Analysis.System
    Value: CreateObject


ADDITIONAL_XML: 1

OS_BUILD_LAYERS: 1

BUGCHECK_CODE:  8e

BUGCHECK_P1: ffffffffc0000005

BUGCHECK_P2: ffffffffbd29696b

BUGCHECK_P3: ffffffffb1d9750c

BUGCHECK_P4: 0

TRAP_FRAME:  b1d9750c -- (.trap 0xffffffffb1d9750c)
ErrCode = 00000000
eax=e2447b80 ebx=00000000 ecx=e2426ad4 edx=bd3e43a8 esi=bd3dcab0 edi=bd3e4e70
eip=bd29696b esp=b1d97580 ebp=e2426ad4 iopl=0         nv up ei pl zr na pe nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010246
nv4_disp+0x28496b:
bd29696b 8b03            mov     eax,dword ptr [ebx]  ds:0023:00000000=????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  2

PROCESS_NAME:  gta-vc.exe

STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
b1d9757c bd3e4e70     00000006 e2425c70 00000001 nv4_disp+0x28496b
b1d97580 00000000     e2425c70 00000001 e2426ad4 nv4_disp+0x3d2e70


SYMBOL_NAME:  nv4_disp+28496b

MODULE_NAME: nv4_disp

IMAGE_NAME:  nv4_disp.dll

STACK_COMMAND:  .thread ; .cxr ; kb

FAILURE_BUCKET_ID:  0x8E_nv4_disp+28496b

OSPLATFORM_TYPE:  x86

OSNAME:  Windows XP

FAILURE_ID_HASH:  {13c3f280-b89d-6b4a-341a-5643c66be5cb}

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

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: bd29696b, The address that the exception occurred at
Arg3: b13b150c, Trap Frame
Arg4: 00000000

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


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 499

    Key  : Analysis.DebugAnalysisProvider.CPP
    Value: Create: 8007007e on DESKTOP-62N06FT

    Key  : Analysis.DebugData
    Value: CreateObject

    Key  : Analysis.DebugModel
    Value: CreateObject

    Key  : Analysis.Elapsed.mSec
    Value: 4711

    Key  : Analysis.Memory.CommitPeak.Mb
    Value: 54

    Key  : Analysis.System
    Value: CreateObject


ADDITIONAL_XML: 1

OS_BUILD_LAYERS: 1

BUGCHECK_CODE:  8e

BUGCHECK_P1: ffffffffc0000005

BUGCHECK_P2: ffffffffbd29696b

BUGCHECK_P3: ffffffffb13b150c

BUGCHECK_P4: 0

TRAP_FRAME:  b13b150c -- (.trap 0xffffffffb13b150c)
ErrCode = 00000000
eax=e2447b80 ebx=00000000 ecx=e2426ad4 edx=bd3e43a8 esi=bd3dcab0 edi=bd3e4e70
eip=bd29696b esp=b13b1580 ebp=e2426ad4 iopl=0         nv up ei pl zr na pe nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010246
nv4_disp+0x28496b:
bd29696b 8b03            mov     eax,dword ptr [ebx]  ds:0023:00000000=????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  gta-vc.exe

STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
b13b157c bd3e4e70     00000006 e2425c70 00000001 nv4_disp+0x28496b
b13b1580 00000000     e2425c70 00000001 e2426ad4 nv4_disp+0x3d2e70


SYMBOL_NAME:  nv4_disp+28496b

MODULE_NAME: nv4_disp

IMAGE_NAME:  nv4_disp.dll

STACK_COMMAND:  .thread ; .cxr ; kb

FAILURE_BUCKET_ID:  0x8E_nv4_disp+28496b

OSPLATFORM_TYPE:  x86

OSNAME:  Windows XP

FAILURE_ID_HASH:  {13c3f280-b89d-6b4a-341a-5643c66be5cb}

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

Bu sistem Windows 10 kaldırır mı? Sorunsuz, kasmadan çalıştırmasına gerek yok. Sadece kurmam gerekiyor da.
Kaldırır kaldırmasına da ne kadar performans alırsınız, bilemem.

Ekran kartı konusunda çekiniyorum çünkü kartınızın Windows 10 sürücü desteği yok. Çoğunlukla Windows 7/8/8.1 sürücüleri bir sıkıntı çıkarmıyor ama yine de pek önerdiğimi söyleyemeyeceğim.

RAM miktarınız ne kadar? 2 GB+512 MB mi? Tam anlayamadım. Belki 32 bit deneyebilirsiniz ama 32 bitin yazılım desteği kalmadı.
 

Yeni konular

Geri
Yukarı