je connaissait pas l'outil proposé par StarForce9 mais il a l'air de pouvoir aider, ça peut te lancer sur une piste

"Ce petit utilitaire se révèlera très utile la prochaine fois que votre ordinateur affichera un écran bleu ou qu'il redémarrera automatiquement sans raison. En effet, WhoCrashed permet d'identifier en un clic les causes de plantage du système. Son utilisation est très simple : il suffit de lancer l'installation puis de cliquer sur "Analyse". En cas de défaillance matérielle, le logiciel indique quel pilote ou module du noyau est à l'origine du crash."

voila le raport :

windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
CPU: GenuineIntel Intel(R) Core(TM) i7-2600 CPU @ 3.40GHz Intel586, level: 6
8 logical processors, active mask: 255
RAM: 8571027456 total
VM: 2147352576, free: 1951719424

--------------------------------------------------
------------------------------
Crash Dump Analysis

--------------------------------------------------
------------------------------

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Sun 20/05/2012 10:23:43 GMT your computer crashed
crash dump file: C:\Windows\Minidump\052012-16988-01.dmp
This was probably caused by the following module: fltmgr.sys (fltmgr+0x249BD)
Bugcheck code: 0x19 (0x20, 0xFFFFFA800972C4C0, 0xFFFFFA800972C580, 0xC0C0001)
Error: BAD_POOL_HEADER
file path: C:\Windows\system32\drivers\fltmgr.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Gestionnaire de filtres de système de fichiers Microsoft
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 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 20/05/2012 10:03:23 GMT your computer crashed
crash dump file: C:\Windows\Minidump\052012-17144-01.dmp
This was probably caused by the following module: fltmgr.sys (fltmgr+0x249BD)
Bugcheck code: 0x19 (0x20, 0xFFFFFA800791E5C0, 0xFFFFFA800791E680, 0xC0C0005)
Error: BAD_POOL_HEADER
file path: C:\Windows\system32\drivers\fltmgr.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Gestionnaire de filtres de système de fichiers Microsoft
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 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 20/05/2012 09:56:30 GMT your computer crashed
crash dump file: C:\Windows\Minidump\052012-17830-01.dmp
This was probably caused by the following module: fltmgr.sys (fltmgr+0x249BD)
Bugcheck code: 0x19 (0x20, 0xFFFFFA80078AD780, 0xFFFFFA80078AD840, 0xC0C0008)
Error: BAD_POOL_HEADER
file path: C:\Windows\system32\drivers\fltmgr.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Gestionnaire de filtres de système de fichiers Microsoft
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 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 Sat 19/05/2012 22:45:39 GMT your computer crashed
crash dump file: C:\Windows\Minidump\052012-21481-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0x50 (0xFFFFFA800DE09400, 0x1, 0xFFFFF88007699B52, 0x2)
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 which cannot be identified at this time.

On Fri 18/05/2012 18:31:21 GMT your computer crashed
crash dump file: C:\Windows\Minidump\051812-61635-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0x34 (0x50853, 0xFFFFF88009CE03E8, 0xFFFFF88009CDFC40, 0xFFFFF800038920EE)
Error: CACHE_MANAGER
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 problem occurred in the file system's cache manager.
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 which cannot be identified at this time.

On Fri 18/05/2012 16:08:26 GMT your computer crashed
crash dump file: C:\Windows\Minidump\051812-45474-01.dmp
This was probably caused by the following module: tcpip.sys (tcpip+0x82ACE)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF88001965ACE, 0xFFFFF8800358D5F8, 0xFFFFF8800358CE50)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\tcpip.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote TCP/IP
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.

On Fri 18/05/2012 13:56:53 GMT your computer crashed
crash dump file: C:\Windows\Minidump\051812-26098-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0x50 (0xFFFFFA800D4F42C0, 0x1, 0xFFFFF88000CC3B52, 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 which cannot be identified at this time.

On Wed 02/05/2012 18:49:14 GMT your computer crashed
crash dump file: C:\Windows\Minidump\050212-27612-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x350CA6)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF80003BA6CA6, 0xFFFFF880035A2868, 0xFFFFF880035A20C0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
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 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 the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.

On Wed 02/05/2012 18:43:45 GMT your computer crashed
crash dump file: C:\Windows\Minidump\050212-32838-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC80)
Bugcheck code: 0x50 (0xFFFFFA800F823340, 0x1, 0xFFFFF88000E6DB52, 0x2)
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 which cannot be identified at this time.

