Bonjour les pros !
Depuis plusieurs jours j'ai des crashs sous Seven 32, l'écran se brouille de lignes colorées, passage par un bel écran bleu (wahouu ça rappelle W98 !), et finalement reboot.
La carte graphique ne chauffe à priori pas (une Radeon HD6700), les pilotes et autres sont à jour (CG, CM, MàJ Windows), Antivir et Spybot n'ont rien détecté d'anormal.
Je vous met ci-dessous les rapports de Bluescreen.
Rapport 1 :
"A problem has been detected and Windows has been shut down to prevent damage
to your computer.
The problem seems to be caused by the following file: win32k.sys
PFN_LIST_CORRUPT
If this is the first time you've seen this stop error screen,
restart your computer. If this screen appears again, follow
these steps:
Check to make sure any new hardware or software is properly installed.
If this is a new installation, ask your hardware or software manufacturer
for any Windows updates you might need.
If problems continue, disable or remove any newly installed hardware
or software. Disable BIOS memory options such as caching or shadowing.
If you need to use safe mode to remove or disable components, restart
your computer, press F8 to select Advanced Startup Options, and then
select Safe Mode.
Technical Information:
*** STOP: 0x0000004e (0x00000099, 0x0008d9a4, 0x00000000, 0x000c1e64)
*** win32k.sys - Address 0x9b7e3f6b base at 0x9b720000 DateStamp 0x50aee5c0"
Rapport 2 :
"A problem has been detected and Windows has been shut down to prevent damage
to your computer.
The problem seems to be caused by the following file: win32k.sys
MEMORY_MANAGEMENT
If this is the first time you've seen this stop error screen,
restart your computer. If this screen appears again, follow
these steps:
Check to make sure any new hardware or software is properly installed.
If this is a new installation, ask your hardware or software manufacturer
for any Windows updates you might need.
If problems continue, disable or remove any newly installed hardware
or software. Disable BIOS memory options such as caching or shadowing.
If you need to use safe mode to remove or disable components, restart
your computer, press F8 to select Advanced Startup Options, and then
select Safe Mode.
Technical Information:
*** STOP: 0x0000001a (0x00005003, 0x8c800000, 0x0000d065, 0x0d0670c8)
*** win32k.sys - Address 0x9ab16963 base at 0x9aaf0000 DateStamp 0x50aee5c0"
Rapport 3 :
"A problem has been detected and Windows has been shut down to prevent damage
to your computer.
The problem seems to be caused by the following file: win32k.sys
PFN_LIST_CORRUPT
If this is the first time you've seen this stop error screen,
restart your computer. If this screen appears again, follow
these steps:
Check to make sure any new hardware or software is properly installed.
If this is a new installation, ask your hardware or software manufacturer
for any Windows updates you might need.
If problems continue, disable or remove any newly installed hardware
or software. Disable BIOS memory options such as caching or shadowing.
If you need to use safe mode to remove or disable components, restart
your computer, press F8 to select Advanced Startup Options, and then
select Safe Mode.
Technical Information:
*** STOP: 0x0000004e (0x00000099, 0x00015cf8, 0x00000000, 0x00015c88)
*** win32k.sys - Address 0x9af63f6b base at 0x9aea0000 DateStamp 0x50aee5c0"
Rapport 4 :
"A problem has been detected and Windows has been shut down to prevent damage
to your computer.
The problem seems to be caused by the following file:
KERNEL_MODE_EXCEPTION_NOT_HANDLED
If this is the first time you've seen this stop error screen,
restart your computer. If this screen appears again, follow
these steps:
Check to make sure any new hardware or software is properly installed.
If this is a new installation, ask your hardware or software manufacturer
for any Windows updates you might need.
If problems continue, disable or remove any newly installed hardware
or software. Disable BIOS memory options such as caching or shadowing.
If you need to use safe mode to remove or disable components, restart
your computer, press F8 to select Advanced Startup Options, and then
select Safe Mode.
Technical Information:
*** STOP: 0x1000008e (0xc0000005, 0xb453455d, 0xa77a5bd4, 0x00000000)
*** - Address 0x00000000 base at 0x00000000 DateStamp 0x00000000"
Merci à vous.
Plantages et écrans bleus Seven 32
Modérateur : Mods Windows
Re: Plantages et écrans bleus Seven 32
Salut
As-tu touché à un pilote y'a peu? regarde dans les maj windows également, parfois, il trouve un pilote et le met à jour... ce que je déteste...
Puisque cela date de quelques jours seulement, fais une resto système et revient en arrière de deux semaines par ex.
Puis repasses les maj windows, en excluant les maj de pilote matériel, si y'en a.
et test.
fais cela qu'il n'y ait pas un rootkit planqué
Télécharge TDSSKILLER de Kaspersky sur ton bureau.
*_* Décompresse-le en faisant clic-droit dessus -> extraire tout... (clique sur "suivant", "suivant" et "Terminer".)
*_* Double clique sur "TDSSKiller.exe" pour lancer l'outil.
(Pour les utilisateur de Vista/Windows 7 : effectue un clic droit sur TDSSKiller.exe et sélectionne " Exécuter en tant qu'administrateur. ")
*_* Clique alors sur le bouton "Start Scan".
*_* Laisse le scan s'effectuer.
•Dans la fenêtre de résultat :
• Si TDSS.tdl2 est détecté l'option delete sera cochée par défaut.
• Si TDSS.tdl3 est détecté assure toi que Cure est bien cochée.
• Pour la partie "Suspicious object" laisse sur "Skip"
• Si TDSS.tdl4 (mbr) est détecté assure toi que Cure est bien coché.
• Clique enfin sur "Continue"
• Il te sera surement demandé de redémarrer ton pc, fais le en cliquant sur "Reboot now"
• Au redémarrage va chercher le rapport de suppression, il se trouve ici :
C:\ TDSSKiller.x.x.x.x_date_heure_log.txt
*_* Poste son contenu dans ta prochaine réponse.
As-tu touché à un pilote y'a peu? regarde dans les maj windows également, parfois, il trouve un pilote et le met à jour... ce que je déteste...
Puisque cela date de quelques jours seulement, fais une resto système et revient en arrière de deux semaines par ex.
Puis repasses les maj windows, en excluant les maj de pilote matériel, si y'en a.
et test.
fais cela qu'il n'y ait pas un rootkit planqué
Télécharge TDSSKILLER de Kaspersky sur ton bureau.
*_* Décompresse-le en faisant clic-droit dessus -> extraire tout... (clique sur "suivant", "suivant" et "Terminer".)
*_* Double clique sur "TDSSKiller.exe" pour lancer l'outil.
(Pour les utilisateur de Vista/Windows 7 : effectue un clic droit sur TDSSKiller.exe et sélectionne " Exécuter en tant qu'administrateur. ")
*_* Clique alors sur le bouton "Start Scan".
*_* Laisse le scan s'effectuer.
•Dans la fenêtre de résultat :
• Si TDSS.tdl2 est détecté l'option delete sera cochée par défaut.
• Si TDSS.tdl3 est détecté assure toi que Cure est bien cochée.
• Pour la partie "Suspicious object" laisse sur "Skip"
• Si TDSS.tdl4 (mbr) est détecté assure toi que Cure est bien coché.
• Clique enfin sur "Continue"
• Il te sera surement demandé de redémarrer ton pc, fais le en cliquant sur "Reboot now"
• Au redémarrage va chercher le rapport de suppression, il se trouve ici :
C:\ TDSSKiller.x.x.x.x_date_heure_log.txt
*_* Poste son contenu dans ta prochaine réponse.
Re: Plantages et écrans bleus Seven 32
Merci de ta réponse.
J'ai mis à jour les drivers de la graphique, j'avais 2 versions de retard, depuis plus de problème.
Le "mieux" étant l'ennemi du "bien", on va attendre voir ce que ça donne.
Si ça re-foire, je suis ta procédure et te tiens informé.
Thx !
J'ai mis à jour les drivers de la graphique, j'avais 2 versions de retard, depuis plus de problème.
Le "mieux" étant l'ennemi du "bien", on va attendre voir ce que ça donne.
Si ça re-foire, je suis ta procédure et te tiens informé.
Thx !
Dernière modification par Calimhero le 05 févr. 2013 20:19, modifié 1 fois.
Re: Plantages et écrans bleus Seven 32
Ok
en effet, quand ça roule, on touche plus !
Si cela ne revient pas, penses au résolu ;)
RESOLU:
en effet, quand ça roule, on touche plus !

