מסכים כחולים על ימין ועל שמאל

נוצר על ידי Ronen Mars
2014 באוקטובר 31 ב תמיכה טכנית למחשבים

פתח דיון חדש

Recommended Posts

Ronen Mars

פורסם 2014 באוקטובר 31

- Share

פורסם 2014 באוקטובר 31

היי לכולם,

בהמשך לדיון הזה והזה, אני מצרף את קבצי הדאמפ של הווינדואוס.

נוצר רושם שAVG אשם, אבל לא רק.

אני אודה לעזרתכם, כי כל עניין הקראשים מתחיל לעצבן, כי זה מחשב חדש וזה פשוט מדכא מה שהולך כאן.

החלפתי מערכות הפעלה כבר כמה פעמים וזה לא עוזר(8,8.1,7).

הנה סיכום של 10 הקבצי דאמפ האחרונים(סה"כ יש 29 - מאוגוסט ועד אוקטובר):

System Information (local)
computer name: LITTLEMONSTER
windows version: Windows 8 , 6.2, build: 9200
windows dir: C:\Windows
Hardware: Z97-HD3, Gigabyte Technology Co., Ltd.
CPU: GenuineIntel Intel® Core i7-4790 CPU @ 3.60GHz Intel586, level: 6
8 logical processors, active mask: 255
RAM: 34222153728 total
Crash Dump Analysis
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Fri 10/31/2014 6:03:43 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\103114-14468-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x5A540)
Bugcheck code: 0x19 (0x3, 0xFFFFF8A010A741D0, 0xFFFFF8A0186C3110, 0xFFFFF8A010A741D0)
Error: BAD_POOL_HEADER
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 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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Fri 10/31/2014 6:03:43 AM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: avgmfx64.sys (avgmfx64+0x4111)
Bugcheck code: 0x19 (0x3, 0xFFFFF8A010A741D0, 0xFFFFF8A0186C3110, 0xFFFFF8A010A741D0)
Error: BAD_POOL_HEADER
file path: C:\Windows\system32\drivers\avgmfx64.sys
product: AVG Internet Security
company: AVG Technologies CZ, s.r.o.
description: AVG Resident Shield Minifilter Driver
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.
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: avgmfx64.sys (AVG Resident Shield Minifilter Driver, AVG Technologies CZ, s.r.o.).
Google query: AVG Technologies CZ, s.r.o. BAD_POOL_HEADER
On Sat 10/11/2014 3:18:59 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\101114-6875-01.dmp
This was probably caused by the following module: fltmgr.sys (fltmgr+0x6014)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF880012A2014, 0xFFFFF88018790220, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\drivers\fltmgr.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Microsoft Filesystem Filter Manager
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 that cannot be identified at this time.
On Thu 10/9/2014 7:48:52 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\100914-8328-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x5A540)
Bugcheck code: 0x1A (0x41793, 0xFFFFF68000042FE8, 0x1FE, 0x1FD)
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 caused by another driver that cannot be identified at this time.
On Tue 9/30/2014 3:25:31 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\093014-7296-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x5A540)
Bugcheck code: 0xA (0xFFFFFD7FFFFFFFD0, 0x2, 0x0, 0xFFFFF800BAD5B166)
Error: IRQL_NOT_LESS_OR_EQUAL
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 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.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Mon 9/29/2014 8:17:37 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\092914-6078-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x5A540)
Bugcheck code: 0xA (0xFFFFFD7FFFFFFFD0, 0x2, 0x0, 0xFFFFF80365AD6166)
Error: IRQL_NOT_LESS_OR_EQUAL
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 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.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Mon 9/29/2014 2:02:39 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\092914-8000-01.dmp
This was probably caused by the following module: wdf01000.sys (Wdf01000+0x100A7)
Bugcheck code: 0x10D (0x5, 0x0, 0x1018, 0xFFFFFA802CF7C170)
Error: WDF_VIOLATION
file path: C:\Windows\system32\drivers\wdf01000.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Kernel Mode Driver Framework Runtime
Bug check description: This indicates that Kernel-Mode Driver Framework (KMDF) detected that Windows found an error in a framework-based driver.
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 that cannot be identified at this time.
On Fri 9/26/2014 11:55:53 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\092614-6781-01.dmp
This was probably caused by the following module: wdf01000.sys (Wdf01000+0x100A7)
Bugcheck code: 0x10D (0x5, 0x0, 0x1018, 0xFFFFFA801AAFAC40)
Error: WDF_VIOLATION
file path: C:\Windows\system32\drivers\wdf01000.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Kernel Mode Driver Framework Runtime
Bug check description: This indicates that Kernel-Mode Driver Framework (KMDF) detected that Windows found an error in a framework-based driver.
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 that cannot be identified at this time.
On Fri 9/26/2014 11:38:12 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\092614-6000-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x5A540)
Bugcheck code: 0x1A (0x41284, 0x5B013CF001, 0xA6FE, 0xFFFFF70001080000)
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 caused by another driver that cannot be identified at this time.
On Fri 9/26/2014 7:42:38 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\092614-7437-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x5A540)
Bugcheck code: 0x1A (0x403, 0xFFFFF68000037178, 0xC9A0000788634867, 0xFFFFF68000027178)
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 caused by another driver that cannot be identified at this time.