BlueScreen
Résolu
marley230
Messages postés
36
Date d'inscription
Statut
Membre
Dernière intervention
-
marley230 Messages postés 36 Date d'inscription Statut Membre Dernière intervention -
marley230 Messages postés 36 Date d'inscription Statut Membre Dernière intervention -
Bonjour, j'ai un petit soucis depuis plusieurs semaines , quand je suis sur mon ordinateur , peu importe ce que je fais , c'est aléatoire , d'un coup , bluescreen .
j'ai tenter une restau système mais je n'ai pas de point de restau anterieur au probleme :/
J'suis Sous Vista Pro 32 bits . Voila plus d'info sur le problème :
Signature du problème :
Nom d'événement de problème: BlueScreen
Version du système: 6.0.6002.2.2.0.256.6
Identificateur de paramètres régionaux: 1036
Informations supplémentaires sur le problème :
BCCode: c2
BCP1: 00000007
BCP2: 0000110B
BCP3: 000000F8
BCP4: FDD31BF0
OS Version: 6_0_6002
Service Pack: 2_0
Product: 256_1
Fichiers aidant à décrire le problème :
C:\Windows\Minidump\Mini072612-01.dmp
C:\Users\Vista\AppData\Local\Temp\WER-1356968-0.sysdata.xml
C:\Users\Vista\AppData\Local\Temp\WERE52E.tmp.version.txt
Car je suis sur le point d'réinstaller ma partition , mais je voulais connaitre une eventuelle solution au problème ^^
j'ai tenter une restau système mais je n'ai pas de point de restau anterieur au probleme :/
J'suis Sous Vista Pro 32 bits . Voila plus d'info sur le problème :
Signature du problème :
Nom d'événement de problème: BlueScreen
Version du système: 6.0.6002.2.2.0.256.6
Identificateur de paramètres régionaux: 1036
Informations supplémentaires sur le problème :
BCCode: c2
BCP1: 00000007
BCP2: 0000110B
BCP3: 000000F8
BCP4: FDD31BF0
OS Version: 6_0_6002
Service Pack: 2_0
Product: 256_1
Fichiers aidant à décrire le problème :
C:\Windows\Minidump\Mini072612-01.dmp
C:\Users\Vista\AppData\Local\Temp\WER-1356968-0.sysdata.xml
C:\Users\Vista\AppData\Local\Temp\WERE52E.tmp.version.txt
Car je suis sur le point d'réinstaller ma partition , mais je voulais connaitre une eventuelle solution au problème ^^
A voir également:
- BlueScreen
- Bluescreen - Guide
- BlueScreen - Windows 11
- BlueScreen ✓ - Forum Windows
- BlueScreen ✓ - Forum Windows 7
- Video_tdr_error (bluescreen) - Forum Matériel & Système
5 réponses
Merci le logiciel , voila les infos qu'il me donne :
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Tue 07/08/2012 16:45:54 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini080712-02.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x5AD54)
Bugcheck code: 0xA (0xFFFFFFFF88000008, 0x2, 0x1, 0xFFFFFFFF81AD6A79)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntkrnlpa.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 07/08/2012 16:45:54 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrpamp.exe (nt!Kei386EoiHelper+0x293C)
Bugcheck code: 0xA (0xFFFFFFFF88000008, 0x2, 0x1, 0xFFFFFFFF81AD6A79)
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.
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: ntkrpamp.exe .
Google query: ntkrpamp.exe IRQL_NOT_LESS_OR_EQUAL
On Tue 07/08/2012 14:04:23 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini080712-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0xA5125)
Bugcheck code: 0x50 (0xFFFFFFFFA3FB1DD0, 0x0, 0xFFFFFFFF81A61A2A, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\ntkrnlpa.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 Mon 06/08/2012 20:31:51 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini080612-02.dmp
This was probably caused by the following module: dxgkrnl.sys (dxgkrnl+0x22FFC)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFFFFF8D8F6FFC, 0xFFFFFFFF989D9B08, 0xFFFFFFFF989D9804)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
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 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 Mon 06/08/2012 20:06:18 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini080612-01.dmp
This was probably caused by the following module: dxgkrnl.sys (dxgkrnl+0x22FFC)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFFFFF8DAEFFFC, 0xFFFFFFFF8A1EFB08, 0xFFFFFFFF8A1EF804)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
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 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 Sun 05/08/2012 20:26:03 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini080512-02.dmp
This was probably caused by the following module: dxgkrnl.sys (dxgkrnl+0x2858E)
Bugcheck code: 0xC2 (0x7, 0x110B, 0x1, 0xFFFFFFFF83DF0418)
Error: BAD_POOL_CALLER
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 the current thread is making a bad pool request.
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 Sat 04/08/2012 23:21:52 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini080512-01.dmp
This was probably caused by the following module: watchdog.sys (watchdog+0x1230)
Bugcheck code: 0x113 (0x4, 0xFFFFFFFF83F69848, 0x0, 0x0)
Error: VIDEO_DXGKRNL_FATAL_ERROR
file path: C:\Windows\system32\drivers\watchdog.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Watchdog Driver
Bug check description: This indicates that the dxg kernel has detected a violation.
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
--------------------------------------------------------------------------------
7 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:
ntkrpamp.exe
Je comprend pas tout ce qu'il y a d'écrit si quelqu'un sait ce que je doit faire la réponse est la bienvenue ^^
Ce que je trouve bizarre, c'est même après un formatage et une réinstallation windows donc retour au réglages d'origine , les bluescreen persiste ! et un un autre genre de beug : ecran qui ce bloque et qui ce brouille .
Une petite idée ? ^^
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Tue 07/08/2012 16:45:54 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini080712-02.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x5AD54)
Bugcheck code: 0xA (0xFFFFFFFF88000008, 0x2, 0x1, 0xFFFFFFFF81AD6A79)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntkrnlpa.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 07/08/2012 16:45:54 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrpamp.exe (nt!Kei386EoiHelper+0x293C)
Bugcheck code: 0xA (0xFFFFFFFF88000008, 0x2, 0x1, 0xFFFFFFFF81AD6A79)
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.
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: ntkrpamp.exe .
Google query: ntkrpamp.exe IRQL_NOT_LESS_OR_EQUAL
On Tue 07/08/2012 14:04:23 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini080712-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0xA5125)
Bugcheck code: 0x50 (0xFFFFFFFFA3FB1DD0, 0x0, 0xFFFFFFFF81A61A2A, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\ntkrnlpa.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 Mon 06/08/2012 20:31:51 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini080612-02.dmp
This was probably caused by the following module: dxgkrnl.sys (dxgkrnl+0x22FFC)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFFFFF8D8F6FFC, 0xFFFFFFFF989D9B08, 0xFFFFFFFF989D9804)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
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 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 Mon 06/08/2012 20:06:18 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini080612-01.dmp
This was probably caused by the following module: dxgkrnl.sys (dxgkrnl+0x22FFC)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFFFFF8DAEFFFC, 0xFFFFFFFF8A1EFB08, 0xFFFFFFFF8A1EF804)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
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 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 Sun 05/08/2012 20:26:03 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini080512-02.dmp
This was probably caused by the following module: dxgkrnl.sys (dxgkrnl+0x2858E)
Bugcheck code: 0xC2 (0x7, 0x110B, 0x1, 0xFFFFFFFF83DF0418)
Error: BAD_POOL_CALLER
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 the current thread is making a bad pool request.
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 Sat 04/08/2012 23:21:52 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini080512-01.dmp
This was probably caused by the following module: watchdog.sys (watchdog+0x1230)
Bugcheck code: 0x113 (0x4, 0xFFFFFFFF83F69848, 0x0, 0x0)
Error: VIDEO_DXGKRNL_FATAL_ERROR
file path: C:\Windows\system32\drivers\watchdog.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Watchdog Driver
Bug check description: This indicates that the dxg kernel has detected a violation.
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
--------------------------------------------------------------------------------
7 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:
ntkrpamp.exe
Je comprend pas tout ce qu'il y a d'écrit si quelqu'un sait ce que je doit faire la réponse est la bienvenue ^^
Ce que je trouve bizarre, c'est même après un formatage et une réinstallation windows donc retour au réglages d'origine , les bluescreen persiste ! et un un autre genre de beug : ecran qui ce bloque et qui ce brouille .
Une petite idée ? ^^
up ? ^^^
J'peut plus rien faire avec mon ordinateur je peut avoir plus de 5 blue screen en 1 h
J'peut plus rien faire avec mon ordinateur je peut avoir plus de 5 blue screen en 1 h
Re-Bonjour ! merci Edawards pour ton lien sa m'avance pas pour savoir comment réparer ce problème mais il m'a apporter de nombreuse info precieuse !
Grace au logiciel WinDBG expliqué sur ton lien , j'ai pu decouvrir les rapport derreur ( si je ne me trompe pas ) des blue screen ( minidump )
En utilisant la commande open Crash Dump ( qui m'emmène dans le dossier windows > Minidump )
Une liste de fichier appelés
la plupart Mini090812-01.dmp
ou Mini090812-02.dmp
Mini090812-03.dmp
(les chiffres suivant le mot Mini indique la date , ce qui me donne aussi l'heure dans les infos fichier la date et l'heure des fichier colle parfaitement aux moments ou j'ai eux mes blues screens )
j'en ouvre un au hasard et je tombre sur ce genre de fenêtre
http://imageshack.com/f/41erreurj
tous en bas de ce genre de fenêtre il y à systématiquement écrit
Probably caused by : suivi du nom du fichier
et
Followup: MachineOwner
Alors voici les fichier mit en cause de tout mes mini.dmp :
Probably caused by : dxgkrnl.sys ( dxgkrnl+1f09 )
Probably caused by : dxgkrnl.sys ( dxgkrnl+2858e )
Probably caused by : dxgkrnl.sys ( dxgkrnl+2858e )
Probably caused by : ntkrnlpa.exe ( nt+3dc7d )
Probably caused by : dxgkrnl.sys ( dxgkrnl+1f09 )
Probably caused by : dxgkrnl.sys ( dxgkrnl+2858e )
Probably caused by : dxgkrnl.sys ( dxgkrnl+22ffc )
Probably caused by : dxgkrnl.sys ( dxgkrnl+22ffc )
Probably caused by : ntkrnlpa.exe ( nt+57a2a )
Probably caused by : ntkrnlpa.exe ( nt+a2a79 )
Probably caused by : ntkrnlpa.exe ( nt+cd1cb )
Probably caused by : ntkrnlpa.exe ( nt+57a2a )
Probably caused by : ntkrnlpa.exe ( nt+57a2a )
Probably caused by : dxgkrnl.sys ( dxgkrnl+22ff8 )
Probably caused by : win32k.sys ( win32k+adb39 )
Probably caused by : win32k.sys ( win32k+c1cfa )
Probably caused by : ntkrnlpa.exe ( nt+b34a8 )
Probably caused by : ntkrnlpa.exe ( nt+af2a8 )
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
Probably caused by : ecache.sys ( ecache+af9f )
Probably caused by : dxgkrnl.sys ( dxgkrnl+2858e )
Probably caused by : dxgkrnl.sys ( dxgkrnl+285b6 )
Probably caused by : dxgkrnl.sys ( dxgkrnl+2d419 )
Probably caused by : ecache.sys ( ecache+d51d )
Probably caused by : ntkrnlpa.exe ( nt+cd1cb )
Probably caused by : win32k.sys ( win32k+d3574 )
Probably caused by : ntkrnlpa.exe ( nt+21d67b )
Probably caused by : ntkrnlpa.exe ( nt+37ee0 )
Probably caused by : ecache.sys ( ecache+af9f )
Probably caused by : raspptp.sys ( raspptp+cc84 )
Probably caused by : dxgkrnl.sys ( dxgkrnl+2d3be )
Probably caused by : win32k.sys ( win32k+c4807 )
Probably caused by : ntkrnlpa.exe ( nt+3dc7d )
Probably caused by : dxgkrnl.sys ( dxgkrnl+8f0fc )
Probably caused by : ntkrnlpa.exe ( nt+57a2a )
Probably caused by : dxgkrnl.sys ( dxgkrnl+2d419 )
Probably caused by : dxgkrnl.sys ( dxgkrnl+2d419 )
Followup: MachineOwner
sauf un qu'il n'a pas réussi a identifier
je les ai trouver dans les fichiers windows
ecache.sys : http://imageshack.com/f/1qecachesysj
raspptp.sys : http://imageshack.com/f/6craspptpsysj
win32k.sys : http://imageshack.com/f/5ywin32ksysj
dxgkrnl.sys : http://imageshack.com/f/5brecherchedxgkrnlsysj
ntkrnlpa.exe : http://imageshack.com/f/n7ntkrnlpaexej
Voila tout , avec cela je ne sais que faire de ces fichiers pour supprimé leur anomalies , si quelqu'un à déja eu a faire avec sa , les réponse sont les bienvenue :) ^^
merci
Grace au logiciel WinDBG expliqué sur ton lien , j'ai pu decouvrir les rapport derreur ( si je ne me trompe pas ) des blue screen ( minidump )
En utilisant la commande open Crash Dump ( qui m'emmène dans le dossier windows > Minidump )
Une liste de fichier appelés
la plupart Mini090812-01.dmp
ou Mini090812-02.dmp
Mini090812-03.dmp
(les chiffres suivant le mot Mini indique la date , ce qui me donne aussi l'heure dans les infos fichier la date et l'heure des fichier colle parfaitement aux moments ou j'ai eux mes blues screens )
j'en ouvre un au hasard et je tombre sur ce genre de fenêtre
http://imageshack.com/f/41erreurj
tous en bas de ce genre de fenêtre il y à systématiquement écrit
Probably caused by : suivi du nom du fichier
et
Followup: MachineOwner
Alors voici les fichier mit en cause de tout mes mini.dmp :
Probably caused by : dxgkrnl.sys ( dxgkrnl+1f09 )
Probably caused by : dxgkrnl.sys ( dxgkrnl+2858e )
Probably caused by : dxgkrnl.sys ( dxgkrnl+2858e )
Probably caused by : ntkrnlpa.exe ( nt+3dc7d )
Probably caused by : dxgkrnl.sys ( dxgkrnl+1f09 )
Probably caused by : dxgkrnl.sys ( dxgkrnl+2858e )
Probably caused by : dxgkrnl.sys ( dxgkrnl+22ffc )
Probably caused by : dxgkrnl.sys ( dxgkrnl+22ffc )
Probably caused by : ntkrnlpa.exe ( nt+57a2a )
Probably caused by : ntkrnlpa.exe ( nt+a2a79 )
Probably caused by : ntkrnlpa.exe ( nt+cd1cb )
Probably caused by : ntkrnlpa.exe ( nt+57a2a )
Probably caused by : ntkrnlpa.exe ( nt+57a2a )
Probably caused by : dxgkrnl.sys ( dxgkrnl+22ff8 )
Probably caused by : win32k.sys ( win32k+adb39 )
Probably caused by : win32k.sys ( win32k+c1cfa )
Probably caused by : ntkrnlpa.exe ( nt+b34a8 )
Probably caused by : ntkrnlpa.exe ( nt+af2a8 )
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
Probably caused by : ecache.sys ( ecache+af9f )
Probably caused by : dxgkrnl.sys ( dxgkrnl+2858e )
Probably caused by : dxgkrnl.sys ( dxgkrnl+285b6 )
Probably caused by : dxgkrnl.sys ( dxgkrnl+2d419 )
Probably caused by : ecache.sys ( ecache+d51d )
Probably caused by : ntkrnlpa.exe ( nt+cd1cb )
Probably caused by : win32k.sys ( win32k+d3574 )
Probably caused by : ntkrnlpa.exe ( nt+21d67b )
Probably caused by : ntkrnlpa.exe ( nt+37ee0 )
Probably caused by : ecache.sys ( ecache+af9f )
Probably caused by : raspptp.sys ( raspptp+cc84 )
Probably caused by : dxgkrnl.sys ( dxgkrnl+2d3be )
Probably caused by : win32k.sys ( win32k+c4807 )
Probably caused by : ntkrnlpa.exe ( nt+3dc7d )
Probably caused by : dxgkrnl.sys ( dxgkrnl+8f0fc )
Probably caused by : ntkrnlpa.exe ( nt+57a2a )
Probably caused by : dxgkrnl.sys ( dxgkrnl+2d419 )
Probably caused by : dxgkrnl.sys ( dxgkrnl+2d419 )
Followup: MachineOwner
sauf un qu'il n'a pas réussi a identifier
je les ai trouver dans les fichiers windows
ecache.sys : http://imageshack.com/f/1qecachesysj
raspptp.sys : http://imageshack.com/f/6craspptpsysj
win32k.sys : http://imageshack.com/f/5ywin32ksysj
dxgkrnl.sys : http://imageshack.com/f/5brecherchedxgkrnlsysj
ntkrnlpa.exe : http://imageshack.com/f/n7ntkrnlpaexej
Voila tout , avec cela je ne sais que faire de ces fichiers pour supprimé leur anomalies , si quelqu'un à déja eu a faire avec sa , les réponse sont les bienvenue :) ^^
merci
Bonjour,
Voir ceci également :
https://forum.zebulon.fr/topic/55305-comment-reparer-lerreur-minidump
Voir ceci également :
https://forum.zebulon.fr/topic/55305-comment-reparer-lerreur-minidump
Vous n’avez pas trouvé la réponse que vous recherchez ?
Posez votre question
