Problèmes avec mon ordinateur

[Natindo]

Est-ce que le centre de maintenance te met un message d'erreur ?

[fmicablues7]

Non

C'est bizarre qu'il me note ça, alors que j'ai windows 7 64 bits...

[Inny]

Bonjour,

Va sur le site http://www.ma-config.com
Lance la détection, suis les instructions pour installer le plugin, relance la détection, puis va dans le menu de gauche, tout en bas : Analyse des BSOD. Ca te donnera plus de détails pour comprendre ce qui se passe lorsque ton ordi crashe.
Tiens-nous au courant.

[Shadaoe]

Juste une question vu que je n'ai jamais eu de système 64 bits encore : system32 (fait penser à 32 bits), est-ce normal dans un OS 64 bits ? Voilà question bête mais je peux juste pas vérifier.
(et comme fmicablues7 parle de

L'application C:\Windows\system32\ntoskrnl.exe ne peut être exécutée en mode Win32

ça m'intrigue.

[fmicablues7]

Voila mon analyse des BSOD

le fichier pdf en téléchargement reporte ceux-ci:

http://rapidshare.com/files/379922954/maconfig.pdf.html

[Shadaoe]

Euh ... une idée prends un screen plutôt (si tu vois pas pourquoi essaie ton lien ).

[fmicablues7]

J'ai utilisé le fichier pdf j'ai edité mon post précédent

[papill6n]

Je te recommande sinon l'excellent "WhoCrashed" => http://www.resplendence.com/downloads

Qui est un logiciel gratuit qui analyse tes écrans bleus (BSOD).
Et te dit direct quelle(s) logiciels/dlls/etc.. qui fais buguer ton pc

Moi j'en avais souvent et cela venait d'une dll de Nvidia >.<

[fmicablues7]

Analysis de Whocrashed
--------------------------------------------------------------------------------

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.


On Sun 25.04.2010 10:28:33 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8000297EA5F, 0xFFFFF88003845C70, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
Dump file: C:\Windows\Minidump\042510-21918-01.dmp
file path: C:\Windows\system32\ntoskrnl.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 25.04.2010 09:56:11 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x1A (0x41287, 0x41, 0x0, 0x0)
Error: MEMORY_MANAGEMENT
Dump file: C:\Windows\Minidump\042510-17830-01.dmp
file path: C:\Windows\system32\ntoskrnl.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 25.04.2010 09:18:00 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF800028C99E5, 0xFFFFF88005C07110, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
Dump file: C:\Windows\Minidump\042510-29312-01.dmp
file path: C:\Windows\system32\ntoskrnl.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 25.04.2010 09:10:50 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x50 (0xFFFFF80000001070, 0x0, 0xFFFFF8000287683A, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
Dump file: C:\Windows\Minidump\042510-26863-01.dmp
file path: C:\Windows\system32\ntoskrnl.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 25.04.2010 09:00:56 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF800029ED0BF, 0xFFFFF880031D9020, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
Dump file: C:\Windows\Minidump\042510-16988-01.dmp
file path: C:\Windows\system32\ntoskrnl.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 25.04.2010 08:57:31 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x50 (0xFFFFF8A009C6D550, 0x0, 0xFFFFF80002B7E927, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
Dump file: C:\Windows\Minidump\042510-19016-01.dmp
file path: C:\Windows\system32\ntoskrnl.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 25.04.2010 08:39:14 your computer crashed
This was likely caused by the following module: win32k.sys
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF960000F7354, 0xFFFFF88005E635D0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
Dump file: C:\Windows\Minidump\042510-27393-01.dmp
file path: C:\Windows\system32\win32k.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote Win32 multi-utilisateurs
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 25.04.2010 08:19:09 your computer crashed
This was likely caused by the following module: win32k.sys
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF96000054E5A, 0xFFFFF880024BFAE0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
Dump file: C:\Windows\Minidump\042510-26566-01.dmp
file path: C:\Windows\system32\win32k.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote Win32 multi-utilisateurs
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 24.04.2010 13:17:04 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80002B9B441, 0xFFFFF88002AA7130, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
Dump file: C:\Windows\Minidump\042410-16598-01.dmp
file path: C:\Windows\system32\ntoskrnl.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 Sat 24.04.2010 10:36:10 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF8800665B630, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
Dump file: C:\Windows\Minidump\042410-17316-01.dmp
file path: C:\Windows\system32\ntoskrnl.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 Sat 24.04.2010 08:08:59 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8000297DB07, 0xFFFFF88003874C70, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
Dump file: C:\Windows\Minidump\042410-18517-01.dmp
file path: C:\Windows\system32\ntoskrnl.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 Sat 24.04.2010 08:01:39 your computer crashed
This was likely caused by the following module: win32k.sys
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF960000D2AD3, 0xFFFFF880023E3090, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
Dump file: C:\Windows\Minidump\042410-26910-01.dmp
file path: C:\Windows\system32\win32k.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote Win32 multi-utilisateurs
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 24.04.2010 07:34:49 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0xC5 (0xA, 0x2, 0x1, 0xFFFFF800029AB90D)
Error: DRIVER_CORRUPTED_EXPOOL
Dump file: C:\Windows\Minidump\042410-15069-01.dmp
file path: C:\Windows\system32\ntoskrnl.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 Sat 24.04.2010 07:31:53 your computer crashed
This was likely caused by the following module: ntfs.sys
Bugcheck code: 0x24 (0x1904FB, 0xFFFFF880059D5AE8, 0xFFFFF880059D5340, 0xFFFFF8000289F99C)
Error: NTFS_FILE_SYSTEM
Dump file: C:\Windows\Minidump\042410-16489-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.



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




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

15 crash dumps have been found on your computer. Only 14 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.

[papill6n]

Après recherche quelques recherches, il apparaît que ces erreurs sont souvent causées par un problème de RAM.

Diverses solutions a testé (teste-les toutes ça ne coûte rien après tout et ne peux faire que du bien à ton PC ) :

1) Essaie de changer ta RAM de slot d'emplacement, dans ton boitier.

2) Test ta RAM de ton PC avec ce logiciel là => "Memetest86 +"
Si tu as une clef USB télécharges celui-là 'Download - Pre-Compiled EXE file for USB Key (Pure DOS)'
ou sinon tu peux graver directement le logiciel sur un CD-R(W) (regarde sur le site les options disponibles)

3) Contrôle complet antivirus + antispywares.
Contrôle antivirus avec Kaspersky si tu as (sinon un autre antivirus performant comme le gratuit "Avira Antivir".
Ensuite un contrôle antispywares avec "A-squared", et un deuxième contrôle avec l'incontournable "Spybot".
Bien sûr tous ces logiciels devront posséder leur dernière mise à jour niveau base de données

4)Un scan de l'intégrité de tes fichiers système windows, avec la commande sfc /scannow
- via le Menu démarrer => Accessoires => Invite de commandes et là tapes-y sfc /scannow
- ou via la commande 'Exécuter' du Menu démarrer (là où il y a Panneau de configuration) tapes-y sfc /scannow