Bonjour, tout d'abord merci d'avoir répondu.
Pour le PC j'ai essayé de le remettre au format sortie d'usine et depuis les seuls programmes installés sont google chrome, ma congig.com et who crashed.
Hier j'ai télécharger tous ce que je trouvais sur packard bell pour mettre à jour les pilotes mais je me rends compte que pour certain pilote je suis revenu en arriere par rapport à ce que j'avais installé par tous les drivers.com
J'avais déjà vu pour IEEE1394 sur le support microsoft mais je vais le refaire vu qu'avec les restaurations d'hier je ne sais plus si je l'ai fait avant ou après
J'ai déjà essayé de le demonter et j'ai depoussiéré les ventilo d'ailleurs ils semblent fonctionner vu le bruit de soufflerie quand l'ordi refuse de faire autre chose que de ventiler!!
A savoir que tous ces bugs ont commencé il y a qq mois quand j'ai réussi à remettre internet sur l'ordi chose qu'il n'avait pas eu depuis 2011
Aujourd'hui après plusieurs écran bleus et tentative infructueuse de redemarrer l'ordi j'ai enfin réussi à l'allumer pour lancer whocrashed
Voici d'ailleurs l'analyse de whocrashed si ça permet de pouvoir m'aider:
System Information (local)
computer name: SEPT2009
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
Hardware: imedia S1710, Packard Bell, MCP73T-AD
CPU: GenuineIntel Pentium(R) Dual-Core CPU E5200 @ 2.50GHz Intel586, level: 6
2 logical processors, active mask: 3
RAM: 4294168576 total
VM: 2147352576, free: 1919971328
*** * Crash Dump Analysis*
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Mon 05/05/2014 18:15:31 GMT your computer crashed
crash dump file: C:\Windows\Minidump\050514-23431-01.dmp
This was probably caused by the following module:
ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x44 (0xFFFFFA800482DBE0, 0xEAC, 0x0, 0x0)
Error: MULTIPLE_IRP_COMPLETE_REQUESTS
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 driver has tried to requested an IRP be completed that is already complete.
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 Mon 05/05/2014 18:15:31 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module:
classpnp.sys (CLASSPNP+0x1BCE)
Bugcheck code: 0x44 (0xFFFFFA800482DBE0, 0xEAC, 0x0, 0x0)
Error: MULTIPLE_IRP_COMPLETE_REQUESTS
file path: C:\Windows\system32\drivers\classpnp.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: SCSI Class System Dll
Bug check description: This indicates that a driver has tried to requested an IRP be completed that is already complete.
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 05/05/2014 17:38:13 GMT your computer crashed
crash dump file: C:\Windows\Minidump\050514-22542-01.dmp
This was probably caused by the following module:
ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x19 (0x20, 0xFFFFFA80064B6500, 0xFFFFFA80064B6570, 0x4070005)
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.
On Mon 21/04/2014 14:32:46 GMT your computer crashed
crash dump file: C:\Windows\Minidump\042114-22479-01.dmp
This was probably caused by the following module:
ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0xA (0xFFFFFA7FFFFFD600, 0x2, 0x1, 0xFFFFF800030914EC)
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 that cannot be identified at this time.
On Tue 15/04/2014 11:55:02 GMT your computer crashed
crash dump file: C:\Windows\Minidump\041514-32651-01.dmp
This was probably caused by the following module:
ntoskrnl.exe (nt+0x6F880)
Bugcheck code: 0x1A (0x5001, 0xFFFFF70001080000, 0xB0B, 0x7EFAF009)
Error: MEMORY_MANAGEMENT
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 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.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
Avec toute ma sympathie pour l'aider apportée