Ioannis Atsamis ρώτησε πριν 5 έτη

καλησπερα σας, πριν λιγες μερες μου χαρισαν ενα σταθερο pc, (πριν ειχα λαπτοπ). 3 μερες τωρα οποτε ανοιγω τον υπολογιστη μου βγαζη μπλε οθονη και κανει επανεκινηση με το μηνυμα critical structure corruption, βεβαια εβαλα καποια προγραμματα καθως μου παραδοθηκε με τα widoons 10 μονο, επειτα διεγραψα μερικα και κρατησα τα πιο κυρια, αλλα το προβλημα παραμενει κανοντας επανεκινησης και κατα την διαρκεια της ημερας 1-2, διαβασα προσεκτικα ολα τα αρθρα για την μπλε οθονη κατεβασα και το whocrashed αλλα δεν μπορεσα να βγαλω ακρη, σας παραθετω τι μου εβγαλε το whocrashed μηπως με βοηθησετε καθως δεν ειμαι καθολου γνωστης περα των βασικων, σας ευχαριστω!                                                                                                                                                                                                  Computer name: DESKTOP-FCGB4J3
Windows version: Windows 10 , 10.0, build: 17763
Windows dir: C:\Windows
Hardware: ESPRIMO P5635 , FUJITSU , D2901-A1
CPU: AuthenticAMD AMD Phenom(tm) II X2 545 Processor AMD586, level: 16
2 logical processors, active mask: 3
RAM: 4025335808 bytes (3,7GB)

Crash Dump Analysis

Crash dumps are enabled on your computer.

Crash dump directories:
C:\Windows
C:\Windows\Minidump

On Tue 22/1/2019 11:56:16 μμ your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\012219-27906-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1B1B40)
Bugcheck code: 0x109 (0xA39FF8DA85E0B609, 0x0, 0xD3E1387ECFC3E53, 0x101)
Error: CRITICAL_STRUCTURE_CORRUPTION
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 the kernel has detected critical kernel code or data corruption.
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. This may be because of a hardware issue such as faulty RAM, overheating (thermal issue) or because of a buggy driver. 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 Tue 22/1/2019 11:56:16 μμ your computer crashed or a problem was reported
crash dump file: C:\Windows\MEMORY.DMP
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x109 (0xA39FF8DA85E0B609, 0x0, 0xD3E1387ECFC3E53, 0x101)
Error: CRITICAL_STRUCTURE_CORRUPTION
Bug check description: This indicates that the kernel has detected critical kernel code or data corruption.
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. This may be because of a hardware issue such as faulty RAM, overheating (thermal issue) or because of a buggy driver. 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 Tue 22/1/2019 12:06:59 μμ your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\012219-29484-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1B1B40)
Bugcheck code: 0xA (0x32411, 0x2, 0x0, 0xFFFFF80459A3BA54)
Error: IRQL_NOT_LESS_OR_EQUAL
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 Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above. This is a software bug.
This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.


On Tue 22/1/2019 4:41:23 πμ your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\012219-28250-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1B1B40)
Bugcheck code: 0x12B (0xFFFFFFFFC00002C4, 0x55F, 0x2A5DA975B60, 0xFFFFB880FA6CA000)
Error: FAULTY_HARDWARE_CORRUPTED_PAGE
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 single-bit error was found in this page. This is a hardware memory error.
This is likely to be caused by a hardware problem. This error suggests a case of memory corruption because of a hardware problem. It is suggested you do a test on your RAM modules (memory test) and make sure your system is not getting overheated. 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 Tue 22/1/2019 3:44:31 πμ your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\012219-37796-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1B1B40)
Bugcheck code: 0x1A (0x411, 0xFFFFF97C9F7D60A0, 0xC001FAD2, 0xFFFFD9009D643260)
Error: MEMORY_MANAGEMENT
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 severe memory management error occurred. A page table entry (PTE) has been corrupted. Parameter 2 is the address of the PTE.
This might be a case of memory corruption. This may be because of a hardware issue such as faulty RAM, overheating (thermal issue) or because of a buggy driver. 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 Tue 22/1/2019 2:56:08 πμ your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\012219-30468-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1B1B40)
Bugcheck code: 0x12B (0xFFFFFFFFC00002C4, 0x7BC, 0x1E507AF8FE0, 0xFFFFDD0108DF2000)
Error: FAULTY_HARDWARE_CORRUPTED_PAGE
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 single-bit error was found in this page. This is a hardware memory error.
This is likely to be caused by a hardware problem. This error suggests a case of memory corruption because of a hardware problem. It is suggested you do a test on your RAM modules (memory test) and make sure your system is not getting overheated. 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.
       

5 Απαντήσεις

orestisfraSPDR . απάντησε πριν 5 έτη

εγώ θα έκανα format. άμα δεν θες να κάνεις format θα πρότεινα εανεγκατάσταστη όλων των drivers που εγκαταστάθηκαν χειροκίνητα.

Γιώργος Τράντζας Staff απάντησε πριν 5 έτη

Καλησπέρα Γιάννη
Όπως είπε και ο Ορέστης, η καλύτερη λύση είναι το format ή τουλάχιστον μία επιδιόρθωση των Windows
Μπορείς επίσης να δοκιμάσεις την απεγκατάσταση και την εγκατάσταση από την αρχή των drivers γραφικών και ήχου. 

Ioannis Atsamis απάντησε πριν 5 έτη

καλησπερα ορεστη και γιωργο, μαλλον εφταιγε ενα προσθετο του croome, αν το λεω σωστα croomino νομιζω λεγετε, το απεγκατεστησα και 2 μερες ολα καλα, αν ξαναεμφανιστη θα ακολουθησω της συμβουλες σας, σας ευχαριστω πολυ για τον χρονο σας!

Γιώργος Τράντζας Staff απάντησε πριν 5 έτη

Ευχαριστούμε για την ενημέρωση Γιάννη. Καλή συνέχεια! 

orestisfraSPDR . απάντησε πριν 5 έτη

ένα πρόσθετο στο chrome προκαλούσε το ntoskrnl.exe να κρασάρει;
τι έκανε αυτό το πρόσθετο; γιατί δεν το βρίσκω