offline
- NoOneEver Dreams
- Prijatelj foruma
- Pridružio: 16 Apr 2008
- Poruke: 1159
- Gde živiš: Ank-Morpork
|
Pozdrav.
Imam problema sa BSODovima. Dobijam ih i u različitim trenucima (ali ne uvek):
- u toku rada
- dok je komp idle
- prilikom bootovanja.
Nekada i ne dobijem BSOD nego se komp ukoči, a na monitoru je zamrljana slika, kao "sneg" na antenskoj TV.
Evo konfiguracije: https://snag.gy/fG3NPQ.jpg
A evo i WhoCrashed izveštaja:
--------------------------------------------------------------------------------
Welcome to WhoCrashed (HOME EDITION) v 6.01
--------------------------------------------------------------------------------
This program checks for drivers which have been crashing your computer. If your computer has displayed a blue (or black) screen of death, suddenly rebooted or shut down then this program might help you find the root cause of the problem and a solution.
Whenever a computer suddenly reboots without displaying any notice or blue (or black) screen of death, the first thing that is often thought about is a hardware failure. In reality, on Windows a lot of system crashes are caused by malfunctioning device drivers and kernel modules. In case of a kernel error, many computers do not show a blue or black screen unless they are configured for this. Instead these systems suddenly reboot without any notice.
This program will analyze your crash dumps with the single click of a button. It will tell you what drivers are likely to be responsible for crashing your computer. It will report a conclusion which offers suggestions on how to proceed in any situation while the analysis report will display internet links which will help you further troubleshoot any detected problems.
To obtain technical support visit www.resplendence.com/support
Click here to check if you have the latest version or if an update is available.
Just click the Analyze button for a comprehensible report ...
--------------------------------------------------------------------------------
Home Edition Notice
--------------------------------------------------------------------------------
This version of WhoCrashed is free for use at home only. If you would like to use this software at work or in a commercial environment you should get the professional edition of WhoCrashed which allows you to perform more thorough and detailed analysis. It also offers a range of additional features such as remote analysis on remote directories and remote computers on the network.
Please note that this version of WhoCrashed is not licensed for use by professional support engineers.
Click here for more information on the professional edition.
Click here to buy the the professional edition of WhoCrashed.
--------------------------------------------------------------------------------
System Information (local)
--------------------------------------------------------------------------------
Computer name: KEEPEROFSECRETS
Windows version: Windows 7 Service Pack 1, 6.1, build: 7601
Windows dir: C:\Windows
Hardware: MS-7599, MSI, 870A-G54 (MS-7599)
CPU: AuthenticAMD AMD Athlon(tm) II X2 250 Processor AMD586, level: 16
2 logical processors, active mask: 3
RAM: 5367848960 bytes total
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dumps are enabled on your computer. This system is not configured for complete or automatic crash dumps. For best results, configure your system to write out complete or automatic crash dumps. Select Tools->Crash Dump Configuration from the main menu to configure your system to write out complete memory dumps.
Crash dump directories:
C:\Windows
C:\Windows\Minidump
On Tue 23.10.2018 15:12:41 your computer crashed or a problem was reported
crash dump file: C:\Windows\MEMORY.DMP
This was probably caused by the following module: atikmdag.sys (0xFFFFF88011187E53)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF88011187E53, 0xFFFFF8800911E890, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\drivers\atikmdag.sys
product: ATI Radeon Family
company: Advanced Micro Devices, Inc.
description: ATI Radeon Kernel Mode 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: atikmdag.sys (ATI Radeon Kernel Mode Driver, Advanced Micro Devices, Inc.).
Google query: atikmdag.sys Advanced Micro Devices, Inc. SYSTEM_SERVICE_EXCEPTION
On Sun 21.10.2018 20:00:49 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\102118-11840-02.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x939A0)
Bugcheck code: 0xE3 (0xFFFFFA8006294860, 0xFFFFFA8006E98560, 0x0, 0x2)
Error: RESOURCE_NOT_OWNED
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 thread tried to release a resource it did not own.
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 21.10.2018 19:29:12 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\102118-11887-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x939A0)
Bugcheck code: 0xA (0x30, 0x2, 0x1, 0xFFFFF800030495DF)
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 is a software bug.
This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out.
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 21.10.2018 18:59:27 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\102118-11856-01.dmp
This was probably caused by the following module: hardware.sys (hardware)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF88011974152, 0xFFFFF88006188930, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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: hardware.sys .
Google query: hardware.sys SYSTEM_SERVICE_EXCEPTION
On Sun 21.10.2018 14:45:21 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\102118-11840-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x939A0)
Bugcheck code: 0xA (0x246, 0x2, 0x1, 0xFFFFF800030CEB79)
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 is a software bug.
This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out.
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 21.10.2018 14:40:51 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\102118-11934-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x93970)
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
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 might be a case of memory corruption. This may be because of a hardware issue such as faulty RAM, overheating (thermal issue) or because of a buggy driver.
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 20.10.2018 18:37:23 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\102018-11809-01.dmp
This was probably caused by the following module: aswbidsdrivera.sys (0xFFFFF88003F5E5CE)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF88003F5E5CE, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\drivers\aswbidsdrivera.sys
product: Avast
company: AVAST Software
description: IDS Application Activity Monitor Driver.
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This might be a case of memory corruption. This may be because of a hardware issue such as faulty RAM, overheating (thermal issue) or because of a buggy 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: aswbidsdrivera.sys (IDS Application Activity Monitor Driver., AVAST Software).
Google query: aswbidsdrivera.sys AVAST Software KMODE_EXCEPTION_NOT_HANDLED
On Sat 20.10.2018 15:44:18 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\102018-12698-01.dmp
This was probably caused by the following module: atikmdag.sys (0xFFFFF8801118B788)
Bugcheck code: 0xD1 (0xFFFFF5000E23CB50, 0x2, 0x0, 0xFFFFF8801118B788)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\atikmdag.sys
product: ATI Radeon Family
company: Advanced Micro Devices, Inc.
description: ATI Radeon Kernel Mode 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 bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out.
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: atikmdag.sys (ATI Radeon Kernel Mode Driver, Advanced Micro Devices, Inc.).
Google query: atikmdag.sys Advanced Micro Devices, Inc. DRIVER_IRQL_NOT_LESS_OR_EQUAL
On Fri 19.10.2018 1:14:06 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\101918-11778-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x939A0)
Bugcheck code: 0x109 (0xA3A039D89A2177A6, 0xB3B7465EEC9F2BBC, 0xFFFFF88001519690, 0x1)
Error: CRITICAL_STRUCTURE_CORRUPTION
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 the kernel has detected critical kernel code or data corruption.
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. This may be because of a hardware issue such as faulty RAM, overheating (thermal issue) or because of a buggy driver. This problem might also be caused because of overheating (thermal issue).
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 18.10.2018 18:36:20 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\101818-11809-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x939A0)
Bugcheck code: 0x109 (0xA3A039D899F065AF, 0xB3B7465EEC6E19C5, 0xFFFFF8800151D980, 0x1)
Error: CRITICAL_STRUCTURE_CORRUPTION
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 the kernel has detected critical kernel code or data corruption.
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. This may be because of a hardware issue such as faulty RAM, overheating (thermal issue) or because of a buggy driver. This problem might also be caused because of overheating (thermal issue).
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
On your computer a total of 18 crash dumps have been found. Only 10 have been analyzed. 3 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:
atikmdag.sys (ATI Radeon Kernel Mode Driver, Advanced Micro Devices, Inc.)
aswbidsdrivera.sys (IDS Application Activity Monitor Driver., AVAST Software)
hardware.sys
If no updates for these drivers are available, try searching with Google on the names of these drivers in combination with the errors that have been reported for these drivers. Include the brand and model name of your computer as well in the query. This often yields interesting results from discussions on the web by 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 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.
E, sad, ako sam dobro shvatio, problem pravi drajver za grafičku, te ga treba updateovati.
Međutim, šta činiti sa ovim Avastom i ovim hardware.sys-om?
|
Preuzmi instalaciju za 
Dvoklikom pokreni instalaciju i klikni 
