Forum-seven : Communauté francaise de Windows 7

Je ne connais pas ce logiciel.
Je vais l'essayer.

Merci

Ce logiciel analyse le contenu de C:/Windows/minidump et vous donne la ou les raisons des écrans bleus obtenus et à partir de là il est possible de prendre une décision afin de solutionner le pb.
Si tu as besoin d'autres infos concernant ce logiciel ....

Bonjour
Un petit retour en arrière :

14niepce a écrit :Je ne comprends pas comment une barrette peut fonctionner correctement sous XP et présenter des problèmes avec Win 7.

Simplement parce que XP et Seven ne gèrent pas la mémoire de la même manière et que Seven a une empreinte mémoire plus grosse que XP => il est envisageable que XP n'arrive pas jusqu'à la zone défectueuse alors qu Seven oui.
Un peu comme avec un seau percé : tant que le niveau de l'eau n'arive pas au trou, il ne coule pas !

Bonjour,

Le PC est stable depuis plus de 24h !

Juste après la désactivation de la gestion de la mémoire virtuelle, j’ai également (re)désinstallé les pilotes de l’imprimante. J'avais lu sur un forum que supprimer l'imprimante en "périphériques et imprimantes" n'est toujours pas suffisant et qu'il faut "aller en profondeur".
Via les menus/onglets il faut atteindre la fenêtre du pilote concerné et le supprimer :
-> Panneau de configuration
--> Matériel et audio
---> Périphériques et imprimantes
----> Propriétés du serveur d'impression
-----> Pilotes
Pour enfin de supprimer le pilote concerné (HP 3600 utilisé comme substitut pour une imprimante HP 3420).

Par curiosité, voici un nouveau sfc /scannow. Ces lignes s'ajoutent aux précédentes:

2010-03-25 15:00:31, Info CSI 00000114 [SR] Cannot repair member file [l:34{17}]"TS_OutOfToner.ps1" of Microsoft-Windows-PrinterDiagnostic, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, file is missing

2010-03-25 15:00:32, Info CSI 00000115 [SR] Cannot repair member file [l:34{17}]"TS_OutOfToner.ps1" of Microsoft-Windows-PrinterDiagnostic, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, file is missing

2010-03-25 15:01:04, Info CSI 0000013e [SR] Cannot repair member file [l:18{9}]"spnet.dll" of Microsoft-Windows-Sysprep-SpNet, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, file is missing

2010-03-25 15:01:07, Info CSI 0000013f [SR] Cannot repair member file [l:18{9}]"spnet.dll" of Microsoft-Windows-Sysprep-SpNet, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, file is missing

2010-03-25 15:02:08, Info CSI 00000188 [SR] Cannot repair member file [l:34{17}]"I386\KYCS3225.PPD" of prnky002.inf, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type = [l:24{12}]"driverUpdate", TypeName neutral, PublicKey neutral in the store, hash mismatch

2010-03-25 15:02:08, Info CSI 0000018a [SR] Cannot repair member file [l:34{17}]"I386\KYCS3225.PPD" of prnky002.inf, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type = [l:24{12}]"driverUpdate", TypeName neutral, PublicKey neutral in the store, hash mismatch

2010-03-25 15:02:23, Info CSI 000001ac [SR] Cannot repair member file [l:34{17}]"TS_OutOfToner.ps1" of Microsoft-Windows-PrinterDiagnostic, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, file is missing

2010-03-25 15:02:23, Info CSI 000001ad [SR] Cannot repair member file [l:18{9}]"spnet.dll" of Microsoft-Windows-Sysprep-SpNet, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, file is missing

2010-03-25 15:02:23, Info CSI 000001af [SR] Cannot repair member file [l:34{17}]"I386\KYCS3225.PPD" of prnky002.inf, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type = [l:24{12}]"driverUpdate", TypeName neutral, PublicKey neutral in the store, hash mismatch

