Šta je novo?

win10 restart

oogabooga

Slavan
Učlanjen(a)
20.10.2003
Poruke
2,883
Poena
390
pre neki dan, poceo win10 da izbacuje neku gresku, i da mora da se restartuje. e sad, nisam uspeo da pokupim koje su greske, u stvari dve jesam, doel izbaci i QR kod za skeniranje, jedno 10tak sekundi prikuplja podatke i kao salje microsoftu.
dve greske koje sam uspeo da vidim su: memory management, i luafv.sys, ali bilo je jos nekoliko razlicitih.
prekjuce, pre nego sam odradio ponovo fresh install win-a, poludeo pa se nonstop restartovao sa izbacivanjem te neke greske i QR koda. posle fresh installa, do jutros nista, i evo, sad pocelo opet.
probam na drugom kompu koji nisam palio dosta dugo, a isto je win10, kad ono isto. needs restart, prikuplja za izvestaj, i QR kod.....

ima li ko ideju sta je u pitanju?

hvala
 
Poslednja izmena:
evo:

Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dumps are enabled on your computer.

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

On Thu 1/30/2020 10:34:44 AM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\013020-43281-01.dmp
This was probably caused by the following module: luafv.sys (0xFFFFF80065220FEB)
Bugcheck code: 0xBE (0xFFFFF80065220FEB, 0x89000001259EC121, 0xFFFF9888A3753A30, 0xB)
Error: ATTEMPTED_WRITE_TO_READONLY_MEMORY
file path: C:\Windows\system32\drivers\luafv.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: LUA File Virtualization Filter 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.
The crash took place in a 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 1/30/2020 10:34:44 AM your computer crashed or a problem was reported
crash dump file: C:\Windows\MEMORY.DMP
This was probably caused by the following module: fltmgr.sys (FLTMGR!FltDecodeParameters+0x1CFC)
Bugcheck code: 0xBE (0xFFFFF80065220FEB, 0x89000001259EC121, 0xFFFF9888A3753A30, 0xB)
Error: ATTEMPTED_WRITE_TO_READONLY_MEMORY
file path: C:\Windows\system32\drivers\fltmgr.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Microsoft Filesystem Filter Manager
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.
The crash took place in a file system driver. Since there is no other responsible driver detected, this could be pointing to a malfunctioning drive or corrupted disk. It's suggested that you run CHKDSK.



On Thu 1/30/2020 10:29:22 AM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\013020-36937-01.dmp
This was probably caused by the following module: ntfs.sys (0xFFFFF80228A4B4D0)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF80228A4B4D0, 0xFFFFD30310636018, 0xFFFFD30310635860)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
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 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 file system driver. Since there is no other responsible driver detected, this could be pointing to a malfunctioning drive or corrupted disk. It's suggested that you run CHKDSK.



On Thu 1/30/2020 8:18:14 AM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\013020-35218-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1C14E0)
Bugcheck code: 0xA (0x48, 0x2, 0x1, 0xFFFFF8066DA30126)
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 Thu 1/30/2020 2:15:06 AM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\013020-36156-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1C14E0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80663E3AD44, 0xFFFFD300C48D1930, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 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.
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 1/29/2020 2:57:25 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\012920-36671-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1C14E0)
Bugcheck code: 0xA (0xA0000000, 0x2, 0x1, 0xFFFFF8004D405E4E)
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.





--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------

6 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.
 
Kao što rekoh memorija ili disk. prvih 3 su disk ( kaže da radiš CHKDIK a ostali za memoriju , mogućno za virtuelnu a to je na disku.
 
disk ne verujem da jeste, jer sam instalirao win10 na skroz drugom disku, i opet isto.....

mem test za sada nista ne pokazuje..... :

m1.jpg
 
ne, to nije na toj masini iz potpisa, ovo je gigabyte B450 aorus M, ryzen 2600X i samsung 1x16gb DDR4

ova iz potpisa radi perfektno vec duze meseci :)
 
Da li vidiš koliko je temperatura na procesoru?
Pazi, nisam odavno radio memtest pa ne znam koliko je to realno na ryzen-ima.
 
neznam za ovo u memtestu, ali u igrama nije presao 50C nikad, u leru je 28-30C

cpu.PNG
 
Proveri da li ti je instaliran update KB4528760. Ako jeste deinstaliraj ga.
 
da bi otklonio sumnju oko temperature cpu, evo prime 95, vrteo oko pola sata, nije presao 68C:

prime1.PNG
 
deinstalirao taj update, komp trazio restart, ja kliknuo da se restartuje, i u sre d restarta, izbaci ovo:

error2.jpg

e lepo cu ga polupati
 
Koliko vidim imaš slične simptome koje imaju mnogi korisnici kojima se instalirao taj update. Za sada nema hotfix-a. Pokušaj na tom drugom kompu da ponovo intaliraš Win i prati situaciju. Moja preporuka je da staviš neki update bloker i da osvešavaš windows mesečno kada se već sve ispegla. Možda grešim u vezi ovoga ali pošto imaš isti simptom na 2 kompa može biti to ili da si "pazario" neki virus.
 
najludje, ja deinstaliram taj update, on se posle restarta instalira sam ponovo.
na drugom kompu sam ubio windows ali sa izvucenim lan kablom, pa mi nije povukao nikakve apdejte, i za sada on radi kako treba
 
Skini "Windows update blocker" pokreni ga i onemogući sistem update. Onda deinstaliraj pomenuti KB i prati situaciju.
 
evo sad ga nema, posle treceg deinstaliranja, ali se mmisteriozno pojavio update KB4524570, neznam moze li taj praviti neke probleme.....
 
Koliko vidim na netu se samo žale da KB4524570 puca pri instalaciji. Tebi je prošao i to je to.
 
znaci, sem uodate blockera sto cu instalirati, da vise nista ne cackam onda?
 
Da samo klika na disable updates u appy, napiši kakva je situacija...
 
Nazad
Vrh Dno