Analyza Crasch dump souborů

valice00 (3)|21.2.2012 12:44

Dobrý den našel by se tu někdo kdo umí alespoň částečně vyhodnotit dump soubory. Systém celkem poměrně často padá(modrá smrt +- 1 týdně). PC je staré asi 1,5 roku první rok jelo bez sebemenších problémů. Teď už to nějákou dobu padá. Sestava obsahuje 2 x 2 GB OP, 250 GB disk OS, 1TB disk data, obě smart tabulky OK. Paměti testovány Mem testem po dobu asi 1 hodiny, také v pořádku. Osazený zdroj fortron 400w (nic moc), ale byl na 14 dní použit i jiný a padá stále. Grafika integrovaná(AMD 3000) chipset AMD 760G.Windows 7 64 bit(oficiální) Přikládám zkopírovaný výpis ze zmíněných 5 ti dump souborů.

Crash dump file: C:\Windows\Minidump\010612-18673-01.dmp
Date/time: 6.1.2012 20:39:12 GMT
Uptime: 04:44:25
Machine:
Bug check name: BUGCODE_USB_DRIVER
Bug check code: 0xFE
Bug check parm 1: 0x5
Bug check parm 2: 0xFFFFFA8004C1F1A0
Bug check parm 3: 0x10024396
Bug check parm 4: 0xFFFFFA80058ADC48
Probably caused by: usbport.sys
Driver description: USB 1.1 & 2.0 Port Driver
Driver product: Microsoft® Windows® Operating System
Driver company: Microsoft Corporation
OS build: Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Architecture: x64 (64 bit)
CPU count: 4
Page size: 4096

Bug check description:
This indicates that an error has occurred in a Universal Serial Bus (USB) driver.

Comments:

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.

Crash dump file: C:\Windows\Minidump\021612-18969-01.dmp
Date/time: 16.2.2012 18:16:05 GMT
Uptime: 00:09:17
Machine:
Bug check name: SYSTEM_PTE_MISUSE
Bug check code: 0xDA
Bug check parm 1: 0x504
Bug check parm 2: 0xFFFFF6FC50038A28
Bug check parm 3: 0x3
Bug check parm 4: 0x2007145
Probably caused by: ntoskrnl.exe
Driver description: NT Kernel & System
Driver product: Microsoft® Windows® Operating System
Driver company: Microsoft Corporation
OS build: Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Architecture: x64 (64 bit)
CPU count: 4
Page size: 4096

Bug check description:
This indicates that a page table entry (PTE) routine has been used in an improper way.

Comments:
There is a possibility this problem was caused by a virus or other malware.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.

Crash dump file: C:\Windows\Minidump\012412-17269-01.dmp
Date/time: 24.1.2012 19:05:26 GMT
Uptime: 08:02:35
Machine:
Bug check name: SYSTEM_SERVICE_EXCEPTION
Bug check code: 0x3B
Bug check parm 1: 0xC0000005
Bug check parm 2: 0xFFFFF80002CDCF96
Bug check parm 3: 0xFFFFF880095D5FF0
Bug check parm 4: 0x0
Probably caused by: ntoskrnl.exe
Driver description: NT Kernel & System
Driver product: Microsoft® Windows® Operating System
Driver company: Microsoft Corporation
OS build: Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Architecture: x64 (64 bit)
CPU count: 4
Page size: 4096

Bug check description:
This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.

Comments:
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.

Crash dump file: C:\Windows\Minidump\122911-18517-01.dmp
Date/time: 29.12.2011 11:25:39 GMT
Uptime: 00:00:07
Machine:
Bug check name: MEMORY_MANAGEMENT
Bug check code: 0x1A
Bug check parm 1: 0x41284
Bug check parm 2: 0xFFFFF9800220D001
Bug check parm 3: 0xA30
Bug check parm 4: 0xFFFFF780C0000000
Probably caused by: hal.dll
Driver description: Hardware Abstraction Layer DLL
Driver product: Microsoft® Windows® Operating System
Driver company: Microsoft Corporation
OS build: Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Architecture: x64 (64 bit)
CPU count: 4
Page size: 4096

Bug check description:
This indicates that a severe memory management error occurred.

Comments:
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.

Crash dump file: C:\Windows\Minidump\112611-19484-01.dmp
Date/time: 26.11.2011 20:45:41 GMT
Uptime: 11:49:52
Machine:
Bug check name: MEMORY_MANAGEMENT
Bug check code: 0x1A
Bug check parm 1: 0x41284
Bug check parm 2: 0xBB33001
Bug check parm 3: 0x5250
Bug check parm 4: 0xFFFFF70001080000
Probably caused by: ntoskrnl.exe
Driver description: NT Kernel & System
Driver product: Microsoft® Windows® Operating System
Driver company: Microsoft Corporation
OS build: Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Architecture: x64 (64 bit)
CPU count: 4
Page size: 4096

Bug check description:
This indicates that a severe memory management error occurred.

Comments:
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 caused by another driver which cannot be identified at this time.

Děkuji

r34ktor (7477)|21.2.2012 13:17

Pro vyhodnocení dumpů je nutné mít k dispozici vlastní soubory. Zabal obsah složky C:\Windows\Minidump, a přilož ho k dalšímu příspěvku.

valice00 (3)|21.2.2012 15:00

Ok díky za info soubory pošlu.

valice00 (3)|21.2.2012 18:01

tady posílám obsah složky minidump existuje nějáký program který umí soubory analyzovat ? já použil who crashed, ale ten umí soubory v podstatě jen přečíst jestli se nemýlím.

Minidump.zip

r34ktor (7477)|21.2.2012 19:40

[quote=valice00;494774]texistuje nějáký program který umí soubory analyzovat ?[/quote]
Debugging Tools for Windows