Précédente Accueil Remonter Suivante

Kernel-Power 41

Windows 10

 

Analyse avec WhoCrashed              journal d'évènements

 

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)

H170-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)


Computer name: PCDANIEL
Windows version: Windows 10 , 10.0, build: 15063
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: 17100804096 bytes total

 


Crash Dump Analysis avec Windows Creator

Crash dump directory: C:\WINDOWS\Minidump

Crash dumps are enabled on your computer.

On Wed 26/04/2017 13:02:44 your computer crashed
crash dump file: C:\WINDOWS\Minidump\042617-26312-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x16BF70)
Bugcheck code: 0x12B (0xFFFFFFFFC00002C4, 0x6BD, 0xAF09D80, 0xFFFFA30096E75000)
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 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).
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 26/04/2017 13:02:44 your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: ntfs.sys (NTFS+0xFE4C1)
Bugcheck code: 0x12B (0xFFFFFFFFC00002C4, 0x6BD, 0xAF09D80, 0xFFFFA30096E75000)
Error: FAULTY_HARDWARE_CORRUPTED_PAGE
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 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 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).
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 Mon 17/04/2017 13:09:35 your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x50 (0xFFFFDE06BC253338, 0x0, 0xFFFFF8021003BE5F, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
Bug check description: This indicates that invalid system memory has been referenced.
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 16/04/2017 19:06:57 your computer crashed
crash dump file: C:\WINDOWS\Minidump\041617-11781-01.dmp
This was probably caused by the following module: ntfs.sys (NTFS+0x19009)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF80584219009, 0xFFFF838072C468D8, 0xFFFF838072C46110)
Error: KMODE_EXCEPTION_NOT_HANDLED
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 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.



On Fri 14/04/2017 08:49:53 your computer crashed
crash dump file: C:\WINDOWS\Minidump\041417-6984-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x16BF70)
Bugcheck code: 0x139 (0x3, 0xFFFF8101416E6610, 0xFFFF8101416E6568, 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.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.


 


Crash Dump Analysis


 

On Wed 05/04/2017 21:17:53 your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: win32kbase.sys (win32kbase!RGNOBJ::bMerge+0x5D)
Bugcheck code: 0x50 (0xFFFFFFFFFFFFFFFC, 0x0, 0xFFFFF013285B8F4D, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\WINDOWS\system32\win32kbase.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote du noyau Base Win32k
Bug check description: This indicates that invalid system memory has been referenced.
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 22/03/2017 11:36:03 your computer crashed
crash dump file: C:\Windows\Minidump\032217-11828-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14E7C0)
Bugcheck code: 0x1A (0x31, 0xFFFF9985078A2D60, 0xFFFFAE815498C000, 0xFFFF890A1199339C)
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).
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 22/03/2017 11:36:03 your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x1A (0x31, 0xFFFF9985078A2D60, 0xFFFFAE815498C000, 0xFFFF890A1199339C)
Error: MEMORY_MANAGEMENT
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).
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 22/03/2017 10:37:41 your computer crashed
crash dump file: C:\Windows\Minidump\032217-8328-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3ED129)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF80210A7C129, 0xFFFFD7815730F548, 0xFFFFD7815730ED70)
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.
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 19/03/2017 21:05:10 your computer crashed
crash dump file: C:\Windows\Minidump\031917-13656-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14E7C0)
Bugcheck code: 0xA (0xFFFFD382A2A588E8, 0x2, 0x0, 0xFFFFF801F3491B6F)
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 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 19/03/2017 17:50:13 your computer crashed
crash dump file: C:\Windows\Minidump\031917-10890-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14E7C0)
Bugcheck code: 0x1A (0x41793, 0xFFFFC7000036B008, 0x2, 0x1)
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).
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 17/03/2017 09:51:46 your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x1A (0x41792, 0xFFFFF8800002D158, 0x10000000, 0x0)
Error: MEMORY_MANAGEMENT
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).
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 16/03/2017 15:57:02 your computer crashed
crash dump file: C:\Windows\Minidump\031617-15250-01.dmp
This was probably caused by the following module: ntfs.sys (NTFS+0x1EB2A)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF8097BB7EB2A, 0xFFFF9F01AE279DF8, 0xFFFF9F01AE279620)
Error: KMODE_EXCEPTION_NOT_HANDLED
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 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.