On Sat 21/04/2012 19:05:08 GMT your computer crashed
crash dump file: C:\Windows\Minidump\042112-59249-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC80)
Bugcheck code: 0x50 (0xFFFFFA8013E07040, 0x1, 0xFFFFF8800F403B52, 0x2)
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 which cannot be identified at this time.

On Wed 21/03/2012 06:02:17 GMT your computer crashed
crash dump file: C:\Windows\Minidump\032112-18735-01.dmp
This was probably caused by the following module: aswsnx.sys (aswSnx+0x460B8)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF880041150B8, 0xFFFFF8800B874ED0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\drivers\aswsnx.sys
product: avast! Antivirus System
company: AVAST Software
description: avast! Virtualization Driver
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.
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: aswsnx.sys (avast! Virtualization Driver, AVAST Software).
Google query: aswsnx.sys AVAST Software SYSTEM_SERVICE_EXCEPTION

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

--------------------------------------------------
------------------------------

11 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:

aswsnx.sys (avast! Virtualization Driver, AVAST Software)

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

vous comprenez quelque chose ?

il semblerait que ce soit avast . j'ai fait la MAJ . vous pensez que sa ira ?

tu devrais commencer par ça oui

l'informatique c'est bien quand ça marche, quand ça marche pas ça peut venir de tellement de choses... parfois ça requiert pas mal d'explication, ça prend du temps... t'auras probablement pas la réponse toute faites ici, à moins d'un coup de chance, il faut faire des essais et encore des essais (en cherchant sur le net) jusqu'à trouver la solution :/

étape par étape, petit à petit en essayant de comprendre la logique

met à jour avast oui, puis les drivers, désinstalles ce que tu as installé en dernier (c'est logiquement ce qui a apporté le problème)

Devinez quoi ... j'ai encore eu un ecran bleu , s'est arrivé en lancant Lost PLanet 2 Justement .

windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
CPU: GenuineIntel Intel(R) Core(TM) i7-2600 CPU @ 3.40GHz Intel586, level: 6
8 logical processors, active mask: 255
RAM: 8571027456 total
VM: 2147352576, free: 1954234368

--------------------------------------------------
------------------------------
Crash Dump Analysis

--------------------------------------------------
------------------------------

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Sun 20/05/2012 13:57:14 GMT your computer crashed
crash dump file: C:\Windows\Minidump\052012-17940-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0x50 (0xFFFFFA800D712AC0, 0x1, 0xFFFFF88007BB4B52, 0x2)
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 which cannot be identified at this time.

On Sun 20/05/2012 13:57:14 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: gcdbus.sys (gcdbus+0x3B52)
Bugcheck code: 0x50 (0xFFFFFA800D712AC0, 0x1, 0xFFFFF88007BB4B52, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\drivers\gcdbus.sys
product: gcdbus
company: Power Software Ltd
description: gBurner Virtual Drive
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.
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: gcdbus.sys (gBurner Virtual Drive, Power Software Ltd).
Google query: gcdbus.sys Power Software Ltd PAGE_FAULT_IN_NONPAGED_AREA

On Sun 20/05/2012 10:23:43 GMT your computer crashed
crash dump file: C:\Windows\Minidump\052012-16988-01.dmp
This was probably caused by the following module: fltmgr.sys (fltmgr+0x249BD)
Bugcheck code: 0x19 (0x20, 0xFFFFFA800972C4C0, 0xFFFFFA800972C580, 0xC0C0001)
Error: BAD_POOL_HEADER
file path: C:\Windows\system32\drivers\fltmgr.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Gestionnaire de filtres de système de fichiers Microsoft
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 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 20/05/2012 10:03:23 GMT your computer crashed
crash dump file: C:\Windows\Minidump\052012-17144-01.dmp
This was probably caused by the following module: fltmgr.sys (fltmgr+0x249BD)
Bugcheck code: 0x19 (0x20, 0xFFFFFA800791E5C0, 0xFFFFFA800791E680, 0xC0C0005)
Error: BAD_POOL_HEADER
file path: C:\Windows\system32\drivers\fltmgr.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Gestionnaire de filtres de système de fichiers Microsoft
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 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 20/05/2012 09:56:30 GMT your computer crashed
crash dump file: C:\Windows\Minidump\052012-17830-01.dmp
This was probably caused by the following module: fltmgr.sys (fltmgr+0x249BD)
Bugcheck code: 0x19 (0x20, 0xFFFFFA80078AD780, 0xFFFFFA80078AD840, 0xC0C0008)
Error: BAD_POOL_HEADER
file path: C:\Windows\system32\drivers\fltmgr.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Gestionnaire de filtres de système de fichiers Microsoft
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 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 Sat 19/05/2012 22:45:39 GMT your computer crashed
crash dump file: C:\Windows\Minidump\052012-21481-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0x50 (0xFFFFFA800DE09400, 0x1, 0xFFFFF88007699B52, 0x2)
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 which cannot be identified at this time.

On Fri 18/05/2012 18:31:21 GMT your computer crashed
crash dump file: C:\Windows\Minidump\051812-61635-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0x34 (0x50853, 0xFFFFF88009CE03E8, 0xFFFFF88009CDFC40, 0xFFFFF800038920EE)
Error: CACHE_MANAGER
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 problem occurred in the file system's cache manager.
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 which cannot be identified at this time.

On Fri 18/05/2012 16:08:26 GMT your computer crashed
crash dump file: C:\Windows\Minidump\051812-45474-01.dmp
This was probably caused by the following module: tcpip.sys (tcpip+0x82ACE)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF88001965ACE, 0xFFFFF8800358D5F8, 0xFFFFF8800358CE50)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\tcpip.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote TCP/IP
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.

On Fri 18/05/2012 13:56:53 GMT your computer crashed
crash dump file: C:\Windows\Minidump\051812-26098-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0x50 (0xFFFFFA800D4F42C0, 0x1, 0xFFFFF88000CC3B52, 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 which cannot be identified at this time.

On Wed 02/05/2012 18:49:14 GMT your computer crashed
crash dump file: C:\Windows\Minidump\050212-27612-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x350CA6)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF80003BA6CA6, 0xFFFFF880035A2868, 0xFFFFF880035A20C0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
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 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 the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.

On Wed 02/05/2012 18:43:45 GMT your computer crashed
crash dump file: C:\Windows\Minidump\050212-32838-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC80)
Bugcheck code: 0x50 (0xFFFFFA800F823340, 0x1, 0xFFFFF88000E6DB52, 0x2)
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 which cannot be identified at this time.

