BSOD

tohle je první

Tohle je druhý

A třetí... moc vám děkuji!

sestava ...
ZD: Zdroj Seasonic S12II-520W (SS-520GB F3) 80Plus Bronze
MB: GIGABYTE s.AM4 AB350-Gaming 3, AMD B350 Ryzen
GK: MSI NVIDIA GTX 1050 Ti AERO ITX 4G OCV1
CPU: AMD RYZEN 3 1200 chladič Wraith Stealth
RAM: DIMM ADATA DDR4 XPG Gammix D10, 8GB, 3000MHz, CL16
HD: CRUCIAL BX500 SSD 480GB SATA 6Gb/s

Tobe také dobry vecer.
- Myslis ze by jsi mohl stahnout a spustit BSOD MS nebo "what crashed" pro lepsi prehlednost ?

prosim hodite mi odkaz? pod BSOD MS jsem ke staženi nic nenašel :)

nebo z Who Crashed
System Information (local)
--------------------------------------------------------------------------------

Computer name: PATRIK
Windows version: Windows 10 , 10.0, build: 17134
Windows dir: C:\Windows
Hardware: AB350-Gaming 3, Gigabyte Technology Co., Ltd., AB350-Gaming 3-CF
CPU: AuthenticAMD AMD Ryzen 3 1200 Quad-Core Processor AMD586, level: 23
4 logical processors, active mask: 15
RAM: 8538116096 bytes total

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

Crash dumps are enabled on your computer.

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

On Tue 20.11.2018 16:45:39 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\112018-6828-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1A9690)
Bugcheck code: 0xA (0xFFFFF80280B0E070, 0x2, 0x0, 0xFFFFF80281BC5806)
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 Tue 20.11.2018 16:45:39 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!setjmpex+0x7499)
Bugcheck code: 0xA (0xFFFFF80280B0E070, 0x2, 0x0, 0xFFFFF80281BC5806)
Error: IRQL_NOT_LESS_OR_EQUAL
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 Tue 20.11.2018 16:35:24 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\112018-6343-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1A9690)
Bugcheck code: 0x3B (0xC0000047, 0xFFFFF80105483758, 0xFFFFBE8E8963D930, 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 Tue 20.11.2018 16:11:23 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\112018-20171-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1A9690)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF800C0178270, 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.

- Ano podivam se, mel bys ho najit nekde tady : https://docs.microsoft.com/en-us/sysinternals/downloads/process-utilities. Klidne muzes pouzit i :
• WHO_Crached → https://www.majorgeeks.com/files/details/whocrashed_free_home_edition.html
• BlueScreen → https://www.nirsoft.net/utils/blue_screen_view.html

PS : Z vyse uvedeného CRASH je uvedeno ze jde oproblém s : " kernel-- ntoskrnl.exe".
- Vice informaci naleznes zde : https://en.wikipedia.org/wiki/Ntoskrnl.exe
*Zdroj Wikipedia.

[INFO] ~ Popripade nez se na to podivame hloubeji , by pomohlo, kdyby jsi provedl rychli [Memory_Test], sputit ho muzes pres prikazovy radek - kombinace klaves [WIN + R] → a do radku napis :

mdsched

* Jestli nemas otevrenou nejakou praci, tak nasledovne zadej → "Restartovat nyni".

dobře udělam test ramek... za nějakou chvili něco mam rozdělane.... je možne ale že to zpusobila graficka karta která byla jak jsem si až ted všiml silně přetaktovana??? procesor byl take přetaktovan a raději už je vše v defaultu... stavalo se to při hrani CSGO... ted už to neděla... :O

Ano muze, tak jak jeho ovladac, ale k tomu se dostaneme pozdeji po provedeném testu pameti.
* U Overclockingu jsou (kernel) chyby bezné, v pripade ze nedoslo k HW poskozen jdou zpravidla odstranit.

takže.. nevim kam se vysledek uložil ale dokud to nezmizlo tak test nezjistil potíže

dodatek.. po tom co jsem si všiml že ja idiot jsem přetaktoval grafiku na +50 +150 MHz a dal to zpátky na default... taktež pro sichr i CPU na default clock tak jsem dělal ještě testy CPU, ramek i GPU přes OCCT, při hraní CSGO (ta hra předtim padala a pak i ty BSOD) už žadný problém.... nechci to zakřiknout ale snad mam pokoj... jinak na Facebooku jsem psal do komentu jakou mam voltaž a psali mi že to mam podvoltovane.... ja se toho bojim těch voltu, že mi to spálí obvody... měl jsem to na 1,2*** ...pak jsem zkoušel i 1,3 a jelo to v zatěži vpoho.. až pak po zapnutí cska to začalo házet BSOD a padat.... v poradně na FB mi psali že ty AMDčka mají volty rády, že max mužu jit až 1,45... tak snad už to bude vpoho.. dam tomu radši pokoj

Na FB sa kazdy tyzden pise ze ak das like prispevku tak ze vyhras pracku, vsetci lajkuju, a nikdy nikdo na FB ziadnu pracku nevyhral.

však jasne... :D