Profil temporaire + écran bleu + problème NTFS, disque dur bon.
Fermé
Kairros
Messages postés
9
Date d'inscription
jeudi 17 juillet 2014
Statut
Membre
Dernière intervention
18 mars 2015
-
14 déc. 2014 à 18:30
Malekal_morte- Messages postés 180304 Date d'inscription mercredi 17 mai 2006 Statut Modérateur, Contributeur sécurité Dernière intervention 15 décembre 2020 - 15 déc. 2014 à 08:27
Malekal_morte- Messages postés 180304 Date d'inscription mercredi 17 mai 2006 Statut Modérateur, Contributeur sécurité Dernière intervention 15 décembre 2020 - 15 déc. 2014 à 08:27
A voir également:
- Profil temporaire + écran bleu + problème NTFS, disque dur bon.
- Cloner disque dur - Guide
- Defragmenter disque dur - Guide
- Qui regarde mon profil facebook - Guide
- Remplacer disque dur par ssd - Guide
- Double ecran - Guide
7 réponses
Malekal_morte-
Messages postés
180304
Date d'inscription
mercredi 17 mai 2006
Statut
Modérateur, Contributeur sécurité
Dernière intervention
15 décembre 2020
24 631
14 déc. 2014 à 18:31
14 déc. 2014 à 18:31
Salut,
- Dans le journal d'événement, le problème NTFS aparait souvent.
Que dit l'onglet Health d'HDD tune : https://forum.malekal.com/viewtopic.php?t=43963&start=
ça dit quoi le BSOD ?
- Dans le journal d'événement, le problème NTFS aparait souvent.
Que dit l'onglet Health d'HDD tune : https://forum.malekal.com/viewtopic.php?t=43963&start=
ça dit quoi le BSOD ?
Kairros
Messages postés
9
Date d'inscription
jeudi 17 juillet 2014
Statut
Membre
Dernière intervention
18 mars 2015
14 déc. 2014 à 18:53
14 déc. 2014 à 18:53
Malekal_morte >
Voici un screen de l'onglet Health :
http://hpics.li/9d1abca
Quand au message d'erreur, j'ai pas le temps de le voir, il reste 0.2sec et ça reboot direct.
Voici un screen de l'onglet Health :
http://hpics.li/9d1abca
Quand au message d'erreur, j'ai pas le temps de le voir, il reste 0.2sec et ça reboot direct.
Malekal_morte-
Messages postés
180304
Date d'inscription
mercredi 17 mai 2006
Statut
Modérateur, Contributeur sécurité
Dernière intervention
15 décembre 2020
24 631
14 déc. 2014 à 18:56
14 déc. 2014 à 18:56
Déjà y a un prob de disque.
Y a des secteurs défectueux.
Tu peux fournir un rapport whocrashed ?
=> https://forum.malekal.com/viewtopic.php?t=47660&start=
Y a des secteurs défectueux.
Tu peux fournir un rapport whocrashed ?
=> https://forum.malekal.com/viewtopic.php?t=47660&start=
Kairros
Messages postés
9
Date d'inscription
jeudi 17 juillet 2014
Statut
Membre
Dernière intervention
18 mars 2015
14 déc. 2014 à 19:04
14 déc. 2014 à 19:04
Malekal_morte >
Voici le rapport whocrashed :
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Sat 13/12/2014 15:59:04 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: hal.sys (hal!KfLowerIrql+0x61)
Bugcheck code: 0x8E (0xFFFFFFFFC0000005, 0xFFFFFFFF9B45BD01, 0xFFFFFFFFA171FBC4, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED
Bug check description: This bug check indicates that a kernel-mode application generated an exception that the error handler did not catch.
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: hal.sys .
Google query: hal.sys KERNEL_MODE_EXCEPTION_NOT_HANDLED
On Sat 13/12/2014 00:12:35 GMT your computer crashed
crash dump file: C:\Windows\Minidump\121314-25552-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0x3D687)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF9B31D687, 0xFFFFFFFFA254F730, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\win32k.sys
product: Systeme d'exploitation MicrosoftR WindowsR
company: Microsoft Corporation
description: Pilote Win32 multi-utilisateurs
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 Tue 09/12/2014 23:04:21 GMT your computer crashed
crash dump file: C:\Windows\Minidump\121014-27487-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0xBD593)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF82D22795, 0xFFFFFFFFA6AEFB04, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\win32k.sys
product: Systeme d'exploitation MicrosoftR WindowsR
company: Microsoft Corporation
description: Pilote Win32 multi-utilisateurs
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 08/12/2014 23:45:30 GMT your computer crashed
crash dump file: C:\Windows\Minidump\120914-26161-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0x3D687)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF9B6ED687, 0xFFFFFFFF8D117730, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\win32k.sys
product: Systeme d'exploitation MicrosoftR WindowsR
company: Microsoft Corporation
description: Pilote Win32 multi-utilisateurs
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 24/11/2014 00:20:39 GMT your computer crashed
crash dump file: C:\Windows\Minidump\112414-23790-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0x6CCD6)
Bugcheck code: 0x50 (0xFFFFFFFFFD827524, 0x0, 0xFFFFFFFF98F4CC3F, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\win32k.sys
product: Systeme d'exploitation MicrosoftR WindowsR
company: Microsoft Corporation
description: Pilote Win32 multi-utilisateurs
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 Mon 17/11/2014 19:42:14 GMT your computer crashed
crash dump file: C:\Windows\Minidump\111714-19515-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0xBED8E)
Bugcheck code: 0xA (0x28, 0x2, 0x1, 0xFFFFFFFF82CA62B9)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\win32k.sys
product: Systeme d'exploitation MicrosoftR WindowsR
company: Microsoft Corporation
description: Pilote Win32 multi-utilisateurs
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 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 16/11/2014 22:49:56 GMT your computer crashed
crash dump file: C:\Windows\Minidump\111614-19812-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0x1BC6BA)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF9913C6BA, 0xFFFFFFFF9EFF7BE0, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\win32k.sys
product: Systeme d'exploitation MicrosoftR WindowsR
company: Microsoft Corporation
description: Pilote Win32 multi-utilisateurs
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 Wed 12/11/2014 03:53:13 GMT your computer crashed
crash dump file: C:\Windows\Minidump\111214-22120-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0xBBD01)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF9970BD01, 0xFFFFFFFF9B5F7B98, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\win32k.sys
product: Systeme d'exploitation MicrosoftR WindowsR
company: Microsoft Corporation
description: Pilote Win32 multi-utilisateurs
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 Tue 11/11/2014 14:15:39 GMT your computer crashed
crash dump file: C:\Windows\Minidump\111114-22292-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0xBBD01)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF99DDBD01, 0xFFFFFFFF9E447B98, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\win32k.sys
product: Systeme d'exploitation MicrosoftR WindowsR
company: Microsoft Corporation
description: Pilote Win32 multi-utilisateurs
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 10/11/2014 00:18:19 GMT your computer crashed
crash dump file: C:\Windows\Minidump\111014-21496-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0x3D687)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF99D3D687, 0xFFFFFFFF9B9DFB10, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\win32k.sys
product: Systeme d'exploitation MicrosoftR WindowsR
company: Microsoft Corporation
description: Pilote Win32 multi-utilisateurs
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.
Voici le rapport whocrashed :
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Sat 13/12/2014 15:59:04 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: hal.sys (hal!KfLowerIrql+0x61)
Bugcheck code: 0x8E (0xFFFFFFFFC0000005, 0xFFFFFFFF9B45BD01, 0xFFFFFFFFA171FBC4, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED
Bug check description: This bug check indicates that a kernel-mode application generated an exception that the error handler did not catch.
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: hal.sys .
Google query: hal.sys KERNEL_MODE_EXCEPTION_NOT_HANDLED
On Sat 13/12/2014 00:12:35 GMT your computer crashed
crash dump file: C:\Windows\Minidump\121314-25552-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0x3D687)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF9B31D687, 0xFFFFFFFFA254F730, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\win32k.sys
product: Systeme d'exploitation MicrosoftR WindowsR
company: Microsoft Corporation
description: Pilote Win32 multi-utilisateurs
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 Tue 09/12/2014 23:04:21 GMT your computer crashed
crash dump file: C:\Windows\Minidump\121014-27487-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0xBD593)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF82D22795, 0xFFFFFFFFA6AEFB04, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\win32k.sys
product: Systeme d'exploitation MicrosoftR WindowsR
company: Microsoft Corporation
description: Pilote Win32 multi-utilisateurs
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 08/12/2014 23:45:30 GMT your computer crashed
crash dump file: C:\Windows\Minidump\120914-26161-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0x3D687)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF9B6ED687, 0xFFFFFFFF8D117730, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\win32k.sys
product: Systeme d'exploitation MicrosoftR WindowsR
company: Microsoft Corporation
description: Pilote Win32 multi-utilisateurs
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 24/11/2014 00:20:39 GMT your computer crashed
crash dump file: C:\Windows\Minidump\112414-23790-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0x6CCD6)
Bugcheck code: 0x50 (0xFFFFFFFFFD827524, 0x0, 0xFFFFFFFF98F4CC3F, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\win32k.sys
product: Systeme d'exploitation MicrosoftR WindowsR
company: Microsoft Corporation
description: Pilote Win32 multi-utilisateurs
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 Mon 17/11/2014 19:42:14 GMT your computer crashed
crash dump file: C:\Windows\Minidump\111714-19515-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0xBED8E)
Bugcheck code: 0xA (0x28, 0x2, 0x1, 0xFFFFFFFF82CA62B9)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\win32k.sys
product: Systeme d'exploitation MicrosoftR WindowsR
company: Microsoft Corporation
description: Pilote Win32 multi-utilisateurs
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 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 16/11/2014 22:49:56 GMT your computer crashed
crash dump file: C:\Windows\Minidump\111614-19812-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0x1BC6BA)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF9913C6BA, 0xFFFFFFFF9EFF7BE0, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\win32k.sys
product: Systeme d'exploitation MicrosoftR WindowsR
company: Microsoft Corporation
description: Pilote Win32 multi-utilisateurs
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 Wed 12/11/2014 03:53:13 GMT your computer crashed
crash dump file: C:\Windows\Minidump\111214-22120-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0xBBD01)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF9970BD01, 0xFFFFFFFF9B5F7B98, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\win32k.sys
product: Systeme d'exploitation MicrosoftR WindowsR
company: Microsoft Corporation
description: Pilote Win32 multi-utilisateurs
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 Tue 11/11/2014 14:15:39 GMT your computer crashed
crash dump file: C:\Windows\Minidump\111114-22292-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0xBBD01)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF99DDBD01, 0xFFFFFFFF9E447B98, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\win32k.sys
product: Systeme d'exploitation MicrosoftR WindowsR
company: Microsoft Corporation
description: Pilote Win32 multi-utilisateurs
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 10/11/2014 00:18:19 GMT your computer crashed
crash dump file: C:\Windows\Minidump\111014-21496-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0x3D687)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF99D3D687, 0xFFFFFFFF9B9DFB10, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\win32k.sys
product: Systeme d'exploitation MicrosoftR WindowsR
company: Microsoft Corporation
description: Pilote Win32 multi-utilisateurs
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.
Vous n’avez pas trouvé la réponse que vous recherchez ?
Posez votre question
Quelqu'un d'autre pour me décrire le rapport ?
Sinon j'ai un autre problème, au démarrage de l'ordi, j'ai parfois des BIP, 1 long, 3 court.
Je dois enlever une barrette de ram, et l'ordi redémarre, et quand je remet la barette ça remarche pendant quelque temps.
Sinon j'ai un autre problème, au démarrage de l'ordi, j'ai parfois des BIP, 1 long, 3 court.
Je dois enlever une barrette de ram, et l'ordi redémarre, et quand je remet la barette ça remarche pendant quelque temps.
Malekal_morte-
Messages postés
180304
Date d'inscription
mercredi 17 mai 2006
Statut
Modérateur, Contributeur sécurité
Dernière intervention
15 décembre 2020
24 631
Modifié par Malekal_morte- le 14/12/2014 à 22:46
Modifié par Malekal_morte- le 14/12/2014 à 22:46
Tes problèmes sont d'ordre matériel, incompatibilité barrette ou une qui a un prob.
Et le disque dur;
Like the angel you are, you laugh creating a lightness in my chest,
Your eyes they penetrate me,
(Your answer's always 'maybe')
That's when I got up and left
Et le disque dur;
Like the angel you are, you laugh creating a lightness in my chest,
Your eyes they penetrate me,
(Your answer's always 'maybe')
That's when I got up and left
Oui je comprend bien, donc que puis-je faire?
Sachant que 1 bip long + 3 bip court = problème avec clavier.
J'ai changer de clavier ça le fait plus la.
Mais la session temporaire est toujours la, j'ai fait le test de RAM elles sont niquel.
Je pense que ça viens du disque dur, mais avant d'en changer j'aimerais m'assurer que ce ne sois pas logiciel, vous comprenez?
Sachant que 1 bip long + 3 bip court = problème avec clavier.
J'ai changer de clavier ça le fait plus la.
Mais la session temporaire est toujours la, j'ai fait le test de RAM elles sont niquel.
Je pense que ça viens du disque dur, mais avant d'en changer j'aimerais m'assurer que ce ne sois pas logiciel, vous comprenez?
Malekal_morte-
Messages postés
180304
Date d'inscription
mercredi 17 mai 2006
Statut
Modérateur, Contributeur sécurité
Dernière intervention
15 décembre 2020
24 631
15 déc. 2014 à 08:27
15 déc. 2014 à 08:27
Si tu veux être sûr que ne soit pas logiciel et au vu des descriptif y a des chances que...
Tu surfs pendant deux jours sur un CD Live, si ça plante, c'est pas logiciels.
Tu surfs pendant deux jours sur un CD Live, si ça plante, c'est pas logiciels.
