Μπλε οθόνη σε windows 10

Ρίξε μια ματιά στο whocrashed και γράψε μας τι θα σου βγάλει
https://www.pcsteps.gr/450-ανάλυση-μπλε-οθόνης/

 Αυτά έβγαλε:
Crash Dump Analysis

Crash dump directory: C:\WINDOWS\Minidump

Crash dumps are enabled on your computer.

On Wed 8/6/2016 1:39:06 πμ GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\060816-81156-01.dmp
This was probably caused by the following module: dxgkrnl.sys (dxgkrnl!ADAPTER_RENDER::DdiRender+0x143)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8006B73B7F3, 0xFFFFD000E2E5A640, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\WINDOWS\system32\drivers\dxgkrnl.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics Kernel
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 a standard 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 Wed 8/6/2016 1:39:06 πμ GMT your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: dxgkrnl.sys (dxgkrnl!ADAPTER_RENDER::DdiRender+0x143)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8006B73B7F3, 0xFFFFD000E2E5A640, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\WINDOWS\system32\drivers\dxgkrnl.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics Kernel
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 a standard 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 Wed 8/6/2016 1:25:31 πμ GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\060816-85421-01.dmp
This was probably caused by the following module: npfs.sys (Npfs!NpFsdWrite+0x80)
Bugcheck code: 0xA (0xFFFFF8002D592240, 0x2, 0x0, 0xFFFFF8002C303E4E)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\WINDOWS\system32\drivers\npfs.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NPFS Driver
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
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 standard 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 Wed 8/6/2016 1:09:48 πμ GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\060816-100265-01.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF80033E84292, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
Bug check description: This indicates that a kernel-mode program 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.

Conclusion

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

Αρχικά κάνε απεγκατάσταση των drivers της κάρτας γραφικών και εγκατάσταση ξανά, τα περισσότερα δείχνουν εκεί, και δοκίμασε μετά ξανά το μηχάνημα σου.

Οκ, ευχαριστώ.

Γειά σας, έχω πρόβλημα με τις μπλέ οθόνες τελευταία και δεν ξέρω τι να κάνω.Έχω windows 10 και έχω φτιάξει εγώ ο ίδιος το pc μου πρίν 2 μήνες με όλα τα συμβατά εξαρτήματα, ωστόσο ο σκληρός δίσκος που του έβαλα είναι από τον παλιό μου υπολογιστή και έχει περίπου 6 χρόνια που λειτουργεί, μήπως γι αυτό μου βγάζει το πρόβλημα? γιατί όταν μου είχε βγάλει και ποιό πριν μπλέ οθόνη τα διόρθωνα όλα με το who crashed, αλλά τις 3 τελευταίες μέρες μου βγάζει μπλέ οθόνη ενώ μετά δεν μου λέει τίποτα στο who crashed λες και δεν υπήρξε κανένα πρόβλημα. Η μπλέ οθόνη που λέω εμφανίζεται κάθε φορά που αποσυνδέω - επανασυνδέω το usb της Wifi κεραίας μου πάνω απο 2 φορές ή μπορεί και την 1η φορά. Περιμένω την απάντησή σας ...

Θα πρέπει να ανοίξεις δικιά σου ερώτηση, κάνε έναν έλεγχο πάντως τον σκληρό σου με το Crystal disk info
https://www.pcsteps.gr/1385-πρόβλεψη-αποτυχίας-δίσκου-εγκαίρως/