On Mon 13/03/2017 12:07:14 your computer crashed
crash dump file: C:\Windows\Minidump\031317-13828-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14A6F0)
Bugcheck code: 0x19 (0x3, 0xFFFF93887AE21010, 0x0, 0xFFFF93887AE21010)
Error: BAD_POOL_HEADER
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 pool header is corrupt.
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. 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).
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 10/03/2017 13:41:40 your computer crashed
crash dump file: C:\Windows\Minidump\031017-57031-01.dmp
This was probably caused by the following module: ntfs.sys (0xFFFFF807CDAAEE64)
Bugcheck code: 0x50 (0xFFFF800CEFA5F350, 0x0, 0xFFFFF807CDAAEE64, 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.
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 09/03/2017 21:21:47 your computer crashed
crash dump file: C:\Windows\Minidump\030917-12015-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14A6F0)
Bugcheck code: 0x12B (0xFFFFFFFFC00002C4, 0x6D4, 0xF6DCF30, 0xFFFFD481BAB7E000)
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 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).
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 09/03/2017 18:29:58 your computer crashed
crash dump file: C:\Windows\Minidump\030917-11703-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14A6F0)
Bugcheck code: 0x50 (0xFFFFCE04D4976060, 0x2, 0xFFFFF80360424822, 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.
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 Thu 09/03/2017 10:40:23 your computer crashed
crash dump file: C:\Windows\Minidump\030917-6265-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14A6F0)
Bugcheck code: 0x1A (0x41793, 0xFFFFDD80002A7FF8, 0x200, 0x1FF)
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).
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 07/03/2017 22:05:43 your computer crashed
crash dump file: C:\Windows\Minidump\030717-17593-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14A6F0)
Bugcheck code: 0xE3 (0xFFFFBE8890617170, 0xFFFFBE887C825800, 0x0, 0x2)
Error: RESOURCE_NOT_OWNED
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 thread tried to release a resource it did not own.
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 03/03/2017 12:21:09 your computer crashed
crash dump file: C:\Windows\Minidump\030317-7312-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14A6F0)
Bugcheck code: 0x4E (0x99, 0x331A8, 0x2, 0xC000030000331A7)
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 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. 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 Fri 03/03/2017 03:35:37 your computer crashed
crash dump file: C:\Windows\Minidump\030317-8515-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14A6F0)
Bugcheck code: 0x1A (0x8887, 0xFFFF82800B131E30, 0xFFFF8280003E15D0, 0x205)
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).
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 02/03/2017 15:10:27 your computer crashed
crash dump file: C:\Windows\Minidump\030217-6078-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14A6F0)
Bugcheck code: 0x139 (0x3, 0xFFFFA501B8576660, 0xFFFFA501B85765B8, 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.
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 01/03/2017 22:53:58 your computer crashed
crash dump file: C:\Windows\Minidump\030117-6437-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14A6F0)
Bugcheck code: 0x139 (0x3, 0xFFFF9300D09EF1D0, 0xFFFF9300D09EF128, 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.
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/02/2017 20:15:41 your computer crashed
crash dump file: C:\Windows\Minidump\022617-6375-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14A6F0)
Bugcheck code: 0x4E (0x99, 0x6D7E8, 0x2, 0xC000050000554E7)
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 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. 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 Fri 24/02/2017 20:58:00 your computer crashed
crash dump file: C:\Windows\Minidump\022417-5968-01.dmp
This was probably caused by the following module: win32kfull.sys (0xFFFFF5A3D38D1050)
Bugcheck code: 0x109 (0xA3A00F6015C8B6A8, 0xB3B71BE6684A49A6, 0xFFFFF5A3D38D1050, 0xC)
Error: CRITICAL_STRUCTURE_CORRUPTION
file path: C:\Windows\system32\win32kfull.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Full/Desktop Win32k Kernel Driver
Bug check description: This indicates that the kernel has detected critical kernel code or data corruption.
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 Mon 20/02/2017 11:59:05 your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntfs.sys (NTFS+0x101603)
Bugcheck code: 0x50 (0xFFFF958D928C31C4, 0x0, 0xFFFFF8052C311603, 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.
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 16/02/2017 17:27:25 your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x1A (0x41792, 0xFFFFEF80000339E8, 0x8000000, 0x0)
Error: MEMORY_MANAGEMENT
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).
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 15/02/2017 17:33:49 your computer crashed
crash dump file: C:\Windows\Minidump\021517-8125-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14A6F0)
Bugcheck code: 0x12B (0xFFFFFFFFC00002C4, 0x9B5, 0xD49400, 0xFFFF9A8070DA8000)
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 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).
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 14/02/2017 23:23:38 your computer crashed
crash dump file: C:\Windows\Minidump\021417-7031-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14A6F0)
Bugcheck code: 0xC2 (0xB, 0xFFFF9B0303E08000, 0x490400, 0xFFFF9B0303E084A0)
Error: BAD_POOL_CALLER
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 current thread is making a bad pool request.
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 Mon 13/02/2017 11:29:05 your computer crashed
crash dump file: C:\Windows\Minidump\021317-6390-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14A6F0)
Bugcheck code: 0x1A (0x41792, 0xFFFFA000000BE030, 0x1000000, 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).
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 04/02/2017 15:40:18 your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x50 (0xFFFF9481D87CA688, 0x0, 0xFFFFF80076E25FC4, 0x1)
Error: PAGE_FAULT_IN_NONPAGED_AREA
Bug check description: This indicates that invalid system memory has been referenced.
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 03/02/2017 12:01:46 your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: hal.dll (hal!HalPerformEndOfInterrupt+0x245)
Bugcheck code: 0x133 (0x1, 0x1E00, 0x0, 0x0)
Error: DPC_WATCHDOG_VIOLATION
file path: C:\Windows\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
Bug check description: The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might also be caused because of overheating (thermal issue).
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 31/01/2017 21:12:19 your computer crashed
crash dump file: C:\Windows\Minidump\013117-6062-01.dmp
This was probably caused by the following module: ntfs.sys (0xFFFFF808AF914EAF)
Bugcheck code: 0x50 (0xFFFFD48C354C9048, 0x0, 0xFFFFF808AF914EAF, 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.
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 Tue 31/01/2017 19:23:23 your computer crashed
crash dump file: C:\Windows\Minidump\013117-8578-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14A6F0)
Bugcheck code: 0x19 (0x3, 0xFFFFE489DC4C4290, 0x1, 0xFFFFE489DC4C4290)
Error: BAD_POOL_HEADER
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 pool header is corrupt.
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. 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).
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 31/01/2017 19:23:23 your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntfs.sys (NTFS+0xA19CD)
Bugcheck code: 0x19 (0x3, 0xFFFFE489DC4C4290, 0x1, 0xFFFFE489DC4C4290)
Error: BAD_POOL_HEADER
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 pool header is corrupt.
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. 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).
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 22/01/2017 09:55:01 your computer crashed
crash dump file: C:\Windows\Minidump\012217-6812-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14A6F0)
Bugcheck code: 0xEF (0xFFFFDE07188E6080, 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 20/01/2017 17:03:00 your computer crashed
crash dump file: C:\Windows\Minidump\012017-8359-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14A6F0)
Bugcheck code: 0x133 (0x1, 0x1E00, 0x0, 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 appears to be a typical software driver bug and is not likely to be caused by a hardware problem. 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 Thu 19/01/2017 15:55:45 your computer crashed
crash dump file: C:\Windows\Minidump\011917-6593-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14A6F0)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF80136141450, 0x0, 0x4000000)
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 Thu 19/01/2017 15:55:45 your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: aswsnx.sys (aswSnx+0x25D01)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF80136141450, 0x0, 0x4000000)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\drivers\aswsnx.sys
product: Avast Antivirus
company: AVAST Software
description: avast! Virtualization 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.
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: aswsnx.sys (avast! Virtualization Driver, AVAST Software).
Google query: AVAST Software KMODE_EXCEPTION_NOT_HANDLED

 