On Sat 21/04/2012 19:05:08 GMT your computer crashed
crash dump file: C:\Windows\Minidump\042112-59249-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC80)
Bugcheck code: 0x50 (0xFFFFFA8013E07040, 0x1, 0xFFFFF8800F403B52, 0x2)
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 which cannot be identified at this time.

On Wed 21/03/2012 06:02:17 GMT your computer crashed
crash dump file: C:\Windows\Minidump\032112-18735-01.dmp
This was probably caused by the following module: aswsnx.sys (aswSnx+0x460B8)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF880041150B8, 0xFFFFF8800B874ED0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\drivers\aswsnx.sys
product: avast! Antivirus System
company: AVAST Software
description: avast! Virtualization Driver
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.
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: aswsnx.sys (avast! Virtualization Driver, AVAST Software).
Google query: aswsnx.sys AVAST Software SYSTEM_SERVICE_EXCEPTION

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

--------------------------------------------------
------------------------------

13 crash dumps have been found and analyzed. 2 third party drivers have 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:

aswsnx.sys (avast! Virtualization Driver, AVAST Software)

gcdbus.sys (gBurner Virtual Drive, Power Software Ltd)

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.

le probleme serait du a Gburner ...

comment je dois procédées ?

StarForce9
Posté le 20 mai 2012 à 15:25:52
elles chauffent beaucoup les nvidia

ma 7850 est a 30°C au repos

c'est un troll de faire une generalité...les 460 chauffent mais une 670/680 dcu est à 25°c en idle...
mais bon t'en es pas à ton coup d'essai en matiere de troll

heu ... ouai mais sa serait possible de me repondre SVP

Ma 460 monte à 82 donc normal. Le proco par contre trop trop chaud.

le proco est trop chaud . donc sa peut le bousiller a long terme ?

peut être... mais surtout il peu diminuer sa fréquence pour diminuer sa chaleur et te faire perdre des performances.

passe faudrais que tu passe cette nuit un coup de memtest a tes barrette de ram semblerai qu'il aurait peut être un souci avec

et comment eviter sa ?