Bonsoir,
Tout d'abord désolé de passer de la case "inscription" à la case "veuillez m'aider j'ai un problème".
Je rencontre actuellement un dysfonctionnement sur mon PC puisque celui-ci m'affiche de manière aléatoire des écrans bleus.
J'ai fais des recherches de mon coté, mais rien de spécialement concluant.
J'ai installé "WhoCrashed" pour obtenir davantage d'informations en ce qui concerne le rapport d'erreur généré avec ces écrans bleus, et les voici :
Crash dump file: C:\Windows\Minidump0514-22214-01.dmp
Date/time: 05/01/2014 18:26:55 GMT
Uptime: 05:48:07
Machine: NICOLAS-PC
Bug check name: PAGE_FAULT_IN_NONPAGED_AREA
Bug check code: 0x50
Bug check parm 1: 0xFFFFF900C0165900
Bug check parm 2: 0x0
Bug check parm 3: 0xFFFFF960000983ED
Bug check parm 4: 0x0
Probably caused by: win32k.sys
Driver description: Pilote Win32 multi-utilisateurs
Driver product: Système d’exploitation Microsoft® Windows®
Driver company: Microsoft Corporation
OS build: Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Architecture: x64 (64 bit)
CPU count: 4
Page size: 4096
Bug check description:
This indicates that invalid system memory has been referenced.
Comments:
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.
Crash dump file: C:\Windows\Minidump0814-21621-01.dmp
Date/time: 08/01/2014 22:08:03 GMT
Uptime: 04:51:51
Machine: NICOLAS-PC
Bug check name: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
Bug check code: 0x1000007E
Bug check parm 1: 0xFFFFFFFFC0000005
Bug check parm 2: 0xFFFFF88003CB8D3C
Bug check parm 3: 0xFFFFF880033AF9A8
Bug check parm 4: 0xFFFFF880033AF200
Probably caused by: idmwfp.sys
Driver description: Internet Download Manager WFP Driver
Driver product: Internet Download Manager
Driver company: Tonec Inc.
OS build: Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Architecture: x64 (64 bit)
CPU count: 4
Page size: 4096
Bug check description:
This indicates that a system thread generated an exception which the error handler did not catch.
Comments:
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: idmwfp.sys (Internet Download Manager WFP Driver, Tonec Inc.).
Crash dump file: C:\Windows\Minidump2214-14820-01.dmp
Date/time: 22/01/2014 21:02:04 GMT
Uptime: 00:50:31
Machine: NICOLAS-PC
Bug check name: SYSTEM_SERVICE_EXCEPTION
Bug check code: 0x3B
Bug check parm 1: 0xC0000005
Bug check parm 2: 0xFFFFF9600027C9ED
Bug check parm 3: 0xFFFFF88005320100
Bug check parm 4: 0x0
Probably caused by: win32k.sys
Driver description: Pilote Win32 multi-utilisateurs
Driver product: Système d’exploitation Microsoft® Windows®
Driver company: Microsoft Corporation
OS build: Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Architecture: x64 (64 bit)
CPU count: 4
Page size: 4096
Bug check description:
This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
Comments:
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.
Crash dump file: C:\Windows\Minidump2714-14554-01.dmp
Date/time: 27/01/2014 17:45:15 GMT
Uptime: 01:12:37
Machine: NICOLAS-PC
Bug check name: SYSTEM_SERVICE_EXCEPTION
Bug check code: 0x3B
Bug check parm 1: 0xC0000005
Bug check parm 2: 0xFFFFF96000174283
Bug check parm 3: 0xFFFFF880053F8020
Bug check parm 4: 0x0
Probably caused by: win32k.sys
Driver description: Pilote Win32 multi-utilisateurs
Driver product: Système d’exploitation Microsoft® Windows®
Driver company: Microsoft Corporation
OS build: Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Architecture: x64 (64 bit)
CPU count: 4
Page size: 4096
Bug check description:
This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
Comments:
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.
Crash dump file: C:\Windows\Minidump2814-20670-01.dmp
Date/time: 28/01/2014 19:32:15 GMT
Uptime: 03:09:59
Machine: NICOLAS-PC
Bug check name: PAGE_FAULT_IN_NONPAGED_AREA
Bug check code: 0x50
Bug check parm 1: 0xFFFFF900C2A48CF0
Bug check parm 2: 0x0
Bug check parm 3: 0xFFFFF9600029C69D
Bug check parm 4: 0x0
Probably caused by: win32k.sys
Driver description: Pilote Win32 multi-utilisateurs
Driver product: Système d’exploitation Microsoft® Windows®
Driver company: Microsoft Corporation
OS build: Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Architecture: x64 (64 bit)
CPU count: 4
Page size: 4096
Bug check description:
This indicates that invalid system memory has been referenced.
Comments:
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.
Crash dump file: C:\Windows\memory.dmp
Date/time: 30/01/2014 21:38:31 GMT
Uptime: 05:04:58
Machine: NICOLAS-PC
Bug check name: SYSTEM_SERVICE_EXCEPTION
Bug check code: 0x3B
Bug check parm 1: 0xC0000005
Bug check parm 2: 0xFFFFF960002AC46E
Bug check parm 3: 0xFFFFF880052A6F00
Bug check parm 4: 0x0
Probably caused by: win32k.sys
Driver description: Pilote Win32 multi-utilisateurs
Driver product: Système d’exploitation Microsoft® Windows®
Driver company: Microsoft Corporation
OS build: Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Architecture: x64 (64 bit)
CPU count: 4
Page size: 4096
Bug check description:
This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
Comments:
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.
Le PC tourne très bien depuis son achat (environ 3ans). Le dernier matériel acheté -> 2 barettes de ram (identiques aux premières, achetées il y a environ 6 mois).
Après l'installation des barrettes, j'ai eu quelques quelques écrans bleus les premiers jours. J'ai donc fait un memtest (en attendant des heures qu'il se termine pour finalement me rendre compte qu'il bouclait et faisait plusieurs passages...) et résultat : 0 erreur.
J'ai formaté mon Windows et ensuite, plus de problème.
L'ennui c'est donc que depuis fin décembre, j'ai à nouveau des écrans bleus, et les rapport d'erreur de m'aide pas des masses, vu que les causes sont souvent différentes.
J'ai fais un memtest le 28/01 : 1 passage = 0 erreur.
J'ai réinstallé mon pilote nvidia fin décembre de tête, au début des écrans bleus , ça persiste.
Je précise que l'utilisation que je fais de mon PC est différente à chaque écran bleu pratiquement (alt+tab dans un jeu et je réduis mon raidcall -> écran bleu, je ferme ma VM -> écran bleu , ou parfois je navigue sur la toile -> écran bleu).
Pourriez-vous m'aiguiller afin que je puisse résoudre ce problème?
Tout d'abord désolé de passer de la case "inscription" à la case "veuillez m'aider j'ai un problème".
Je rencontre actuellement un dysfonctionnement sur mon PC puisque celui-ci m'affiche de manière aléatoire des écrans bleus.
J'ai fais des recherches de mon coté, mais rien de spécialement concluant.
J'ai installé "WhoCrashed" pour obtenir davantage d'informations en ce qui concerne le rapport d'erreur généré avec ces écrans bleus, et les voici :
Citation:
Crash dump file: C:\Windows\Minidump0514-22214-01.dmp
Date/time: 05/01/2014 18:26:55 GMT
Uptime: 05:48:07
Machine: NICOLAS-PC
Bug check name: PAGE_FAULT_IN_NONPAGED_AREA
Bug check code: 0x50
Bug check parm 1: 0xFFFFF900C0165900
Bug check parm 2: 0x0
Bug check parm 3: 0xFFFFF960000983ED
Bug check parm 4: 0x0
Probably caused by: win32k.sys
Driver description: Pilote Win32 multi-utilisateurs
Driver product: Système d’exploitation Microsoft® Windows®
Driver company: Microsoft Corporation
OS build: Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Architecture: x64 (64 bit)
CPU count: 4
Page size: 4096
Bug check description:
This indicates that invalid system memory has been referenced.
Comments:
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.
Citation:
Crash dump file: C:\Windows\Minidump0814-21621-01.dmp
Date/time: 08/01/2014 22:08:03 GMT
Uptime: 04:51:51
Machine: NICOLAS-PC
Bug check name: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
Bug check code: 0x1000007E
Bug check parm 1: 0xFFFFFFFFC0000005
Bug check parm 2: 0xFFFFF88003CB8D3C
Bug check parm 3: 0xFFFFF880033AF9A8
Bug check parm 4: 0xFFFFF880033AF200
Probably caused by: idmwfp.sys
Driver description: Internet Download Manager WFP Driver
Driver product: Internet Download Manager
Driver company: Tonec Inc.
OS build: Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Architecture: x64 (64 bit)
CPU count: 4
Page size: 4096
Bug check description:
This indicates that a system thread generated an exception which the error handler did not catch.
Comments:
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: idmwfp.sys (Internet Download Manager WFP Driver, Tonec Inc.).
Citation:
Crash dump file: C:\Windows\Minidump2214-14820-01.dmp
Date/time: 22/01/2014 21:02:04 GMT
Uptime: 00:50:31
Machine: NICOLAS-PC
Bug check name: SYSTEM_SERVICE_EXCEPTION
Bug check code: 0x3B
Bug check parm 1: 0xC0000005
Bug check parm 2: 0xFFFFF9600027C9ED
Bug check parm 3: 0xFFFFF88005320100
Bug check parm 4: 0x0
Probably caused by: win32k.sys
Driver description: Pilote Win32 multi-utilisateurs
Driver product: Système d’exploitation Microsoft® Windows®
Driver company: Microsoft Corporation
OS build: Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Architecture: x64 (64 bit)
CPU count: 4
Page size: 4096
Bug check description:
This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
Comments:
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.
Citation:
Crash dump file: C:\Windows\Minidump2714-14554-01.dmp
Date/time: 27/01/2014 17:45:15 GMT
Uptime: 01:12:37
Machine: NICOLAS-PC
Bug check name: SYSTEM_SERVICE_EXCEPTION
Bug check code: 0x3B
Bug check parm 1: 0xC0000005
Bug check parm 2: 0xFFFFF96000174283
Bug check parm 3: 0xFFFFF880053F8020
Bug check parm 4: 0x0
Probably caused by: win32k.sys
Driver description: Pilote Win32 multi-utilisateurs
Driver product: Système d’exploitation Microsoft® Windows®
Driver company: Microsoft Corporation
OS build: Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Architecture: x64 (64 bit)
CPU count: 4
Page size: 4096
Bug check description:
This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
Comments:
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.
Citation:
Crash dump file: C:\Windows\Minidump2814-20670-01.dmp
Date/time: 28/01/2014 19:32:15 GMT
Uptime: 03:09:59
Machine: NICOLAS-PC
Bug check name: PAGE_FAULT_IN_NONPAGED_AREA
Bug check code: 0x50
Bug check parm 1: 0xFFFFF900C2A48CF0
Bug check parm 2: 0x0
Bug check parm 3: 0xFFFFF9600029C69D
Bug check parm 4: 0x0
Probably caused by: win32k.sys
Driver description: Pilote Win32 multi-utilisateurs
Driver product: Système d’exploitation Microsoft® Windows®
Driver company: Microsoft Corporation
OS build: Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Architecture: x64 (64 bit)
CPU count: 4
Page size: 4096
Bug check description:
This indicates that invalid system memory has been referenced.
Comments:
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.
Citation:
Crash dump file: C:\Windows\memory.dmp
Date/time: 30/01/2014 21:38:31 GMT
Uptime: 05:04:58
Machine: NICOLAS-PC
Bug check name: SYSTEM_SERVICE_EXCEPTION
Bug check code: 0x3B
Bug check parm 1: 0xC0000005
Bug check parm 2: 0xFFFFF960002AC46E
Bug check parm 3: 0xFFFFF880052A6F00
Bug check parm 4: 0x0
Probably caused by: win32k.sys
Driver description: Pilote Win32 multi-utilisateurs
Driver product: Système d’exploitation Microsoft® Windows®
Driver company: Microsoft Corporation
OS build: Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Architecture: x64 (64 bit)
CPU count: 4
Page size: 4096
Bug check description:
This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
Comments:
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.
Après l'installation des barrettes, j'ai eu quelques quelques écrans bleus les premiers jours. J'ai donc fait un memtest (en attendant des heures qu'il se termine pour finalement me rendre compte qu'il bouclait et faisait plusieurs passages...) et résultat : 0 erreur.
J'ai formaté mon Windows et ensuite, plus de problème.
L'ennui c'est donc que depuis fin décembre, j'ai à nouveau des écrans bleus, et les rapport d'erreur de m'aide pas des masses, vu que les causes sont souvent différentes.
J'ai fais un memtest le 28/01 : 1 passage = 0 erreur.
J'ai réinstallé mon pilote nvidia fin décembre de tête, au début des écrans bleus , ça persiste.
Je précise que l'utilisation que je fais de mon PC est différente à chaque écran bleu pratiquement (alt+tab dans un jeu et je réduis mon raidcall -> écran bleu, je ferme ma VM -> écran bleu , ou parfois je navigue sur la toile -> écran bleu).
Pourriez-vous m'aiguiller afin que je puisse résoudre ce problème?
Aucun commentaire:
Enregistrer un commentaire