Précédente Accueil Remonter Suivante

Ecran bleu - BSOD

Windows 10

 

Analyse avec WhoCrashed 

 

 

17 01 2019

Vérifier avec le Vérificateur de pilotes

 

15 01 2019 MAJ INTEL

Les tests Windows approfondis se sont terminés par un blocage...

Avec MemTest86, au test 10, de nombreuses erreurs sur la RAM Crucial isolée

Enlevée & contact vendeur

BlueScreenView

 

 

9 -01 - 2019 maj Asmedia usb 3.1

 

2-12-2018 nouveaux drivers INTEL avec maj normes windows

31 10 2018

MAJ pilote HD Graphics 530 Intel

 

03-10-2018 maj windows 1809

 

21 09 2018

tests poussés de mémoire avec option F1

windows ne trouve plus rien...

isoler les barrettes puis les deux...

20 09 2018

les tests mémoire approfondis de Windows m'indique qu'il y a un problème

15-09

j'ai récupéré une barrette mémoire sur l'ordi de mon fils (il a une carte presque semblable à la mienne Asus H170 pro gaming)

Une G.SKILL F4-2133C15D-16GNT

Dans les docs associées aux mémoires, pour ma carte mère il y a ambigüité entre le 16FA11 et le C16FA

RAM DDR4 - 16 Go - Crucial technology - CT8G4DFD8213.C16FA - A62148DC

8 Go et 32 Go

 

14-09-2018

je me questionne sur une barrette mémoire...

j'avais réduis mon système au minimum pour les tests

donc une seul barrette de 8 Go

que j'avais changé de place (pour tester les emplacements)

bien sûr avec tests mémoires poussés

 

le système avec cette configuration mémoire semblait plus stable

j'ai remis les deux barrettes

06-09-2018

 

 

Avec la mise à jour du MEUUpdatetool et l'Intel Chipset SATA

Cela semble s'améliorer...

 

  

Ordi presque entièrement démonté pour vérifier, une nouvelle fois, si ce n'est pas un problème matériel...

2 disques durs & 1 SSD dans le deuxième ordi : aucun problème

volonté de changer le matériel tout en scrutant les maj...

le 2° ordi est quand même moins réactif

test

9 -08 -2018 maj...

Instabilité chronique

Surtout des problèmes lors des recopies des disques dur ou de mon site entier

13-07-2017

MAJ bios 3805 - Nvidia - Intel gestion & réseau - carte son

12-06-2018

11-06-2018

mai 2018

MAJ BIOS 3610 ASUS

maj intel ethernet connection I219-V 12.17.8.9

maj nvidia geforce gtx 24.21.13.9755

maj asmedia usb 3.1  1.16.51.1

__________________________

18 03 2018

 

15/02/2018

Mode sans échec...

 

15/02/2018

pour solliciter au maximum le système

 

 

 

9-2-2018

Après les instructions envoyées, l'outil ME update tool a fonctionné

J'ai pu également mettre à jour le Chipset Intel 11.7.0.1040

outil intel SA-00086 a bien noté que mon système n'est plus vulnérable.

En attente de l'arrêt des écrans bleus...

 

 

 

Windows 10 - 1709 - build: 16299.192
 

BIOS 3016

 

Carte mère : ASUSTeK COMPUTER INC., H170-PRO/USB 3.1

intel H170 Socket 1151
 

CPU: Intel(R) Core(TM) i5-6500 CPU @ 3.20GHz Intel586, level: 6
 

RAM DDR4 - 16 Go - Crucial technology - CT8G4DFD8213.C16FA - A62148DC

 

4 Disques durs
KINGSTON SUV400S37240G SSD

SAMSUNG SSD 840 series

ST1000DM003-9YN162

WDC WD20EZRX-00D8PB0

 

CARTE GRAPHIQUE : NVIDIA GeForce GTX 1060 6GB

 

31/01/2018

Changement BIOS 3016

tentative MAJ driver Intel

 

dans le DOS sfc /scannow m'informait La protection des ressources Windows a trouvé des fichiers endommagés

 

janvier 2018 - réinstallation complète

18-10-2017 MAJ Windows 10  1709

