- Beranda
- Komunitas
- Tech
- Computer Stuff
CRASH DUMP di PC help please


TS
Siirioshoguner
CRASH DUMP di PC help please
ane beberapa hari lalu abis ganti mobo sama hdd gan..
coz mobo ane yang lama udah usang dan koid

nah untuk hdd juga udah koid dan gamau detect, direpair pun ga bisa..
sekarang ane dah pake mobo baru MSI 770T-C45, VGA ane ATI RADEON X1650..
ane coba buat install pes dan app laen, tp kok tiap di tengah jalan selalu bluescreen kaya crash dump gitu.
tp bluescreen ini kalo buat game, kalo cuma player ma browser lancar jaya..
nah ane coba pake app whocrased buat detect..
hasilnya :
adakah agan"yang udah pernah ngalami??
dan apa solusinya?
mohon bantuan yak
nuwun...


coz mobo ane yang lama udah usang dan koid


nah untuk hdd juga udah koid dan gamau detect, direpair pun ga bisa..
sekarang ane dah pake mobo baru MSI 770T-C45, VGA ane ATI RADEON X1650..
ane coba buat install pes dan app laen, tp kok tiap di tengah jalan selalu bluescreen kaya crash dump gitu.
tp bluescreen ini kalo buat game, kalo cuma player ma browser lancar jaya..
nah ane coba pake app whocrased buat detect..
hasilnya :
Spoiler for berisi ini:
Crash dumps are enabled on your computer.
On Fri 21/06/2013 6:05:00 GMT your computer crashed
crash dump file: C:\Windows\Minidump\062113-19671-01.dmp
This was probably caused by the following module: atikmdag.sys (atikmdag+0x275CE)
Bugcheck code: 0x100000EA (0xFFFFFFFF86E47948, 0x0, 0x0, 0x0)
Error: THREAD_STUCK_IN_DEVICE_DRIVER_M
file path: C:\Windows\system32\drivers\atikmdag.sys
product: ATI Radeon Family
company: ATI Technologies Inc.
description: ATI Radeon Kernel Mode Driver
Bug check description: This indicates that a thread in a device driver is endlessly spinning.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: atikmdag.sys (ATI Radeon Kernel Mode Driver, ATI Technologies Inc.).
Google query: ATI Technologies Inc. THREAD_STUCK_IN_DEVICE_DRIVER_M
On Fri 21/06/2013 6:05:00 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: atikmdag.sys (atikmdag+0x275CE)
Bugcheck code: 0xEA (0xFFFFFFFF86E47948, 0x0, 0x0, 0x0)
Error: THREAD_STUCK_IN_DEVICE_DRIVER
file path: C:\Windows\system32\drivers\atikmdag.sys
product: ATI Radeon Family
company: ATI Technologies Inc.
description: ATI Radeon Kernel Mode Driver
Bug check description: This indicates that a thread in a device driver is endlessly spinning.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: atikmdag.sys (ATI Radeon Kernel Mode Driver, ATI Technologies Inc.).
Google query: ATI Technologies Inc. THREAD_STUCK_IN_DEVICE_DRIVER
On Fri 21/06/2013 5:35:15 GMT your computer crashed
crash dump file: C:\Windows\Minidump\062113-21871-01.dmp
This was probably caused by the following module: dxgmms1.sys (dxgmms1+0x144F3)
Bugcheck code: 0x7F (0xD, 0x0, 0x0, 0x0)
Error: UNEXPECTED_KERNEL_MODE_TRAP
file path: C:\Windows\system32\drivers\dxgmms1.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics MMS
Bug check description: This bug check indicates that the Intel CPU generated a trap and the kernel failed to catch this trap.
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 that cannot be identified at this time.
On Fri 21/06/2013 5:20:20 GMT your computer crashed
crash dump file: C:\Windows\Minidump\062113-17830-01.dmp
This was probably caused by the following module: dxgkrnl.sys (dxgkrnl+0x8C92C)
Bugcheck code: 0x116 (0xFFFFFFFF87343008, 0xFFFFFFFF9322C8FE, 0x0, 0x2)
Error: VIDEO_TDR_ERROR
file path: C:\Windows\system32\drivers\dxgkrnl.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics Kernel
Bug check description: This indicates that an attempt to reset the display driver and recover from a timeout failed.
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 that cannot be identified at this time.
On Fri 21/06/2013 5:17:58 GMT your computer crashed
crash dump file: C:\Windows\Minidump\062113-17893-01.dmp
This was probably caused by the following module: hal.sys (hal+0xEF3F)
Bugcheck code: 0x124 (0x0, 0xFFFFFFFF861F2024, 0xFFFFFFFFB6004000, 0xFFFFFFFFE3000145)
Error: WHEA_UNCORRECTABLE_ERROR
Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).
This is likely to be caused by a hardware problem problem. This problem might be caused by a thermal issue.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: hal.sys .
Google query: hal.sys WHEA_UNCORRECTABLE_ERROR
On Thu 20/06/2013 14:53:54 GMT your computer crashed
crash dump file: C:\Windows\Minidump\062013-21013-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x452B3)
Bugcheck code: 0x1000008E (0xFFFFFFFF80000004, 0xFFFFFFFF82A982B3, 0xFFFFFFFF8ECD3CC0, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\ntkrnlpa.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 that cannot be identified at this time.
On Wed 19/06/2013 13:37:00 GMT your computer crashed
crash dump file: C:\Windows\Minidump\061913-14398-01.dmp
This was probably caused by the following module: hal.sys (hal+0x599E)
Bugcheck code: 0xA (0x0, 0x2, 0x1, 0xFFFFFFFF82E2999E)
Error: IRQL_NOT_LESS_OR_EQUAL
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: hal.sys .
Google query: hal.sys IRQL_NOT_LESS_OR_EQUAL
On Fri 21/06/2013 6:05:00 GMT your computer crashed
crash dump file: C:\Windows\Minidump\062113-19671-01.dmp
This was probably caused by the following module: atikmdag.sys (atikmdag+0x275CE)
Bugcheck code: 0x100000EA (0xFFFFFFFF86E47948, 0x0, 0x0, 0x0)
Error: THREAD_STUCK_IN_DEVICE_DRIVER_M
file path: C:\Windows\system32\drivers\atikmdag.sys
product: ATI Radeon Family
company: ATI Technologies Inc.
description: ATI Radeon Kernel Mode Driver
Bug check description: This indicates that a thread in a device driver is endlessly spinning.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: atikmdag.sys (ATI Radeon Kernel Mode Driver, ATI Technologies Inc.).
Google query: ATI Technologies Inc. THREAD_STUCK_IN_DEVICE_DRIVER_M
On Fri 21/06/2013 6:05:00 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: atikmdag.sys (atikmdag+0x275CE)
Bugcheck code: 0xEA (0xFFFFFFFF86E47948, 0x0, 0x0, 0x0)
Error: THREAD_STUCK_IN_DEVICE_DRIVER
file path: C:\Windows\system32\drivers\atikmdag.sys
product: ATI Radeon Family
company: ATI Technologies Inc.
description: ATI Radeon Kernel Mode Driver
Bug check description: This indicates that a thread in a device driver is endlessly spinning.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: atikmdag.sys (ATI Radeon Kernel Mode Driver, ATI Technologies Inc.).
Google query: ATI Technologies Inc. THREAD_STUCK_IN_DEVICE_DRIVER
On Fri 21/06/2013 5:35:15 GMT your computer crashed
crash dump file: C:\Windows\Minidump\062113-21871-01.dmp
This was probably caused by the following module: dxgmms1.sys (dxgmms1+0x144F3)
Bugcheck code: 0x7F (0xD, 0x0, 0x0, 0x0)
Error: UNEXPECTED_KERNEL_MODE_TRAP
file path: C:\Windows\system32\drivers\dxgmms1.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics MMS
Bug check description: This bug check indicates that the Intel CPU generated a trap and the kernel failed to catch this trap.
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 that cannot be identified at this time.
On Fri 21/06/2013 5:20:20 GMT your computer crashed
crash dump file: C:\Windows\Minidump\062113-17830-01.dmp
This was probably caused by the following module: dxgkrnl.sys (dxgkrnl+0x8C92C)
Bugcheck code: 0x116 (0xFFFFFFFF87343008, 0xFFFFFFFF9322C8FE, 0x0, 0x2)
Error: VIDEO_TDR_ERROR
file path: C:\Windows\system32\drivers\dxgkrnl.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics Kernel
Bug check description: This indicates that an attempt to reset the display driver and recover from a timeout failed.
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 that cannot be identified at this time.
On Fri 21/06/2013 5:17:58 GMT your computer crashed
crash dump file: C:\Windows\Minidump\062113-17893-01.dmp
This was probably caused by the following module: hal.sys (hal+0xEF3F)
Bugcheck code: 0x124 (0x0, 0xFFFFFFFF861F2024, 0xFFFFFFFFB6004000, 0xFFFFFFFFE3000145)
Error: WHEA_UNCORRECTABLE_ERROR
Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).
This is likely to be caused by a hardware problem problem. This problem might be caused by a thermal issue.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: hal.sys .
Google query: hal.sys WHEA_UNCORRECTABLE_ERROR
On Thu 20/06/2013 14:53:54 GMT your computer crashed
crash dump file: C:\Windows\Minidump\062013-21013-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x452B3)
Bugcheck code: 0x1000008E (0xFFFFFFFF80000004, 0xFFFFFFFF82A982B3, 0xFFFFFFFF8ECD3CC0, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\ntkrnlpa.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 that cannot be identified at this time.
On Wed 19/06/2013 13:37:00 GMT your computer crashed
crash dump file: C:\Windows\Minidump\061913-14398-01.dmp
This was probably caused by the following module: hal.sys (hal+0x599E)
Bugcheck code: 0xA (0x0, 0x2, 0x1, 0xFFFFFFFF82E2999E)
Error: IRQL_NOT_LESS_OR_EQUAL
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: hal.sys .
Google query: hal.sys IRQL_NOT_LESS_OR_EQUAL
adakah agan"yang udah pernah ngalami??
dan apa solusinya?
mohon bantuan yak
nuwun...



0
3.1K
Kutip
20
Balasan
Thread Digembok
Urutan
Terbaru
Terlama
Thread Digembok
Komunitas Pilihan