Bij-B Publié le 9 août 2013 Signalement Share Publié le 9 août 2013 Bonjour ! Je viens sur ce forum suite à un problème très énervant de blue screen, en effet il m'arrive depuis 2 - 3 jours d'avoir des blue screen (qui surgissent à n'importe quel moment, au bout d'une heure ou au bout de 10 ...) J'ai récemment formaté mes disques dur puis ré installé windows il y a 4-5 jours (tout semblait bien se passer) Je me suis ensuite laissé séduire par l'achat de 3 composants à savoir :- ssd samsung 250 go (840 series) ----> en remplacement d'un hdd 250go- Ati Radeon 7870 2go (de marque His) ----> en remplacement d'une 4870 sapphire 1go- 2*4 Go de ddr3 cas 9 corsair vengeance LP 1333 ----> que j'ai d'abord ajouté a mes 2*2 go de samsung aussi en 1333 J'ai monté le tout dans le pc puis j'ai modifier l'ide en aihc pour mon nouveau ssd. J'ai jouer l'après midi et la soirée sur Test drive unlimited 2 et Battlefield 3 (rien d'anormal températures très correctes j'ai perdu 20° par rapport a mon ancienne carte graphique). Ce n'est que le lendemain que j'ai eu le premier bluescreen et depuis il s'en est produit une dizaines à intervalle très irrégulier. J'ai d'abord cru que c'était un problème de drivers mais ils semblent tous à jour.J'ai donc essayer d'enlever mes anciennes barrettes de ram pour voir s'il s'agissait d'une incompatibilité, il semble que les bluescreen soit plus espacés dans le temps mais ils sont toujours là ... Je me tourne donc vers vous ! Dans l'attente de vos réponses, D'avance MERCI ! Bij-B Ps: Le tout est monté sur une carte mère asus M4A77T/USB3 avec un processeur phenom II x6 le tout alimenté par une corsair TX 650 WattsPs²: J'ai encore eu un blue screen pendant la rédaction de ce post Citer Lien vers le commentaire Partager sur d'autres sites More sharing options...
inarticulomortis Publié le 9 août 2013 Signalement Share Publié le 9 août 2013 bonjour,le bsod (blue screen) indique souvant un soucis de conflit hardware ou une infection tu as toujours un détail de ce bsod genre capture (ccjoint) ou photo? Citer Lien vers le commentaire Partager sur d'autres sites More sharing options...
Bij-B Publié le 10 août 2013 Auteur Signalement Share Publié le 10 août 2013 voici le rapport au redémarrage de windows : 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: a BCP1: FFFFFFFFFFFFFFFF BCP2: 0000000000000000 BCP3: 0000000000000001 BCP4: FFFFF800022A79C9 OS Version: 6_1_7601 Service Pack: 1_0 Product: 768_1 Fichiers aidant à décrire le problème : C:\Windows\Minidump\081013-11388-01.dmp C:\Users\Bij-B\AppData\Local\Temp\WER-13899-0.sysdata.xml Lire notre déclaration de confidentialité en ligne : http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x040c Si la déclaration de confidentialité en ligne n’est pas disponible, lisez la version hors connexion : C:\Windows\system32\fr-FR\erofflps.txt et celui de whocrashed : Crash dump directory: C:\Windows\MinidumpCrash dumps are enabled on your computer.On Fri 09/08/2013 21:12:31 GMT your computer crashedcrash dump file: C:\Windows\Minidump\081013-11388-01.dmpThis was probably caused by the following module: ntoskrnl.exe (nt+0x75C00)Bugcheck code: 0xA (0xFFFFFFFFFFFFFFFF, 0x0, 0x1, 0xFFFFF800022A79C9)Error: IRQL_NOT_LESS_OR_EQUALfile path: C:\Windows\system32\ntoskrnl.exeproduct: Microsoft® Windows® Operating Systemcompany: Microsoft Corporationdescription: NT Kernel & SystemBug 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 Fri 09/08/2013 13:18:05 GMT your computer crashedcrash dump file: C:\Windows\Minidump\080913-11029-01.dmpThis was probably caused by the following module: ntoskrnl.exe (nt+0x75C00)Bugcheck code: 0x1A (0x41201, 0xFFFFF68000002448, 0xCEB00001FCE76867, 0xFFFFFA8007C1F5A0)Error: MEMORY_MANAGEMENTfile path: C:\Windows\system32\ntoskrnl.exeproduct: Microsoft® Windows® Operating Systemcompany: Microsoft Corporationdescription: NT Kernel & SystemBug 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.On Fri 09/08/2013 04:24:20 GMT your computer crashedcrash dump file: C:\Windows\Minidump\080913-11512-01.dmpThis was probably caused by the following module: ntoskrnl.exe (nt+0x75C00)Bugcheck code: 0x4A (0x777C167A, 0x2, 0x0, 0xFFFFF8800C61BCA0)Error: IRQL_GT_ZERO_AT_SYSTEM_SERVICEfile path: C:\Windows\system32\ntoskrnl.exeproduct: Microsoft® Windows® Operating Systemcompany: Microsoft Corporationdescription: NT Kernel & SystemBug check description: This indicates that a thread is returning to user mode from a system call when its IRQL is still above PASSIVE_LEVEL.The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.On Thu 08/08/2013 18:50:38 GMT your computer crashedcrash dump file: C:\Windows\Minidump\080813-11310-01.dmpThis was probably caused by the following module: ntoskrnl.exe (nt+0x75C00)Bugcheck code: 0x1E (0xFFFFFFFFC000001D, 0xFFFFF8800C935E20, 0x0, 0x0)Error: KMODE_EXCEPTION_NOT_HANDLEDfile path: C:\Windows\system32\ntoskrnl.exeproduct: Microsoft® Windows® Operating Systemcompany: Microsoft Corporationdescription: NT Kernel & SystemBug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.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 Thu 08/08/2013 17:37:08 GMT your computer crashedcrash dump file: C:\Windows\Minidump\080813-10467-01.dmpThis was probably caused by the following module: win32k.sys (win32k+0xCC781)Bugcheck code: 0x3B (0xC000001D, 0xFFFFF9600016C781, 0xFFFFF8800D737F70, 0x0)Error: SYSTEM_SERVICE_EXCEPTIONfile path: C:\Windows\system32\win32k.sysproduct: Système d’exploitation Microsoft® Windows®company: Microsoft Corporationdescription: Pilote Win32 multi-utilisateursBug 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 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 Thu 08/08/2013 16:27:37 GMT your computer crashedcrash dump file: C:\Windows\Minidump\080813-10389-01.dmpThis was probably caused by the following module: ntoskrnl.exe (nt+0x75C00)Bugcheck code: 0x109 (0xA3A039D89C701A16, 0xB3B7465EEEECE96C, 0xFFFFF80002369810, 0x1)Error: CRITICAL_STRUCTURE_CORRUPTIONfile path: C:\Windows\system32\ntoskrnl.exeproduct: Microsoft® Windows® Operating Systemcompany: Microsoft Corporationdescription: NT Kernel & SystemBug check description: This indicates that the kernel has detected critical kernel code or data corruption.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 Thu 08/08/2013 03:04:09 GMT your computer crashedcrash dump file: C:\Windows\Minidump\080813-10810-02.dmpThis was probably caused by the following module: ntoskrnl.exe (nt+0x75C00)Bugcheck code: 0x109 (0xA3A039D89C505548, 0xB3B7465EEECD249E, 0xFFFFF8000226D830, 0x1)Error: CRITICAL_STRUCTURE_CORRUPTIONfile path: C:\Windows\system32\ntoskrnl.exeproduct: Microsoft® Windows® Operating Systemcompany: Microsoft Corporationdescription: NT Kernel & SystemBug check description: This indicates that the kernel has detected critical kernel code or data corruption.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 Wed 07/08/2013 23:37:33 GMT your computer crashedcrash dump file: C:\Windows\Minidump\080813-10654-01.dmpThis was probably caused by the following module: rt64win7.sys (Rt64win7+0x31B8)Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)Error: KMODE_EXCEPTION_NOT_HANDLEDfile path: C:\Windows\system32\drivers\rt64win7.sysproduct: Realtek 8136/8168/8169 PCI/PCIe Adapters company: Realtek description: Realtek 8136/8168/8169 NDIS 6.20 64-bit DriverBug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.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: rt64win7.sys (Realtek 8136/8168/8169 NDIS 6.20 64-bit Driver , Realtek ).Google query: Realtek KMODE_EXCEPTION_NOT_HANDLEDOn Wed 07/08/2013 23:13:13 GMT your computer crashedcrash dump file: C:\Windows\Minidump\080813-10810-01.dmpThis was probably caused by the following module: hidclass.sys (HIDCLASS+0x109C)Bugcheck code: 0xD1 (0x64, 0x2, 0x8, 0x64)Error: DRIVER_IRQL_NOT_LESS_OR_EQUALfile path: C:\Windows\system32\drivers\hidclass.sysproduct: Microsoft® Windows® Operating Systemcompany: Microsoft Corporationdescription: Hid Class LibraryBug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.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 Wed 07/08/2013 23:06:38 GMT your computer crashedcrash dump file: C:\Windows\Minidump\080813-10436-01.dmpThis was probably caused by the following module: hidclass.sys (HIDCLASS+0x109C)Bugcheck code: 0xD1 (0x14, 0x2, 0x8, 0x14)Error: DRIVER_IRQL_NOT_LESS_OR_EQUALfile path: C:\Windows\system32\drivers\hidclass.sysproduct: Microsoft® Windows® Operating Systemcompany: Microsoft Corporationdescription: Hid Class LibraryBug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.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 Wed 07/08/2013 22:56:15 GMT your computer crashedcrash dump file: C:\Windows\Minidump\080813-10452-01.dmpThis was probably caused by the following module: ntoskrnl.exe (nt+0x75C00)Bugcheck code: 0x109 (0xA3A039D89ECF665E, 0xB3B7465EF14C35B4, 0xFFFFF8000221B140, 0x1)Error: CRITICAL_STRUCTURE_CORRUPTIONfile path: C:\Windows\system32\ntoskrnl.exeproduct: Microsoft® Windows® Operating Systemcompany: Microsoft Corporationdescription: NT Kernel & SystemBug check description: This indicates that the kernel has detected critical kernel code or data corruption.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 Wed 07/08/2013 21:28:39 GMT your computer crashedcrash dump file: C:\Windows\Minidump\080713-8892-01.dmpThis was probably caused by the following module: ntoskrnl.exe (nt+0x75C00)Bugcheck code: 0x109 (0xA3A039D89ED2A5B1, 0xB3B7465EF14F7507, 0xFFFFF80002082FF8, 0x1)Error: CRITICAL_STRUCTURE_CORRUPTIONfile path: C:\Windows\system32\ntoskrnl.exeproduct: Microsoft® Windows® Operating Systemcompany: Microsoft Corporationdescription: NT Kernel & SystemBug check description: This indicates that the kernel has detected critical kernel code or data corruption.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 Wed 07/08/2013 19:30:35 GMT your computer crashedcrash dump file: C:\Windows\Minidump\080713-9453-01.dmpThis was probably caused by the following module: ntoskrnl.exe (nt+0x75C00)Bugcheck code: 0xD1 (0xFFFFF80001F967D2, 0x0, 0x8, 0xFFFFF80001F967D2)Error: DRIVER_IRQL_NOT_LESS_OR_EQUALfile path: C:\Windows\system32\ntoskrnl.exeproduct: Microsoft® Windows® Operating Systemcompany: Microsoft Corporationdescription: NT Kernel & SystemBug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.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 Wed 07/08/2013 11:49:13 GMT your computer crashedcrash dump file: C:\Windows\Minidump\080713-8330-01.dmpThis was probably caused by the following module: ntoskrnl.exe (nt+0x75C00)Bugcheck code: 0xE3 (0xFFFFFA800B076B70, 0xFFFFFA800BF91590, 0xFFFFFA800B7D91F0, 0x3)Error: RESOURCE_NOT_OWNEDfile path: C:\Windows\system32\ntoskrnl.exeproduct: Microsoft® Windows® Operating Systemcompany: Microsoft Corporationdescription: NT Kernel & SystemBug check description: This indicates that a thread tried to release a resource it did not own.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. Conclusion14 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:rt64win7.sys (Realtek 8136/8168/8169 NDIS 6.20 64-bit Driver , Realtek )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 ne sais pas si c'est de ça que tu parlais je m'y connais pas trop en Blue Screen (j'ai toujours eu de la chance jusqu'ici ... Citer Lien vers le commentaire Partager sur d'autres sites More sharing options...
Bij-B Publié le 10 août 2013 Auteur Signalement Share Publié le 10 août 2013 Je me permet de up j'ai vraiment besoin de l'ordinateur pour quelques réalisations graphiques... Citer Lien vers le commentaire Partager sur d'autres sites More sharing options...
inarticulomortis Publié le 11 août 2013 Signalement Share Publié le 11 août 2013 bonjour,bon reprennons dans l'ordreFait une capture de ton bsop je vais voir ce que je peux faireTéléchargement ou visionnage?mise a jours genre flash-player ou autres?Installation de nouveau harware? (bon site pour les soluces harware.fr) Citer Lien vers le commentaire Partager sur d'autres sites More sharing options...
Bij-B Publié le 11 août 2013 Auteur Signalement Share Publié le 11 août 2013 les rapport ne servent pas ? comment faire pour prendre un screen lors d'un BSOD ? j'ai des photos de 2 blue screen sur mon portable, les voici : en voici un :et un autre : PS : Voici tout mes rapports whocrashed jusqu'à ce jour : System Information (local) computer name: REALTHUGwindows version: Windows 7 Service Pack 1, 6.1, build: 7601windows dir: C:\WindowsCPU: AuthenticAMD AMD Phenom II X6 1055T Processor AMD586, level: 166 logical processors, active mask: 63RAM: 8588021760 totalVM: 2147352576, free: 1913012224 Crash Dump Analysis Crash dump directory: C:\Windows\MinidumpCrash dumps are enabled on your computer.On Sun 11/08/2013 03:05:01 GMT your computer crashedcrash dump file: C:\Windows\Minidump\081113-11793-01.dmpThis was probably caused by the following module: ntoskrnl.exe (nt+0x75C00)Bugcheck code: 0x109 (0xA3A039D89C5166AC, 0xB3B7465EEECE3612, 0xFFFFF80002321980, 0x1)Error: CRITICAL_STRUCTURE_CORRUPTIONfile path: C:\Windows\system32\ntoskrnl.exeproduct: Microsoft® Windows® Operating Systemcompany: Microsoft Corporationdescription: NT Kernel & SystemBug check description: This indicates that the kernel has detected critical kernel code or data corruption.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 Sun 11/08/2013 02:27:02 GMT your computer crashedcrash dump file: C:\Windows\Minidump\081113-11637-01.dmpThis was probably caused by the following module: ntoskrnl.exe (nt+0x75C00)Bugcheck code: 0x109 (0xA3A039D89BAEDBAD, 0xB3B7465EEE2BAB03, 0xFFFFF800026A7910, 0x1)Error: CRITICAL_STRUCTURE_CORRUPTIONfile path: C:\Windows\system32\ntoskrnl.exeproduct: Microsoft® Windows® Operating Systemcompany: Microsoft Corporationdescription: NT Kernel & SystemBug check description: This indicates that the kernel has detected critical kernel code or data corruption.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 Sun 11/08/2013 00:57:38 GMT your computer crashedcrash dump file: C:\Windows\Minidump\081113-10826-01.dmpThis was probably caused by the following module: ntoskrnl.exe (nt+0x75C00)Bugcheck code: 0x109 (0xA3A039D89C2CD856, 0xB3B7465EEEA9A7BC, 0xFFFFF80002561860, 0x1)Error: CRITICAL_STRUCTURE_CORRUPTIONfile path: C:\Windows\system32\ntoskrnl.exeproduct: Microsoft® Windows® Operating Systemcompany: Microsoft Corporationdescription: NT Kernel & SystemBug check description: This indicates that the kernel has detected critical kernel code or data corruption.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 Sat 10/08/2013 22:00:32 GMT your computer crashedcrash dump file: C:\Windows\Minidump\081113-11466-01.dmpThis was probably caused by the following module: luafv.sys (luafv+0x11C0F)Bugcheck code: 0x50 (0xFFFFFA7F999FB0DB, 0x1, 0xFFFFF800025E39C9, 0x7)Error: PAGE_FAULT_IN_NONPAGED_AREAfile path: C:\Windows\system32\drivers\luafv.sysproduct: Système d’exploitation Microsoft® Windows®company: Microsoft Corporationdescription: Pilote de filtre de virtualisation de fichier LUABug 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 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 Fri 09/08/2013 21:12:31 GMT your computer crashedcrash dump file: C:\Windows\Minidump\081013-11388-01.dmpThis was probably caused by the following module: ntoskrnl.exe (nt+0x75C00)Bugcheck code: 0xA (0xFFFFFFFFFFFFFFFF, 0x0, 0x1, 0xFFFFF800022A79C9)Error: IRQL_NOT_LESS_OR_EQUALfile path: C:\Windows\system32\ntoskrnl.exeproduct: Microsoft® Windows® Operating Systemcompany: Microsoft Corporationdescription: NT Kernel & SystemBug 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 Fri 09/08/2013 13:18:05 GMT your computer crashedcrash dump file: C:\Windows\Minidump\080913-11029-01.dmpThis was probably caused by the following module: ntoskrnl.exe (nt+0x75C00)Bugcheck code: 0x1A (0x41201, 0xFFFFF68000002448, 0xCEB00001FCE76867, 0xFFFFFA8007C1F5A0)Error: MEMORY_MANAGEMENTfile path: C:\Windows\system32\ntoskrnl.exeproduct: Microsoft® Windows® Operating Systemcompany: Microsoft Corporationdescription: NT Kernel & SystemBug 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. On Fri 09/08/2013 04:24:20 GMT your computer crashedcrash dump file: C:\Windows\Minidump\080913-11512-01.dmpThis was probably caused by the following module: ntoskrnl.exe (nt+0x75C00)Bugcheck code: 0x4A (0x777C167A, 0x2, 0x0, 0xFFFFF8800C61BCA0)Error: IRQL_GT_ZERO_AT_SYSTEM_SERVICEfile path: C:\Windows\system32\ntoskrnl.exeproduct: Microsoft® Windows® Operating Systemcompany: Microsoft Corporationdescription: NT Kernel & SystemBug check description: This indicates that a thread is returning to user mode from a system call when its IRQL is still above PASSIVE_LEVEL.The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time. On Thu 08/08/2013 18:50:38 GMT your computer crashedcrash dump file: C:\Windows\Minidump\080813-11310-01.dmpThis was probably caused by the following module: ntoskrnl.exe (nt+0x75C00)Bugcheck code: 0x1E (0xFFFFFFFFC000001D, 0xFFFFF8800C935E20, 0x0, 0x0)Error: KMODE_EXCEPTION_NOT_HANDLEDfile path: C:\Windows\system32\ntoskrnl.exeproduct: Microsoft® Windows® Operating Systemcompany: Microsoft Corporationdescription: NT Kernel & SystemBug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.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 Thu 08/08/2013 17:37:08 GMT your computer crashedcrash dump file: C:\Windows\Minidump\080813-10467-01.dmpThis was probably caused by the following module: win32k.sys (win32k+0xCC781)Bugcheck code: 0x3B (0xC000001D, 0xFFFFF9600016C781, 0xFFFFF8800D737F70, 0x0)Error: SYSTEM_SERVICE_EXCEPTIONfile path: C:\Windows\system32\win32k.sysproduct: Système d’exploitation Microsoft® Windows®company: Microsoft Corporationdescription: Pilote Win32 multi-utilisateursBug 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 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 Thu 08/08/2013 16:27:37 GMT your computer crashedcrash dump file: C:\Windows\Minidump\080813-10389-01.dmpThis was probably caused by the following module: ntoskrnl.exe (nt+0x75C00)Bugcheck code: 0x109 (0xA3A039D89C701A16, 0xB3B7465EEEECE96C, 0xFFFFF80002369810, 0x1)Error: CRITICAL_STRUCTURE_CORRUPTIONfile path: C:\Windows\system32\ntoskrnl.exeproduct: Microsoft® Windows® Operating Systemcompany: Microsoft Corporationdescription: NT Kernel & SystemBug check description: This indicates that the kernel has detected critical kernel code or data corruption.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 Thu 08/08/2013 03:04:09 GMT your computer crashedcrash dump file: C:\Windows\Minidump\080813-10810-02.dmpThis was probably caused by the following module: ntoskrnl.exe (nt+0x75C00)Bugcheck code: 0x109 (0xA3A039D89C505548, 0xB3B7465EEECD249E, 0xFFFFF8000226D830, 0x1)Error: CRITICAL_STRUCTURE_CORRUPTIONfile path: C:\Windows\system32\ntoskrnl.exeproduct: Microsoft® Windows® Operating Systemcompany: Microsoft Corporationdescription: NT Kernel & SystemBug check description: This indicates that the kernel has detected critical kernel code or data corruption.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 Wed 07/08/2013 23:37:33 GMT your computer crashedcrash dump file: C:\Windows\Minidump\080813-10654-01.dmpThis was probably caused by the following module: rt64win7.sys (Rt64win7+0x31B8)Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)Error: KMODE_EXCEPTION_NOT_HANDLEDfile path: C:\Windows\system32\drivers\rt64win7.sysproduct: Realtek 8136/8168/8169 PCI/PCIe Adapters company: Realtek description: Realtek 8136/8168/8169 NDIS 6.20 64-bit DriverBug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.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: rt64win7.sys (Realtek 8136/8168/8169 NDIS 6.20 64-bit Driver , Realtek ).Google query: Realtek KMODE_EXCEPTION_NOT_HANDLEDOn Wed 07/08/2013 23:13:13 GMT your computer crashedcrash dump file: C:\Windows\Minidump\080813-10810-01.dmpThis was probably caused by the following module: hidclass.sys (HIDCLASS+0x109C)Bugcheck code: 0xD1 (0x64, 0x2, 0x8, 0x64)Error: DRIVER_IRQL_NOT_LESS_OR_EQUALfile path: C:\Windows\system32\drivers\hidclass.sysproduct: Microsoft® Windows® Operating Systemcompany: Microsoft Corporationdescription: Hid Class LibraryBug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.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 Wed 07/08/2013 23:06:38 GMT your computer crashedcrash dump file: C:\Windows\Minidump\080813-10436-01.dmpThis was probably caused by the following module: hidclass.sys (HIDCLASS+0x109C)Bugcheck code: 0xD1 (0x14, 0x2, 0x8, 0x14)Error: DRIVER_IRQL_NOT_LESS_OR_EQUALfile path: C:\Windows\system32\drivers\hidclass.sysproduct: Microsoft® Windows® Operating Systemcompany: Microsoft Corporationdescription: Hid Class LibraryBug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.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 Wed 07/08/2013 22:56:15 GMT your computer crashedcrash dump file: C:\Windows\Minidump\080813-10452-01.dmpThis was probably caused by the following module: ntoskrnl.exe (nt+0x75C00)Bugcheck code: 0x109 (0xA3A039D89ECF665E, 0xB3B7465EF14C35B4, 0xFFFFF8000221B140, 0x1)Error: CRITICAL_STRUCTURE_CORRUPTIONfile path: C:\Windows\system32\ntoskrnl.exeproduct: Microsoft® Windows® Operating Systemcompany: Microsoft Corporationdescription: NT Kernel & SystemBug check description: This indicates that the kernel has detected critical kernel code or data corruption.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. Conclusion 18 crash dumps have been found and analyzed. Only 15 are included in this report. 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:rt64win7.sys (Realtek 8136/8168/8169 NDIS 6.20 64-bit Driver , Realtek )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. Citer Lien vers le commentaire Partager sur d'autres sites More sharing options...
Bij-B Publié le 11 août 2013 Auteur Signalement Share Publié le 11 août 2013 Installation de nouveau harware? (bon site pour les soluces harware.fr) Evidemment (c'est pas comme si je l'avais bien décrit et expliquer en détail dès mon premier message ... j'ai même mis des couleurs ^^) PS: Je précise que lors de mon changement de dd principal je n'ai pas réinstaller windows "proprement" car j'ai cloné l'ancien disque sur le quel l'installation windows était récente. Le problême pourrait-il venir de ça? dois-je réinstaller win 7 ? D'avance merci de vos réponses Citer Lien vers le commentaire Partager sur d'autres sites More sharing options...
Bij-B Publié le 11 août 2013 Auteur Signalement Share Publié le 11 août 2013 Nouveau BlueScreen ... Son rapport whocrashed : Crash dump directory: C:\Windows\MinidumpCrash dumps are enabled on your computer.On Sun 11/08/2013 16:56:47 GMT your computer crashedcrash dump file: C:\Windows\Minidump\081113-11122-01.dmpThis was probably caused by the following module: ntoskrnl.exe (nt+0x75C00)Bugcheck code: 0x50 (0xFFFFFFFF8B482C74, 0x0, 0xFFFFF800022A79C7, 0x5)Error: PAGE_FAULT_IN_NONPAGED_AREAfile path: C:\Windows\system32\ntoskrnl.exeproduct: Microsoft® Windows® Operating Systemcompany: Microsoft Corporationdescription: NT Kernel & SystemBug 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 that cannot be identified at this time. Citer Lien vers le commentaire Partager sur d'autres sites More sharing options...
djromixunited01 Publié le 11 août 2013 Signalement Share Publié le 11 août 2013 bonjour tu devrais utiliser l'outil proposer par ce site, tu lances une détection et tu cliques sur le bouton partager. il suffit de suivre la procédure et un lien sera généré qu'il faudra nous communiquer pour obtenir les détails de ta configuration et des crash qui s'en suivent. Citer Lien vers le commentaire Partager sur d'autres sites More sharing options...
Bij-B Publié le 11 août 2013 Auteur Signalement Share Publié le 11 août 2013 si j'ai bien compris tes indications voici le lien : http://www.ma-config.com/fr/configurationpubliee/133662-0-1_resume.html Citer Lien vers le commentaire Partager sur d'autres sites More sharing options...
djromixunited01 Publié le 12 août 2013 Signalement Share Publié le 12 août 2013 retu peux contrôler ta ram avec memtest voir si celle ci ne serait pas en cause? Citer Lien vers le commentaire Partager sur d'autres sites More sharing options...
Bij-B Publié le 12 août 2013 Auteur Signalement Share Publié le 12 août 2013 j'ai déjà effectué un test windows et elle ne semble pas en cause Je test avec memtest et je poste le resultat? (par contre je n'ai jamais utilisé ce logiciel) 1 Citer Lien vers le commentaire Partager sur d'autres sites More sharing options...
Bij-B Publié le 12 août 2013 Auteur Signalement Share Publié le 12 août 2013 Mem test ma affiché que je ne pouvais pas tester toute la ram dun coup et quil fallait que je lance 2 memtest avec 2047 mo chacun mais jai 8 go au total cest bizarre non ? Je dois le lancer 4 fois peut etre ? EDIT : Dans le doute j'ai lancé memtest 2 fois avec 2047 mo sur chacun (j'ai lu qu'il fallait le faire tourner 20 min je l'ai fait pendant 40 et aucune erreur) Est ce suffisant? Citer Lien vers le commentaire Partager sur d'autres sites More sharing options...
lethumier olivier Publié le 13 août 2013 Signalement Share Publié le 13 août 2013 bonjour , je ne sait ci cela peut aidée , mais perso , il a fallu que je change l'alimentation quand je suis passez au Phenom II X6 + HD 7xxx les 650W de mon ancienne ( la même que toi ) était plus que limite .Bon maintenant, il faut que j'en rechange mon actuel OCZ 850w est très fatiguée et ne supporte que très péniblement , mon Crossfire HD 7870 OC Citer Lien vers le commentaire Partager sur d'autres sites More sharing options...
djromixunited01 Publié le 13 août 2013 Signalement Share Publié le 13 août 2013 re, pour la ramça doit être bon il faut chercher ailleur, as-tu essayé de remettre ton ancienne carte graphique pour voir ? et puis comme l'a dit nounours il reste la possibilité de l'alimentation. Citer Lien vers le commentaire Partager sur d'autres sites More sharing options...
Bij-B Publié le 13 août 2013 Auteur Signalement Share Publié le 13 août 2013 non je n'ai pas essayé de la remettre (j'ai peur de re découvrir son vacarme infernal ><) mais je vais le faire. Par contre comme mes bluescreen sont très aléatoires je ne sais pas combien de temps il va falloir attendre pour savoir ... Vous pensez que ça peu venir de l'alim ? mais 650 watts sont suffisants normalement non ? vous pensez que c'est du a l'usure si ça vient de l'alim? Vous ne pensez pas que ça peut venir de l'installation de windows (via clonage sur le ssd ) ? Surtout que le bluescreen ne se produit pas (en tout cas pas particulièrement) lorsque je sollicite beaucoup la machine, je joue au max et souvent c'est quand je suis sur windaube en dehors des jeux que le pc m'affiche le BS. Citer Lien vers le commentaire Partager sur d'autres sites More sharing options...
djromixunited01 Publié le 13 août 2013 Signalement Share Publié le 13 août 2013 et bien essaie tout de même la carte graphique même sur plusieurs jours si il faut Citer Lien vers le commentaire Partager sur d'autres sites More sharing options...
Bij-B Publié le 13 août 2013 Auteur Signalement Share Publié le 13 août 2013 D'accord je fais ça de suite ( si je n'ai plus de bluescreen en remettant l'ancienne qu'est ce qu'il faudra en conclure ?) Citer Lien vers le commentaire Partager sur d'autres sites More sharing options...
Bij-B Publié le 14 août 2013 Auteur Signalement Share Publié le 14 août 2013 Au final je viens tout juste de remettre mon ancienne mais les drivers ne fonctionnent plus et sur touslesdrivers ils me disent que j'ai les derniers (mais pour ma nouvelle pas l'ancienne) je dois désinstaller ceux de ma 7870 pour remettre ma 4870 ? Edit : Je viens de remarqué quelque chose qui m'intrigue sur ma cm ( m4a77t/usb3 ), les slots de ram sont bizarrement disposés je m'explique : j'ai 2 slots cote à cote bleu et 2 cote a cote noir (donc pas d'alternance) mais a coté il est noté dans l'ordre coresspondant aux slots "A1 / B1 / A2 / B2" les slots sont donc sous la forme "Bleu / Bleu / Noir / Noir" Or ma ram est installé sur le premier bleu et le premier noir donc A1 et A2 (en théorie je devrais donc etre en dual channel mais cpuz m'affiche un single channel est ce normal? ) Citer Lien vers le commentaire Partager sur d'autres sites More sharing options...
lethumier olivier Publié le 14 août 2013 Signalement Share Publié le 14 août 2013 Re pour les drivers , effectivement tu doit désinstallé tous les ancien pilotes ATI , pour cela AMD a un utilitaire très efficace ; Clean Uninstall Utility en ce qui concerne ta carte maman , ci tu a toujour le manuel réfère t'en sinon tu le trouvera > Là <et d' après ce qu'il dit , c'est bleu+bleu et noir +noir pour le dual Citer Lien vers le commentaire Partager sur d'autres sites More sharing options...
eVs Publié le 15 août 2013 Signalement Share Publié le 15 août 2013 avez-vous remarqué dans surveillance matérielle que le 5V est à 3,70 ? Si cela s'avère exact, cela semble confirmer le problème d'alim suggéré par nounours33 Citer Lien vers le commentaire Partager sur d'autres sites More sharing options...
Bij-B Publié le 15 août 2013 Auteur Signalement Share Publié le 15 août 2013 Bonjour, j'étais absent ces derniers temps, je n'ai pas encore eu le courage de remettre l'ancienne carte je le fais demain a moins que celà ne vienne réellement de l'alim. Edit : En cas d'achat d'une alim que me conseillez vous? de préférence une modulaire Citer Lien vers le commentaire Partager sur d'autres sites More sharing options...
lethumier olivier Publié le 18 août 2013 Signalement Share Publié le 18 août 2013 bonjour tout depend de ton budget , une alimentation peu passez du simple ( bas de gamme) au double voir triple ( haute de gamme et très haut de gamme ) Citer Lien vers le commentaire Partager sur d'autres sites More sharing options...
charon Publié le 18 août 2013 Signalement Share Publié le 18 août 2013 Bonjour Bij-B Peux tu m'envoyer les fichiers minidumps dans le dossier c:\windows\minidump sur mon mail: charon@ma-config.com . Les données que renvoient le module BSOD de ma-config semblent incorrectes. Je pourrai aussi peut être mieux analyser la cause de ton BSOD. Citer Lien vers le commentaire Partager sur d'autres sites More sharing options...
Bij-B Publié le 18 août 2013 Auteur Signalement Share Publié le 18 août 2013 Salut ! Je t'ai envoyé les dmp charon pour l'alim je n'ai pas vraiment de budget précis mais je voudrais une alim suffisamment puissante pour un changement de processeur et de cm vers noël (je ne sais pas encore quoi exactement mais surement un i5) et avec un rapport qualité/prix intéressant. Dans l'idéal vers la centaine d'euros (moins si possible) Edit : est ce que ça pourrais venir du cable d'alim en lui même ? Citer Lien vers le commentaire Partager sur d'autres sites More sharing options...
Publications recommandées
Joignez-vous à la conversation
Vous pouvez publier maintenant et vous inscrire plus tard. Si vous avez un compte, connectez-vous maintenant pour publier avec votre compte.