28-10-2017 un plantage (cause : avast)

 

23 07 2017

installé BIOS 3013 au lieu de 3016 (ambigüité sur le site ASUS au niveau des versions : la 3013 apparait après)

le mode XMP apparait dans le BIOS (partie simple) mais il est désactivé et non activable (du aux modules de ram installés)

CPU-Z : DDR4 2132 (1066 Mhz) Crucial technology - CT8G4DFD8213.C16FA

 

dans le DOS sfc /scannow m'informait La protection des ressources Windows a trouvé des fichiers endommagés

10 07 2017 réinstallation complète

formatage disque dur et installation windows 10 1703

plantages à répétion

01 06 2017 enlever second écran

23 05 2017 MAJ driver nvidia écran bleu carte 1060

plantage à répétition

26 04 2017 MAJ driver nvidia 381.89

dans la doc : écran bleu avec carte gtx 1060

7 04 2017 MAJ Windows 10 Creators Update

MAJ et 3 plantages

19-03 2017

Toujours des écrans bleus...

MAJ BIOS 3016

Les plantages ne remettent plus en cause le système

En attendant la MAJ Windows 10 avril...

 

13 02 2017 écran bleu...

10 02 2017

MAJ BIOS ASUS 3013 (ancien 2002)

h270-PRO/USB 3.1 BIOS 3013
Improve system stability

MAJ driver carte graphique Nvidia

MAJ Realtek

08 02 2017

Intervention à nouveau de Microsoft

le code erreur 0xC004F012 leur pose problème

1 heure d'intervention avec multiple manipulations sans succès - le code erreur n'est pas résolu

Le spécialiste veut faire un sfc /scannow du système

je lui réponds que cette commande ne va jamais jusqu'au bout...

il me répond qu'il va falloir tout réinstaller Windows en formatant le disque dur

Fin de l'intervention.

 

j'essaye quand même le sfc /scannow pour voir...

 

C:\Windows\system32>sfc /scannow

Démarrage de la phase de vérification de l’analyse du système.
La vérification 100% est terminée.

La protection des ressources Windows a trouvé des fichiers endommagés et a pu les réparer. Des détails sont fournis dans le journal CBS.Log
windir\Logs\CBS\CBS.log. Par exemple C:\Windows\Logs\CBS\CBS.log.

Notez que la journalisation n’est pas actuellement prise en charge dans les scénarios de service hors connexion.

Donc Windows s'est réparé !

Redémarrage et activation possible !

 

windows script host
etat de la licence : avec licence
nombre de réinitialisation de windows restant : 1001
nombre de réinitialisation de la référence (SKU) restant : 1001

 


6 02 2017

Activation

windows script host
etat de la licence : avec licence
nombre de réinitialisation de windows restant : -1
nombre de réinitialisation de la référence (SKU) restant : -1

slmgr.vbs /dli
slmgr.vbs /dlv
slmgr.vbs /xpr

