Aller au contenu

Le petit malch'

Membres
  • Compteur de contenus

    6
  • Inscription

  • Dernière visite

À propos de Le petit malch'

  • Date de naissance 25/08/1993

Profile Information

  • Sexe
    Male

Autres informations

  • Mes langues
    francais,anglais et espagnol

Le petit malch''s Achievements

Junior Member

Junior Member (3/12)

0

Réputation sur la communauté

  1. Bon désolé de l'attente mais je n'ai pu venir avant. Semblerait-il que ce soit tout bon ... je n'ai pas mis a jour les drivers... Donc je ne sais pas trop... J'ai vidé tout les caches ect... avec CCLEANER et aprés cela n'a plus sauté . Donc merci a vous de l'aide apporter .
  2. D'accord je vais donc faire cela . Voici un petit apercu du site DriverAgent par rapport a mes drivers: Je vais faire un tour demain driver par driver dés que je me réveille et je vous dirais cela .
  3. Je m'excuse du temps de mes réponses je rencontre quelque soucis niveau de la connexion . Donc ce serait un problème de Mise a jour de mes drivers si j'ai bien compris. Pouriez vous s'il vous plait me procurer un site , sur lequel je pourrais voir mes drivers et leur mise a jour a fournir, merci d'avance .
  4. Tonton je viens de regarder dans gestionnaires de périphériques et non je n'ai pas des "?" ou des "!" .
  5. Alors alors j'ai instalé whoCrashed et en voici le résultat : System Information (local) -------------------------------------------------------------------------------- computer name: CALVIN-PC windows version: Windows 7 Service Pack 1, 6.1, build: 7601 windows dir: C:\Windows CPU: GenuineIntel Pentium® Dual-Core CPU T4300 @ 2.10GHz Intel586, level: 6 2 logical processors, active mask: 3 RAM: 4220420096 total VM: 2147352576, free: 1913446400 -------------------------------------------------------------------------------- Crash Dump Analysis -------------------------------------------------------------------------------- Crash dump directory: C:\Windows\Minidump Crash dumps are enabled on your computer. On Fri 28/10/2011 13:27:17 GMT your computer crashed crash dump file: C:\Windows\Minidump\102811-31761-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40) Bugcheck code: 0x76 (0x0, 0xFFFFFA8006EDC060, 0x33, 0x0) Error: PROCESS_HAS_LOCKED_PAGES 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 a driver failed to release locked pages after an I/O operation, or that it attempted to unlock pages that were already unlocked. 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 28/10/2011 13:27:17 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: 0x76 (0x0, 0xFFFFFA8006EDC060, 0x33, 0x0) Error: PROCESS_HAS_LOCKED_PAGES Bug check description: This bug check indicates that a driver failed to release locked pages after an I/O operation, or that it attempted to unlock pages that were already unlocked. 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 27/10/2011 19:52:20 GMT your computer crashed crash dump file: C:\Windows\Minidump\102711-25116-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40) Bugcheck code: 0x76 (0x0, 0xFFFFFA800736D060, 0x33, 0x0) Error: PROCESS_HAS_LOCKED_PAGES 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 a driver failed to release locked pages after an I/O operation, or that it attempted to unlock pages that were already unlocked. 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 27/10/2011 19:05:15 GMT your computer crashed crash dump file: C:\Windows\Minidump\102711-26364-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40) Bugcheck code: 0x76 (0x0, 0xFFFFFA80070D0060, 0x33, 0x0) Error: PROCESS_HAS_LOCKED_PAGES 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 a driver failed to release locked pages after an I/O operation, or that it attempted to unlock pages that were already unlocked. 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 27/10/2011 15:25:11 GMT your computer crashed crash dump file: C:\Windows\Minidump\102711-32682-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40) Bugcheck code: 0x76 (0x0, 0xFFFFFA80070AD740, 0x33, 0x0) Error: PROCESS_HAS_LOCKED_PAGES 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 a driver failed to release locked pages after an I/O operation, or that it attempted to unlock pages that were already unlocked. 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 27/10/2011 14:30:10 GMT your computer crashed crash dump file: C:\Windows\Minidump\102711-33602-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40) Bugcheck code: 0x76 (0x0, 0xFFFFFA8006ED6230, 0x33, 0x0) Error: PROCESS_HAS_LOCKED_PAGES 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 a driver failed to release locked pages after an I/O operation, or that it attempted to unlock pages that were already unlocked. The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time. On Tue 04/10/2011 23:28:39 GMT your computer crashed crash dump file: C:\Windows\Minidump\100511-25334-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x705C0) Bugcheck code: 0x76 (0x0, 0xFFFFFA8006F25710, 0x33, 0x0) Error: PROCESS_HAS_LOCKED_PAGES 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 a driver failed to release locked pages after an I/O operation, or that it attempted to unlock pages that were already unlocked. 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 04/09/2011 00:05:14 GMT your computer crashed crash dump file: C:\Windows\Minidump\090411-19936-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x705C0) Bugcheck code: 0x76 (0x0, 0xFFFFFA8006EA85F0, 0x33, 0x0) Error: PROCESS_HAS_LOCKED_PAGES 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 a driver failed to release locked pages after an I/O operation, or that it attempted to unlock pages that were already unlocked. The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time. -------------------------------------------------------------------------------- Conclusion -------------------------------------------------------------------------------- 8 crash dumps have been found and analyzed. 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. Merci de l'aide apporté .
  6. Bonjour à tous je vous explique mon problème ... J'allume l'ordinateur normalement sans soucis, puis je fais ce que je veux pendant environ 30 voir 45 minutes puis il me met un écran bleu ... voici le code d'erreur : " Signature du problème : Nom d’événement de problème: BlueScreen Version du système: 6.1.7601.2.1.0.768.3 Identificateur de paramètres régionaux: 1036 Informations supplémentaires sur le problème : BCCode: 76 BCP1: 0000000000000000 BCP2: FFFFFA8006EDC060 BCP3: 0000000000000033 BCP4: 0000000000000000 OS Version: 6_1_7601 Service Pack: 1_0 Product: 768_1 " Ma cofig étant : Acer Aspire 7736Z-434G32Mn Si vous connaisez la solution du problème je serais ravis de la connaitre merci d'avance pour avoir pris la peine de lire mon post. Malcha =).
×
×
  • Créer...