Ecran bleu.
DizZorder
-
DizZorder -
DizZorder -
Bonjour,
Je me décide finalement de demander de l'aide après quelques jours de recherche et de tentatives infructueuses pour stopper l'apparition de ce BSOF sur mon PC.
J'ai parcouru plusieurs sujets sur vos forums et déjà vérifié plusieurs raisons possible à ces BS, notamment:
- Nettoyage complet des fichiers inutiles sur mon PC, fichiers .tmp etc.
- Dépoussiérage physique des ventilateurs, carte graphique et mère.
- Vérification de la température des CPU et GPU ( environ 35° "repos" et monte à plus de 75°-90°, ce qui est normale d'après quelques info du net)
- Màj de la carte graphique.
- Suppression des derniers programmes installés.
- Vérification globale du système via le bootmenu, notamment pour vérifier si les barrettes sont défaillantes, tout est ok.
Et le problème persiste.
Après le téléchargement de l'aplli WhoCrashed, et le scan des fichiers .dmp, voici les résultats que j'obtiens:
*********
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
CPU: GenuineIntel Intel(R) Core(TM) i7-2600 CPU @ 3.40GHz Intel586, level: 6
8 logical processors, active mask: 255
RAM: 8571527168 total
VM: 2147352576, free: 1927532544
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Wed 29.05.2013 10:20:35 GMT your computer crashed
crash dump file: C:\Windows\Minidump\052913-12027-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C00)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF80003691750, 0x0, 0x20)
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 Wed 29.05.2013 10:20:35 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: fltmgr.sys (fltmgr!FltAcquirePushLockShared+0x762)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF80003691750, 0x0, 0x20)
Error: KMODE_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 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 27.05.2013 18:46:24 GMT your computer crashed
crash dump file: C:\Windows\Minidump\052713-22230-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C00)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF800036DE87E, 0xFFFFF8800D07DE00, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Sun 19.05.2013 11:59:34 GMT your computer crashed
crash dump file: C:\Windows\Minidump\051913-20685-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C00)
Bugcheck code: 0x3B (0xC0000096, 0xFFFFF800036D2E47, 0xFFFFF8800A84B8E0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Fri 10.05.2013 11:56:59 GMT your computer crashed
crash dump file: C:\Windows\Minidump\051013-16270-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C00)
Bugcheck code: 0x19 (0x20, 0xFFFFFA800725A8A0, 0xFFFFFA800725A960, 0x40C0018)
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.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
**************
Malgré mon anglais plus qu'approximatif, je pense comprendre qu'il s'agit d'un problème de driver Windows, notamment dû aux fichiers ntoskrnl.exe et fltmgr.sys.
Malheureusement, à partir de la, je suis complétement démuni, plus aucun résultat crédible sur la toile concernant ces deux fichiers.
Est il possible d'avoir un coup de main de votre part s'il vous plait, avant que je formate le tout.
Je suis à votre disposition pour tout complément d'information.
Merci d'avance et meilleures salutations.
Victor.
Je me décide finalement de demander de l'aide après quelques jours de recherche et de tentatives infructueuses pour stopper l'apparition de ce BSOF sur mon PC.
J'ai parcouru plusieurs sujets sur vos forums et déjà vérifié plusieurs raisons possible à ces BS, notamment:
- Nettoyage complet des fichiers inutiles sur mon PC, fichiers .tmp etc.
- Dépoussiérage physique des ventilateurs, carte graphique et mère.
- Vérification de la température des CPU et GPU ( environ 35° "repos" et monte à plus de 75°-90°, ce qui est normale d'après quelques info du net)
- Màj de la carte graphique.
- Suppression des derniers programmes installés.
- Vérification globale du système via le bootmenu, notamment pour vérifier si les barrettes sont défaillantes, tout est ok.
Et le problème persiste.
Après le téléchargement de l'aplli WhoCrashed, et le scan des fichiers .dmp, voici les résultats que j'obtiens:
*********
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
CPU: GenuineIntel Intel(R) Core(TM) i7-2600 CPU @ 3.40GHz Intel586, level: 6
8 logical processors, active mask: 255
RAM: 8571527168 total
VM: 2147352576, free: 1927532544
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Wed 29.05.2013 10:20:35 GMT your computer crashed
crash dump file: C:\Windows\Minidump\052913-12027-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C00)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF80003691750, 0x0, 0x20)
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 Wed 29.05.2013 10:20:35 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: fltmgr.sys (fltmgr!FltAcquirePushLockShared+0x762)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF80003691750, 0x0, 0x20)
Error: KMODE_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 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 27.05.2013 18:46:24 GMT your computer crashed
crash dump file: C:\Windows\Minidump\052713-22230-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C00)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF800036DE87E, 0xFFFFF8800D07DE00, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Sun 19.05.2013 11:59:34 GMT your computer crashed
crash dump file: C:\Windows\Minidump\051913-20685-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C00)
Bugcheck code: 0x3B (0xC0000096, 0xFFFFF800036D2E47, 0xFFFFF8800A84B8E0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Fri 10.05.2013 11:56:59 GMT your computer crashed
crash dump file: C:\Windows\Minidump\051013-16270-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C00)
Bugcheck code: 0x19 (0x20, 0xFFFFFA800725A8A0, 0xFFFFFA800725A960, 0x40C0018)
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.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
**************
Malgré mon anglais plus qu'approximatif, je pense comprendre qu'il s'agit d'un problème de driver Windows, notamment dû aux fichiers ntoskrnl.exe et fltmgr.sys.
Malheureusement, à partir de la, je suis complétement démuni, plus aucun résultat crédible sur la toile concernant ces deux fichiers.
Est il possible d'avoir un coup de main de votre part s'il vous plait, avant que je formate le tout.
Je suis à votre disposition pour tout complément d'information.
Merci d'avance et meilleures salutations.
Victor.
A voir également:
- Ecran bleu.
- Supprimer rond bleu whatsapp - Guide
- Double ecran - Guide
- Écran bleu - Guide
- Capture d'écran whatsapp - Accueil - Messagerie instantanée
- Retourner ecran pc - Guide