activation demandée : impossible de personnaliser windows (début d'un limitation progressive ?)

dans paramètres
code d'erreur : 0xC004F012

dans changement clé produit
code d'erreur : 0x80004001

2 02 2017

Toujours un peu la même chose : des bugs à répétition puis un problème plus important qui oblige à tout réinstaller...

intervention de Microsoft pour résoudre le problème

dans propriétés système il y avait bien réactivation mais dans paramètres non...

 3 02 2017 j'ai fait une récupération du système à une date antérieur : non résolu

non résolu...   16 01 2017

Erreurs système jamais les mêmes...

Au niveau du SSD samsung de démarrage, il y avait parfois un problème. je pense qu'il est dû au plantage du système.

plusieurs fois, le plantage m'a obligé à éteindre volontairement.

j'ai revu les partitions avec le système win10 car il y en avait trop du au fait des réinstallations successives de Windows.

Un autre logiciel m'indiquait des erreurs au moment du répartionnement

 

j'ai donc changé de SSD pour le démarrage et réinstaller à nouveau totalement Windows 10

j'ai reformaté en bas niveau le SSD samsung que j'ai mis en disque auxiliaire

mise à jour tous les drivers

BIOS à jour (2002)

21 12 2016 : plantage à nouveau... 2 fois...

ce matin, j'ai ôté la clé Wifi et j'ai mis en Ethernet...

pilote asmédia usb 3.1   1.16.26 - assistance Asus

 

24 12 2016

plantage -

J'ai tendance à éteindre l'ordi dès que je ne l'utilise pas

 

27 12 2016

Chez mon fils Clément il y a également ce problème

Je l'ai vu en analysant son journal d'évènements

il ne s'était aperçu de rien.

Les erreurs étaient à zéro

 

25 11 2016

j'ai installé à nouveau le bios

chkdisk pour vérifier les disques

dans le bios : voir l'état des disques

test RAM

Clear RTC RAM (clear le CMOS de la carte mère + enlever la pile)

wocrashed :  ntoskrnl.exe   ntfs.sys    noyau système

msinfo32 : informations système

prévention :  création de point de restauration plus fréquents

maj de tous les composants logiciels

plantage le 24/11

le hard enlevé n'est pas en cause...

remonter le pc complètement

23/11/2016

j'ai remis mon ancienne alimentation

20/11/2016

J'ai éliminé presque tout le matériel : deuxième écran - carte graphique - ports USB supplémentaires

blocage système : ne peut plus accéder au compte utilisateur au démarrage  : message windows avertissant du pb

Reformater disque dur SSD et installation à nouveau d'un système Windows 10

plantages à nouveau

30/10/2016 : nombreux plantages (plusieurs fois par jour)

EventData

BugcheckCode 313 BugcheckParameter1 0x3 BugcheckParameter2 0xffffb3816e6d7130 BugcheckParameter3 0xffffb3816e6d7088 BugcheckParameter4 0x0 SleepInProgress 0 PowerButtonTimestamp 0 BootAppStatus 0 Checkpoint 0 ConnectedStandbyInProgress false SystemSleepTransitionsToOn 11 CsEntryScenarioInstanceId 0

 

 

27/10/2016 : Pilote geforce 375.63 n'a pas résolu ces plantages répétitifs ?

-> Matériel + écran Asus ProArt 1920x1200


System Information (local)



Windows version: Windows 10 , 10.0 build: 17763



Computer name: PC-DANIEL
Windows version: Windows 10 , 10.0, build: 17763
Windows dir: C:\WINDOWS
Hardware: ASUSTeK COMPUTER INC., H170-PRO/USB 3.1
CPU: GenuineIntel Intel(R) Core(TM) i5-6500 CPU @ 3.20GHz Intel586, level: 6
4 logical processors, active mask: 15
RAM: 17025146880 bytes total
 


CPU-Z : DDR4 2132 (1066 Mhz) Crucial technology - CT8G4DFD8213.C16FA - A62148DC

 

On constate que les erreurs ne sont jamais les mêmes...


On Mon 14/01/2019 14:05:41 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\011419-14703-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0xC4F35)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF8046E76EF35, 0xFFFFC70CDFEEEFE8, 0xFFFFC70CDFEEE830)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
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 system thread generated an exception which the error handler did not catch.
 
On Mon 14/01/2019 14:05:41 your computer crashed or a problem was reported
crash dump file: C:\Windows\MEMORY.DMP
This was probably caused by the following module: fltmgr.sys (FLTMGR+0x3C1B0)
Bugcheck code: 0x7E (0xFFFFFFFFC0000005, 0xFFFFF8046E76EF35, 0xFFFFC70CDFEEEFE8, 0xFFFFC70CDFEEE830)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
file path: C:\WINDOWS\system32\drivers\fltmgr.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Gestionnaire de filtres de système de fichiers Microsoft
Bug check description: This bug check indicates that a system thread generated an exception that the error handler did not catch.
The crash took place in a file system driver. Since there is no other responsible driver detected, this could be pointing to a malfunctioning drive or corrupted disk. It's suggested that you run CHKDSK.


On Fri 11/01/2019 18:23:29 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\011119-16515-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1B1B40)
Bugcheck code: 0x1C7 (0x0, 0xFFFF9C0B7BEEC000, 0x5DF28A04, 0x3FE09B)
Error: CUSTOM_ERROR
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System


