J'ai depuis ces 5 derniers jours de gros problème avec GTA Episode from liberty city des que je le lance le pc fige et le son se répète en boucle, la même chose dans j'appuie sur la touche imp écran (?). Je suis sur un pc fixe et j'ai déjà eu 1 blue screen avant ces 5 derniers jours.

La touche imp écran marche sur le clavier virtuel.

J'ai pas de restauration avant le 01/08/14 et celle ci ne résous pas mon problème

Une solution j'ai vraiment besoin de GTA pour vendredi.

Bon alors dl ce petit log il analyse les écrans bleus :

http://www.resplendence.com/download/whocrashedSetup.exe

Une fois lancé tu cliques sur analyses en haut , une fois fini tu vas recevoir le message suivant :

Please scroll down .....

Et tu vas me copier/coller tout ce qui est indiqué en dessous de Crash Dump Analysis ds le logiciel en allant voir vers le bas

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

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Sun 27/07/2014 00:51:53 GMT your computer crashed
crash dump file: C:\Windows\Minidump\072714-27453-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0xC6483)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF96000166483, 0xFFFFF8800673C070, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\win32k.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote Win32 multi-utilisateurs
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 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 Sun 27/07/2014 00:51:53 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: win32k.sys (win32k+0xC6483)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF96000166483, 0xFFFFF8800673C070, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\win32k.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote Win32 multi-utilisateurs
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 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.

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

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

2 crash dumps have been found and analyzed. No offending third party drivers have been found. Connsider using WhoCrashed Professional which offers more detailed analysis using symbol resolution. Also configuring your system to produce a full memory dump may help you.

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.

Essaie de mettre à jour ton pilote de carte graphique

Il est a jour

Problème résolu

il faut faire bcdedit /debug OFF

• Dans le cmd en admin et redémarrer apres