blue screen windows 7

Δες την αναφορά του whocrashed και κάνε επικόλληση την αναφορά εδώ.
https://www.pcsteps.gr/450-ανάλυση-μπλε-οθόνης/

αυτο το αποτελεσμα με βγαζει και πριν το φορματ και μετα  το προβλημα παραμενει σου ανεβαζω το report
System Information (local)

Computer name: DESKTOP-AEIOR8T
Windows version: Windows 10 , 10.0, build: 10586
Windows dir: C:\Windows
Hardware: ASUSTeK Computer INC., P5QPL-AM
CPU: GenuineIntel Intel(R) Core(TM)2 Quad CPU Q6600 @ 2.40GHz Intel586, level: 6
4 logical processors, active mask: 15
RAM: 2110902272 bytes total

Crash Dump Analysis

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Mon 18/7/2016 11:35:37 πμ GMT your computer crashed
crash dump file: C:\Windows\Minidump\071816-9078-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x253522)
Bugcheck code: 0x124 (0x0, 0xFFFFFFFF8AFB6024, 0x0, 0x0)
Error: WHEA_UNCORRECTABLE_ERROR
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).
This is likely to be caused by a hardware problem problem. This problem might also be caused because of overheating (thermal issue).
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 18/7/2016 11:04:46 πμ GMT your computer crashed
crash dump file: C:\Windows\Minidump\071816-8437-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x117F10)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFFFFF82309615, 0x0, 0x1665B8)
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 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 18/7/2016 11:04:46 πμ GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrpamp.exe (nt+0x117F10)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFFFFF82309615, 0x0, 0x1665B8)
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.
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: ntkrpamp.exe .
Google query: ntkrpamp.exe KMODE_EXCEPTION_NOT_HANDLED

On Mon 18/7/2016 10:53:27 πμ GMT your computer crashed
crash dump file: C:\Windows\Minidump\071816-7484-01.dmp
This was probably caused by the following module: hal.sys (hal+0x36846)
Bugcheck code: 0x124 (0x0, 0xFFFFFFFF8B7B501C, 0xFFFFFFFFB2000040, 0x800)
Error: WHEA_UNCORRECTABLE_ERROR
Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).
This is likely to be caused by a hardware problem problem. This problem might also be caused because of overheating (thermal issue).
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: hal.sys .
Google query: hal.sys WHEA_UNCORRECTABLE_ERROR

On Mon 18/7/2016 10:47:39 πμ GMT your computer crashed
crash dump file: C:\Windows\Minidump\071816-8390-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x117EC0)
Bugcheck code: 0x50 (0xFFFFFFFF83A142F0, 0x0, 0xFFFFFFFF81CE8667, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
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 invalid system memory has been referenced.
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 18/7/2016 9:16:30 πμ GMT your computer crashed
crash dump file: C:\Windows\Minidump\071816-9453-01.dmp
This was probably caused by the following module: ntfs.sys (NTFS+0x80373)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFFFFF81CE387A, 0x0, 0x3A517750)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\drivers\ntfs.sys
product: Λειτουργικό σύστημα Microsoft® Windows®
company: Microsoft Corporation
description: Πρόγραμμα οδήγησης συστήματος αρχείων NT
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 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.

Conclusion

6 crash dumps have been found and analyzed. 2 third party drivers have been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers:

hal.sys
ntkrpamp.exe

If no updates for these drivers are available, try searching with Google on the names of these drivers in combination with the errors that have been reported for these drivers. Include the brand and model name of your computer as well in the query. This often yields interesting results from discussions on the web by users who have been experiencing similar problems.

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 για τα 10, το πρόβλημα μπορεί να προέρχεται από εκεί.
Αν έχεις στο σύστημα σου διάφορα tune-up utilities οι εφαρμογές για drivers αφαίρεσε τες και δες αν το πρόβλημα συνεχίζεται.

ΚΑΙ ΣΤΑ WINDOWS 7 ΕΚΑΝΕ ΤΟ ΙΔΙΟ ΠΡΟΒΛΗΜΑ ΤΕΛΙΚΑ ΑΝΑΚΑΛΥΨΑ ΟΤΙ ΠΡΟΕΡΧΟΤΑΝ ΑΠΟ ΕΝΑΝ ΕΚΤΥΠΩΤΗ ΤΗΣ HP F4580 ΜΟΛΙΣ ΕΚΑΝΑ ΕΓΚΑΤΑΣΤΑΣΗ ΤΟ ΛΟΓΙΣΜΙΚΟ  ΤΟΥ ΤΟΤΕ ΞΕΚΙΝΟΥΣΑΝ ΟΙ ΜΠΛΕ ΟΘΟΝΕΣ ΠΡΟΤΟΥ ΜΠΕΙ ΑΥΤΟ ΤΙΠΟΤΑ ΟΛΑ ΚΑΛΑ ΜΗΠΩΣ ΥΠΑΡΧΕΙ ΑΛΛΟΣ ΟΔΗΓΟΣ ΓΙΑ ΤΟΝ ΣΥΓΚΕΚΡΙΜΕΝΟ ΕΚΤΥΠΩΤΗ ΕΚΤΟΣ ΑΠΟ ΤΗΣ ΣΕΛΙΔΑΣ ΤΟΥ ΠΟΥ ΝΑ ΜΗΝ ΔΗΜΙΟΥΡΓΕΙ ΛΕΤΕ ΤΕΤΟΙΑ ΠΡΟΒΗΜΑΤΑ????

Εδώ είναι οι οδηγοί, οι οποίοι είναι εγγυημένο ότι δουλεύουν, drivers από οπουδήποτε άλλου μπορεί να μην είναι αυτό που λένε
http://support.hp.com/gr-el/drivers/selfservice/HP-Deskjet-F4500-All-in-One-Printer-series/3944755/model/3944756
Κάτω από τους drivers έχει και βοηθητικές εφαρμογές, δοκίμασε τες μήπως βρουν το πρόβλημα

Τους εχω κατεβασει και για 7 και για 10 αυτους δουλευω αλλα ενω υπαρχεi drivers για 10 μολις κανω εγκατασταση μου πεταει μυνημα για το hp bar που υπαρχει μεσα στην εγκατασταση οτι δεν ειναι συμβατο και μπορει να δημιουργησει προβλημα στον υπολογιστη , ολα αυτο και το μυνημα ειναι της εγκαταστασης ειναι απο τον υπολογιστη και οχι απο το προγραμμα εγκαταστασης.εντωμεταξυ που τον εχω κουμπωσει σε αλλο υπολογιστη δεν πολυ μικροτερο σε ισχυ δεν κανει απολυτως τιποτα παλι με windows 10.Φοβαμαι μηπως στην μητρικη ειναι το προβλημα απο τον controller των usb αλλιως το βλεπω αδυνατο

Δεν είναι λάθος το σκεπτικό σου, από την στιγμή που δεν διαθέτει επίσημους drivers για τα 10 η μητρική, μπορεί όντως να είναι πρόβλημα με τον controller usb.

Μπορείς να δοκιμάσεις από την διαχείριση συσκευών, να κάνεις κατάργηση όλα τα usb ports και μετά επανεκκίνηση, μήπως και είσαι τυχερός και λυθεί το πρόβλημα.