Espace membre :
flechePublicité

6 messages
Filtrer ok

Seven : ecrans bleus intempestifs.

Bonjour,

Cela dure depuis plusieurs semaines, j'ai des bluescreens intempestifs et à tous moment ( que ce soit en jeu, à regarder une video ...)

J'ai utilisé "Whocrashed" pour annalyser mon problème, voici le rapport :

On Sat 26/05/2012 12:06:59 GMT your computer crashed
crash dump file: C:\Windows\Minidump\052612-31090-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0x109 (0xA3A039D899359759, 0xB3B7465EEBB266AF, 0xFFFFF800033D9140, 0x1)
Error: CRITICAL_STRUCTURE_CORRUPTION
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 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 the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Sat 26/05/2012 12:06:59 GMT 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: 0x109 (0xA3A039D899359759, 0xB3B7465EEBB266AF, 0xFFFFF800033D9140, 0x1)
Error: CRITICAL_STRUCTURE_CORRUPTION
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 the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Mon 21/05/2012 21:12:54 GMT your computer crashed
crash dump file: C:\Windows\Minidump\052212-20966-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8000337920B, 0xFFFFF8800B302A80, 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 which cannot be identified at this time.


On Mon 21/05/2012 17:59:33 GMT your computer crashed
crash dump file: C:\Windows\Minidump\052112-29390-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0x109 (0xA3A039D898FA34FF, 0xB3B7465EEB770455, 0xFFFFF800031391EA, 0x1)
Error: CRITICAL_STRUCTURE_CORRUPTION
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 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 the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Sun 20/05/2012 12:08:20 GMT your computer crashed
crash dump file: C:\Windows\Minidump\052012-22230-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x5A8
Bugcheck code: 0x24 (0x1904FB, 0xFFFFF8800BFD3718, 0xFFFFF8800BFD2F70, 0xFFFFF800030B920
Error: NTFS_FILE_SYSTEM
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 a problem occurred in the NTFS file system.
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 which cannot be identified at this time.


On Sun 20/05/2012 12:06:05 GMT your computer crashed
crash dump file: C:\Windows\Minidump\052012-22152-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0x109 (0xA3A039D8968D88E8, 0xB3B7465EE90A584E, 0xFFFFF80003058B10, 0x1)
Error: CRITICAL_STRUCTURE_CORRUPTION
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 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 the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Fri 18/05/2012 18:36:34 GMT your computer crashed
crash dump file: C:\Windows\Minidump\051812-43165-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0x109 (0xA3A039D898E3754B, 0xB3B7465EEB6044A1, 0xFFFFF800033D9140, 0x1)
Error: CRITICAL_STRUCTURE_CORRUPTION
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 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 the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Thu 17/05/2012 20:06:27 GMT your computer crashed
crash dump file: C:\Windows\Minidump\051812-20030-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0x109 (0xA3A039D896649690, 0xB3B7465EE8E165E6, 0xFFFFF800030D91EA, 0x1)
Error: CRITICAL_STRUCTURE_CORRUPTION
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 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 the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Thu 17/05/2012 19:47:54 GMT your computer crashed
crash dump file: C:\Windows\Minidump\051712-22120-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0x109 (0xA3A039D8966009E5, 0xB3B7465EE8DCD93B, 0xFFFFF800033D9140, 0x1)
Error: CRITICAL_STRUCTURE_CORRUPTION
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 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 the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Thu 17/05/2012 19:30:58 GMT your computer crashed
crash dump file: C:\Windows\Minidump\051712-21528-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0x109 (0xA3A039D898CC5B5C, 0xB3B7465EEB492AB2, 0xFFFFF800033591A0, 0x1)
Error: CRITICAL_STRUCTURE_CORRUPTION
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 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 the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Sat 12/05/2012 12:57:06 GMT your computer crashed
crash dump file: C:\Windows\Minidump\051212-24226-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0x109 (0xA3A039D898C398EC, 0xB3B7465EEB406842, 0xFFFFF800031B911A, 0x1)
Error: CRITICAL_STRUCTURE_CORRUPTION
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 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 the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Fri 11/05/2012 14:50:13 GMT your computer crashed
crash dump file: C:\Windows\Minidump\051112-38391-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x13D70)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF88001239D70, 0xFFFFF8800ADA7E10, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\drivers\ntfs.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote du système de fichiers NT
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
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 which cannot be identified at this time.


On Fri 11/05/2012 11:49:24 GMT your computer crashed
crash dump file: C:\Windows\Minidump\051112-33290-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0x7F (0x8, 0x80050031, 0x406F8, 0xFFFFF800030B683E)
Error: UNEXPECTED_KERNEL_MODE_TRAP
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 the Intel CPU generated a trap and the kernel failed to catch this trap.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Sat 05/05/2012 19:35:40 GMT your computer crashed
crash dump file: C:\Windows\Minidump\050512-23400-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC80)
Bugcheck code: 0x7F (0x8, 0x80050031, 0x406F8, 0xFFFFF800030B433E)
Error: UNEXPECTED_KERNEL_MODE_TRAP
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 the Intel CPU generated a trap and the kernel failed to catch this trap.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Sat 05/05/2012 18:05:56 GMT your computer crashed
crash dump file: C:\Windows\Minidump\050512-30404-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC80)
Bugcheck code: 0xA (0x7FFFEF1DF8, 0x2, 0x0, 0xFFFFF800030DEBB3)
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 which cannot be identified at this time.


Merci infinniment
 
 
Bonjour.

En général , il s'agit d'un driver non adéquat , voir l'erreur BCC 0x109 :
msdn.microsoft.com...

Mettre ceux-ci à jour :
www.touslesdrivers.com...
 
 
Merci pour ta réponse mais pilotes sont à jours . J'ai aussi fait un memtest non concluant
Pour l'erreur 0x109, comment la fixer ?

Cordialement
 
 
Démarrer -> Tous les programmes -> Accessoires
Clic droit sur Invite de commandes
Choisir Exécuter en tant qu'administrateur
Dans la fenêtre d'invite , saisir ceci :

sfc /scannow (Entrée pour valider).

Redémarrer

(D'autre part, (Si c'est sous Windows 7) , le service Pack 1 , est' il installé ?).
Edité le 27/05/2012 à 09:02
 
 
J'ai fais l’opération, rien n'y change...
Oui le sp1 est installé.

Encore merci !

dernier crash :

On Fri 01/06/2012 17:21:13 GMT your computer crashed
crash dump file: C:\Windows\Minidump\060112-27097-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0xA (0xFFFFF80043247988, 0x2, 0x1, 0xFFFFF800030D9204)
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 which cannot be identified at this time.
 
 
Ces genre d'erreurs peuvent provenir de n'importe quoi , voir si il y' a un problème sur la mémoire RAM avec la commande

mdsched.exe ou alors concernant les secteurs défectueux du disque utiliser la commande chkdsk /f /r

Bien sûr sous la commande CMD.EXE (Invite de commandes) en mode administrateur .

Et en dernière solution (je suppose que vous l'avez exécutez ) , c'est de mettre à jour les pilotes :

www.touslesdrivers.com...
Edité le 01/06/2012 à 21:37
 
 
     
6 messages
Filtrer ok
Vous devez être connecté pour écrire un message !

BE GEEK ! Avec Clubic Logo

flechePublicité