[Résolu] BSOD

[Untenshu]

Après plusieurs vérification avec Memtest , chkdsk et sfc ,Réinstallation avec le DVD et ensuite.
j'ai le code : 0X80070241 qui est découvert , malheureusement pour moi je ne sais plus quoi faire ?
A votre bon coeur les spécialistes.Par avance , Merci aux bonnes idées.
Cordialement.

[EinsteinZero]

Salut

malgré le BSOD le PC démarre-t-il ? le BSOD a-t-il lui alors que windows (quelle version) fonctionne ?

[Untenshu]

Bonjour.
lorsque j'ai l'écran bleu , normalement, mon ordinateur redémarrait mais ces derniers temps il me fallait rester appuyer sur le bouton "power" afin de l'éteindre et de le rallumer. Je suis sous Windows 7 familiale.
Merci pour les idées qui pourront être suggérées.
Cordialement.

[Untenshu]

j'ai oublié de marqué en 64 bits !
mille excuses !

[EinsteinZero]

Bonsoir

plutôt que de poster une suite, utilise le bouton "EDITER" pour modifier/compléter ton message précédent

sinon, comme tu as accès à windows, télécharge Whocrashed >>ici (external mirror 1)<<

lance le logiciel et poste son rapport (par un copier/coller)

[RobinSG]

Bonjour EZ.
Voici le rapport demandé :

Code: Tout sélectionner

System Information (local)
--------------------------------------------------------------------------------

computer name: GILLES-PC
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
CPU: AuthenticAMD AMD Phenom(tm) II X4 955 Processor AMD586, level: 16
4 logical processors, active mask: 15
RAM: 4292403200 total
VM: 2147352576, free: 1968312320



--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.


On Mon 27/02/2012 08:16:03 GMT your computer crashed
crash dump file: C:\Windows\Minidump\022712-28314-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x864A9)
Bugcheck code: 0x24 (0x1904FB, 0xFFFFF88009E931B8, 0xFFFFF88009E92A10, 0xFFFFF8800127A8E4)
Error: NTFS_FILE_SYSTEM
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates a problem occurred in the NTFS file system.
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 27/02/2012 08:16:03 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeRemoveQueueEx+0x1839)
Bugcheck code: 0x24 (0x1904FB, 0xFFFFF88009E931B8, 0xFFFFF88009E92A10, 0xFFFFF8800127A8E4)
Error: NTFS_FILE_SYSTEM
Bug check description: This indicates a problem occurred in the NTFS file system.
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 26/02/2012 19:04:50 GMT your computer crashed
crash dump file: C:\Windows\Minidump\022612-31917-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF800036C3B65, 0xFFFFF8800B654890, 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 Fri 17/02/2012 17:04:16 GMT your computer crashed
crash dump file: C:\Windows\Minidump\021712-28376-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x864A9)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF800036C5B65, 0xFFFFF8800B831890, 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 Thu 16/02/2012 14:15:11 GMT your computer crashed
crash dump file: C:\Windows\Minidump\021612-25084-01.dmp
This was probably caused by the following module: tdrpman.sys (tdrpman+0x20462)
Bugcheck code: 0x24 (0x1904FB, 0xFFFFF8800A706D38, 0xFFFFF8800A706590, 0xFFFFF800037CA617)
Error: NTFS_FILE_SYSTEM
file path: C:\Windows\system32\drivers\tdrpman.sys
product: Acronis Try&Decide and Restore Points
company: Acronis
description: Acronis Try&Decide and Restore Points Volume Filter Driver
Bug check description: This indicates a problem occurred in the NTFS file system.
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: tdrpman.sys (Acronis Try&Decide and Restore Points Volume Filter Driver, Acronis).
Google query: tdrpman.sys Acronis NTFS_FILE_SYSTEM




