Download Conclusion - PC poradna

Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Sat 8.12.2012 17:45:07 GMT your computer crashed
crash dump file: C:\Windows\Minidump\120812-33509-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0)
Bugcheck code: 0x9F (0x3, 0xFFFFFA800823B590, 0xFFFFF80000B92748, 0xFFFFFA8003ED97A0)
Error: DRIVER_POWER_STATE_FAILURE
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that the driver is in an inconsistent or invalid power
state.
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 Sat 8.12.2012 17:45:07 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x9F (0x3, 0xFFFFFA800823B590, 0xFFFFF80000B92748, 0xFFFFFA8003ED97A0)
Error: DRIVER_POWER_STATE_FAILURE
Bug check description: This bug check indicates that the driver is in an inconsistent or invalid power
state.
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 Thu 6.12.2012 18:05:27 GMT your computer crashed
crash dump file: C:\Windows\Minidump\120612-54709-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0)
Bugcheck code: 0x1000009F (0x4, 0x258, 0xFFFFFA8003B68B50, 0xFFFFF80000B92740)
Error: CUSTOM_ERROR
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
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 5.12.2012 10:50:37 GMT your computer crashed
crash dump file: C:\Windows\Minidump\120512-21715-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x81E7A)
Bugcheck code: 0x1000009F (0x4, 0x258, 0xFFFFFA8003B69040, 0xFFFFF80000B92740)
Error: CUSTOM_ERROR
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that
cannot be identified at this time.
On Thu 29.11.2012 22:17:11 GMT your computer crashed
crash dump file: C:\Windows\Minidump\113012-19250-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0)
Bugcheck code: 0x9F (0x3, 0xFFFFFA80081F3790, 0xFFFFF80000B92748, 0xFFFFFA80075B1790)
Error: DRIVER_POWER_STATE_FAILURE
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that the driver is in an inconsistent or invalid power
state.
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 Sat 24.11.2012 19:19:23 GMT your computer crashed
crash dump file: C:\Windows\Minidump\112412-41028-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x16BA)
Bugcheck code: 0x1000009F (0x4, 0x258, 0xFFFFFA8003B69660, 0xFFFFF80000B8C510)
Error: CUSTOM_ERROR
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
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 7.10.2012 9:25:44 GMT your computer crashed
crash dump file: C:\Windows\Minidump\100712-33087-01.dmp
This was probably caused by the following module: aswndis2.sys (aswNdis2+0x1ED30)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8800161ED30, 0xFFFFF88007484420, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\drivers\aswndis2.sys
product: avast! Antivirus
company: AVAST Software
description: avast! Filtering NDIS driver
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.
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: aswndis2.sys (avast! Filtering NDIS driver, AVAST Software).
Google query: AVAST Software SYSTEM_SERVICE_EXCEPTION
On Sat 29.9.2012 7:41:09 GMT your computer crashed
crash dump file: C:\Windows\Minidump\092912-28984-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x16AC)
Bugcheck code: 0x1000009F (0x4, 0x258, 0xFFFFFA8003B67040, 0xFFFFF80000B92740)
Error: CUSTOM_ERROR
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
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 11.9.2012 20:13:44 GMT your computer crashed
crash dump file: C:\Windows\Minidump\091212-17737-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x8207A)
Bugcheck code: 0x1000009F (0x4, 0x258, 0xFFFFFA8003B67040, 0xFFFFF800045A2740)
Error: CUSTOM_ERROR
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
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 28.8.2012 7:03:10 GMT your computer crashed
crash dump file: C:\Windows\Minidump\082812-18969-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x8826B)
Bugcheck code: 0x1000009F (0x4, 0x258, 0xFFFFFA8003B7BB50, 0xFFFFF80000B92740)
Error: CUSTOM_ERROR
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that
cannot be identified at this time.
On Thu 16.8.2012 21:01:24 GMT your computer crashed
crash dump file: C:\Windows\Minidump\081712-20170-01.dmp
This was probably caused by the following module: ndis.sys (ndis+0x64110)
Bugcheck code: 0x1000009F (0x4, 0x258, 0xFFFFFA8003B68040, 0xFFFFF80000B8C510)
Error: CUSTOM_ERROR
file path: C:\Windows\system32\drivers\ndis.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NDIS 6.2 driver
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 8.8.2012 5:30:26 GMT your computer crashed
crash dump file: C:\Windows\Minidump\080812-22120-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0x9F (0x3, 0xFFFFFA800877DE20, 0xFFFFF80000B92748, 0xFFFFFA8008466620)
Error: DRIVER_POWER_STATE_FAILURE
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that the driver is in an inconsistent or invalid power
state.
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 6.8.2012 19:48:10 GMT your computer crashed
crash dump file: C:\Windows\Minidump\080712-19047-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x395CD)
Bugcheck code: 0x1000009F (0x4, 0x258, 0xFFFFFA8003B67B50, 0xFFFFF80000B92740)
Error: CUSTOM_ERROR
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
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 18.7.2012 20:04:30 GMT your computer crashed
crash dump file: C:\Windows\Minidump\071912-19266-01.dmp
This was probably caused by the following module: aswndis2.sys (aswNdis2+0x9200)
Bugcheck code: 0x1000009F (0x4, 0x258, 0xFFFFFA8003B68B50, 0xFFFFF80000B8C510)
Error: CUSTOM_ERROR
file path: C:\Windows\system32\drivers\aswndis2.sys
product: avast! Antivirus
company: AVAST Software
description: avast! Filtering NDIS driver
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: aswndis2.sys (avast! Filtering NDIS driver, AVAST Software).
Google query: AVAST Software CUSTOM_ERROR
On Thu 12.7.2012 20:07:36 GMT your computer crashed
crash dump file: C:\Windows\Minidump\071312-21169-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x8207A)
Bugcheck code: 0x1000009F (0x4, 0x258, 0xFFFFFA8003B67040, 0xFFFFF80000B8C510)
Error: CUSTOM_ERROR
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that
cannot be identified at this time.
Conclusion
17 crash dumps have been found and analyzed. Only 15 are included in this report. A third party driver
has 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:
aswndis2.sys (avast! Filtering NDIS driver, AVAST Software)
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.