Thomas Athanasiou ρώτησε πριν 7 έτη
ΚΑΛΗΣΠΕΡΑ. ΑΝΤΙΜΕΤΩΠΙΖΩ ΠΡΟΒΛΗΜΑ ΜΕ BLUE SCREEN. ΣΥΝΗΘΩΣ ΑΝΟΙΓΩ ΤΟΝ ΥΠΟΛΟΓΙΣΤΗ ΚΑΙ ΜΠΑΙΝΩ ΣΤΗΝ ΕΠΙΦΑΝΕΙΑ ΕΡΓΑΣΙΑΣ. ΚΑΙ ΜΕΤΑ ΑΠΟ ΛΙΓΟ ΒΓΑΖΕΙ BLUE SCREEN ΜΕ ΜΗΝΥΜΑ “IRQ_NOT_LESS_OR_EQUAL” Ή ΚΑΤΙ ΠΟΥ ΕΧΕΙ ΝΑ ΚΑΝΕΙ ΜΕ “win32k.sys”. ΣΤΗ ΣΥΝΕΧΕΙΑ Ο ΥΠΟΛΟΓΙΣΤΗΣ ΚΑΝΕΙ ΕΠΑΝΕΚΚΙΝΗΣΕΙΣ ΕΜΦΑΝΙΖΟΝΤΑΣ Κ ΠΑΛΙ ΤΗΝ ΜΠΛΕ ΟΘΟΝΗ. ΕΧΩ ΚΑΝΕΙ ΦΟΡΜΑΤ. ΤΟ ΠΡΟΒΛΗΜΑ ΟΜΩΣ ΣΥΝΕΧΙΖΕΙ ΝΑ ΥΠΑΡΧΕΙ.

10 Απαντήσεις

Υποστήριξη PCsteps (Νίκος) απάντησε πριν 7 έτη

Ο πιο πιθανός ύποπτος είναι η κάρτα γραφικών. Αν έχεις onboard σύνδεσε την οθόνη σου εκεί και κάνε απεγκατάσταση των drivers της gpu. Ζόρισε τον έτσι όσο μπορείς. Αν ξαναπετάξει κάνεις ένα check την μνήμη με το memtest

Αλέξανδρος Ρούσσης απάντησε πριν 7 έτη

Γειά σας.Κάλο είναι να κάνετε πρώτα έναν έλεγχο με την γραμμή εντολών(cmd)  πληκτρολογώντας την εντολή sfc/scannow.Πιθανός το πρόβλημα να οφείλετε και στους drivers μπορείς να δεις αυτόν τον οδηγό για να κάνεις αναλυτικό έλεγχο για σφάλματα με το πρόγραμμα WhoCrashed.
https://www.pcsteps.gr/450-analiste-ta-sfalmata-tis-mple-othonis-me-to-whocrashed/
Είχα και εγώ πρόβλημα με μπλε οθόνη και είχα κάνει έλεγχο με το WhoCrashed και από’τι θυμάμαι μου είχε εμφανίσει παρόμοιο πρόβλημα με win32k.sys.Έπειτα το δεύτερο βήμα που έκανα ήταν ο έλεγχος με την εντολή sfc/scannow και μετά από αυτόν τον έλεγχο δεν ξαναεμφανίστηκε μπλε οθόνη.Πάντως το πρόβλημα δεν ξέρω πως εξαφανίστηκε πιθανός με τoν έλεγχο της εντολής sfc/scannow.Αν το πρόβλημα δεν λυθεί γράψε απάντηση μήπως βρεθεί και άλλη λύση.

 

Thomas Athanasiou απάντησε πριν 7 έτη

ΕΚΑΝΑ ΤΟΝ ΕΛΕΓΧΟ ΜΕ ΤΗΝ ΕΝΤΟΛΗ sfc/scannow ΑΛΛΑ ΤΟ ΠΡΟΒΛΗΜΑ ΣΥΝΕΧΙΖΕΙ ΝΑ ΥΠΑΡΧΕΙ. ΚΥΡΙΩΣ ΕΜΦΑΝΙΖΕΤΑΙ BLUE SCREEN ΜΕ ΜΗΝΥΜΑ “IRQ_NOT_LESS_OR_EQUAL”

Υποστήριξη PCsteps (Νίκος) απάντησε πριν 7 έτη

