Μπλε οθόνη, το αιτιο γνωστο η λυση αγνωστη!

[gepapani]

Καλησπερα, τελευταια ο υπολογιστης μου κολαει και βγαζει μπλε οθονη. katebasa to whocrashed και μου εβγαλε τα παρακατω αποτελεσματα. δε μπορω να βρω λυση και τι πρεπει να κανω, καθως και ουτε στο windows update καμια ενημερωση για να διορθώσω τα λάθη. γνωριζει κανεις τι πρεπει να κανω? ευχαριστω εκ των προταιρων. 

Τα αποτελεσματα παρακατω: 

 

 

 

System Information (local)

computer name: GIORGOS-PC
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
Hardware: P5Q-PRO, , ASUSTeK Computer INC.
CPU: GenuineIntel Intel® Core2 Quad CPU Q9550 @ 2.83GHz Intel586, level: 6
4 logical processors, active mask: 15
RAM: 4293976064 total
VM: 2147352576, free: 1931448320


 

Crash Dump Analysis

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Sun 2/2/2014 2:16:19 μμ GMT your computer crashed
crash dump file: C:\Windows\Minidump\020214-9562-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80002CD4E9A, 0xFFFFF88009A70960, 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 Sun 2/2/2014 2:16:19 μμ GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: fltmgr.sys (fltmgr+0x4AAE)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80002CD4E9A, 0xFFFFF88009A70960, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\drivers\fltmgr.sys
product: Λειτουργικό σύστημα Microsoft® Windows®
company: Microsoft Corporation
description: Διαχείριση φίλτρων συστήματος αρχείων της Microsoft
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 Sat 1/2/2014 7:24:08 μμ GMT your computer crashed
crash dump file: C:\Windows\Minidump\020114-9531-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80002C9DB46, 0xFFFFF88002F48FC0, 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 Sat 1/2/2014 3:30:10 μμ GMT your computer crashed
crash dump file: C:\Windows\Minidump\020114-15210-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75B90)
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
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 Fri 31/1/2014 10:54:14 μμ GMT your computer crashed
crash dump file: C:\Windows\Minidump\020114-8158-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75B90)
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
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 Wed 29/1/2014 3:56:11 μμ GMT your computer crashed
crash dump file: C:\Windows\Minidump\012914-12916-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75B90)
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
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 Wed 29/1/2014 3:34:58 μμ GMT your computer crashed
crash dump file: C:\Windows\Minidump\012914-8236-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x78A8A)
Bugcheck code: 0x1000009F (0x4, 0x258, 0xFFFFFA80039E3B50, 0xFFFFF80000B9C4D0)
Error: CUSTOM_ERROR
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
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 27/1/2014 4:14:38 μμ GMT your computer crashed
crash dump file: C:\Windows\Minidump\012714-11372-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75B90)
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
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 Sun 26/1/2014 4:38:29 μμ GMT your computer crashed
crash dump file: C:\Windows\Minidump\012614-9625-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75B90)
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
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. 

 

 

Επεξ/σία 2 Φεβρουαρίου 2014 από Gi0
spoiler tag

[Grey Warden]

Με μια πρόχειρη αναζήτηση βρήκα 2 περιπτώσεις με το ίδιο πρόβλημα που η μία λύθηκε με format και η άλλη με χρησιμοποίηση άλλου σκληρού δίσκου (που σημαίνει νέα windows και πάλι) οπότε μάλλον κάτι τέτοιο παίζει. Ας γράψουν κι άλλοι πιο σχετικοί.

[Gi0]

BSOD:..και μετά τι;

Δωσε περισσοτερες πληροφοριες για το προβλημα. Τι software τρεχεις, εαν εχεις αλλαξει κατι προσφατα σε software (updates, drivers, οτιδηποτε), τι hardware εχεις, εαν εχεις κανει προσφατα αλλαγες στο hardware, εαν εχεις ελεγξει τη σταθεροτητα του hardware και με ποιους τροπους, overclocking, κατι κοινο στις μπλε οθονες (πχ ειναι παντα idle ο υπολογιστης οταν συμβαινει), κλπ, κλπ, κλπ.