On Fri 11/01/2019 12:49:26 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\011119-18140-01.dmp
This was probably caused by the following module: hardware.sys (hardware)
Bugcheck code: 0x1A (0x41792, 0xFFFF81014D241148, 0x2000000, 0x0)
Error: MEMORY_MANAGEMENT
Bug check description: This indicates that a severe memory management error occurred. A corrupted PTE has been detected.
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).
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: hardware.sys .
Google query: hardware.sys MEMORY_MANAGEMENT

On Mon 31/12/2018 17:17:13 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\123118-15437-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1B1B40)
Bugcheck code: 0x12B (0xFFFFFFFFC00002C4, 0x299, 0x2100062B5A0, 0xFFFFCD000768C000)
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).


On Mon 31/12/2018 08:35:25 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\123118-19640-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1B1B40)
Bugcheck code: 0x50 (0xFFFF9503FD700010, 0x0, 0xFFFFF8012174ADA5, 0x2)
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.
 

On Sun 30/12/2018 14:08:25 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\123018-17687-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1B1B40)
Bugcheck code: 0x4E (0x2, 0x38A895, 0x435FFF, 0x1)
Error: PFN_LIST_CORRUPT
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 page frame number (PFN) list is corrupted.
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.


On Sun 30/12/2018 09:42:27 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\123018-18359-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1B1B40)
Bugcheck code: 0x139 (0x3, 0xFFFFEA846F28F4C0, 0xFFFFEA846F28F418, 0x0)
Error: KERNEL_SECURITY_CHECK_FAILURE
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: The kernel has detected the corruption of a critical data structure.


On Sun 30/12/2018 08:35:41 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\123018-25718-01.dmp
This was probably caused by the following module: ntfs.sys (0xFFFFF8018A07B826)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF8018A07B826, 0xFFFFFD0F5DB1F3E8, 0xFFFFFD0F5DB1EC30)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\WINDOWS\system32\drivers\ntfs.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote du système de fichiers NT
Bug check description: This indicates that a system thread generated an exception which the error handler did not catch.
 
The crash took place in a file system driver. Since there is no other responsible driver detected, this could be pointing to a malfunctioning drive or corrupted disk. It's suggested that you run CHKDSK.


On Sat 15/12/2018 14:23:01 your computer crashed or a problem was reported
crash dump file: C:\Windows\MEMORY.DMP
This was probably caused by the following module: ntfs.sys (Ntfs+0x109F01)
Bugcheck code: 0x139 (0x3, 0xFFFFC10FC1DC72F0, 0xFFFFC10FC1DC7248, 0x0)
Error: KERNEL_SECURITY_CHECK_FAILURE
file path: C:\WINDOWS\system32\drivers\ntfs.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote du système de fichiers NT
Bug check description: The kernel has detected the corruption of a critical data structure.
The crash took place in a file system driver. Since there is no other responsible driver detected, this could be pointing to a malfunctioning drive or corrupted disk. It's suggested that you run CHKDSK.


On Fri 14/12/2018 21:43:07 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\121418-16234-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1B1B40)
Bugcheck code: 0x4E (0x2, 0x46CB, 0x435FFF, 0x1)
Error: PFN_LIST_CORRUPT
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 page frame number (PFN) list is corrupted.
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.


On Tue 11/12/2018 21:08:09 your computer crashed or a problem was reported
crash dump file: C:\Windows\MEMORY.DMP
This was probably caused by the following module: ntfs.sys (0xFFFFF80736D1963A)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80736D1963A, 0xFFFFC5043EF66610, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\WINDOWS\system32\drivers\ntfs.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote du système de fichiers NT
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
 
The crash took place in a file system driver. Since there is no other responsible driver detected, this could be pointing to a malfunctioning drive or corrupted disk. It's suggested that you run CHKDSK.


