Bonjour,  
 
Voici les descriptifs du crash qui arrive systématiquement après le même temps de jeu (j'ai pas chronométré mais c'est de l'ordre de 15 minutes de jeu). J'ai testé avec Catalyst 12.2, puis la dernière version 12.3 et la dernière tentative c'est après avoir viré Catalyst. J'ai pas touché aux drivers Realtek qui sont à jour (2.67).
 
Config
Win 7 x64
PhII x4 955
HD 4870  
2*2 Go DDR3 OCZ PC12800
SpinPoint 1To
 
 

 
 
 
J'ai plein de fichiers dmp puisque j'ai eu plein de crahs, mais je n'arrive pas à les lire correctement (lié au sympath mais j'y comprends pas grand chose à part qu'il faut lui indiquer une adresse pour un catalogue). J'ai quand même la dernière ligne à  chaque fois :
 

 
Le truc entre parenthèses varie mais c'est toujours le même .exe SAUF après le dernier crash :  
 

 
Merci d'avance...

hello, vire moi ces cata de merde et remet des drivers du style 11.10
 
http://www.oldapps.com/ati.php?old_ati=6782
 
surtout pour une 4870

J'essaie mais j'y crois pas trop. J'ai quand même un écran bleu même après avoir désinstallé Catalyst...

Edit : j'ai essayé et j'ai pas envie de m'emballer mais ça a l'air de fonctionner.

J'ai encore eu un crash.

Cette fois ntoskrnl.exe encore.

desinstalle les drivers ati AMD passe un coup de regcleaner ou de CCleaner, et recupere les drivers officiel AMD de l epoque , et reinstalle

C'est ce que j'étais en train de faire .  
 
Je lance ME et je le laisse tourner en background pendant que je fais autre chose pour voir. C'est bizarre qu'il fonctionne proprement hier soir et pas aujourd'hui alors que je n'ai rien changé...

C'est quoi ta carte son ?
Pour ma part, ma creative X-FI crée parfois des bluescreen sur les jeux ayant comme moteur l'Unreal engine 3. Dans mon cas, c'est UT3. Donc je pense que ton probleme peut provenir de là car ME1 utilise l'UE3.
 

Crash encore. Toujours ntoskrnl.
 
Ma carte son est intégrée à la mobo (Gigabyte).

Essaie de la désactiver pour voir.
Pour ma part, pour résoudre le problème j'ai installé la dernière version d'OpenAl. Je suppose que ME1 l'utilise aussi.

Il faut désactiver les Hauts Parleurs dans le panneau de config c'est ça ?
 
C'est pas vraiment une solution mais on va voir...

 
Non désactiver la carte son dans le gestionnaire de périphériques

J'ai laissé le jeu tourner pendant plusieurs heures et il n'a pas planté.
 
Donc faut j'installe des drivers de son plus ancients ?

En fait, essaie de mettre à jour OpenAL
http://connect.creativelabs.com/op [...] Items.aspx
C'est ça qui causait problème chez moi.

Rapide l'installation...
 
Je lance une autre session....

Je l'ai laissé tourné toute la nuit. Il a planté vers 3h du mat donc il a quand même marché pendant plusieurs heures...

J'ai pas eu le temps de retester depuis mais taleur je voulais y jouer et il a planté au bout de 20 minutes même pas avec cette fois "dxgkrnl.sys"  qui est incriminé.

UP.

Installe Whocrashed, il donne pas mal d'info sur les écrans bleus
http://www.resplendence.com/downlo [...] dSetup.exe

Le rapport de Who Crashed :  
 
 
On Mon 02/04/2012 00:37:55 GMT your computer crashed
crash dump file: C:\Windows\Minidump\040212-23509-01.dmp
This was probably caused by the following module: dxgkrnl.sys (dxgkrnl+0x8901)  
Bugcheck code: 0xA (0xFFFFF7D0039A4060, 0x2, 0x1, 0xFFFFF8000309AAE2)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\dxgkrnl.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics Kernel
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 a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.  
 
 
On Mon 02/04/2012 00:37:55 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: 0xA (0xFFFFF7D0039A4060, 0x2, 0x1, 0xFFFFF8000309AAE2)
Error: IRQL_NOT_LESS_OR_EQUAL
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 which cannot be identified at this time.  
 
 
On Sun 01/04/2012 16:08:22 GMT your computer crashed
crash dump file: C:\Windows\Minidump\040112-23446-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CD40)  
Bugcheck code: 0xA (0xFFFFF78080000320, 0xD, 0x0, 0xFFFFF80003091367)
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 which cannot be identified at this time.  
 
 
On Sun 01/04/2012 15:01:10 GMT your computer crashed
crash dump file: C:\Windows\Minidump\040112-23244-01.dmp
This was probably caused by the following module: dxgkrnl.sys (dxgkrnl+0x8901)  
Bugcheck code: 0xA (0xFFFFF7D003CB8E80, 0x2, 0x1, 0xFFFFF8000308FAE2)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\dxgkrnl.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics Kernel
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 a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.  
 
 
On Thu 29/03/2012 00:54:54 GMT your computer crashed
crash dump file: C:\Windows\Minidump\032912-22120-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CD40)  
Bugcheck code: 0xA (0x60, 0x2, 0x1, 0xFFFFF800030E11B3)
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 which cannot be identified at this time.  
 
 
On Wed 28/03/2012 21:29:22 GMT your computer crashed
crash dump file: C:\Windows\Minidump\032812-23446-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CD40)  
Bugcheck code: 0xA (0x0, 0x2, 0x1, 0xFFFFF8000309669D)
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 which cannot be identified at this time.  
 
 
On Wed 28/03/2012 16:31:22 GMT your computer crashed
crash dump file: C:\Windows\Minidump\032812-26972-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CD40)  
Bugcheck code: 0xA (0xFFFFF88003766354, 0xD, 0x1, 0xFFFFF80003076278)
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 which cannot be identified at this time.  
 
 
On Tue 27/03/2012 19:34:24 GMT your computer crashed
crash dump file: C:\Windows\Minidump\032712-25740-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CD40)  
Bugcheck code: 0xA (0x1F1BF, 0x2, 0x1, 0xFFFFF800030861AD)
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 which cannot be identified at this time.  
 
 
On Tue 27/03/2012 17:51:57 GMT your computer crashed
crash dump file: C:\Windows\Minidump\032712-31605-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CD40)  
Bugcheck code: 0xA (0x0, 0x2, 0x1, 0xFFFFF800030E31B3)
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 which cannot be identified at this time.  
 
 
On Mon 26/03/2012 19:20:09 GMT your computer crashed
crash dump file: C:\Windows\Minidump\032612-23961-01.dmp
This was probably caused by the following module: termdd.sys (termdd+0x128C0)  
Bugcheck code: 0xD3 (0xFFFFF88003FD78C0, 0xD, 0x1, 0xFFFFF8000308C11F)
Error: DRIVER_PORTION_MUST_BE_NONPAGED
file path: C:\Windows\system32\drivers\termdd.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Remote Desktop Server Driver
Bug check description: This indicates that the system 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 which cannot be identified at this time.  
 
 
On Sun 25/03/2012 01:57:00 GMT your computer crashed
crash dump file: C:\Windows\Minidump\032512-31933-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CD40)  
Bugcheck code: 0xA (0xFFFFF78080000320, 0xD, 0x0, 0xFFFFF800030E2367)
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 which cannot be identified at this time.  
 
 
On Sat 24/03/2012 13:40:21 GMT your computer crashed
crash dump file: C:\Windows\Minidump\032412-33477-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CD10)  
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
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 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 which cannot be identified at this time.  
 
 
On Sat 24/03/2012 01:33:18 GMT your computer crashed
crash dump file: C:\Windows\Minidump\032412-16723-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CD10)  
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
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 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 which cannot be identified at this time.  
 
 
On Fri 23/03/2012 01:29:59 GMT your computer crashed
crash dump file: C:\Windows\Minidump\032312-16972-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CD40)  
Bugcheck code: 0xA (0xFFFFF88002FCEBEE, 0x2, 0x1, 0xFFFFF80002E8A94C)
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 which cannot be identified at this time.  
 
 
On Fri 23/03/2012 00:56:21 GMT your computer crashed
crash dump file: C:\Windows\Minidump\032312-28470-01.dmp
This was probably caused by the following module: dxgmms1.sys (dxgmms1+0x38570)  
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF88002DB6570, 0xFFFFF88003D1B8A8, 0xFFFFF88003D1B100)
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 which cannot be identified at this time.  
 
 
 
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
 
22 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:  
 
unknown_module_00000000`00044040.sys

Hum ça sent la mémoire defectueuse ça.
Fais un memtest ou un diagnotic mémoire Windows (moins rigoureux mais détecte quand même les problèmes de mémoire importants)

Déjà fait un test avec le truc de Windows.  
 
Rien trouvé.

Up.