»RSS Benchmark sajt

      Strana 1 od 2 12 PoslednjaPoslednja
      Prikazani rezultati od 1 do 15 od ukupno 24

      Tema: win10 restart

      1. #1
        Member
        Na forumu od
        Oct 2003
        Lokacija
        Beograd
        Poruka
        2.521
      2. Moja mašina
        • CPU: Ryzen 2600
        • MoBo: Asrock B450M Pro 4
        • RAM: 2x8GB Kingston Predator 3200Mhz
        • VGA: Radeon RX 580 8gb
        • MON: AOC C24G1 24"/bravia xe8096 55"/FOX TV 50DLE888 50"
        • HDD: 256gb ssd/480gb ssd/2x1tb hdd
        • Case: Chieftec
        • SND: integrale :)
        • OS: win7 64bit/OSX High Sierra
        • LAP: MacBook Pro/HP Elitebook 8570P
        • INET: Kablovska
        • Ostalo: PS4 Pro/iMac upgraded to i7
      3. win10 restart

        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
        Menjao oogabooga : 30.01.2020. u 10:59
        ooga....

      4. #2
        Member Avatar korisnika CountMike
        Na forumu od
        Jul 2012
        Lokacija
        Beograd. Toronto
        Poruka
        6.942
      5. Moja mašina
        • CPU: Ryzen R7 3700X, CM Nepton 140XL
        • MoBo: Asus PRIME X470 PRO
        • RAM: 2x8GB Kingston Predator 3600MHz
        • VGA: Asus strix 570 OC 4gb
        • MON: BenQ 28" + 2x Samsung 2494
        • HDD: Samsung 960Evo, 250GB, SP V70 240GB, WD Blue 2TB,WD Blue 1TB
        • Case: Raidmax Agusta (customized)
        • SND: On Board
        • OS: Win 10 Pro, Linux Mint
      6. Probaj da prikupiš više podataka sa https://www.resplendence.com/downloads za sada smrdi na memoriju ili disk.

      7. #3
        Member
        Na forumu od
        Oct 2003
        Lokacija
        Beograd
        Poruka
        2.521
      8. Moja mašina
        • CPU: Ryzen 2600
        • MoBo: Asrock B450M Pro 4
        • RAM: 2x8GB Kingston Predator 3200Mhz
        • VGA: Radeon RX 580 8gb
        • MON: AOC C24G1 24"/bravia xe8096 55"/FOX TV 50DLE888 50"
        • HDD: 256gb ssd/480gb ssd/2x1tb hdd
        • Case: Chieftec
        • SND: integrale :)
        • OS: win7 64bit/OSX High Sierra
        • LAP: MacBook Pro/HP Elitebook 8570P
        • INET: Kablovska
        • Ostalo: PS4 Pro/iMac upgraded to i7
      9. 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.
        ooga....

      10. #4
        Member Avatar korisnika djalf
        Na forumu od
        Nov 2004
        Poruka
        6.460
        Prvo MemTest86 pa sve ostalo, uradi test RAM memorije.

      11. #5
        Member Avatar korisnika CountMike
        Na forumu od
        Jul 2012
        Lokacija
        Beograd. Toronto
        Poruka
        6.942
      12. Moja mašina
        • CPU: Ryzen R7 3700X, CM Nepton 140XL
        • MoBo: Asus PRIME X470 PRO
        • RAM: 2x8GB Kingston Predator 3600MHz
        • VGA: Asus strix 570 OC 4gb
        • MON: BenQ 28" + 2x Samsung 2494
        • HDD: Samsung 960Evo, 250GB, SP V70 240GB, WD Blue 2TB,WD Blue 1TB
        • Case: Raidmax Agusta (customized)
        • SND: On Board
        • OS: Win 10 Pro, Linux Mint
      13. 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.

      14. #6
        Member
        Na forumu od
        Oct 2003
        Lokacija
        Beograd
        Poruka
        2.521
      15. Moja mašina
        • CPU: Ryzen 2600
        • MoBo: Asrock B450M Pro 4
        • RAM: 2x8GB Kingston Predator 3200Mhz
        • VGA: Radeon RX 580 8gb
        • MON: AOC C24G1 24"/bravia xe8096 55"/FOX TV 50DLE888 50"
        • HDD: 256gb ssd/480gb ssd/2x1tb hdd
        • Case: Chieftec
        • SND: integrale :)
        • OS: win7 64bit/OSX High Sierra
        • LAP: MacBook Pro/HP Elitebook 8570P
        • INET: Kablovska
        • Ostalo: PS4 Pro/iMac upgraded to i7
      16. disk ne verujem da jeste, jer sam instalirao win10 na skroz drugom disku, i opet isto.....

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

        Click image for larger version. 