On Tue 11/12/2018 20:15:45 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\121118-17406-01.dmp
This was probably caused by the following module: ntfs.sys (0xFFFFF8084631415E)
Bugcheck code: 0x50 (0xFFFFB90A90A7A198, 0x0, 0xFFFFF8084631415E, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\WINDOWS\system32\drivers\ntfs.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote du système de fichiers NT
Bug check description: This indicates that invalid system memory has been referenced.
 
The crash took place in a file system driver. Since there is no other responsible driver detected, this could be pointing to a malfunctioning drive or corrupted disk. It's suggested that you run CHKDSK.

 

On Mon 03/12/2018 22:02:16 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\120318-16625-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1B1040)
Bugcheck code: 0x139 (0x3, 0xFFFFFE8840BDE480, 0xFFFFFE8840BDE3D8, 0x0)
Error: KERNEL_SECURITY_CHECK_FAILURE
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: The kernel has detected the corruption of a critical data structure.


On Fri 30/11/2018 21:41:44 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\113018-15125-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1B1040)
Bugcheck code: 0xEF (0xFFFF9F8D2C724080, 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.


On Fri 30/11/2018 21:41:44 your computer crashed or a problem was reported
crash dump file: C:\Windows\MEMORY.DMP
This was probably caused by the following module: ntdll.sys (ntdll!NtTerminateProcess+0x14)
Bugcheck code: 0xEF (0xFFFF9F8D2C724080, 0x0, 0x0, 0x0)
Error: CRITICAL_PROCESS_DIED
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.
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: ntdll.sys .
Google query: ntdll.sys CRITICAL_PROCESS_DIED


On Tue 20/11/2018 13:03:19 your computer crashed or a problem was reported
crash dump file: C:\Windows\MEMORY.DMP
This was probably caused by the following module: fltmgr.sys (FLTMGR!FltObjectDereference+0x351)
Bugcheck code: 0x7E (0xFFFFFFFFC0000005, 0xFFFFF80154AA6659, 0xFFFFCE0839737258, 0xFFFFCE0839736AA0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
file path: C:\WINDOWS\system32\drivers\fltmgr.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Gestionnaire de filtres de système de fichiers Microsoft
Bug check description: This bug check indicates that a system thread generated an exception that the error handler did not catch.
The crash took place in a file system driver. Since there is no other responsible driver detected, this could be pointing to a malfunctioning drive or corrupted disk. It's suggested that you run CHKDSK.


On Mon 19/11/2018 18:48:34 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\111918-7609-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1B1040)
Bugcheck code: 0x21 (0xFFFFC606C2E1E540, 0x2, 0x10000000C, 0xFFF991B0)
Error: QUOTA_UNDERFLOW
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 quota charges have been mishandled by returning more quota to a particular block than was previously charged.


On Wed 31/10/2018 20:25:08 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\103118-6359-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1B0F30)
Bugcheck code: 0xA (0xE4C, 0xFF, 0x53, 0xFFFFF804546EDE82)
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.


On Wed 31/10/2018 15:13:04 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\103118-6218-01.dmp
This was probably caused by the following module: hardware.sys (hardware)
Bugcheck code: 0x1A (0x41792, 0xFFFFFB8000A47120, 0x4000000, 0x0)
Error: MEMORY_MANAGEMENT
Bug check description: This indicates that a severe memory management error occurred. A corrupted PTE has been detected.
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).
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: hardware.sys .
Google query: hardware.sys MEMORY_MANAGEMENT
 

On Mon 29/10/2018 18:37:27 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\102918-6781-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1B0F30)
Bugcheck code: 0xBE (0xFFFF82BEFA6AA8E0, 0x1A000000880AB025, 0xFFFF9F88E99624C0, 0xA)
Error: ATTEMPTED_WRITE_TO_READONLY_MEMORY
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This is issued if a driver attempts to write to a read-only memory segment.
 

On Mon 29/10/2018 18:37:27 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!memset+0x777F5)
Bugcheck code: 0xBE (0xFFFF82BEFA6AA8E0, 0x1A000000880AB025, 0xFFFF9F88E99624C0, 0xA)
Error: ATTEMPTED_WRITE_TO_READONLY_MEMORY
Bug check description: This is issued if a driver attempts to write to a read-only memory segment.
 

On Tue 09/10/2018 12:00:50 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\100918-8812-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1B0F30)
Bugcheck code: 0x4E (0x2, 0x4188B, 0x435FFF, 0x1)
Error: PFN_LIST_CORRUPT
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 page frame number (PFN) list is corrupted.
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.