Si cela ne revient pas, penses au résolu ;)
RESOLU:
Penses à mettre "résolu" dans ton titre en éditant le premier message![]()
Que cela aide ceux qui recherchent ensuite des solutions.
Re: Plantages et écrans bleus Seven 32
C'est re-moi.
Plantage à nouveau ce matin pendant une partie de Far Cry 2 (en local), après 2 jours sans problèmes.
J'ai juste eu le temps de voir BAD_POOL_HEADER sur l'écran bleu. Si besoin je t'en dis plus avec BlueScreenView.
TDSSKILLER n'a absolument rien detecté, 0 objects found...
Thx.
*Edit* : c'est beaucoup moins fréquent qu'auparavant.

Plantage à nouveau ce matin pendant une partie de Far Cry 2 (en local), après 2 jours sans problèmes.
J'ai juste eu le temps de voir BAD_POOL_HEADER sur l'écran bleu. Si besoin je t'en dis plus avec BlueScreenView.
TDSSKILLER n'a absolument rien detecté, 0 objects found...
Thx.
*Edit* : c'est beaucoup moins fréquent qu'auparavant.
Re: Plantages et écrans bleus Seven 32
Yep
donne le rapport qu'on voit les infos.
Donnes-moi le modèle exact de machine, qu'on repasse le pilote d'origine.
désinstalles spybot qui ne sert à rien.
donne le rapport qu'on voit les infos.
Donnes-moi le modèle exact de machine, qu'on repasse le pilote d'origine.
désinstalles spybot qui ne sert à rien.
Re: Plantages et écrans bleus Seven 32
Le rapport :
A problem has been detected and Windows has been shut down to prevent damage
to your computer.
The problem seems to be caused by the following file: watchdog.sys
BAD_POOL_HEADER
If this is the first time you've seen this stop error screen,
restart your computer. If this screen appears again, follow
these steps:
Check to make sure any new hardware or software is properly installed.
If this is a new installation, ask your hardware or software manufacturer
for any Windows updates you might need.
If problems continue, disable or remove any newly installed hardware
or software. Disable BIOS memory options such as caching or shadowing.
If you need to use safe mode to remove or disable components, restart
your computer, press F8 to select Advanced Startup Options, and then
select Safe Mode.
Technical Information:
*** STOP: 0x00000019 (0x00000003, 0x859016e0, 0x859016e0, 0x859016e2)
*** watchdog.sys - Address 0x8bdcf1b0 base at 0x8bdce000 DateStamp 0x4a5bc21a
La machine (assembleur) :
Boitier Antec Sonata I
Alim Corsair CX400 (400W)
Carte mère MSI K9n-Neo V2
Processeur Athlon X2 64 5600+
4 Go de RAM DDR2 800 Samsung
Carte graphique MSI Radeon HD6700 1Go DDR5
Disque dur Seagate SATA2 Barracuda 500Go 7200 trs/mn
Windows Seven 32 bits
A problem has been detected and Windows has been shut down to prevent damage
to your computer.
The problem seems to be caused by the following file: watchdog.sys
BAD_POOL_HEADER
If this is the first time you've seen this stop error screen,
restart your computer. If this screen appears again, follow
these steps:
Check to make sure any new hardware or software is properly installed.
If this is a new installation, ask your hardware or software manufacturer
for any Windows updates you might need.
If problems continue, disable or remove any newly installed hardware
or software. Disable BIOS memory options such as caching or shadowing.
If you need to use safe mode to remove or disable components, restart
your computer, press F8 to select Advanced Startup Options, and then
select Safe Mode.
Technical Information:
*** STOP: 0x00000019 (0x00000003, 0x859016e0, 0x859016e0, 0x859016e2)
*** watchdog.sys - Address 0x8bdcf1b0 base at 0x8bdce000 DateStamp 0x4a5bc21a
La machine (assembleur) :
Boitier Antec Sonata I
Alim Corsair CX400 (400W)
Carte mère MSI K9n-Neo V2
Processeur Athlon X2 64 5600+
4 Go de RAM DDR2 800 Samsung
Carte graphique MSI Radeon HD6700 1Go DDR5
Disque dur Seagate SATA2 Barracuda 500Go 7200 trs/mn
Windows Seven 32 bits
Re: Plantages et écrans bleus Seven 32
Repasse le pilote graphique à jour ainsi:
http://support.amd.com/us/gpudownload/Pages/index.aspx
PILOTE VIDEO:
http://support.amd.com/us/gpudownload/Pages/index.aspx
PILOTE VIDEO:
Spoiler!
Re: Plantages et écrans bleus Seven 32
OK, je fais ça. Tu penses à une installe foirée du Catalyst ?
*Edit* : après désinstallation du pilote et nettoyage en mode sans échec avec le Driversweeper, impossible de redemmarer, j'ai eu un écran bleu à chaque fois. J'ai dû passer en "dernière bonne configuration connue".
Autre chose, pour le driver,je dois prendre la suite logicielle ou le dernier en Beta ? (http://support.amd.com/us/gpudownload/w ... sta32.aspx)
L'analyse par WhoCrashed donne ceci (BlueScreenView n'a rien trouvé...):
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Sat 09/02/2013 10:45:27 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ndistapi.sys (ndistapi!NdisTapiCompleteRequest+0x7B8E)
Bugcheck code: 0x50 (0xFFFFFFFF91E95CA6, 0x8, 0xFFFFFFFF91E95CA6, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\drivers\ndistapi.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NDIS 3.0 connection wrapper driver
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 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.
*Edit* : après désinstallation du pilote et nettoyage en mode sans échec avec le Driversweeper, impossible de redemmarer, j'ai eu un écran bleu à chaque fois. J'ai dû passer en "dernière bonne configuration connue".
Autre chose, pour le driver,je dois prendre la suite logicielle ou le dernier en Beta ? (http://support.amd.com/us/gpudownload/w ... sta32.aspx)
L'analyse par WhoCrashed donne ceci (BlueScreenView n'a rien trouvé...):
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Sat 09/02/2013 10:45:27 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ndistapi.sys (ndistapi!NdisTapiCompleteRequest+0x7B8E)
Bugcheck code: 0x50 (0xFFFFFFFF91E95CA6, 0x8, 0xFFFFFFFF91E95CA6, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\drivers\ndistapi.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NDIS 3.0 connection wrapper driver
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 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.
Re: Plantages et écrans bleus Seven 32
Très bizarre que tu plantes en sortie de nettoyage... cela ne m'est jamais arrivé...
oui, je pensais à un souci du coté install du nouveau pilote.
Prends le pilote certifié, pas le béta.
Tu installes bien avec un clic droit pour exécuter en admin?
oui, je pensais à un souci du coté install du nouveau pilote.
Prends le pilote certifié, pas le béta.
Tu installes bien avec un clic droit pour exécuter en admin?
Re: Plantages et écrans bleus Seven 32
C'est parti avec la dernière version certifiée, installée avec un splendide Clic droit/Exécuter en tant qu'administrateur.
Le rapport d'installation me dit que tout est OK.
Ce qui m'inquiète le plus c'est le coté aléatoire de ces plantages...j'espère que ce n'est pas le disque dur qui commence à lâcher.
Que dois-je faire d'autre ?

Le rapport d'installation me dit que tout est OK.
Ce qui m'inquiète le plus c'est le coté aléatoire de ces plantages...j'espère que ce n'est pas le disque dur qui commence à lâcher.
Que dois-je faire d'autre ?
Re: Plantages et écrans bleus Seven 32
attendre pour voir si cela tient ;)
Pannes aléatoires, plutôt la CM, ce qui n'est pas plus rassurant... ou la RAM...
Pannes aléatoires, plutôt la CM, ce qui n'est pas plus rassurant... ou la RAM...
Re: Plantages et écrans bleus Seven 32
Hello.
Ça a pas tenu longtemps...
J'ai entièrement démonté mon PC pour le dépoussiérer, ça m'a permis de vérifier que tout était bien connecté.
Et bien replantages : 1 fois en jouant à Far Cry, et 5 autres fois en voulant installer les pilotes de la carte son, la sortie audio de la carte mère étant morte, j'ai réinstallé ma vieille Hercules Muse DVD 5.1 avant le nettoyage, ça marchait impeccable, depuis impossible de mettre les pilotes. Ça pourrait venir de là ?
La vérification du disque système avec Seatools DOS n'a retourné aucune erreur.
Voici les rapports BlueScreenView :
A problem has been detected and Windows has been shut down to prevent damage
to your computer.
The problem seems to be caused by the following file: ntkrnlpa.exe
UNEXPECTED_KERNEL_MODE_TRAP
If this is the first time you've seen this stop error screen,
restart your computer. If this screen appears again, follow
these steps:
Check to make sure any new hardware or software is properly installed.
If this is a new installation, ask your hardware or software manufacturer
for any Windows updates you might need.
If problems continue, disable or remove any newly installed hardware
or software. Disable BIOS memory options such as caching or shadowing.
If you need to use safe mode to remove or disable components, restart
your computer, press F8 to select Advanced Startup Options, and then
select Safe Mode.
Technical Information:
*** STOP: 0x0000007f (0x0000000d, 0x00000000, 0x00000000, 0x00000000)
*** ntkrnlpa.exe - Address 0x83a973bb base at 0x83a56000 DateStamp 0x50e793e8
-----------------------------------------------------------------------------------------------------
A problem has been detected and Windows has been shut down to prevent damage
to your computer.
The problem seems to be caused by the following file: cmudax3.sys
SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
If this is the first time you've seen this stop error screen,
restart your computer. If this screen appears again, follow
these steps:
Check to make sure any new hardware or software is properly installed.
If this is a new installation, ask your hardware or software manufacturer
for any Windows updates you might need.
If problems continue, disable or remove any newly installed hardware
or software. Disable BIOS memory options such as caching or shadowing.
If you need to use safe mode to remove or disable components, restart
your computer, press F8 to select Advanced Startup Options, and then
select Safe Mode.
Technical Information:
*** STOP: 0x1000007e (0xc0000005, 0xc7dd890e, 0x8e927b58, 0x8e927730)
*** cmudax3.sys - Address 0xc7dd890e base at 0xc7c35000 DateStamp 0x49c06bf7
-----------------------------------------------------------------------------------------------------
A problem has been detected and Windows has been shut down to prevent damage
to your computer.
The problem seems to be caused by the following file: cmudax3.sys
SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
If this is the first time you've seen this stop error screen,
restart your computer. If this screen appears again, follow
these steps:
Check to make sure any new hardware or software is properly installed.
If this is a new installation, ask your hardware or software manufacturer
for any Windows updates you might need.
If problems continue, disable or remove any newly installed hardware
or software. Disable BIOS memory options such as caching or shadowing.
If you need to use safe mode to remove or disable components, restart
your computer, press F8 to select Advanced Startup Options, and then
select Safe Mode.
Technical Information:
*** STOP: 0x1000007e (0xc0000005, 0xa9fbf90e, 0x8e91bb58, 0x8e91b730)
*** cmudax3.sys - Address 0xa9fbf90e base at 0xa9e1c000 DateStamp 0x49c06bf7
-----------------------------------------------------------------------------------------------------
A problem has been detected and Windows has been shut down to prevent damage
to your computer.
The problem seems to be caused by the following file: cmudax3.sys
SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
If this is the first time you've seen this stop error screen,
restart your computer. If this screen appears again, follow
these steps:
Check to make sure any new hardware or software is properly installed.
If this is a new installation, ask your hardware or software manufacturer
for any Windows updates you might need.
If problems continue, disable or remove any newly installed hardware
or software. Disable BIOS memory options such as caching or shadowing.
If you need to use safe mode to remove or disable components, restart
your computer, press F8 to select Advanced Startup Options, and then
select Safe Mode.
Technical Information:
*** STOP: 0x1000007e (0xc0000005, 0xb13898ac, 0x8e927b6c, 0x8e927750)
*** cmudax3.sys - Address 0xb13898ac base at 0xb1231000 DateStamp 0x49c06bcf
-----------------------------------------------------------------------------------------------------
A problem has been detected and Windows has been shut down to prevent damage
to your computer.
The problem seems to be caused by the following file: cmudax3.sys
SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
If this is the first time you've seen this stop error screen,
restart your computer. If this screen appears again, follow
these steps:
Check to make sure any new hardware or software is properly installed.
If this is a new installation, ask your hardware or software manufacturer
for any Windows updates you might need.
If problems continue, disable or remove any newly installed hardware
or software. Disable BIOS memory options such as caching or shadowing.
If you need to use safe mode to remove or disable components, restart
your computer, press F8 to select Advanced Startup Options, and then
select Safe Mode.
Technical Information:
*** STOP: 0x1000007e (0xc0000005, 0xe03c090e, 0x8e927b58, 0x8e927730)
*** cmudax3.sys - Address 0xe03c090e base at 0xe021d000 DateStamp 0x49c06bf7
-----------------------------------------------------------------------------------------------------
A problem has been detected and Windows has been shut down to prevent damage
to your computer.
The problem seems to be caused by the following file: cmudax3.sys
SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
If this is the first time you've seen this stop error screen,
restart your computer. If this screen appears again, follow
these steps:
Check to make sure any new hardware or software is properly installed.
If this is a new installation, ask your hardware or software manufacturer
for any Windows updates you might need.
If problems continue, disable or remove any newly installed hardware
or software. Disable BIOS memory options such as caching or shadowing.
If you need to use safe mode to remove or disable components, restart
your computer, press F8 to select Advanced Startup Options, and then
select Safe Mode.
Technical Information:
*** STOP: 0x1000007e (0xc0000005, 0xb2fbd90e, 0x8e917b58, 0x8e917730)
*** cmudax3.sys - Address 0xb2fbd90e base at 0xb2e1a000 DateStamp 0x49c06bf7
Ah oui, j'ai oublié de te dire que la tour avait été déplacée juste avant que ces soucis ne commencent.
Ça a pas tenu longtemps...
J'ai entièrement démonté mon PC pour le dépoussiérer, ça m'a permis de vérifier que tout était bien connecté.
Et bien replantages : 1 fois en jouant à Far Cry, et 5 autres fois en voulant installer les pilotes de la carte son, la sortie audio de la carte mère étant morte, j'ai réinstallé ma vieille Hercules Muse DVD 5.1 avant le nettoyage, ça marchait impeccable, depuis impossible de mettre les pilotes. Ça pourrait venir de là ?
La vérification du disque système avec Seatools DOS n'a retourné aucune erreur.
Voici les rapports BlueScreenView :
A problem has been detected and Windows has been shut down to prevent damage
to your computer.
The problem seems to be caused by the following file: ntkrnlpa.exe
UNEXPECTED_KERNEL_MODE_TRAP
If this is the first time you've seen this stop error screen,
restart your computer. If this screen appears again, follow
these steps:
Check to make sure any new hardware or software is properly installed.
If this is a new installation, ask your hardware or software manufacturer
for any Windows updates you might need.
If problems continue, disable or remove any newly installed hardware
or software. Disable BIOS memory options such as caching or shadowing.
If you need to use safe mode to remove or disable components, restart
your computer, press F8 to select Advanced Startup Options, and then
select Safe Mode.
Technical Information:
*** STOP: 0x0000007f (0x0000000d, 0x00000000, 0x00000000, 0x00000000)
*** ntkrnlpa.exe - Address 0x83a973bb base at 0x83a56000 DateStamp 0x50e793e8
-----------------------------------------------------------------------------------------------------
A problem has been detected and Windows has been shut down to prevent damage
to your computer.
The problem seems to be caused by the following file: cmudax3.sys
SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
If this is the first time you've seen this stop error screen,
restart your computer. If this screen appears again, follow
these steps:
Check to make sure any new hardware or software is properly installed.
If this is a new installation, ask your hardware or software manufacturer
for any Windows updates you might need.
If problems continue, disable or remove any newly installed hardware
or software. Disable BIOS memory options such as caching or shadowing.
If you need to use safe mode to remove or disable components, restart
your computer, press F8 to select Advanced Startup Options, and then
select Safe Mode.
Technical Information:
*** STOP: 0x1000007e (0xc0000005, 0xc7dd890e, 0x8e927b58, 0x8e927730)
*** cmudax3.sys - Address 0xc7dd890e base at 0xc7c35000 DateStamp 0x49c06bf7
-----------------------------------------------------------------------------------------------------
A problem has been detected and Windows has been shut down to prevent damage
to your computer.
The problem seems to be caused by the following file: cmudax3.sys
SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
If this is the first time you've seen this stop error screen,
restart your computer. If this screen appears again, follow
these steps:
Check to make sure any new hardware or software is properly installed.
If this is a new installation, ask your hardware or software manufacturer
for any Windows updates you might need.
If problems continue, disable or remove any newly installed hardware
or software. Disable BIOS memory options such as caching or shadowing.
If you need to use safe mode to remove or disable components, restart
your computer, press F8 to select Advanced Startup Options, and then
select Safe Mode.
Technical Information:
*** STOP: 0x1000007e (0xc0000005, 0xa9fbf90e, 0x8e91bb58, 0x8e91b730)
*** cmudax3.sys - Address 0xa9fbf90e base at 0xa9e1c000 DateStamp 0x49c06bf7
-----------------------------------------------------------------------------------------------------
A problem has been detected and Windows has been shut down to prevent damage
to your computer.
The problem seems to be caused by the following file: cmudax3.sys
SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
If this is the first time you've seen this stop error screen,
restart your computer. If this screen appears again, follow
these steps:
Check to make sure any new hardware or software is properly installed.
If this is a new installation, ask your hardware or software manufacturer
for any Windows updates you might need.
If problems continue, disable or remove any newly installed hardware
or software. Disable BIOS memory options such as caching or shadowing.
If you need to use safe mode to remove or disable components, restart
your computer, press F8 to select Advanced Startup Options, and then
select Safe Mode.
Technical Information:
*** STOP: 0x1000007e (0xc0000005, 0xb13898ac, 0x8e927b6c, 0x8e927750)
*** cmudax3.sys - Address 0xb13898ac base at 0xb1231000 DateStamp 0x49c06bcf
-----------------------------------------------------------------------------------------------------
A problem has been detected and Windows has been shut down to prevent damage
to your computer.
The problem seems to be caused by the following file: cmudax3.sys
SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
If this is the first time you've seen this stop error screen,
restart your computer. If this screen appears again, follow
these steps:
Check to make sure any new hardware or software is properly installed.
If this is a new installation, ask your hardware or software manufacturer
for any Windows updates you might need.
If problems continue, disable or remove any newly installed hardware
or software. Disable BIOS memory options such as caching or shadowing.
If you need to use safe mode to remove or disable components, restart
your computer, press F8 to select Advanced Startup Options, and then
select Safe Mode.
Technical Information:
*** STOP: 0x1000007e (0xc0000005, 0xe03c090e, 0x8e927b58, 0x8e927730)
*** cmudax3.sys - Address 0xe03c090e base at 0xe021d000 DateStamp 0x49c06bf7
-----------------------------------------------------------------------------------------------------
A problem has been detected and Windows has been shut down to prevent damage
to your computer.
The problem seems to be caused by the following file: cmudax3.sys
SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
If this is the first time you've seen this stop error screen,
restart your computer. If this screen appears again, follow
these steps:
Check to make sure any new hardware or software is properly installed.
If this is a new installation, ask your hardware or software manufacturer
for any Windows updates you might need.
If problems continue, disable or remove any newly installed hardware
or software. Disable BIOS memory options such as caching or shadowing.
If you need to use safe mode to remove or disable components, restart
your computer, press F8 to select Advanced Startup Options, and then
select Safe Mode.
Technical Information:
*** STOP: 0x1000007e (0xc0000005, 0xb2fbd90e, 0x8e917b58, 0x8e917730)
*** cmudax3.sys - Address 0xb2fbd90e base at 0xb2e1a000 DateStamp 0x49c06bf7
Ah oui, j'ai oublié de te dire que la tour avait été déplacée juste avant que ces soucis ne commencent.
-
- Sujets similaires
- Réponses
- Vues
- Dernier message
-
- 6 Réponses
- 222 Vues
-
Dernier message par Parisien_entraide
-
- 39 Réponses
- 319 Vues
-
Dernier message par Parisien_entraide
-
- 8 Réponses
- 155 Vues
-
Dernier message par Malekal_morte
-
- 3 Réponses
- 61 Vues
-
Dernier message par Guill5
-
-
Perte de signal de mes écrans de façon aléatoire
par Empereur » » dans Windows : Résoudre les problèmes - 9 Réponses
- 201 Vues
-
Dernier message par Malekal_morte
-