Windows XP mavi ekran hatası

İşletim sistemi
Windows XP

Sirain

Decapat
Katılım
10 Nisan 2021
Mesajlar
317
Çözümler
1
Daha fazla  
Sistem Özellikleri
İntel İ5-3210M
8 GB Ram
GT-610M
İntel HD Graphics 4000
Cinsiyet
Erkek
Meslek
Öğrenciyim boşuna bakma param yok :(
PC'im Windows XP, donanımlar yeterli olmadığından upgrade yapamıyorum ve sürekli oyuna girince mavi ekran hatası alıyorum.

RAM'im 512 MB, ekran kartım 64 MB. Hatayı yedikten sonra geri bildirim göndermek ister misiniz diye sorulduğunda şu veri dosyalarını gösteriyor:
  • C:\Windows\minidump\"miNI081914-"04.dmp
  • C:\Docume~|\f\Locals~|\Temp\werb.tmp.dir00\sysdata.xml
 
Son düzenleyen: Moderatör:
Öncelikle sorunun kaynağı ekran kartınız gibi görünüyor. Epey eski bir donanım ve muhtemelen sorununuz donanımsal. Ekran kartı sürücünüzü kaldırıp tekrar kurmayı deneyebilirsiniz fakat işe yarayıp yaramayacağının garantisini ne yazık ki veremem. Ayrıca yazım kurallarına uyarsanız sevinirim.

[CODE title="Dökümler"]*******************************************************************************
* *
* 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: c000008e, The exception code that was not handled
Arg2: 3001651c, The address that the exception occurred at
Arg3: f177a790, Trap Frame
Arg4: 00000000

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

***** Kernel symbols are WRONG. Please fix symbols to do analysis.
KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 328

Key : Analysis.DebugAnalysisManager
Value: Create

Key : Analysis.Elapsed.mSec
Value: 9408

Key : Analysis.Init.CPU.mSec
Value: 1031

Key : Analysis.Init.Elapsed.mSec
Value: 70811

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


ADDITIONAL_DEBUG_TEXT:
You can run '.symfix; .reload' to try to fix the symbol path and load symbols.

WRONG_SYMBOLS_TIMESTAMP: 3d6de35c

WRONG_SYMBOLS_SIZE: 1f3100

FAULTING_MODULE: 804d4000 nt

BUGCHECK_CODE: 8e

BUGCHECK_P1: ffffffffc000008e

BUGCHECK_P2: 3001651c

BUGCHECK_P3: fffffffff177a790

BUGCHECK_P4: 0

TRAP_FRAME: f177a790 -- (.trap 0xfffffffff177a790)
ErrCode = 00000000
eax=0000000c ebx=00000003 ecx=00000000 edx=00000060 esi=00000000 edi=bfaacf6c
eip=bf9e4fb4 esp=f177a804 ebp=e13f4018 iopl=0 vif nv up ei pl zr na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00090246
SiSGRV+0x29fb4:
bf9e4fb4 db442420 fild dword ptr [esp+20h] ss:0010:f177a824=00000000
Resetting default scope

CUSTOMER_CRASH_COUNT: 4

STACK_TEXT:
f177a800 00000000 e10b7a24 e13f4018 00000008 SiSGRV+0x29fb4


STACK_COMMAND: .thread ; .cxr ; kb

EXCEPTION_CODE_STR: 3D6DE35C

EXCEPTION_STR: WRONG_SYMBOLS

PROCESS_NAME: ntoskrnl.wrong.symbols.exe

IMAGE_NAME: ntoskrnl.wrong.symbols.exe

MODULE_NAME: nt_wrong_symbols

SYMBOL_NAME: nt_wrong_symbols!3D6DE35C1F3100

FAILURE_BUCKET_ID: WRONG_SYMBOLS_X86_TIMESTAMP_020829-090324_3D6DE35C_nt_wrong_symbols!3D6DE35C1F3100

OSPLATFORM_TYPE: x86

OSNAME: Windows XP

FAILURE_ID_HASH: {68328ab6-b30b-404f-ff11-cccf24d40928}

Followup: MachineOwner
---------[/CODE]
 
Öncelikle sorunun kaynağı ekran kartınız gibi görünüyor. Epey eski bir donanım ve muhtemelen sorununuz donanımsal. Ekran kartı sürücünüzü kaldırıp tekrar kurmayı deneyebilirsiniz fakat işe yarayıp yaramayacağının garantisini ne yazık ki veremem. Ayrıca yazım kurallarına uyarsanız sevinirim.

[CODE title="Dökümler"]*******************************************************************************
* *
* 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: c000008e, The exception code that was not handled
Arg2: 3001651c, The address that the exception occurred at
Arg3: f177a790, Trap Frame
Arg4: 00000000

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

***** Kernel symbols are WRONG. Please fix symbols to do analysis.
KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 328

Key : Analysis.DebugAnalysisManager
Value: Create

Key : Analysis.Elapsed.mSec
Value: 9408

Key : Analysis.Init.CPU.mSec
Value: 1031

Key : Analysis.Init.Elapsed.mSec
Value: 70811

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

ADDITIONAL_DEBUG_TEXT:
You can run '.symfix; .reload' to try to fix the symbol path and load symbols.

WRONG_SYMBOLS_TIMESTAMP: 3d6de35c

WRONG_SYMBOLS_SIZE: 1f3100

FAULTING_MODULE: 804d4000 nt

BUGCHECK_CODE: 8e

BUGCHECK_P1: ffffffffc000008e

BUGCHECK_P2: 3001651c

BUGCHECK_P3: fffffffff177a790

BUGCHECK_P4: 0

TRAP_FRAME: f177a790 -- (.trap 0xfffffffff177a790)
ErrCode = 00000000
eax=0000000c ebx=00000003 ecx=00000000 edx=00000060 esi=00000000 edi=bfaacf6c
eip=bf9e4fb4 esp=f177a804 ebp=e13f4018 iopl=0 vif nv up ei pl zr na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00090246
SiSGRV+0x29fb4:
bf9e4fb4 db442420 fild dword ptr [esp+20h] ss:0010:f177a824=00000000
Resetting default scope

CUSTOMER_CRASH_COUNT: 4

STACK_TEXT:
f177a800 00000000 e10b7a24 e13f4018 00000008 SiSGRV+0x29fb4

STACK_COMMAND: .thread ; .cxr ; kb

EXCEPTION_CODE_STR: 3D6DE35C

EXCEPTION_STR: WRONG_SYMBOLS

PROCESS_NAME: ntoskrnl.wrong.symbols.exe

IMAGE_NAME: ntoskrnl.wrong.symbols.exe

MODULE_NAME: nt_wrong_symbols

SYMBOL_NAME: nt_wrong_symbols!3D6DE35C1F3100

FAILURE_BUCKET_ID: WRONG_SYMBOLS_X86_TIMESTAMP_020829-090324_3D6DE35C_nt_wrong_symbols!3D6DE35C1F3100

OSPLATFORM_TYPE: x86

OSNAME: Windows XP

FAILURE_ID_HASH: {68328ab6-b30b-404f-ff11-cccf24d40928}

Followup: MachineOwner
---------[/CODE]

Bilgisayar eski olduğu için sürücüleri çok eski güncellemeyi deneyeceğim bugün format attım. Bilgisayarda bayağı virüs vardı işlemci zorlanıyordu.
@Enes3078 Hocam kernel32.dll hatasından anlar mısınız?
 
Son düzenleme:
OS düzgün kurulmamışsa bu hata olabilir. Biliyorum zor durumda olabilirsiniz fakat bu sistemle de bir yere kadar idare edebilirsiniz. İkinci el uygun aygıtlara yönelmenizi tavsiye ederim.
 

Yeni konular

Geri
Yukarı