Έκανες update λειτουργικού πριν εμφανίσει το πρόβλημα; Γράψε μας τι υπολογιστή έχεις και το λειτουργικό.
Στα αποτελέσματα του sfc /scannow βρήκε σφάλματα;

Thomas Athanasiou απάντησε πριν 7 έτη

ΠΡΙΝ ΚΑΝΩ ΤΟ ΦΟΡΜΑΤ ΤΟ ΛΕΙΤΟΥΡΓΙΚΟ ΗΤΑΝ ΕΝΗΜΕΡΩΜΕΝΟ ΟΤΑΝ ΞΕΚΙΝΗΣΕ ΤΟ ΠΡΟΒΛΗΜΑ.ΜΕΤΑ ΤΟ ΦΟΡΜΑΤ ΜΕΤΑ ΑΠΟ ΟΛΕΣ ΤΙΣ ΕΝΗΜΕΡΩΣΕΙΣ ΕΜΦΑΝΙΣΤΗΚΕ ΠΑΛΙ. Ο ΕΛΕΓΧΟΣ sfc /scannow ΔΕΝ ΕΜΦΑΝΙΣΕ ΣΦΑΛΜΑΤΑ.
DESKTOP
CPU: INTEL CORE2 DUO E8400 @3 GHZ
WINDOWS 7 PROFFESIONAL 32-BIT OPERATING SYSTEM
RAM: 4GB
GPU: NVIDIA GEFORCE GTX 460

Αλέξανδρος Ρούσσης απάντησε πριν 7 έτη

Δοκίμασες το WhoCrashed αν ναι καλύτερα στείλε και μία φωτογραφία με τα αποτελέσματα που σου εμφάνισε μήπως μπορέσει να σε βοηθήσει η υποστήριξη PCsteps.

Thomas Athanasiou απάντησε πριν 7 έτη

Crash Dump Analysis
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.

On Wed 9/30/2015 9:02:51 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\093015-16317-01.dmp
uptime: 00:00:37
This was probably caused by the following module: win32k.sys (win32k!PALLOCMEM+0x29)
Bugcheck code: 0xA (0xFFFFFFFFE411DA28, 0x2, 0x1, 0xFFFFFFFF82AE4B44)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\win32k.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Multi-User Win32 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 9/30/2015 9:02:51 AM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
uptime: 00:00:37
This was probably caused by the following module: win32k.sys (win32k!PALLOCMEM+0x29)
Bugcheck code: 0xA (0xFFFFFFFFE411DA28, 0x2, 0x1, 0xFFFFFFFF82AE4B44)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\win32k.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Multi-User Win32 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 9/30/2015 9:00:54 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\093015-17362-01.dmp
uptime: 00:00:17
This was probably caused by the following module: rdyboost.sys (rdyboost!SMKM_STORESMD_TRAITS::SmStMapRegion+0x3F)
Bugcheck code: 0xA (0xFFFFFFFFBC4026B0, 0x2, 0x1, 0xFFFFFFFF82A99F56)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\rdyboost.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: ReadyBoost 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 Sun 9/27/2015 10:28:45 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\092715-18657-01.dmp
uptime: 01:56:17
This was probably caused by the following module: hal.sys (hal!HaliAcpiSleep+0xBB)
Bugcheck code: 0xA (0xDC8AD8, 0xFF, 0x1, 0xFFFFFFFF82E3B4AB)
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 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: hal.sys .
Google query: hal.sys IRQL_NOT_LESS_OR_EQUAL

On Fri 9/25/2015 10:04:56 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\092515-21637-01.dmp
uptime: 00:00:10
This was probably caused by the following module: ntkrpamp.exe (nt!KeBugCheck+0x14)
Bugcheck code: 0x6B (0x0, 0x0, 0x0, 0x0)
Error: PROCESS1_INITIALIZATION_FAILED
Bug check description: This bug check indicates that the initialization of the Microsoft Windows operating system failed.
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 PROCESS1_INITIALIZATION_FAILED

