HJT+WhoCrashed log - pády systému, firefoxu Vyřešeno

[Clorky]

On Mon 4.2.2013 10:42:55 GMT your computer crashed
crash dump file: C:\Windows\Minidump\020413-23359-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x1A9A9)
Bugcheck code: 0x24 (0x1904FB, 0xFFFFFFFF95DF3A10, 0xFFFFFFFF95DF35F0, 0xFFFFFFFF819272C6)
Error: NTFS_FILE_SYSTEM
file path: C:\Windows\system32\drivers\ntfs.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT File System Driver
Bug check description: This indicates a problem occurred in the NTFS file system.
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 Mon 4.2.2013 9:19:59 GMT your computer crashed
crash dump file: C:\Windows\Minidump\020413-21296-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0xC2D47)
Bugcheck code: 0x1000008E (0xFFFFFFFFC000001D, 0xFFFFFFFF8C932D47, 0xFFFFFFFF8F3E74B4, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\win32k.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Multi-User Win32 Driver
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 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 Sat 2.2.2013 13:54:29 GMT your computer crashed
crash dump file: C:\Windows\Minidump\020213-19078-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x1A9A9)
Bugcheck code: 0x24 (0x1904FB, 0xFFFFFFFF8594E82C, 0xFFFFFFFF8594E410, 0xFFFFFFFF818A2AF1)
Error: NTFS_FILE_SYSTEM
file path: C:\Windows\system32\drivers\ntfs.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT File System Driver
Bug check description: This indicates a problem occurred in the NTFS file system.
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 Sat 2.2.2013 12:39:21 GMT your computer crashed
crash dump file: C:\Windows\Minidump\020213-26171-01.dmp
This was probably caused by the following module: aswsnx.sys (aswSnx+0x1C954)
Bugcheck code: 0x1A (0x41284, 0x864B001, 0x0, 0xFFFFFFFFC0402000)
Error: MEMORY_MANAGEMENT
file path: C:\Windows\system32\drivers\aswsnx.sys
product: avast! Antivirus
company: AVAST Software
description: avast! Virtualization Driver
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.
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: aswsnx.sys (avast! Virtualization Driver, AVAST Software).
Google query: AVAST Software MEMORY_MANAGEMENT



On Fri 1.2.2013 19:06:24 GMT your computer crashed
crash dump file: C:\Windows\Minidump\020113-23687-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1FB618)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF81A34618, 0xFFFFFFFF96443BB4, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
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 that cannot be identified at this time.



On Fri 1.2.2013 19:01:07 GMT your computer crashed
crash dump file: C:\Windows\Minidump\020113-24109-01.dmp
This was probably caused by the following module: aswsnx.sys (aswSnx+0x1CA02)
Bugcheck code: 0xBE (0xFFFFFFFF8F553EEB, 0x429EB021, 0xFFFFFFFFA2FABB04, 0xB)
Error: ATTEMPTED_WRITE_TO_READONLY_MEMORY
file path: C:\Windows\system32\drivers\aswsnx.sys
product: avast! Antivirus
company: AVAST Software
description: avast! Virtualization Driver
Bug check description: This is issued if a driver attempts to write to a read-only memory segment.
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: aswsnx.sys (avast! Virtualization Driver, AVAST Software).
Google query: AVAST Software ATTEMPTED_WRITE_TO_READONLY_MEMORY



On Fri 1.2.2013 18:45:09 GMT your computer crashed
crash dump file: C:\Windows\Minidump\020113-19406-01.dmp
This was probably caused by the following module: aswmonflt.sys (aswMonFlt+0x2C1F)
Bugcheck code: 0x19 (0x3, 0xFFFFFFFF833B0FB0, 0xFFFFFFFF833B0FB0, 0xFFFFFFFF833B4FB0)
Error: BAD_POOL_HEADER
file path: C:\Windows\system32\drivers\aswmonflt.sys
product: avast! Antivirus
company: AVAST Software
description: avast! File System Minifilter for Windows 2003/Vista
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: aswmonflt.sys (avast! File System Minifilter for Windows 2003/Vista, AVAST Software).
Google query: AVAST Software BAD_POOL_HEADER



On Fri 1.2.2013 18:41:34 GMT your computer crashed
crash dump file: C:\Windows\Minidump\020113-20875-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0xDC987)
Bugcheck code: 0x50 (0xFFFFFFFFFFFFFFD8, 0x0, 0xFFFFFFFF8126C987, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\win32k.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Multi-User Win32 Driver
Bug check description: This indicates that invalid system memory has been referenced.
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 Tue 22.1.2013 7:58:12 GMT your computer crashed
crash dump file: C:\Windows\Minidump\012213-23203-01.dmp
This was probably caused by the following module: aswsnx.sys (aswSnx+0x1C954)
Bugcheck code: 0x1A (0x41284, 0xBE65001, 0x3C44, 0xFFFFFFFFC0402000)
Error: MEMORY_MANAGEMENT
file path: C:\Windows\system32\drivers\aswsnx.sys
product: avast! Antivirus
company: AVAST Software
description: avast! Virtualization Driver
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.
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: aswsnx.sys (avast! Virtualization Driver, AVAST Software).
Google query: AVAST Software MEMORY_MANAGEMENT



On Sun 20.1.2013 16:50:40 GMT your computer crashed
crash dump file: C:\Windows\Minidump\012013-19890-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0xD23F8)
Bugcheck code: 0x1A (0x41790, 0xFFFFFFFFC0402400, 0xFFFF, 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 caused by another driver that cannot be identified at this time.

[Reklama]

[Žbeky]

Na disku C není?

[Clorky]

Ne. Jinak bych ho tady dal.

[Žbeky]

Tak udělej CF bez skriptu

[Clorky]

Po výměně HDD je to už fajn.

Nevidím nutnost posílat další logy, PC je stařeček a není třeba ho trápit.

Každopádně děkuji za pomoc.