Name:	m1.jpg 
Views:	52 
Size:	188,7 KB 
ID:	280849
        ooga....

      17. #7
        Member Avatar korisnika djalf
        Na forumu od
        Nov 2004
        Poruka
        6.460
        Vidim da imas 4x8GB, nisi nesto overklokovao memoriju pa to zeza? Probaj spusti je nize na 2133 da vidis da li ce da bude isto.

      18. #8
        Member
        Na forumu od
        Oct 2003
        Lokacija
        Beograd
        Poruka
        2.521
      19. Moja mašina
        • CPU: Ryzen 2600
        • MoBo: Asrock B450M Pro 4
        • RAM: 2x8GB Kingston Predator 3200Mhz
        • VGA: Radeon RX 580 8gb
        • MON: AOC C24G1 24"/bravia xe8096 55"/FOX TV 50DLE888 50"
        • HDD: 256gb ssd/480gb ssd/2x1tb hdd
        • Case: Chieftec
        • SND: integrale :)
        • OS: win7 64bit/OSX High Sierra
        • LAP: MacBook Pro/HP Elitebook 8570P
        • INET: Kablovska
        • Ostalo: PS4 Pro/iMac upgraded to i7
      20. 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
        ooga....

      21. #9
        Member
        Na forumu od
        Oct 2003
        Lokacija
        Beograd
        Poruka
        2.521
      22. Moja mašina
        • CPU: Ryzen 2600
        • MoBo: Asrock B450M Pro 4
        • RAM: 2x8GB Kingston Predator 3200Mhz
        • VGA: Radeon RX 580 8gb
        • MON: AOC C24G1 24"/bravia xe8096 55"/FOX TV 50DLE888 50"
        • HDD: 256gb ssd/480gb ssd/2x1tb hdd
        • Case: Chieftec
        • SND: integrale :)
        • OS: win7 64bit/OSX High Sierra
        • LAP: MacBook Pro/HP Elitebook 8570P
        • INET: Kablovska
        • Ostalo: PS4 Pro/iMac upgraded to i7
      23. i dalje vrti bez gresaka.....:

        Click image for larger version. 

Name:	m2.jpg 
Views:	58 
Size:	209,2 KB 
ID:	280852
        ooga....

      24. #10
        Member
        Na forumu od
        Jan 2002
        Lokacija
        Pančevo
        Poruka
        359
        Da li vidiš koliko je temperatura na procesoru?
        Pazi, nisam odavno radio memtest pa ne znam koliko je to realno na ryzen-ima.

      25. #11
        Member Avatar korisnika djalf
        Na forumu od
        Nov 2004
        Poruka
        6.460
        Ako je tacno onda nesto nije u redu, 91C?

      26. #12
        Member
        Na forumu od
        Oct 2003
        Lokacija
        Beograd
        Poruka
        2.521
      27. Moja mašina
        • CPU: Ryzen 2600
        • MoBo: Asrock B450M Pro 4
        • RAM: 2x8GB Kingston Predator 3200Mhz
        • VGA: Radeon RX 580 8gb
        • MON: AOC C24G1 24"/bravia xe8096 55"/FOX TV 50DLE888 50"
        • HDD: 256gb ssd/480gb ssd/2x1tb hdd
        • Case: Chieftec
        • SND: integrale :)
        • OS: win7 64bit/OSX High Sierra
        • LAP: MacBook Pro/HP Elitebook 8570P
        • INET: Kablovska
        • Ostalo: PS4 Pro/iMac upgraded to i7
      28. neznam za ovo u memtestu, ali u igrama nije presao 50C nikad, u leru je 28-30C

        Click image for larger version. 

Name:	cpu.PNG 
Views:	45 
Size:	24,5 KB 
ID:	280861
        ooga....

      29. #13
        Member Avatar korisnika djalf
        Na forumu od
        Nov 2004
        Poruka
        6.460
        Onda nije tacno u mem testu verovatno.

      30. #14
        Member
        Na forumu od
        Mar 2011
        Poruka
        44
        Proveri da li ti je instaliran update KB4528760. Ako jeste deinstaliraj ga.

      31. #15
        Member
        Na forumu od
        Oct 2003
        Lokacija
        Beograd
        Poruka
        2.521
      32. Moja mašina
        • CPU: Ryzen 2600
        • MoBo: Asrock B450M Pro 4
        • RAM: 2x8GB Kingston Predator 3200Mhz
        • VGA: Radeon RX 580 8gb
        • MON: AOC C24G1 24"/bravia xe8096 55"/FOX TV 50DLE888 50"
        • HDD: 256gb ssd/480gb ssd/2x1tb hdd
        • Case: Chieftec
        • SND: integrale :)
        • OS: win7 64bit/OSX High Sierra
        • LAP: MacBook Pro/HP Elitebook 8570P
        • INET: Kablovska
        • Ostalo: PS4 Pro/iMac upgraded to i7
      33. da bi otklonio sumnju oko temperature cpu, evo prime 95, vrteo oko pola sata, nije presao 68C:

        Click image for larger version. 

Name:	prime1.PNG 
Views:	37 
Size:	511,6 KB 
ID:	280890
        ooga....

      Strana 1 od 2 12 PoslednjaPoslednja

      Bookmarks

      Dozvoljeni tagovi

      • Ne možete pokrenuti nove teme
      • Ne možete odgovoriti u temi
      • Ne možete okačiti atačmente
      • Ne možete izmeniti svoje poruke
      •