2010-03-25 15:02:23, Info CSI 000001b0 [SR] Cannot repair member file [l:18{9}]"spnet.dll" of Microsoft-Windows-Sysprep-SpNet, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, file is missing

2010-03-25 15:02:23, Info CSI 000001b2 [SR] Cannot repair member file [l:34{17}]"TS_OutOfToner.ps1" of Microsoft-Windows-PrinterDiagnostic, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, file is missing

2010-03-25 15:02:23, Info CSI 000001b5 [SR] Cannot repair member file [l:34{17}]"I386\KYCS3225.PPD" of prnky002.inf, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type = [l:24{12}]"driverUpdate", TypeName neutral, PublicKey neutral in the store, hash mismatch


Maintenant je vais réactiver la gestion de la mémoire virtuelle et espérer que le problème venait du pilote de l’imprimante.

@+

Bonjour,

Tu sais un rapport de fichiers système non réparés n'est pas très significatif pour des écrans bleus.
Un rapport Whocrashed serait plus explicite.
Les fichiers système corrompus provoquent surtout des dysfonctionnements dans Windows ou dans des applications.

Les écrans bleus sont en général la conséquence soit d'une incompatibilité matérielle (y compris la mémoire), soit d'une incompatibilité logicielle (y compris les pilotes), soit un mauvais réglage dans le Bios.

@+

Dans ce cas, voici le résultat de mon WhoCrashed :

Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.


On Wed 24/03/2010 11:20:10 your computer crashed
This was likely caused by the following module: ntkrnlpa.exe
Bugcheck code: 0x1A (0x41790, 0xC08020D8, 0xFFFF, 0x0)
Error: MEMORY_MANAGEMENT
Dump file: C:\Windows\Minidump\032410-12745-01.dmp
file path: C:\Windows\system32\ntkrnlpa.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



On Wed 24/03/2010 09:47:24 your computer crashed
This was likely caused by the following module: ntkrnlpa.exe
Bugcheck code: 0x1A (0x41790, 0xC0802754, 0xFFFF, 0x0)
Error: MEMORY_MANAGEMENT
Dump file: C:\Windows\Minidump\032410-12589-01.dmp
file path: C:\Windows\system32\ntkrnlpa.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



On Wed 24/03/2010 09:46:02 your computer crashed
This was likely caused by the following module: ntkrnlpa.exe
Bugcheck code: 0x19 (0x3, 0x855EB530, 0x855EB530, 0x2000A8C0)
Error: BAD_POOL_HEADER
Dump file: C:\Windows\Minidump\032410-10140-01.dmp
file path: C:\Windows\system32\ntkrnlpa.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



On Wed 24/03/2010 09:36:30 your computer crashed
This was likely caused by the following module: fileinfo.sys
Bugcheck code: 0x19 (0x20, 0xA826FAB8, 0xA826FAF0, 0xA070205)
Error: BAD_POOL_HEADER
Dump file: C:\Windows\Minidump\032410-11310-01.dmp
file path: C:\Windows\system32\drivers\fileinfo.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: FileInfo Filter Driver
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



On Wed 24/03/2010 09:34:29 your computer crashed
This was likely caused by the following module: ntkrnlpa.exe
Bugcheck code: 0xA (0x14, 0x2, 0x0, 0x82AA16D1)
Error: IRQL_NOT_LESS_OR_EQUAL
Dump file: C:\Windows\Minidump\032410-10358-01.dmp
file path: C:\Windows\system32\ntkrnlpa.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



On Wed 24/03/2010 09:30:44 your computer crashed
This was likely caused by the following module: nvlddmkm.sys
Bugcheck code: 0x19 (0x3, 0x82B6EB20, 0x82F6EB20, 0x82B6EB20)
Error: BAD_POOL_HEADER
Dump file: C:\Windows\Minidump\032410-10233-01.dmp
file path: C:\Windows\system32\drivers\nvlddmkm.sys
product: NVIDIA Windows Kernel Mode Driver, Version 196.21
company: NVIDIA Corporation
description: NVIDIA Windows Kernel Mode Driver, Version 196.21



