Bonjour à toutes et tous,  
 
je sais que ce problème a déjà été maintes fois évoqué mais je n'ai toujours pas trouvé la solution.
 
Voici ma config : http://www.ma-config.com/fr/publis [...] 1-1_resume
 
Cet écran bleu intervient plusieurs fois par jour quelque soit le programme que j'utilise, cela arrive même lorsque je  
regarde un film...
 
Voici le rapport de WhoCrashed :  
 
On Mon 01-09-14 11:05:19 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\090114-21312-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x153FA0)  
Bugcheck code: 0x1 (0x7FFA4659C7FA, 0x0, 0x1000000, 0xFFFFD000324C6B80)
Error: APC_INDEX_MISMATCH
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 there has been a mismatch in the APC state index.
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 01-09-14 11:05:19 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: 0x1 (0x7FFA4659C7FA, 0x0, 0x1000000, 0xFFFFD000324C6B80)
Error: APC_INDEX_MISMATCH
Bug check description: This indicates that there has been a mismatch in the APC state index.
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 31-08-14 06:19:08 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\083114-19781-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x153FA0)  
Bugcheck code: 0x50 (0xFFFFD000328733C0, 0x0, 0xFFFFF8016FF153AB, 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 that cannot be identified at this time.  
 
On Sat 30-08-14 12:44:30 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\083014-18515-01.dmp
This was probably caused by the following module: dxgmms1.sys (dxgmms1+0x2A670)  
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF8007B28D670, 0xFFFFD00071C8F568, 0xFFFFD00071C8ED70)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\WINDOWS\system32\drivers\dxgmms1.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics MMS
Bug check description: This indicates that a system thread 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 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 28-08-14 04:12:26 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\082814-20703-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x153FA0)  
Bugcheck code: 0x109 (0xA3A01F59537B5563, 0x0, 0xF1E8708897688EC9, 0x101)
Error: CRITICAL_STRUCTURE_CORRUPTION
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 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 27-08-14 18:56:07 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\082714-23343-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x153FA0)  
Bugcheck code: 0x19 (0x22, 0x400000, 0x0, 0x0)
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 25-08-14 10:55:29 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\082514-20328-01.dmp
This was probably caused by the following module: rt630x64.sys (0xFFFFF80044213556)  
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF80044213556, 0xFFFFD000213545E8, 0xFFFFD00021353DF0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\WINDOWS\system32\drivers\rt630x64.sys
product: Realtek 8136/8168/8169 PCI/PCIe Adapters  
company: Realtek  
description: Realtek 8101E/8168/8169 NDIS 6.30 64-bit Driver  
Bug check description: This indicates that a system thread 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: rt630x64.sys (Realtek 8101E/8168/8169 NDIS 6.30 64-bit Driver , Realtek ).  
Google query: Realtek SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
 
On Sun 24-08-14 10:19:31 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\082414-22281-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x153FA0)  
Bugcheck code: 0x1A (0x5003, 0xFFFFF58010804000, 0x36151, 0x46404009)
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.  
 
On Sat 23-08-14 08:22:03 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\082314-19687-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x153FA0)  
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF800FEA53828, 0xFFFFD00032B857A0, 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 that cannot be identified at this time.  
 
On Thu 21-08-14 07:42:17 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\082114-19171-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x153FA0)  
Bugcheck code: 0xA (0xFFFFFA801CD8BD00, 0x2, 0x1, 0xFFFFF8001F0B5482)
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.  
 
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
 
51 crash dumps have been found and analyzed. Only 10 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:  
 
rt630x64.sys (Realtek 8101E/8168/8169 NDIS 6.30 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.
 
Désolé pour la longueur de ce post, je souhaite vous donner un maximum d'infos afin de trouver une solution à ce problème qui en touche plus d'un(e).
 
Merci d'avance pour votre aide,  
 
Jean-Louis

Ne poste pas des rapports directement ici (c'est interdit) : colle-les sur CJoint et ensuite, indique le lien vers ton rapport (qu'il faudra supprimer d'ici si tu ne veux pas que ton fil soit fermé par la modération).

Salut Trit',  
 
j'ai posté ce rapport car j'ai vu que d'autres l'ont fait avant moi.
 
Un modérateur peut-il me confirmer que cela est interdit ?
 
Amicalement,
 
Jean-Louis

Je ne sais ce qui est interdit ou pas, mais le rapport ci-dessus indique un fichier fautif. La solution est là, non ?

Salut Laurent, merci pour ta réponse. Peux-tu me dire quel fichier est fautif ? Désolé mais je suis nul en informatique...