Windows 10 se seká.

od **vlado33** 29. 4. 2019 13:26

CHybu 10016 budu ignorovat.Já mysle že může za to že mi občas zamrzne PC,nic nejde jenom kurzorem myši mohu pohybovat.V MINIDUMPU je toto :

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

Crash dumps are enabled on your computer.

Crash dump directories:
C:\WINDOWS
C:\WINDOWS\Minidump

On Mon 29.4.2019 10:37:25 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\042919-31890-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x318794)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF80418FC1794, 0xFFFFC90321CFB6A8, 0xFFFFC90321CFAEF0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
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 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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

On Mon 29.4.2019 10:37:25 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\MEMORY.DMP
This was probably caused by the following module: usbhub.sys (usbhub+0x48991)
Bugcheck code: 0x7E (0xFFFFFFFFC0000005, 0xFFFFF80418FC1794, 0xFFFFC90321CFB6A8, 0xFFFFC90321CFAEF0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
file path: C:\WINDOWS\system32\drivers\usbhub.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Default Hub Driver for USB
Bug check description: This bug check indicates that a system thread generated an exception that the error handler did not catch.
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.

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

On Mon 29.4.2019 10:37:25 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\042919-31890-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x318794)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF80418FC1794, 0xFFFFC90321CFB6A8, 0xFFFFC90321CFAEF0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
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 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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

On Mon 29.4.2019 10:37:25 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\MEMORY.DMP
This was probably caused by the following module: usbhub.sys (usbhub+0x48991)
Bugcheck code: 0x7E (0xFFFFFFFFC0000005, 0xFFFFF80418FC1794, 0xFFFFC90321CFB6A8, 0xFFFFC90321CFAEF0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
file path: C:\WINDOWS\system32\drivers\usbhub.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Default Hub Driver for USB
Bug check description: This bug check indicates that a system thread generated an exception that the error handler did not catch.
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.
Prosím kde je chyba.

od **Milanr1** 29. 4. 2019 14:03

Je to napsané v protokolu:

vlado33 usbhub.sys
company: Microsoft Corporation
description: Default Hub Driver for USB

Kde spáchal admin chyby:
nezakázal nejhorší zhůvěřilosti W10, především:
1) FastBoot;
2) automatickou instalaci ovladačů z MS WU.
Co s tím?
1) Naprav chyby admina.
2) Stáhni a nainstaluj korektní ovladač od výrobce řadiče USB.
Obecné parodie na ovladače z MS WU málokdy pracují korektně.

od **vlado33** 29. 4. 2019 15:07

Mám Windows 10 home a z.d.MSI 7380 a ovladače USB 10.0.17763.1 z roku 2006.Bud tak hodný a dej mi odkaz kde stáhnu jiný ovladač.Děkuji

od **Milanr1** 29. 4. 2019 18:00

Není Ti jasné, že ovladač z r. 2006 nemůže být kompatibilní s W10, který byl uveden až v r. 2015 (v komerční verzi)?

vlado33 píše: kde stáhnu jiný ovladač

Nikde.
Daný MB není kompatibilní s W10.
Co s tím?
1) Do daného MB Instaluj podporovaný OS.
2) Pro W10 kup moderní hw sestavu.

od **vlado33** 29. 4. 2019 18:07

Díky Tebě tak to mě nenapadlo.KONEC

od **Kaulik** 30. 4. 2019 06:48

Milan jen vše říká napřímo a nebalí to do žádné vaty, ale má pravda. Stejně jako je hloupost a není moc funkční na nový HW instalovat starší windows, tak není rozumné na starý HW nainstalovat nové windows..

Dle oficiálních stránek, má deska poslední podporu pro win 7. Ale ovladače tam jsou ještě i z roku 2010/2011, takže 2006 doopravdy není dobré.

V konečné fázi má Milan zkrátka pravda. Řešení pádů je vrátit se na w7 nebo upgrade sestavy. Upřímně socket 775 je dneska doopravdy už muzejní kousek.

od **nuvi_joe** 30. 4. 2019 08:08

Kaulik: "...Stejně jako je hloupost a není moc funkční na nový HW instalovat starší windows, tak není rozumné na starý HW nainstalovat nové windows..."

Marketing Microsoftu v roce 2015 uváděl, že W10 půjdou spustit i na starším HW. Instalace W10 obsahuje tzv. generické ovladače - rozuměj očesané ovladače výrobce periferií. Ty měly zajišťovat základní funkce. Obvykle to nějak fungovalo.
Když ne, byla možnost zahrát v loterii a zkusit ovladače pro W8, nebo dokonce pro W7.
A potom vypnout automatickou aktualizaci ovladačů, což Mikrosoft velkoryse dovolil.