Šta je novo?

Plavi ekran ili...

  • Začetnik teme skole
  • Datum pokretanja
S

skole

Član
Učlanjen(a)
08.07.2009
Poruka
31
Danas u toku rada već nekoliko puta mi se pojavljuje sledeća poruka (slika u prilogu), zatim se računar restartuje, pa radi malo, pa opet isto...
Da li imate nekakav predlog, a da nije instalacija novog windowsa...
 

Prilozi

S

skole

Član
Učlanjen(a)
08.07.2009
Poruka
31
I evo ga izveštaj...

System Information (local)

Computer name: DESKTOP-MV1HOCQ
Windows version: Windows 10 , 10.0, version 1809, build: 17763
Windows dir: C:\Windows
Hardware: GA-78LMT-USB3 6.0, Gigabyte Technology Co., Ltd.
CPU: AuthenticAMD AMD FX(tm)-8300 Eight-Core Processor AMD8664, level: 21
8 logical processors, active mask: 255
RAM: 17160515584 bytes (16,0GB)




Crash Dump Analysis



Crash dumps are enabled on your computer.

Crash dump directories:
C:\Windows
C:\Windows\Minidump

On Sun 28.6.2020. 17:12:55 your computer crashed or a problem was reported
crash dump file: C:\Windows\MEMORY.DMP
This was probably caused by the following module: ntkrnlmp.exe (nt!KeWriteProtectPAT+0x12AA)
Bugcheck code: 0xC000021A (0xFFFFAF868A52FD50, 0xFFFFFFFFC0000428, 0x0, 0x1EE80010000)
Error: STATUS_SYSTEM_PROCESS_TERMINATED
Bug check description: This means that an error has occurred in a crucial user-mode subsystem.
There is a possibility this problem was caused by a virus or other malware.
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 28.6.2020. 16:49:19 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\062820-12359-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1B6980)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF805813CE697, 0x0, 0xFFFFFFFFFFFFFFFF)
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 Sun 28.6.2020. 16:45:46 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\062820-12515-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1B6980)
Bugcheck code: 0x139 (0x3, 0xFFFFFD838D058E70, 0xFFFFFD838D058DC8, 0x0)
Error: KERNEL_SECURITY_CHECK_FAILURE
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: The kernel has detected the corruption of a critical data structure.
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 28.6.2020. 16:40:25 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\062820-12015-01.dmp
This was probably caused by the following module: hardware.sys (hardware)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80763802610, 0xFFFFE40E3882F480, 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 28.6.2020. 15:36:53 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\062820-16250-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1B6980)
Bugcheck code: 0x1A (0x403, 0xFFFF85F44C280008, 0x86000002DDCE8863, 0xFFFF00F44C280008)
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. The page table and PFNs are out of sync . This is probably a hardware error, especially if parameters 3 & 4 differ by only a single bit.
This is likely to be caused by a hardware problem. This error suggests a case of memory corruption because of a hardware problem. It is suggested you do a test on your RAM modules (memory test) and make sure your system is not getting overheated. 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.



The following dump files were found but could not be read. These files may be corrupted:
C:\Windows\Minidump\062820-10281-01.dmp




Conclusion



6 crash dumps have been found and analyzed. Only 5 are included in this report. If dump files are found and they could not be analuzed, it means they are corrupted. Because crash dumps are an emergency measure it is not uncommon for this to happen, however often it points to a problem in the storage stack. It is suggested that you run CHKDSK on your system drive to check your drive for errors.
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.
 
HyperSnap

HyperSnap

VIP
Učlanjen(a)
28.02.2012
Poruka
4.082
Treba da napravis odnosno da uradis dijagnostiku racunara. Dijagnostiku hard diska, ram memorije i drajvere grafike. Predlazem da prvo deinstaliras taj drajver, restartuj racunar i pogledaj kako ce se ponasati bez drajvera. Ako bude opet problema uradi dijagnostiku hard diska i ram memorije.
 
1

1mapstnod