@User Youtube, @Υποστήριξη PCsteps (Νίκος)  : Το δικό μου πρόβλημα συνεχίζεται. Έκανα format και πέρασα από την αρχή τα windows 10. Για δύο μέρες όλα πήγαιναν μια χαρά. Από την τρίτη μέρα, μόλις πάω να δω κάποιο βίντεο, σε ένα-δυο λεπτά μου βγάζει μπλε οθόνη. Να σημειώσω ότι αν κατεβάσω και αποθηκεύσω το βίντεο, δεν έχω πρόβλημα. Αν, όμως, θέλω να το δω on-line, μου βγάζει μπλε οθόνη. Προσπάθησα να κάνω αναβάθμιση τους drivers, από τη Διαχείριση Συσκευών, αλλά μου βγάζει ότι είναι ενημερωμένοι.
Αυτή είναι η διάγνωση με το WhoCrashed:
On Fri 24/6/2016 12:37:28 πμ GMT your computer crashed
crash dump file: C:\Windows\Minidump\062416-44046-01.dmp
This was probably caused by the following module: npfs.sys (Npfs!NpWriteDataQueue+0x112)
Bugcheck code: 0x19 (0xE, 0xFFFFE000990DBB00, 0x5CF919ECBEE4E729, 0x5CF919EC24E4E729)
Error: BAD_POOL_HEADER
file path: C:\Windows\system32\drivers\npfs.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NPFS Driver
Bug check description: This indicates that a pool header is corrupt.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in a standard 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 Fri 24/6/2016 12:37:28 πμ GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: npfs.sys (Npfs!NpWriteDataQueue+0x112)
Bugcheck code: 0x19 (0xE, 0xFFFFE000990DBB00, 0x5CF919ECBEE4E729, 0x5CF919EC24E4E729)
Error: BAD_POOL_HEADER
file path: C:\Windows\system32\drivers\npfs.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NPFS Driver
Bug check description: This indicates that a pool header is corrupt.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in a standard 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 23/6/2016 2:24:05 πμ GMT your computer crashed
crash dump file: C:\Windows\Minidump\062316-48921-01.dmp
This was probably caused by the following module: athw8x.sys (athw8x+0x19836A)
Bugcheck code: 0xBE (0xFFFFF8019FD66D50, 0x2387B4121, 0xFFFFF800879C62B0, 0xA)
Error: ATTEMPTED_WRITE_TO_READONLY_MEMORY
file path: C:\Windows\system32\drivers\athw8x.sys
product: Driver for Qualcomm Atheros CB42/CB43/MB42/MB43 Network Adapter
company: Qualcomm Atheros Communications, Inc.
description: Qualcomm Atheros Extensible Wireless LAN device 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.
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: athw8x.sys (Qualcomm Atheros Extensible Wireless LAN device driver, Qualcomm Atheros Communications, Inc.).
Google query: Qualcomm Atheros Communications, Inc. ATTEMPTED_WRITE_TO_READONLY_MEMORY

On Wed 22/6/2016 11:42:40 μμ GMT your computer crashed
crash dump file: C:\Windows\Minidump\062316-40703-01.dmp
This was probably caused by the following module: athw8x.sys (athw8x+0x67CC3)
Bugcheck code: 0x1E (0xFFFFFFFFC000001D, 0xFFFFF801FAF07CC3, 0xFFFFE001EB040800, 0xFFFFF801F9C02240)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\drivers\athw8x.sys
product: Driver for Qualcomm Atheros CB42/CB43/MB42/MB43 Network Adapter
company: Qualcomm Atheros Communications, Inc.
description: Qualcomm Atheros Extensible Wireless LAN device driver
Bug check description: This indicates that a kernel-mode program 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.
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: athw8x.sys (Qualcomm Atheros Extensible Wireless LAN device driver, Qualcomm Atheros Communications, Inc.).
Google query: Qualcomm Atheros Communications, Inc. KMODE_EXCEPTION_NOT_HANDLED

@theodoros chloridis Αν το πρόβλημα σου είναι στα online videos, πήγαινε από τις ρυθμίσεις του chrome στις σύνθετες ρυθμίσεις και απενεργοποίησε την επιτάχυνση υλικού.
Στο crashdump βλέπω και ένα πρόβλημα με atheros wireless lan, δες αν υπάρχουν drivers για αυτό ή αν είναι συμβατό με το λειτουργικό σου.

@Υποστήριξη PCsteps (Νίκος): Οι drivers για το atheros wireless lan είναι συμβατοί και είναι ενημερωμένοι. Παρ' όλα αυτά, τους διέγραψα  και τους εγκατέστησα από την αρχή, χωρίς όμως αποτέλεσμα.
Απενεργοποίησα και την επιτάχυνση υλικού του chrome και αναμένω το αποτέλεσμα.
Ευχαριστώ για άλλη μια φορά.