Mavi Ekran hatası "Crush Dump"

HPQ-User
29-09-2011, 14:43   |  #1  
OP CHIP Online
Teşekkür Sayısı: 29
30,996 mesaj
Kayıt Tarihi:Kayıt: Mar 2007

jorge sormuş:
En ufak bir program çalıştırmadan yada şu an ki crysis modern mod gibi benzer oyunaları oynarken bile aynı sorunu alıyorum "Crush Dump"   ,forumlarda baya bi araştırma yaptım güncelleme format herşeyi denetim sorun yine aynı windows media playarı açarken bile bazen "Crush Dump" hatası alıyorum. Size who crashed programı yükleyip oradaki raporları çıkardım umarım yardımcı olursunuz yoksa bu kasayı apartmanın 7. katından aşağıya atıcam Şimdiden teşekkürler ...


System Information (local)
--------------------------------------------------------------------------------

computer name: BILAL-PC
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
CPU: AuthenticAMD AMD Phenom(tm) II X4 955 Processor AMD586, level: 16
4 logical processors, active mask: 15
RAM: 2146623488 total
VM: 2147352576, free: 1957945344

--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.


On Sat 24.09.2011 18:40:36 GMT your computer crashed
crash dump file: C:\Windows\Minidump\092411-22198-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF800031BDDD3, 0xFFFFF88008BD3B80, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Sat 24.09.2011 18:40:36 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: dxgmms1.sys (dxgmms1!VidMmInterface+0x9D2C)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF800031BDDD3, 0xFFFFF88008BD3B80, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\drivers\dxgmms1.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics MMS
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.


On Sat 24.09.2011 18:34:40 GMT your computer crashed
crash dump file: C:\Windows\Minidump\092411-27346-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF800030BDB65, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Sat 24.09.2011 18:31:00 GMT your computer crashed
crash dump file: C:\Windows\Minidump\092411-26317-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0x223BCF)
Bugcheck code: 0x19 (0x20, 0xFFFFF900C26364D0, 0xFFFFF900C2636560, 0x2509001D)
Error: BAD_POOL_HEADER
file path: C:\Windows\system32\win32k.sys
product: Microsoft® Windows® İşletim Sistemi
company: Microsoft Corporation
description: Çok Kullanıcılı Win32 Sürücüsü
Bug check description: This indicates that a pool header is corrupt.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.


On Sat 24.09.2011 18:00:50 GMT your computer crashed
crash dump file: C:\Windows\Minidump\092411-18782-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0x1A (0x41287, 0x7C5E1, 0x0, 0x0)
Error: MEMORY_MANAGEMENT
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is cau

Soru Türü: Donanım
İşletim Sistemi: Windows 7
Sistem Özellikleri:
AMD Phenom II X4 955 Black Edition AM3 3.2 Ghz.

MSI 870A G54 DDR3 2000 Mhz anakart

Gskill 2x2  4 Gb DDR3 1600 Mhz RAm

3.5" 500 gb Baruucuda Sata 3 HDD

Saphhire Hd 5860 Extreme 1 Gb 256 Bit Ati Rodeon Dx11 Ekran kartı

USP 500W Coller master ATx siyah kasa

İnternet Tarayıcı: Mozilla/5.0 (compatible; MSIE 9.0; Windows NT 6.1; WOW64; Trident/5.0)