On Tue 09/10/2018 12:00:50 your computer crashed or a problem was reported
crash dump file: C:\Windows\MEMORY.DMP
This was probably caused by the following module: ntfs.sys (Ntfs+0xCB133)
Bugcheck code: 0x4E (0x2, 0x4188B, 0x435FFF, 0x1)
Error: PFN_LIST_CORRUPT
file path: C:\WINDOWS\system32\drivers\ntfs.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote du système de fichiers NT
Bug check description: This indicates that the page frame number (PFN) list is corrupted.
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 a file system driver. Since there is no other responsible driver detected, this could be pointing to a ma

On Wed 03/10/2018 18:55:46 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\100318-6578-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1B0F30)
Bugcheck code: 0x50 (0xFFFFC50306973010, 0x2, 0x0, 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.
 

On Wed 03/10/2018 18:55:46 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!memset+0x5077C)
Bugcheck code: 0x50 (0xFFFFC50306973010, 0x2, 0x0, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
Bug check description: This indicates that invalid system memory has been referenced.
 
C:\Windows\Minidump

On Fri 28/09/2018 09:23:17 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\092818-11375-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1A9380)
Bugcheck code: 0x50 (0xFFFF8A25C0FEE022, 0x0, 0xFFFFF8025A531734, 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.
 

On Fri 14/09/2018 22:34:01 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\091418-7953-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1A9380)
Bugcheck code: 0x12B (0xFFFFFFFFC00002C4, 0x88B, 0x304F610, 0xFFFF9480B0447000)
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).


On Fri 26/01/2018 21:53:32 your computer crashed
crash dump file: C:\WINDOWS\Minidump\012618-13250-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1756E0)
Bugcheck code: 0x133 (0x1, 0x1E00, 0xFFFFF803BEC11370, 0x0)
Error: DPC_WATCHDOG_VIOLATION
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL or above.
 This problem might also be caused because of overheating (thermal issue).


On Thu 25/01/2018 17:12:39 your computer crashed
crash dump file: C:\WINDOWS\Minidump\012518-13968-01.dmp
This was probably caused by the following module: ntfs.sys (NTFS+0x1F4C59)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF80132428AC3, 0xFFFF9900210F5428, 0xFFFF9900210F4C70)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\WINDOWS\system32\drivers\ntfs.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote du système de fichiers NT
Bug check description: This indicates that a system thread generated an exception which the error handler did not catch.
 
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 12/12/2017 12:18:48 your computer crashed
crash dump file: C:\WINDOWS\Minidump\121217-15687-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1640E0)
Bugcheck code: 0x50 (0xFFFFDF02BDAEBE38, 0x0, 0xFFFFF803B0ABD7F9, 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.
 

On Tue 12/12/2017 11:35:06 your computer crashed
crash dump file: C:\WINDOWS\Minidump\121217-15093-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1640E0)
Bugcheck code: 0x50 (0xFFFF97097B7A359A, 0x0, 0xFFFFF80168EC589D, 0x2)
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.
 

On Mon 11/12/2017 18:18:54 your computer crashed
crash dump file: C:\WINDOWS\Minidump\121117-56390-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1640E0)
Bugcheck code: 0x1A (0x41792, 0xFFFFD7805853E3F8, 0x40000000, 0x0)
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. This problem might also be caused because of overheating (thermal issue).


Crash dumps are enabled on your computer.

On Mon 30/10/2017 15:47:43 your computer crashed
crash dump file: C:\WINDOWS\Minidump\103017-9406-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x163960)
Bugcheck code: 0x12B (0xFFFFFFFFC00002C4, 0x473, 0x655E960, 0xFFFFBF803E143000)
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).


On Sat 28/10/2017 00:43:45 your computer crashed
crash dump file: C:\WINDOWS\Minidump\102817-6343-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x163960)
Bugcheck code: 0x1A (0x31, 0xFFFFAA8DD9A3B200, 0xFFFF9A814E878000, 0xFFFFD40EEB2587CE)
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. This problem might also be caused because of overheating (thermal issue).

 

 

Précédente Accueil Remonter Suivante