On Fri 9/25/2015 7:30:11 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\092515-19094-01.dmp
uptime: 00:00:15
This was probably caused by the following module: rdyboost.sys (rdyboost!SMKM_STORESMD_TRAITS::SmStMapRegion+0x3F)
Bugcheck code: 0xA (0xFFFFFFFFA011C288, 0x2, 0x1, 0xFFFFFFFF82AD4B44)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\rdyboost.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: ReadyBoost 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 Thu 9/24/2015 2:31:51 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\092415-19344-01.dmp
uptime: 00:01:53
This was probably caused by the following module: ntkrpamp.exe (nt!KiTrap0E+0x1B3)
Bugcheck code: 0xA (0xFFFFFFFFFFFFFFFF, 0x2, 0x1, 0xFFFFFFFF82AC6260)
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 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 IRQL_NOT_LESS_OR_EQUAL

On Thu 9/24/2015 2:11:15 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\092415-19453-01.dmp
uptime: 00:00:16
This was probably caused by the following module: ntkrpamp.exe (nt!KiTrap0E+0x1B3)
Bugcheck code: 0xA (0x5041F9DF, 0x2, 0x0, 0xFFFFFFFF82ADBD0E)
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 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 IRQL_NOT_LESS_OR_EQUAL

On Thu 9/24/2015 9:10:56 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\092415-15880-01.dmp
uptime: 00:00:18
This was probably caused by the following module: rdyboost.sys (rdyboost!SMKM_STORESMD_TRAITS::SmStMapRegion+0x3F)
Bugcheck code: 0xA (0x4411C090, 0x2, 0x1, 0xFFFFFFFF82AEAB44)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\rdyboost.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: ReadyBoost 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 Thu 9/24/2015 5:37:56 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\092415-19016-01.dmp
uptime: 00:01:09
This was probably caused by the following module: ntkrpamp.exe (nt!KiTrap0E+0x1B3)
Bugcheck code: 0xA (0x28903090, 0x2, 0x1, 0xFFFFFFFF82AA5B44)
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 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 IRQL_NOT_LESS_OR_EQUAL

On Thu 9/24/2015 5:33:39 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\092415-17534-01.dmp
uptime: 00:02:22
This was probably caused by the following module: ntfs.sys (Ntfs!NtfsExceptionFilter+0xAD)
Bugcheck code: 0x24 (0x1904FB, 0xFFFFFFFF9C17B85C, 0xFFFFFFFF9C17B440, 0xFFFFFFFF8AEB7A9F)
Error: NTFS_FILE_SYSTEM
file path: C:\Windows\system32\drivers\ntfs.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT File System Driver
Bug check description: This indicates a problem occurred in the NTFS file system.
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 Tue 9/22/2015 5:54:06 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\092215-16208-01.dmp
uptime: 00:05:18
This was probably caused by the following module: win32k.sys (win32k!TimersProc+0x75)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF97D3444E, 0xFFFFFFFF8CEFDC38, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\win32k.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Multi-User Win32 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.
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
12 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:
ntkrpamp.exe
hal.sys
If no updates for these drivers are available, try searching with Google on the names of these drivers in combination the errors that have been reported for these drivers and include the brand and model name of your computer as well in the query. This often yields interesting results from discussions from 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 actually 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.

Υποστήριξη PCsteps (Νίκος) απάντησε πριν 7 έτη

Δοκίμασε να μπεις σε safe mode, και παίξε μαζί του λίγο, σου βγάζει πάλι blue screen;

Thomas Athanasiou απάντησε πριν 7 έτη

ΔΕΝ ΒΓΑΖΕΙ ΠΑΝΤΑ BLUE. ΜΠΟΡΕΙ ΝΑ ΜΗΝ ΒΓΑΛΕΙ ΓΙΑ 2 ΜΕΡΕΣ ΚΑΙ ΜΠΟΡΕΙ ΝΑ ΒΓΑΛΕΙ 3 ΦΟΡΕΣ ΣΕ ΜΙΑ ΜΕΡΑ. ΜΠΗΚΑ 2 ΦΟΡΕΣ ΣΕ SAFE ΚΑΙ ΔΕΝ ΕΒΓΑΛΕ..

Thomas Athanasiou απάντησε πριν 7 έτη

Για κάποιον περίεργο λόγο εδώ και αρκετές ημέρες δεν έχει εμφαανίσει κανένα πρόβλημα ( blue ). Γραφικά ακόμα στην gpu. Αν κάνει πάλι κάτι θα δοκιμάσω τις τελευταίες οδηγίες. Ευχαριστώ πολύ.