Član
Učlanjen(a)
07.12.2011
Poruka
261
This was probably caused by the following module: ntoskrnl.exe (nt+0x1B6980)
...
Error: MEMORY_MANAGEMENT
...
The following dump files were found but could not be read. These files may be corrupted:
Ovo nagoveštava na problem sa RAM-om ili HD-om.
Prvo proveri RAM sa MemTest86 [1] ili MemTest86+ [2].
Ako nema grešaka sa RAM-om, proveri sa nekim live win-om ili linux-om da li HD ima loših sektora.

[1]
https://www.memtest86.com/download.htm

[2]
http://www.memtest.org/#downiso
 
S

skole

Član
Učlanjen(a)
08.07.2009
Poruka
31
I opet...

Crash dumps are enabled on your computer.

Crash dump directories:
C:\Windows
C:\Windows\Minidump

On Sun 5.7.2020. 21:59:39 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\070520-9234-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1C23A0)
Bugcheck code: 0x139 (0x4, 0xFFFFBF01B3917FF0, 0xFFFFBF01B3917F48, 0x0)
Error: KERNEL_SECURITY_CHECK_FAILURE
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: The kernel has detected the corruption of a critical data structure.
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 5.7.2020. 21:57:07 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\070520-8640-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1C23A0)
Bugcheck code: 0x139 (0x3, 0xFFFFEF06156296A0, 0xFFFFEF06156295F8, 0x0)
Error: KERNEL_SECURITY_CHECK_FAILURE
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: The kernel has detected the corruption of a critical data structure.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.





Conclusion



2 crash dumps have been found and analyzed. No offending third party drivers have been found. Connsider using WhoCrashed Professional which offers more detailed analysis using symbol resolution. Also configuring your system to produce a full memory dump may help you.


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.
 
1

1mapstnod

Član
Učlanjen(a)
07.12.2011
Poruka
261
I opet...

Crash dumps are enabled on your computer.
Naravno da je opet. Problem neće nestati sam od sebe. Ako ništa ne preduzmeš biće stalno "i opet..." i "i opet..." i ...
Sve u svemu to nije vest. Vest će biti kada uradiš nešto od predloženog i javiš rezultate?

Ako nešto ne razumeš u preporukama koje su ti poslate, pitaj.
 
S

skole

Član
Učlanjen(a)
08.07.2009
Poruka
31
1mapstnod, potpuno si u pravu izvinjavam se. Imao sam problema sa pokretanjem memtesta. Juče sam radio test memorije, ali sam ga prekinuo jer je test trajao 5 sati... Danas ću se potruditi da probam ponovo, za sada, ako to išta znači kačim sliku pre prekida... Do sada nikad nisam testirao memoriju i nemam pojma u kom obliku treba da bude izveštaj kako bi ste znali da uočite/rešite problem? Unapred zahvalan na pomoći koju mi pružate. Nisam napisao da na ploči imam tri slota popunjena, jedan sa memorijom od 8 Gb HyperX Kingston na 1600 MHz i dva puta po 4 Gb HyperX Kingston, čini mi se od 1866 MHz.
 

Prilozi

HyperSnap

HyperSnap

VIP
Učlanjen(a)
28.02.2012
Poruka
4.082
Pa eto, imas problem sa memorijom. Testiraj jednu po jednu, ne moras dugo pustat, izbaci eror odmah na pocetku, nakon 3,4 minuta.
 
1

1mapstnod

Član
Učlanjen(a)
07.12.2011
Poruka
261
... nemam pojma u kom obliku treba da bude izveštaj kako bi ste znali da uočite/rešite problem?
Greške su označene crveno. Kada nema grešaka, tada je ta polovina ekrana prazna.

imam tri slota popunjena,
Testiraj svaki modul zasebno da bi utvrdio koji je neispravan. Čim se pojave crveni rezultati možeš prekinuti test i smatrati da je modul neispravan.

Inače, kada kompletno testiranje završi, automatski krene ponovo. Indikacija da je ceo test završio se nalazi u liniji iznad grešaka: Pass. Broj iza pokazuje koliko puta je test urađen, tj. kada ispiše 1, a pri tome nema grešaka možeš modul(e) smatrati ispravnim.
 
Top