Ecran bleu et reboot
Fermé
kls972
Messages postés
116
Date d'inscription
mardi 14 octobre 2008
Statut
Membre
Dernière intervention
19 août 2014
-
19 août 2014 à 13:29
kls972 Messages postés 116 Date d'inscription mardi 14 octobre 2008 Statut Membre Dernière intervention 19 août 2014 - 19 août 2014 à 13:44
kls972 Messages postés 116 Date d'inscription mardi 14 octobre 2008 Statut Membre Dernière intervention 19 août 2014 - 19 août 2014 à 13:44
A voir également:
- Ecran bleu et reboot
- Ecran noir pc - Guide
- Retourner ecran windows - Guide
- Double ecran - Guide
- Écran bleu - Guide
- Enregistrer son ecran - Guide
1 réponse
kls972
Messages postés
116
Date d'inscription
mardi 14 octobre 2008
Statut
Membre
Dernière intervention
19 août 2014
2
19 août 2014 à 13:44
19 août 2014 à 13:44
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Tue 19/08/2014 01:00:55 GMT your computer crashed
crash dump file: C:\Windows\Minidump\081914-111681-01.dmp
This was probably caused by the following module: ntfs.sys (0xFFFFF880014AF28E)
Bugcheck code: 0x50 (0xFFFFFFFF840F0315, 0x1, 0xFFFFF880014AF28E, 0x5)
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 19/08/2014 01:00:55 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0xA428E)
Bugcheck code: 0x50 (0xFFFFFFFF840F0315, 0x1, 0xFFFFF880014AF28E, 0x5)
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.
Crash dumps are enabled on your computer.
On Tue 19/08/2014 01:00:55 GMT your computer crashed
crash dump file: C:\Windows\Minidump\081914-111681-01.dmp
This was probably caused by the following module: ntfs.sys (0xFFFFF880014AF28E)
Bugcheck code: 0x50 (0xFFFFFFFF840F0315, 0x1, 0xFFFFF880014AF28E, 0x5)
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 19/08/2014 01:00:55 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0xA428E)
Bugcheck code: 0x50 (0xFFFFFFFF840F0315, 0x1, 0xFFFFF880014AF28E, 0x5)
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.