On Wed 18/01/2017 20:06:25 your computer crashed
crash dump file: C:\Windows\Minidump\011817-9609-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14A6F0)
Bugcheck code: 0x139 (0x3, 0xFFFFC580F7B8F390, 0xFFFFC580F7B8F2E8, 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.
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 18/01/2017 20:06:25 your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntfs.sys (NTFS+0xE076)
Bugcheck code: 0x139 (0x3, 0xFFFFC580F7B8F390, 0xFFFFC580F7B8F2E8, 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 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 Mon 16/01/2017 14:15:38 your computer crashed
crash dump file: C:\Windows\Minidump\011617-7921-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14A6F0)
Bugcheck code: 0x50 (0xFFFF92C940000200, 0x0, 0x0, 0x6)
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.
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 Mon 16/01/2017 14:15:38 your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: aswmonflt.sys (aswMonFlt+0x9AD5)
Bugcheck code: 0x50 (0xFFFF92C940000200, 0x0, 0x0, 0x6)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\drivers\aswmonflt.sys
product: Avast Antivirus
company: AVAST Software
description: avast! File System Minifilter for Windows 2003/Vista
Bug check description: This indicates that invalid system memory has been referenced.
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: aswmonflt.sys (avast! File System Minifilter for Windows 2003/Vista, AVAST Software).
Google query: AVAST Software PAGE_FAULT_IN_NONPAGED_AREA
 

On Fri 13/01/2017 10:43:07 your computer crashed
crash dump file: C:\Windows\Minidump\011317-8828-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14A6F0)
Bugcheck code: 0x1A (0x41792, 0xFFFFA3000036C850, 0x2000000, 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).
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 13/01/2017 10:43:07 your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x1A (0x41792, 0xFFFFA3000036C850, 0x2000000, 0x0)
Error: MEMORY_MANAGEMENT
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).
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 08/01/2017 09:52:52 your computer crashed
crash dump file: C:\Windows\Minidump\010817-6500-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14A6F0)
Bugcheck code: 0x50 (0xFFFF8102732E7188, 0x2, 0xFFFFF8027E921039, 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.
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.

Crash dumps are enabled on your computer.

On Sat 24/12/2016 18:44:35 your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: fltmgr.sys (FLTMGR!FltGetStreamContext+0x647)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF803AB607827, 0xFFFFB58149820820, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 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 24/12/2016 10:06:57 your computer crashed
crash dump file: C:\Windows\Minidump\122416-11421-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14A6F0)
Bugcheck code: 0x1A (0x41792, 0xFFFF8D00000D60E0, 0x10000000, 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).
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 21/12/2016 21:30:41 your computer crashed
crash dump file: C:\Windows\Minidump\122116-6390-01.dmp
This was probably caused by the following module: ntfs.sys (NTFS+0xAEE70)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF8058B4AEE70, 0x0, 0x10000018)
Error: KMODE_EXCEPTION_NOT_HANDLED
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 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.

 

