Όλες οι Ερωτήσεις στο PCstepsΚαλησπέρα αντιμετωπίζω ένα πρόβλημα με εμφάνιση μπλε οθόνης και επανεκκίνησης του λαπτοπ όταν είμαι στο google chhrome
George Skevas ρώτησε πριν 6 έτη
ακολούθησα μια διαδικασία που είδα σε ένα θέμα εδώ, αλλά δεν ξέρω τι πρέπει να κάνω για την επίλυση του προβλήματος : Παραθέτω τα αποτελέσματα από την ανάλυση του WhoCrashed όποιος μπορεί ας μου πει τι πρέπει να κάνω για να σταματήσει να συμβαίνει αυτό το γεγονός, ευχαριστώ                                                                                                                                                                                                                                                                         Crash Dump Analysis

Crash dump directory: C:\WINDOWS\Minidump

Crash dumps are enabled on your computer.

On Sun 28/2/2016 2:28:25 μμ GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\022816-25187-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14F4D0)
Bugcheck code: 0x1A (0x5200, 0xFFFFE00072252000, 0x2000200020002000, 0xD0ED88F690AA7887)
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.
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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.


On Sun 28/2/2016 2:28:25 μμ GMT your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: ntfs.sys (NTFS+0x1002C)
Bugcheck code: 0x1A (0x5200, 0xFFFFE00072252000, 0x2000200020002000, 0xD0ED88F690AA7887)
Error: MEMORY_MANAGEMENT
file path: C:\WINDOWS\system32\drivers\ntfs.sys
product: Λειτουργικό σύστημα Microsoft® Windows®
company: Microsoft Corporation
description: Πρόγραμμα οδήγησης συστήματος αρχείων NT
Bug check description: This indicates that a severe memory management error occurred.
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 Sun 28/2/2016 11:24:18 πμ GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\022816-24187-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14F4D0)
Bugcheck code: 0x7A (0x4, 0x0, 0xFFFFE00046452010, 0xF9E5EF0000)
Error: KERNEL_DATA_INPAGE_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 the requested page of kernel data from the paging file could not be read into memory.
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 27/2/2016 6:33:20 μμ GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\022716-25531-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14F4D0)
Bugcheck code: 0x7A (0x4, 0x0, 0xFFFFE001F9274860, 0x212D9FEBD0)
Error: KERNEL_DATA_INPAGE_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 the requested page of kernel data from the paging file could not be read into memory.
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 26/2/2016 9:57:16 μμ GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\022616-25015-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14F4D0)
Bugcheck code: 0xEF (0xFFFFE0018E39B080, 0x0, 0x0, 0x0)
Error: CRITICAL_PROCESS_DIED
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 critical system process died.
There is a possibility this problem was caused by a virus or other malware.
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 26/2/2016 4:47:16 μμ GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\022616-49953-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14F4D0)
Bugcheck code: 0x7A (0x4, 0x0, 0xFFFFE001FADB2010, 0xEE3B3344D0)
Error: KERNEL_DATA_INPAGE_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 the requested page of kernel data from the paging file could not be read into memory.
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 26/2/2016 8:45:04 πμ GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\022616-24921-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14F4D0)
Bugcheck code: 0x7A (0x4, 0x0, 0xFFFFE00092FB5E50, 0xD7379E0000)
Error: KERNEL_DATA_INPAGE_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 the requested page of kernel data from the paging file could not be read into memory.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.


On Thu 25/2/2016 11:34:08 πμ GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\022516-21781-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14F4D0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF800D90FE096, 0xFFFFD0010DF10E80, 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 Tue 23/2/2016 12:32:13 μμ GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\022316-39531-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14F4D0)
Bugcheck code: 0x1A (0x41201, 0xFFFFF6BFFD7EA000, 0x6BB06BB12F746C3, 0xFFFFE00142772B50)
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.
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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.


On Mon 22/2/2016 6:45:20 μμ GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\022216-27343-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14F4D0)
Bugcheck code: 0x7A (0x4, 0x0, 0xFFFFE001A5D3E3F0, 0x7057EC1E40)
Error: KERNEL_DATA_INPAGE_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 the requested page of kernel data from the paging file could not be read into memory.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

Conclusion

24 crash dumps have been found and analyzed. Only 10 are included in this report. 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.

7 Απαντήσεις

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

Αν το πρόβλημα εμφανίζεται μόνο όταν έχεις ανοιχτό τον chrome, δοκίμασε από τις ρυθμίσεις -> Σύνθετες ρυθμίσεις, να απενεργοποιήσεις την επιτάχυνση υλικού.

George Skevas απάντησε πριν 6 έτη

Το δοκίμασα αλλά και πάλι κόλλησε και έβγαλε μπλε οθόνη με το μήνυμα Error: ΚΕRΝΕL DATA INPAGE ERROR.., γιατι ειμαι ασχετος έχω την εντύπωση πως κολλαει οταν ανοιγω 4-5 παραθυρα στο chrome. Οσες φορες εχει βγαλει μπλε οθονη ειναι σε αυτα τα αποτελεσματα που εβαλα από WhoCrashed με κυρια αιτία απο οτι καταλαβα το kernel data inpage error τι ειναι αυτο και πως μπορω να το αντιμετωπισω

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

Γράψε μας τα στοιχεία του υπολογιστή και το λειτουργικό. Δοκίμασε άλλον browser να δεις αν κάνει το ίδιο πρόβλημα
Τρέξε από την γραμμή εντολών το chkdsk /f και μετά sfc /scannow

George Skevas απάντησε πριν 6 έτη

o υπολογιστής είναι sony vaio SVF1521A6EW και το καλοκαίρι όταν μου εμφανίστηκε το εικονίδιο έκανα την λήψη από windows 8.1 σε windows 10 home. Tο πρόβλημα αυτό με την μπλε οθόνη εμφανίστηκε πριν λίγες μέρες, και προέκυψε ξαφνικά χωρίς να παρουσιάσει πότε ξανά πρόβλημα, από τότε που εμφανίστηκε το κάνει συχνά.               Δεν ξέρω αν παίζει ρόλο αλλα την μερα πριν εμφανιστεί πρωτη φορα το συστημα δεν αναγνώριζε το antivairus nod32 eset 8, Και πηγα στο vaio care για να κανω ελεγχο και ειχε καποια updates εκει και τα εκανε Μπορεί να επειρεαστηκε και απο εκεί δεν ξερω…,

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

Σε ευχαριστώ για τις πληροφορίες, ποιο antivirus έχεις τώρα επάνω; Έχεις αλλά αντίστοιχα ή παρόμοια προγράμματα για έλεγχο της σύνδεσης, για ιούς κλπ;

George Skevas απάντησε πριν 6 έτη

τωρα λειτουργει κανονικα το eset nod32 και δειχνει ενημερωμενο οχι δεν εχω αλλα προγραμματα

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

Δοκίμασες τις εντολές; Σου έβγαλαν σφάλματα;