On Sun 12/02/2012 11:41:18 GMT your computer crashed
crash dump file: C:\Windows\Minidump\021212-26020-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0xC2 (0x7, 0x109B, 0x41031402, 0xFFFFF8A010C8E541)
Error: BAD_POOL_CALLER
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 current thread is making a bad pool request.
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 Fri 10/02/2012 14:50:19 GMT your computer crashed
crash dump file: C:\Windows\Minidump\021012-24242-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x864A9)
Bugcheck code: 0x50 (0xFFFFF8A01B50B684, 0x1, 0xFFFFF880012A7665, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
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 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 the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.



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

7 crash dumps have been found and analyzed. A third party driver has been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers:

tdrpman.sys (Acronis Try&Decide and Restore Points Volume Filter Driver, Acronis)

If no updates for these drivers are available, try searching with Google on the names of these drivers in combination the errors that have been reported for these drivers and include the brand and model name of your computer as well in the query. This often yields interesting results from discussions from users who have been experiencing similar problems.


Read the topic general suggestions for troubleshooting system crashes for more information.

Note that it's not always possible to state with certainty whether a reported driver is actually 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.

Je remarque , d'après ce que j'ai réussi à traduire , qu'il s'agit de problèmes causés par les drivers ...
J'avais essayé de réinstaller le système mais une erreur 0X80070241 m'a été signalée.
Cordialement.

[EinsteinZero]

Bonjour

le problème semble tourner autour du disque dur , un logiciel Acronis étant mis régulièrement en cause...

peut-être est t-il fautif...il serait alors judicieux de le désinstaller pour voir

si le pb persiste, c'est plus ennuyeux car le disque dur est peut-être en cause, il faudrait alors le tester

[Untenshu]

Bonjour EZ.
Ouf , ce n'est pas aussi grave que ça car j'ai commandé un SSD hier. J' avais de gros doutes quand à mon disque dur mais lors de la réception de mon SSD je testerais l'autre ( celui qui contient mon OS ) . Y-a-t'il un logiciel qui pourrait le faire correctement ?
Cordialement.
PS : J'ai désinstallé Acronis Drive Monitor , je verrais ce que ça donne par la suite.

[EinsteinZero]

Bonsoir

Y-a-t'il un logiciel qui pourrait le faire correctement ?
..........
PS : J'ai désinstallé Acronis Drive Monitor ......

je pensais justement à "Acronis Drive Monitor".....je crois qu'on va éviter

sinon il y a >>CrystalDiskInfo Portable<<

au-moins celui là il ne mettra pas dans le système son petit pilote à lui

[Untenshu]

Bonjour EZ.
J'ai lancé le programme de vérification du disque et tout semble OK . Je verrais lorsque je recevrais mon SSD si le problème continue ou recommence. J'en profiterais pour installer Windows 7 Pro que j'ai, à la place du familiale.
Je crois que je vais pouvoir mettre en "résolu".Enfin je l'espère !
Cordialement et Merci encore EZ .

[EinsteinZero]

Bonjour

on va attendre le SSD pour mettre en réglé..au cas ou

[Untenshu]

Bonjour EZ;
Une question me taraude l'esprit : doit-on formater un SSD avant d'installer un OS ?
Cordialement.

[EinsteinZero]

Le DVD d'installation s'en chargera si nécessaire car un SSD c'est un disque "comme un autre" les seuls soucis sont généralement quand le Bios le gère mal (ça arrive parfois hélas )

[Untenshu]

Bonjour EZ.
Et voici de nouveau un BSOD , obligé de relancer la bécane par un " reset ", je te met le rapport .Peut-être y verras tu un " quelconque " changement ?

Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.


On Wed 29/02/2012 15:08:25 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: Unknown (0x7FEF67A6DB5)
Bugcheck code: 0x1A (0x41284, 0x25EA001, 0x0, 0xFFFFF70001080000)
Error: MEMORY_MANAGEMENT
Bug check description: This indicates that a severe memory management error occurred.
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.
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: Unknown .
Google query: Unknown MEMORY_MANAGEMENT




On Mon 27/02/2012 08:16:03 GMT your computer crashed
crash dump file: C:\Windows\Minidump\022712-28314-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x864A9)
Bugcheck code: 0x24 (0x1904FB, 0xFFFFF88009E931B8, 0xFFFFF88009E92A10, 0xFFFFF8800127A8E4)
Error: NTFS_FILE_SYSTEM
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates a problem occurred in the NTFS file system.
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 26/02/2012 19:04:50 GMT your computer crashed
crash dump file: C:\Windows\Minidump\022612-31917-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF800036C3B65, 0xFFFFF8800B654890, 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 Fri 17/02/2012 17:04:16 GMT your computer crashed
crash dump file: C:\Windows\Minidump\021712-28376-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x864A9)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF800036C5B65, 0xFFFFF8800B831890, 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 Thu 16/02/2012 14:15:11 GMT your computer crashed
crash dump file: C:\Windows\Minidump\021612-25084-01.dmp
This was probably caused by the following module: tdrpman.sys (tdrpman+0x20462)
Bugcheck code: 0x24 (0x1904FB, 0xFFFFF8800A706D38, 0xFFFFF8800A706590, 0xFFFFF800037CA617)
Error: NTFS_FILE_SYSTEM
file path: C:\Windows\system32\drivers\tdrpman.sys
product: Acronis Try&Decide and Restore Points
company: Acronis
description: Acronis Try&Decide and Restore Points Volume Filter Driver
Bug check description: This indicates a problem occurred in the NTFS file system.
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: tdrpman.sys (Acronis Try&Decide and Restore Points Volume Filter Driver, Acronis).
Google query: tdrpman.sys Acronis NTFS_FILE_SYSTEM




On Sun 12/02/2012 11:41:18 GMT your computer crashed
crash dump file: C:\Windows\Minidump\021212-26020-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0xC2 (0x7, 0x109B, 0x41031402, 0xFFFFF8A010C8E541)
Error: BAD_POOL_CALLER
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 current thread is making a bad pool request.
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 Fri 10/02/2012 14:50:19 GMT your computer crashed
crash dump file: C:\Windows\Minidump\021012-24242-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x864A9)
Bugcheck code: 0x50 (0xFFFFF8A01B50B684, 0x1, 0xFFFFF880012A7665, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
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 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 the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.



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

7 crash dumps have been found and analyzed. 2 third party drivers have been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers:

tdrpman.sys (Acronis Try&Decide and Restore Points Volume Filter Driver, Acronis)

unknown

If no updates for these drivers are available, try searching with Google on the names of these drivers in combination the errors that have been reported for these drivers and include the brand and model name of your computer as well in the query. This often yields interesting results from discussions from users who have been experiencing similar problems.


Read the topic general suggestions for troubleshooting system crashes for more information.

Note that it's not always possible to state with certainty whether a reported driver is actually 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.

J'ai remarqué qu'il y avait encore cet " acronis" mais dans une sauvegarde , que j'ai supprimé depuis.
Cordialement.

[EinsteinZero]

Bonsoir

il est normal qu'Acronis soit toujours présent car le logiciel ressort tous les rapports seul le premier est intéressant...

il fait état d'un plantage du a une corruption de la mémoire...

il y a donc soit un pb de pilote soit un pb avec une barrette de Ram