On Fri 09/12/2016 16:20:25 your computer crashed
crash dump file: C:\WINDOWS\Minidump\120916-6546-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14A510)
Bugcheck code: 0x18 (0x0, 0xFFFFD885B86CDE00, 0x20, 0xF7E4BEC8EF75271D)
Error: REFERENCE_BY_POINTER
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 reference count of an object is illegal for the current state of the object.
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. 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 Tue 06/12/2016 17:00:52 your computer crashed
crash dump file: C:\WINDOWS\Minidump\120616-15421-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14A510)
Bugcheck code: 0xEF (0xFFFFD18E41542800, 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 Mon 05/12/2016 17:18:57 your computer crashed
crash dump file: C:\WINDOWS\Minidump\120516-50750-01.dmp
This was probably caused by the following module: ntfs.sys (0xFFFFF8019519AD8F)
Bugcheck code: 0x50 (0xFFFF838255BF7230, 0x0, 0xFFFFF8019519AD8F, 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.
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 04/12/2016 12:44:19 your computer crashed
crash dump file: C:\WINDOWS\Minidump\120416-6890-01.dmp
This was probably caused by the following module: fileinfo.sys (fileinfo+0xBC2F)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF80390210A85, 0xFFFFB700900A72C8, 0xFFFFB700900A6AF0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\WINDOWS\system32\drivers\fileinfo.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: FileInfo Filter Driver
Bug check description: This indicates that a system thread 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.


On Fri 02/12/2016 21:16:16 your computer crashed
crash dump file: C:\WINDOWS\Minidump\120216-6093-01.dmp
This was probably caused by the following module: ntfs.sys (NTFS+0x53F2)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF8051F4053F2, 0x0, 0x4000060)
Error: KMODE_EXCEPTION_NOT_HANDLED
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 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.


On Thu 01/12/2016 21:57:35 your computer crashed
crash dump file: C:\WINDOWS\Minidump\120116-5937-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14A510)
Bugcheck code: 0x50 (0xFFFFD2038D2111C8, 0x0, 0xFFFFF801D230478B, 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.
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 Thu 01/12/2016 20:12:05 your computer crashed
crash dump file: C:\WINDOWS\Minidump\120116-6796-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14A510)
Bugcheck code: 0x1A (0x41793, 0xFFFFDF80000096F8, 0x4A, 0x49)
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).
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 25/11/2016 18:57:27 your computer crashed
crash dump file: C:\WINDOWS\Minidump\112516-9468-01.dmp
This was probably caused by the following module: ntfs.sys (0xFFFFF80D8CDC06AE)
Bugcheck code: 0x50 (0xFFFF828FCC84A184, 0x0, 0xFFFFF80D8CDC06AE, 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.
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 Fri 25/11/2016 17:35:05 your computer crashed
crash dump file: C:\WINDOWS\Minidump\112516-5953-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14A510)
Bugcheck code: 0x1A (0x31, 0xFFFFB885F72826F0, 0xFFFFA1008D6FF000, 0xFFFFCA8FE3E26A92)
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).
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 25/11/2016 17:07:02 your computer crashed
crash dump file: C:\WINDOWS\Minidump\112516-6718-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14A510)
Bugcheck code: 0x139 (0x3, 0xFFFFBF8104C69520, 0xFFFFBF8104C69478, 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.
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 25/11/2016 12:08:51 your computer crashed
crash dump file: C:\WINDOWS\Minidump\112516-7000-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14A510)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8026C829633, 0xFFFF9900A2912A70, 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.

 


Conclusion



8 crash dumps have been found and analyzed. Only 5 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.

 

 

1

 

2

Option-X

 

3

 

4

 

5

 

 

 

Précédente Accueil Remonter Suivante