offline
- Pridružio: 23 Sep 2013
- Poruke: 33
|
Ja se unapred izvinjavam ako sam ovu temu postavio pod pogresan odsek, ja sam ovde jako retko pa ne znam za sta je ovaj moj problem vezan.. Elem, vec sam vam pisao o njemu, ali ne znam gde je ta tema... Neko vreme nije bilo tog problema i opet se pojavio... Znaci, pri pokretanju se momentalno zapuca, da bi posle jednog restarta krenuo normalno da radi i da se opet zapuca.. Tako jos 1-2 puta... Meni se cak desilo pre 10 minuta da se restartovao sam od sebe dok sam bio u Mozili... Rekoste mi da preuzmem WhoCrashed program i evo sta je analizirao:
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Mon 07/07/2014 18:33:03 GMT your computer crashed
crash dump file: C:\Windows\Minidump\070714-17019-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0xBD184)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF98CFD184, 0xFFFFFFFFA688FCA8, 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 Mon 07/07/2014 18:33:03 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: hal.sys (hal+0x5BA9)
Bugcheck code: 0x8E (0xFFFFFFFFC0000005, 0xFFFFFFFF98CFD184, 0xFFFFFFFFA688FCA8, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED
Bug check description: This bug check indicates that a kernel-mode application generated an exception that the error handler did not catch.
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 KERNEL_MODE_EXCEPTION_NOT_HANDLED
On Mon 07/07/2014 12:51:33 GMT your computer crashed
crash dump file: C:\Windows\Minidump\070714-22744-01.dmp
This was probably caused by the following module: rt86win7.sys (Rt86win7+0xF403)
Bugcheck code: 0xD1 (0x15, 0x2, 0x1, 0xFFFFFFFF91F39403)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\rt86win7.sys
product: Realtek 8136/8168/8169 PCI/PCIe Adapters
company: Realtek
description: Realtek 8101E/8168/8169 NDIS 6.20 32-bit Driver
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
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: rt86win7.sys (Realtek 8101E/8168/8169 NDIS 6.20 32-bit Driver , Realtek ).
Google query: Realtek DRIVER_IRQL_NOT_LESS_OR_EQUAL
On Fri 27/06/2014 13:01:56 GMT your computer crashed
crash dump file: C:\Windows\Minidump\062714-26348-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x8D879)
Bugcheck code: 0x50 (0xFFFFFFFFF4E44A8C, 0x0, 0xFFFFFFFF82ED0846, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
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 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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Mon 23/06/2014 16:12:07 GMT your computer crashed
crash dump file: C:\Windows\Minidump\062314-21606-01.dmp
This was probably caused by the following module: aswsnx.sys (aswSnx+0x1660)
Bugcheck code: 0xBE (0xFFFFFFFF88C43F89, 0x3776121, 0xFFFFFFFFA6DA4058, 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 Wed 11/06/2014 15:37:10 GMT your computer crashed
crash dump file: C:\Windows\Minidump\061114-25287-01.dmp
This was probably caused by the following module: dxgmms1.sys (dxgmms1+0x31164)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFFFFF933A5164, 0xFFFFFFFF8E7F9BA0, 0xFFFFFFFF8E7F9780)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
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 a system thread 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 Thu 05/06/2014 11:56:29 GMT your computer crashed
crash dump file: C:\Windows\Minidump\060514-19344-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x8D879)
Bugcheck code: 0x50 (0xFFFFFFFFFFFFFFDC, 0x0, 0xFFFFFFFF830C3B90, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
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 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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Sun 01/06/2014 11:23:03 GMT your computer crashed
crash dump file: C:\Windows\Minidump\060114-21964-01.dmp
This was probably caused by the following module: Unknown (0xFFFFFFFF82E89B7F)
Bugcheck code: 0xA (0x8, 0x1C, 0x1, 0xFFFFFFFF82EC3701)
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.
Google query: IRQL_NOT_LESS_OR_EQUAL
On Wed 28/05/2014 15:41:12 GMT your computer crashed
crash dump file: C:\Windows\Minidump\052814-16348-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x15FCF)
Bugcheck code: 0x7F (0xD, 0x0, 0x0, 0x0)
Error: UNEXPECTED_KERNEL_MODE_TRAP
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 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 Wed 21/05/2014 16:02:01 GMT your computer crashed
crash dump file: C:\Windows\Minidump\052114-20607-01.dmp
This was probably caused by the following module: ataport.sys (ataport+0x4ED6)
Bugcheck code: 0xD1 (0xFFFFFFFFCCCCCC88, 0x5, 0x0, 0xFFFFFFFF88A04ED6)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\ataport.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: ATAPI Driver Extension
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
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 Wed 21/05/2014 15:56:38 GMT your computer crashed
crash dump file: C:\Windows\Minidump\052114-23540-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x8D879)
Bugcheck code: 0x50 (0xFFFFFFFFFFFFFFDC, 0x0, 0xFFFFFFFF830B2B90, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
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 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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Tue 20/05/2014 11:26:21 GMT your computer crashed
crash dump file: C:\Windows\Minidump\052014-18376-01.dmp
This was probably caused by the following module: aswsnx.sys (aswSnx+0x1F7C0)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF98DAC448, 0xFFFFFFFF8EFE3FD8, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
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 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.
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 KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
On Tue 20/05/2014 09:57:00 GMT your computer crashed
crash dump file: C:\Windows\Minidump\052014-18766-01.dmp
This was probably caused by the following module: aswsnx.sys (aswSnx+0x1F700)
Bugcheck code: 0x7F (0xD, 0x0, 0x0, 0x0)
Error: UNEXPECTED_KERNEL_MODE_TRAP
file path: C:\Windows\system32\drivers\aswsnx.sys
product: avast! Antivirus
company: AVAST Software
description: avast! Virtualization Driver
Bug check description: This bug check indicates that the Intel CPU generated a trap and the kernel failed to catch this trap.
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 UNEXPECTED_KERNEL_MODE_TRAP
On Mon 19/05/2014 17:24:34 GMT your computer crashed
crash dump file: C:\Windows\Minidump\051914-27752-01.dmp
This was probably caused by the following module: aswsnx.sys (aswSnx+0x1660)
Bugcheck code: 0xBE (0xFFFFFFFF889D4F89, 0x3775121, 0xFFFFFFFF901EC5E8, 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 Sun 11/05/2014 14:44:16 GMT your computer crashed
crash dump file: C:\Windows\Minidump\051114-19515-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0xDEBFC)
Bugcheck code: 0x1A (0x41289, 0x63150001, 0x30FF, 0x9D31009)
Error: MEMORY_MANAGEMENT
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 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.
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
41 crash dumps have been found and analyzed. Only 15 are included in this report. 4 third party drivers have been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers:
nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 311.06 , NVIDIA Corporation)
aswsnx.sys (avast! Virtualization Driver, AVAST Software)
rt86win7.sys (Realtek 8101E/8168/8169 NDIS 6.20 32-bit Driver , Realtek )
hal.sys
If no updates for these drivers are available, try searching with Google on the names of these drivers in combination the errors that have been reported for these drivers and include the brand and model name of your computer as well in the query. This often yields interesting results from discussions from users who have been experiencing similar problems.
Read the topic general suggestions for troubleshooting system crashes for more information.
Note that it's not always possible to state with certainty whether a reported driver is actually responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.
Obavestite me ako premestite temu i odgovorite sto pre na ovo, jer ne znam sta da radim...
Hvala unapred
|