On Wed 24/03/2010 09:08:43 your computer crashed
This was likely caused by the following module: ntfs.sys
Bugcheck code: 0x24 (0x1904FB, 0xA5017A2C, 0xA5017610, 0x82A87523)
Error: NTFS_FILE_SYSTEM
Dump file: C:\Windows\Minidump\032410-18283-01.dmp
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
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



On Wed 24/03/2010 01:45:04 your computer crashed
This was likely caused by the following module: http.sys
Bugcheck code: 0x50 (0xBFECBFFC, 0x1, 0x93C8791D, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
Dump file: C:\Windows\Minidump\032410-10498-01.dmp
file path: C:\Windows\system32\drivers\http.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: HTTP Pile du protocole
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



On Wed 24/03/2010 01:39:31 your computer crashed
This was likely caused by the following module: ntkrnlpa.exe
Bugcheck code: 0xA (0x14, 0x2, 0x0, 0x82AD46D1)
Error: IRQL_NOT_LESS_OR_EQUAL
Dump file: C:\Windows\Minidump\032410-11325-01.dmp
file path: C:\Windows\system32\ntkrnlpa.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



On Tue 23/03/2010 10:33:28 your computer crashed
This was likely caused by the following module: ntkrnlpa.exe
Bugcheck code: 0x1A (0x31, 0x873B1578, 0xA0192000, 0xA17F792A)
Error: MEMORY_MANAGEMENT
Dump file: C:\Windows\Minidump\032310-10608-01.dmp
file path: C:\Windows\system32\ntkrnlpa.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



On Tue 23/03/2010 10:31:34 your computer crashed
This was likely caused by the following module: ntkrnlpa.exe
Bugcheck code: 0x1A (0x41790, 0xC0802070, 0xFFFF, 0x0)
Error: MEMORY_MANAGEMENT
Dump file: C:\Windows\Minidump\032310-10249-01.dmp
file path: C:\Windows\system32\ntkrnlpa.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



On Tue 23/03/2010 10:30:22 your computer crashed
This was likely caused by the following module: ntkrnlpa.exe
Bugcheck code: 0x1A (0x31, 0x867FBE20, 0x9FD9D000, 0xAD76AA8A)
Error: MEMORY_MANAGEMENT
Dump file: C:\Windows\Minidump\032310-10046-01.dmp
file path: C:\Windows\system32\ntkrnlpa.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



On Tue 23/03/2010 10:23:48 your computer crashed
This was likely caused by the following module: ntfs.sys
Bugcheck code: 0x24 (0x1904FB, 0x807FA71C, 0x807FA300, 0x82AC3182)
Error: NTFS_FILE_SYSTEM
Dump file: C:\Windows\Minidump\032310-9484-01.dmp
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
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



On Tue 23/03/2010 10:15:41 your computer crashed
This was likely caused by the following module: ntkrnlpa.exe
Bugcheck code: 0x1A (0x5003, 0xC0802000, 0x3EC3, 0x3FC5F86)
Error: MEMORY_MANAGEMENT
Dump file: C:\Windows\Minidump\032310-11122-01.dmp
file path: C:\Windows\system32\ntkrnlpa.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



On Tue 23/03/2010 09:12:39 your computer crashed
This was likely caused by the following module: ntkrnlpa.exe
Bugcheck code: 0x1A (0x3452, 0x22C4000, 0xC080493C, 0x0)
Error: MEMORY_MANAGEMENT
Dump file: C:\Windows\Minidump\032310-9906-01.dmp
file path: C:\Windows\system32\ntkrnlpa.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



On Tue 23/03/2010 08:28:33 your computer crashed
This was likely caused by the following module: tcpip.sys
Bugcheck code: 0xD1 (0x18, 0x2, 0x0, 0x8B46B9B6)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
Dump file: C:\Windows\Minidump\032310-9843-01.dmp
file path: C:\Windows\system32\drivers\tcpip.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote TCP/IP
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



On Tue 23/03/2010 08:20:31 your computer crashed
This was likely caused by the following module: luafv.sys
Bugcheck code: 0x1000008E (0xC0000006, 0x96FBB1F1, 0x96CBA5F4, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
Dump file: C:\Windows\Minidump\032310-9266-01.dmp
file path: C:\Windows\system32\drivers\luafv.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote de filtre de virtualisation de fichier LUA
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



On Tue 23/03/2010 07:40:11 your computer crashed
This was likely caused by the following module: ntkrnlpa.exe
Bugcheck code: 0x1A (0x41790, 0xC080205A, 0xFFFF, 0x0)
Error: MEMORY_MANAGEMENT
Dump file: C:\Windows\Minidump\032310-17362-01.dmp
file path: C:\Windows\system32\ntkrnlpa.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



On Tue 23/03/2010 02:51:23 your computer crashed
This was likely caused by the following module: ntkrnlpa.exe
Bugcheck code: 0x50 (0xAD2B40FC, 0x0, 0x82ADA8FA, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
Dump file: C:\Windows\Minidump\032310-13228-01.dmp
file path: C:\Windows\system32\ntkrnlpa.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



On Tue 23/03/2010 01:18:22 your computer crashed
This was likely caused by the following module: ntkrnlpa.exe
Bugcheck code: 0xA (0x14, 0x2, 0x0, 0x82ACB6D1)
Error: IRQL_NOT_LESS_OR_EQUAL
Dump file: C:\Windows\Minidump\032310-10015-01.dmp
file path: C:\Windows\system32\ntkrnlpa.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



On Tue 23/03/2010 01:07:59 your computer crashed
This was likely caused by the following module: ntkrnlpa.exe
Bugcheck code: 0x1000008E (0xC0000005, 0x82A88621, 0x81F43B0C, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
Dump file: C:\Windows\Minidump\032310-18314-01.dmp
file path: C:\Windows\system32\ntkrnlpa.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



On Tue 23/03/2010 01:06:20 your computer crashed
This was likely caused by the following module: bdfsfltr.sys
Bugcheck code: 0xA (0x37, 0x2, 0x1, 0x82A7B108)
Error: IRQL_NOT_LESS_OR_EQUAL
Dump file: C:\Windows\Minidump\032310-10186-01.dmp



On Tue 23/03/2010 00:01:21 your computer crashed
This was likely caused by the following module: trufos.sys
Bugcheck code: 0x1000008E (0xC000001D, 0xB38C87A6, 0x8D19376C, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
Dump file: C:\Windows\Minidump\032310-10530-01.dmp



On Mon 22/03/2010 03:53:42 your computer crashed
This was likely caused by the following module: ntkrnlpa.exe
Bugcheck code: 0x19 (0x3, 0xAAD69810, 0x0, 0xAAD69810)
Error: BAD_POOL_HEADER
Dump file: C:\Windows\Minidump\032210-18579-01.dmp
file path: C:\Windows\system32\ntkrnlpa.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



On Sun 21/03/2010 01:01:57 your computer crashed
This was likely caused by the following module: fileinfo.sys
Bugcheck code: 0x1000008E (0xC0000005, 0x8ADC09EF, 0xB0B456BC, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
Dump file: C:\Windows\Minidump\032110-10795-01.dmp
file path: C:\Windows\system32\drivers\fileinfo.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: FileInfo Filter Driver
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



On Sat 20/03/2010 15:45:11 your computer crashed
This was likely caused by the following module: ntkrnlpa.exe
Bugcheck code: 0x1A (0x41790, 0xC080276A, 0xFFFF, 0x0)
Error: MEMORY_MANAGEMENT
Dump file: C:\Windows\Minidump\032010-11419-01.dmp
file path: C:\Windows\system32\ntkrnlpa.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



On Thu 18/03/2010 19:15:48 your computer crashed
This was likely caused by the following module: ntfs.sys
Bugcheck code: 0x24 (0x1904FB, 0xAF45587C, 0xAF455460, 0x8B09B957)
Error: NTFS_FILE_SYSTEM
Dump file: C:\Windows\Minidump\031810-10545-01.dmp
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
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



On Wed 17/03/2010 17:56:44 your computer crashed
This was likely caused by the following module: ntkrnlpa.exe
Bugcheck code: 0x1A (0x41790, 0xC08020D0, 0xFFFF, 0x0)
Error: MEMORY_MANAGEMENT
Dump file: C:\Windows\Minidump\031710-10358-01.dmp
file path: C:\Windows\system32\ntkrnlpa.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



On Wed 17/03/2010 17:43:37 your computer crashed
This was likely caused by the following module: ntkrnlpa.exe
Bugcheck code: 0x1A (0x41790, 0xC080204C, 0xFFFF, 0x0)
Error: MEMORY_MANAGEMENT
Dump file: C:\Windows\Minidump\031710-12292-01.dmp
file path: C:\Windows\system32\ntkrnlpa.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



On Tue 16/03/2010 00:12:08 your computer crashed
This was likely caused by the following module: trufos.sys
Bugcheck code: 0x19 (0x3, 0xB1550190, 0xB1550190, 0x0)
Error: BAD_POOL_HEADER
Dump file: C:\Windows\Minidump\031610-11200-01.dmp



On Mon 15/03/2010 02:10:39 your computer crashed
This was likely caused by the following module: bdfsfltr.sys
Bugcheck code: 0x19 (0x3, 0x8536A340, 0x0, 0x870E2D58)
Error: BAD_POOL_HEADER
Dump file: C:\Windows\Minidump\031510-9469-01.dmp



The following dump files were found but could not be read. These files may be corrupt:
C:\Windows\Minidump\032410-9469-01.dmp




--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------

32 crash dumps have been found on your computer. Only 31 could be analyzed. Note that it's not always possible to state with certainty whether a reported driver is really 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.

Bonjour,

Hé ! bien ! Perso, à ce stade là, je réinstalle vite fait bien fait

Si tu as overclocké dans le Bios, il faudrait remettre les paramètres par défaut.

Pour les 2 derniers :
Nom : MEMORY_MANAGEMENT
Code : 0x0000001A

Problème de gestion de mémoire ou problème matériel.
[1] Si vous venez d'installer un nouveau matériel, désinstallez-le.
[2] La mémoire vive est peut-être endommagée. Voyez si les barrettes sont bien clipsées sur la carte mère. Si c'est le cas, essayez de repérer une éventuelle barrette défectueuse. Retirez une barrette et redémarrez. Si l'erreur n'apparaît plus, remplacez la barrette extraite par une nouvelle.

Pour les autres :

Nom : BAD_POOL_HEADER
Code : 0x00000019

Si vous venez d'installer le Service Pack 2 de Windows XP, cette erreur peut avoir deux causes :
[1] Le service d'indexation. Cliquez sur Démarrer puis sur Exécuter et tapez msconfig. Dans l'onglet Services, décochez Service d'indexation. Validez et redémarrez Windows.
[2] Un fichier ou un dossier est endommagé. Ouvrez l'Explorateur Windows. Cliquez ensuite sur chaque dossier et sous-dossier. Si l'erreur survient à nouveau, vous saurez que le dossier endommagé est celui que vous venez d'activer. Redémarrez Windows et supprimez le dossier.

Sous Vista et Windows 7, le fichier fileinfo.sys concerne la fonction Superfetch
Le fichier nvlddmkm.sys concerne la carte graphique Nvidia

Nom : IRQL_NOT_LESS_OR_EQUAL
Code : 0x0000000A

[1]Un processus a tenté d'accéder à la mémoire paginée avec une priorité trop élevée. Cette erreur est souvent due à un pilote de périphérique qui utilise des adresses inexactes. Si le périphérique est mentionné, désinstallez-le puis réinstallez-le ou remplacez son pilote.
[2] Windows XP ou Vista - Si l'erreur survient pendant l'installation de Windows XP, c'est le signe qu'un composant matériel n'est pas reconnu par Windows XP.
[3] Windows XP ou Vista - Si l'erreur survient après l'installation de Windows XP, l'un des pilotes de périphérique n'est poeut-être pas compatible avec Windows XP.
[4] Windows XP ou Vista - Si l'erreur apparaît lors du changement rapide d'utilisateur sous Windows XP, le problème est dû au logiciel de gestion du clavier et au pilote fournis par Netropa.
[5] Windows XP ou Vista - Si l'erreur apparaît lorsque vous arrêtez l'ordinateur et que vous utilisez Easy CD Creator 5.0 ou Direct CD 5.0 de Roxio, téléchargez un emise à jour sur le site de l'éditeur du logiciel.

Le fichier ntkrnlpa.exe pour NT Kernel & System, donc un des éléments du noyau

Nom : NTFS_FILE_SYSTEM
Code : 0x00000024

Problème dans le gestionnaire de fichiers NTFS. Il est dû à un contrôleur IDE, un disque ou un câblage IDE défaillant.

Il serait judicieux de procéder à un scandisk avec réparation.
D'autant plus que le fichier ntfs.sys le confirme.

J'arrête là, car il y en a trop.
Ce PC va très mal !

@+

ok pour reinstaller windows.
Par contre il faut d'abord trouver le probleme pour ne le pas repeter.
Pour rappel, j'ai deja reinstallé windows debut fevrier et je n'ai pas envie de le refaire tous les 2 mois.

Bonjour,

Est-ce que les écrans bleus sont arrivés de suite après la ré-installation ou quelques temps après ? Cela pourrait être aussi un logiciel ou un driver totalement incompatible Windows 7.

Le Bios est bien en paramètre par défaut ?

Tu ne veux tester la mémoire pendant quelques jours ?
Une barrette après l'autre.

Tente aussi un double scandisk :

1) Ordinateur -> Clic-droit sur C -> Propriétés -> onglet Outils -> Vérifier maintenant -> coche la case " Réparer automatiquement les erreurs de système de fichiers -> tu réponds "oui" à la demande de planification -> tu redémarres le PC et tu laisses faire l'analyse, le PC redémarrera tout seul.

2) Ordinateur -> Clic-droit sur C -> Propriétés -> onglet Outils -> Vérifier maintenant -> coche la case " Rechercher et tenter une récupération des secteurs défectueux" -> tu réponds "oui" à la demande de planification -> tu redémarres le PC et tu laisses faire l'analyse, le PC redémarrera tout seul.

@+

Les écrans bleu apparaissent quelques semaines (entre 4 et 6) après l'installation et puis deviennent de plus en plus fréquentes, au point d'avoir 11 reboots en une seule matinée!

Concernant le scan disque il n'y a pas d'erreur. Particularité, le drive système (C:) est un disque un SSD (Kingston SSDNow V Series 64GB SATA).
Afin de mieux diagnostiquer le PC, veux-tu une liste plus détaillée des composants et périphériques?

Pour le Bios il n'est pas par defaut, car j'ai downclocked le processeur (intel Quad Core) de 2.3GHz vers 1.8GHz (ça chauffe moins, donc + silencieux).
Je l'ai fait y il a deux semaines. Outre le bruit, je pensais que le problème serait une surchauffe de la mémoire. J’avais tord.
Après cette étape j'ai tournée Cpu Stress MT pendant 8h sans problème.

Il n’a pas eu d’écran bleu depuis 48h. Pour le test scandisk j’étais obligé de reboot la machine, donc 48h sans panne et 1 reboot volontaire.
Ainsi, peut-on écarter le problème avec les barrettes ? Je peut également attendre 1 semaine avec PC allumé 24/24.

@+