LZR
PCAXE Apprentice
- Učlanjen(a)
- 03.09.2019.
- Poruka
- 6
- Rezultat reagovanja
- 1
Moja konfiguracija
CPU & cooler:
AMD Ahtlon x4 845
Motherboard:
ASUS A68HM-K
RAM:
KINGSTON DIMM DDR3 8GB 1600MHz KVR16N11/8BK
Display:
AMD Radeon r7 250
HDD:
SSD : Kingston SATA3 SUV300S37A/120GBK UV300 serija / Toshiba 3.5" SATA3 32MB 7200rpm DT01ACA100
OS & Browser:
Windows 10 / Brave
Unazad mesec dana,problem sa BSOD (prilikom paljenja racunara) u medjuvremenu obaran sistem vise puta,radjen memtest preko 15 sati,9 pass,0 errors,prime95 radio 6 sati bez errora,hdtune i sentinel nisu nasli greske na ssdu i hddu,,grafika testirana sa furmarkom,napajanje provereno,odradjen apdejt biosa,nakon apdejta,vise nije bilo slike,izbacuje samo no video input,odnesem u servis,kazu otisla maticna,ja kupim istu i dalje isti problem sa BSOD,slike sad naravno ima,opet danas nabacim novi sistem i ugasim ga bez instalacije ikakvih drajvera,upalim ponovo opet BSOD,prilikom rada se ne desava bilo kakav bug i slicno.Muci ga hardware.sys koji ne mogu da nikako da resim.Evo sta kaze who crashed :
Maticna ASUS A68HM-K
Grafika :AMD Radeon r7 250
Memorija :KINGSTON DIMM DDR3 8GB 1600MHz KVR16N11/8BK
Procesor:AMD Ahtlon x4 845
SSD : Kingston SATA3 SUV300S37A/120GBK UV300 serija
HDD:Toshiba 3.5" SATA3 32MB 7200rpm DT01ACA100
Crash dump directories:
C:\Windows
C:\Windows\Minidump
On Mon 9/2/2019 7:15:38 AM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\090219-11562-01.dmp
This was probably caused by the following module: hardware.sys (hardware)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF800479C24D6, 0xFFFFEC00081AF818, 0xFFFFEC00081AF060)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
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.
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_THREAD_EXCEPTION_NOT_HANDLED_M
On Mon 9/2/2019 7:15:38 AM your computer crashed or a problem was reported
crash dump file: C:\Windows\MEMORY.DMP
This was probably caused by the following module: hardware.sys (hardware)
Bugcheck code: 0x7E (0xFFFFFFFFC0000005, 0xFFFFF800479C24D6, 0xFFFFEC00081AF818, 0xFFFFEC00081AF060)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
Bug check description: This bug check indicates that a system thread 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: hardware.sys .
Google query: hardware.sys SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
On Sun 9/1/2019 7:27:16 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\090119-12812-01.dmp
This was probably caused by the following module: hardware.sys (hardware)
Bugcheck code: 0x1A (0x41792, 0xFFFFD9BFD6D03460, 0x800000, 0x0)
Error: MEMORY_MANAGEMENT
Bug check description: This indicates that a severe memory management error occurred. A corrupted PTE has been detected.
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).
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 MEMORY_MANAGEMENT
On Sun 9/1/2019 7:25:05 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\090119-10687-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1BFCC0)
Bugcheck code: 0x18 (0x0, 0xFFFFA4095DFD65A0, 0x10, 0xFFFFA4095DFDE568)
Error: REFERENCE_BY_POINTER
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 reference count of an object is illegal for the current state of the object.
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.
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
4 crash dumps have been found and analyzed. 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:
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.
Jos jedan log :
6 crash dumps have been found and analyzed. 2 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:
aftap0901.sys (TAP-Windows Virtual Network Driver (NDIS 6.0), The OpenVPN Project)
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.
Maticna ASUS A68HM-K
Grafika :AMD Radeon r7 250
Memorija :KINGSTON DIMM DDR3 8GB 1600MHz KVR16N11/8BK
Procesor:AMD Ahtlon x4 845
SSD : Kingston SATA3 SUV300S37A/120GBK UV300 serija
HDD:Toshiba 3.5" SATA3 32MB 7200rpm DT01ACA100
Crash dump directories:
C:\Windows
C:\Windows\Minidump
On Mon 9/2/2019 7:15:38 AM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\090219-11562-01.dmp
This was probably caused by the following module: hardware.sys (hardware)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF800479C24D6, 0xFFFFEC00081AF818, 0xFFFFEC00081AF060)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
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.
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_THREAD_EXCEPTION_NOT_HANDLED_M
On Mon 9/2/2019 7:15:38 AM your computer crashed or a problem was reported
crash dump file: C:\Windows\MEMORY.DMP
This was probably caused by the following module: hardware.sys (hardware)
Bugcheck code: 0x7E (0xFFFFFFFFC0000005, 0xFFFFF800479C24D6, 0xFFFFEC00081AF818, 0xFFFFEC00081AF060)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
Bug check description: This bug check indicates that a system thread 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: hardware.sys .
Google query: hardware.sys SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
On Sun 9/1/2019 7:27:16 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\090119-12812-01.dmp
This was probably caused by the following module: hardware.sys (hardware)
Bugcheck code: 0x1A (0x41792, 0xFFFFD9BFD6D03460, 0x800000, 0x0)
Error: MEMORY_MANAGEMENT
Bug check description: This indicates that a severe memory management error occurred. A corrupted PTE has been detected.
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).
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 MEMORY_MANAGEMENT
On Sun 9/1/2019 7:25:05 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\090119-10687-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1BFCC0)
Bugcheck code: 0x18 (0x0, 0xFFFFA4095DFD65A0, 0x10, 0xFFFFA4095DFDE568)
Error: REFERENCE_BY_POINTER
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 reference count of an object is illegal for the current state of the object.
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.
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
4 crash dumps have been found and analyzed. 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:
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.
Jos jedan log :
6 crash dumps have been found and analyzed. 2 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:
aftap0901.sys (TAP-Windows Virtual Network Driver (NDIS 6.0), The OpenVPN Project)
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.
Poslednja izmena:
