bonjour me revoilà

je vais essayer d'expliquer au mieux mon probleme, n'ayant aucune connaissance en info surtout avec le bios ...

je ne parviens pas a arriver sur ma cession sauf apres plusieurs reset car la souris se fige sur mon mot de passe ou quand je suis sur ma cession à un moment donné la souris fige et je suis obliger d'eteindre (reset) je suis sur windows xp (2002).

ma carte graphique est une nvdia geforcefx5200, je suis parvenue a desisntaller mon driver actuel celui de mon cd d'instal, j'ai essayé d'nstaller une autre par le bias de tous les drivers.com soit le 175.19 mais c pareil merci pour votre aide

le systeme a recuperé une erreur serieuse soit

c:\documents\kiki\locals\temp\wer3bfa.dir00\mini121111-02.dmp

c:\documents\kiki\locals\temp\wer3bfa.dir00\sysdata.xml

Bonsoir 77chris70

On va essayer d'y voir plus clair.

T'as Windows XP SP1 ou SP2 ou SP3?

Je vais te donner un lien direct chez Nvidia pour télécharger le driver.

bonjour mac peter

c'est le xp 2000 vu par f2 du bios car je n'arrive plus a rentrer dans ma cession sur mon mot de passe

merci

j'ai reussi a enlever mon mot de passe et rentrer dans proprietes systeme donc c le service pack 3 version 2002

Bonsoir 77chris70

Merci pour ta réponse.

Voici le lien pour télécharger ton driver:

http://www.nvidia.fr/Download/index.aspx?lang=fr

Si t'as des questions il ne faut pas hésiter.

bonjour mac peter

j'espere que j'ai bien installé le pilote j'ai pris le 175.16 sous xp par contre est ce normal que j'ai le fichier nvidia dans mon C: il aurait du etre palcé dans program files non ?

bon mauvais nouvelle c'est pareil ça se fige au bout de quelques instant ... soit le pc est infecté soit j'ai un soiouci avec le bios peut etre ??

mon pc fonctionnait tres bien avant que je ne change mon disque dur et ma carte graphique asus (j'ai posté dans les mains dans le camboui sujet video mode not supported) peut etre allez vous trouvez mon probleme

bien à vous

Bonsoir 77chris70

Avant de passer à la vérification s'il y a une infection j'ai encore une question. Le driver ou pilote de la souris date de quand?

bonjour mac peter,

Avant le pc etait equipé d'une souris sans fil avec pile qui est tombé hs d'ou remplamcement d'une souris avec fil branché sur port usb 2 et le clavier est branché derriere la tour

je n'ai jamais mis à jour le pilote de la souris et sur les autres periphériques d'ailleurs oups !!!!!!!

j'ai un ecran bleu avec message d'erreur

nv4_disp

Bonsoir 77chris70

Merci pour les infos. Mais avant on va s'occuper encore de ton écran bleu. Je vais aller te choisir le bon driver et je reviendrai avec toutes les coordonnées.

Après il va falloir mettre à jour ton driver souris.

merci bien à plus tard

Bonsoir 77chris70


Chez Nvidia ils propose ce driver

285.58 ^WHQL

pour XP

http://www.nvidia.fr/object/winxp-285.58-whql-driver-fr.html

bonjour Mac peter

ça ne fonctionne pas :(

en installant le driver voici le message

please enter the folder where you want to save the nvdia driver.files if the folder does not exist il will be created for you

c:\nvidia\displaydriver\285.58\winxp\international

donc ok puis arrive un message de nvidia

le programme d'installation nvidia ne peut pas continuer

ce pilote graphique n'a pas trouvé de matériel graphique compatible

une question ??? j'ai desinstallé l'ancien pilote avant d'installer celui ci il ne fallait peut etre pas ???

merci à vous

Bonsoir 77chris70

Avec Nvidia c'est conseillé de désinstaller mais on n'est pas obligé. Voilà la situation.

Je vais encore voir si je trouve une solution pour ton pilote et après on va voir s'il y a un problème d'infection sur ton ordi.

T'as bien deux lettres devant le 5200?

Avec ce pilote il semblerait qu'il y ait des problèmes.

Voici un lien plus utile:

http://www.commentcamarche.net/download/telecharger-34056951-driver-geforce-fx-5200

j'ai bien deux lettres avant j'aiu fait un rapport avec everest et c bien une nvidia geforce fx 5200 (msi fx5200)

après installation du pilote 175.19 ecran bleu message d'erreur nv4-disp

que ce soit le 175.16 ou le 175.19 c idem bouh !!!!!

merci à bientot...

Bonsoir 77chris70

OK meri pour la réponse. On va passer à la vérification d'une éventuelle infection. Tu pourrais faire ce qu'on demande ici:

http://forum.pcastuces.com/aide_au_diagnostic_un_pc_infecte_pcastuces-f25s17490.htm

Autrement dit il me faudrait le rapport de Malwarebytes et le rapport de ZHPdiag. Merci

Fichier joint : mbam-log-2011-12-18 (14-28-21).txt

Fichier joint : ZHPDiag.Txt

Fichier joint : ZHPDiag1.txt

Bonsoir 77chris70

Merci pour les deux rapports. Je reviens...

Ok

Bonsoir 77chris70

J'ai regardé les deux rapports:

MBAM et ZHPdiag.

Il n'y a aucune infection. Ton ordi est propre.

On va checher différemment.

Bonjour

MacPeter

Si je peux me permettre, pour voir ce qui a provoqué le BSOD, il y a Whocrashed et pour résoudre les problèmes de la carte graphique : NVidia System Tools

Bonne journée

bonjour nenette58

que dois je faire, installer le logiciel whocrashed ? je ne suis pas doué en anglais ! merci à vous

Bonjour 77chris70

Il te suffit d'installer le logiciel et de le lancer, ensuite tu cliques sur "Analyze" en haut de la fenêtre, un message apparaît : " Please scroll down the information windows to read the report", tu cliques sur "Ok", puis dans la fenêtre de l'outil, tu descends la barre de scroll à droite et ton analyse apparaît.

Reste à copier/coller ce qui est écrit ou faire une capture d'écran

nenette, puis je le faire en mode sans echec car ça bloque je ne peux pas copier coller !!!

Je ne sais pas, je ne l'ai jamais essayé en mode sans échec

Et si tu fais une capture d'image en agrandissant la fenêtre de Whocrashed au maximum ou peut-être un copier/coller d'abord dans le bloc-note ?

System Information (local)

computer name: PARTICUL-BA8E16
windows version: Windows XP Service Pack 3, 5.1, build: 2600
windows dir: C:\WINDOWS
CPU: AuthenticAMD AMD Athlon(tm) XP 2000+ AMD586, level: 6
1 logical processors, active mask: 1
RAM: 1073201152 total
VM: 2147352576, free: 2044555264

Crash Dump Analysis

Crash dump directory: C:\WINDOWS\Minidump

Crash dumps are enabled on your computer.


On Sat 17/12/2011 13:10:20 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini121711-01.dmp
This was probably caused by the following module: watchdog.sys (watchdog+0xA67)
Bugcheck code: 0x100000EA (0xFFFFFFFF865DD7F0, 0xFFFFFFFF861F34B0, 0xFFFFFFFFF7C5ECB4, 0x1)
Error: THREAD_STUCK_IN_DEVICE_DRIVER_M
file path: C:\WINDOWS\system32\watchdog.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Watchdog Driver
Bug check description: This indicates that a thread in a device driver is endlessly spinning.
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 Wed 14/12/2011 17:22:35 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini121411-08.dmp
This was probably caused by the following module: watchdog.sys (watchdog+0xA67)
Bugcheck code: 0x100000EA (0xFFFFFFFF86096260, 0xFFFFFFFF8645B008, 0xFFFFFFFFF7C5ACB4, 0x1)
Error: THREAD_STUCK_IN_DEVICE_DRIVER_M
file path: C:\WINDOWS\system32\watchdog.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Watchdog Driver
Bug check description: This indicates that a thread in a device driver is endlessly spinning.
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 Wed 14/12/2011 13:11:18 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini121411-07.dmp
This was probably caused by the following module: win32k.sys (win32k+0x18B071)
Bugcheck code: 0x100000EA (0xFFFFFFFF864FF3B8, 0xFFFFFFFF86698378, 0xFFFFFFFFF7C5ACB4, 0x1)
Error: THREAD_STUCK_IN_DEVICE_DRIVER_M
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 a thread in a device driver is endlessly spinning.
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 Wed 14/12/2011 13:02:53 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini121411-06.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x48F3)
Bugcheck code: 0x100000EA (0xFFFFFFFF8600F8B8, 0xFFFFFFFF864FE460, 0xFFFFFFFFF7C66CB4, 0x1)
Error: THREAD_STUCK_IN_DEVICE_DRIVER_M
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Système d'exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Noyau et système NT
Bug check description: This indicates that a thread in a device driver is endlessly spinning.
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 14/12/2011 12:57:11 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini121411-05.dmp
This was probably caused by the following module: nv4_mini.sys (nv4_mini+0x53086)
Bugcheck code: 0x100000EA (0xFFFFFFFF86062BA0, 0xFFFFFFFF864D2D38, 0xFFFFFFFFF7C66CB4, 0x1)
Error: THREAD_STUCK_IN_DEVICE_DRIVER_M
file path: C:\WINDOWS\system32\drivers\nv4_mini.sys
product: NVIDIA Compatible Windows 2000 Miniport Driver, Version 175.19
company: NVIDIA Corporation
description: NVIDIA Compatible Windows 2000 Miniport Driver, Version 175.19
Bug check description: This indicates that a thread in a device driver is endlessly spinning.
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: nv4_mini.sys (NVIDIA Compatible Windows 2000 Miniport Driver, Version 175.19 , NVIDIA Corporation).
Google query: nv4_mini.sys NVIDIA Corporation THREAD_STUCK_IN_DEVICE_DRIVER_M




On Wed 14/12/2011 12:28:04 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini121411-04.dmp
This was probably caused by the following module: nv4_mini.sys (nv4_mini+0x7620B)
Bugcheck code: 0x100000EA (0xFFFFFFFF86024628, 0xFFFFFFFF86529F60, 0xFFFFFFFFF7C5ACB4, 0x1)
Error: THREAD_STUCK_IN_DEVICE_DRIVER_M
file path: C:\WINDOWS\system32\drivers\nv4_mini.sys
product: NVIDIA Compatible Windows 2000 Miniport Driver, Version 175.19
company: NVIDIA Corporation
description: NVIDIA Compatible Windows 2000 Miniport Driver, Version 175.19
Bug check description: This indicates that a thread in a device driver is endlessly spinning.
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: nv4_mini.sys (NVIDIA Compatible Windows 2000 Miniport Driver, Version 175.19 , NVIDIA Corporation).
Google query: nv4_mini.sys NVIDIA Corporation THREAD_STUCK_IN_DEVICE_DRIVER_M




On Wed 14/12/2011 12:23:47 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini121411-03.dmp
This was probably caused by the following module: nv4_disp.sys (nv4_disp+0x216E1)
Bugcheck code: 0x100000EA (0xFFFFFFFF864B4B00, 0xFFFFFFFF8636F4B8, 0xFFFFFFFFF7C62CB4, 0x1)
Error: THREAD_STUCK_IN_DEVICE_DRIVER_M
Bug check description: This indicates that a thread in a device driver is endlessly spinning.
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: nv4_disp.sys .
Google query: nv4_disp.sys THREAD_STUCK_IN_DEVICE_DRIVER_M




On Wed 14/12/2011 12:18:51 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini121411-02.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x48F3)
Bugcheck code: 0x100000EA (0xFFFFFFFF863F3778, 0xFFFFFFFF86536A68, 0xFFFFFFFFF7C62CB4, 0x1)
Error: THREAD_STUCK_IN_DEVICE_DRIVER_M
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Système d'exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Noyau et système NT
Bug check description: This indicates that a thread in a device driver is endlessly spinning.
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 14/12/2011 12:11:13 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini121411-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0x18B071)
Bugcheck code: 0x100000EA (0xFFFFFFFF861177D8, 0xFFFFFFFF864D0DB0, 0xFFFFFFFFF7C5ECB4, 0x1)
Error: THREAD_STUCK_IN_DEVICE_DRIVER_M
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 a thread in a device driver is endlessly spinning.
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 Tue 13/12/2011 14:00:50 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini121311-02.dmp
This was probably caused by the following module: watchdog.sys (watchdog+0xA67)
Bugcheck code: 0x100000EA (0xFFFFFFFF86043020, 0xFFFFFFFF86615620, 0xFFFFFFFFF7C62CB4, 0x1)
Error: THREAD_STUCK_IN_DEVICE_DRIVER_M
file path: C:\WINDOWS\system32\watchdog.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Watchdog Driver
Bug check description: This indicates that a thread in a device driver is endlessly spinning.
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 Tue 13/12/2011 12:57:54 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini121311-01.dmp
This was probably caused by the following module: nv4_disp.sys (nv4_disp+0x213E1)
Bugcheck code: 0x100000EA (0xFFFFFFFF86005DA8, 0xFFFFFFFF86669E20, 0xFFFFFFFFF7C5ECB4, 0x1)
Error: THREAD_STUCK_IN_DEVICE_DRIVER_M
Bug check description: This indicates that a thread in a device driver is endlessly spinning.
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: nv4_disp.sys .
Google query: nv4_disp.sys THREAD_STUCK_IN_DEVICE_DRIVER_M




On Mon 12/12/2011 13:19:01 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini121211-02.dmp
This was probably caused by the following module: nv4_disp.sys (nv4_disp+0x214A1)
Bugcheck code: 0x100000EA (0xFFFFFFFF863F1B98, 0xFFFFFFFF864F0EB8, 0xFFFFFFFFF7C5ECB4, 0x1)
Error: THREAD_STUCK_IN_DEVICE_DRIVER_M
Bug check description: This indicates that a thread in a device driver is endlessly spinning.
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: nv4_disp.sys .
Google query: nv4_disp.sys THREAD_STUCK_IN_DEVICE_DRIVER_M




On Mon 12/12/2011 13:13:55 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini121211-01.dmp
This was probably caused by the following module: sptd.sys (sptd+0x17A83)
Bugcheck code: 0x100000EA (0xFFFFFFFF86458850, 0xFFFFFFFF863CEEC0, 0xFFFFFFFFF58DCCB4, 0x1)
Error: THREAD_STUCK_IN_DEVICE_DRIVER_M
file path: C:\WINDOWS\system32\drivers\sptd.sys
product: SCSI Pass Through Direct
company: Duplex Secure Ltd.
description: SCSI Pass Through Direct Host
Bug check description: This indicates that a thread in a device driver is endlessly spinning.
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: sptd.sys (SCSI Pass Through Direct Host, Duplex Secure Ltd.).
Google query: sptd.sys Duplex Secure Ltd. THREAD_STUCK_IN_DEVICE_DRIVER_M




On Sun 11/12/2011 15:34:37 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini121111-02.dmp
This was probably caused by the following module: nv4_mini.sys (nv4_mini+0x53247)
Bugcheck code: 0x100000EA (0xFFFFFFFF85DF4460, 0xFFFFFFFF8663E9F8, 0xFFFFFFFFF7C56CB4, 0x1)
Error: THREAD_STUCK_IN_DEVICE_DRIVER_M
file path: C:\WINDOWS\system32\drivers\nv4_mini.sys
product: NVIDIA Compatible Windows 2000 Miniport Driver, Version 175.19
company: NVIDIA Corporation
description: NVIDIA Compatible Windows 2000 Miniport Driver, Version 175.19
Bug check description: This indicates that a thread in a device driver is endlessly spinning.
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: nv4_mini.sys (NVIDIA Compatible Windows 2000 Miniport Driver, Version 175.19 , NVIDIA Corporation).
Google query: nv4_mini.sys NVIDIA Corporation THREAD_STUCK_IN_DEVICE_DRIVER_M




On Sun 11/12/2011 13:09:55 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini121111-01.dmp
This was probably caused by the following module: nv4_disp.sys (nv4_disp+0xB5474)
Bugcheck code: 0x100000EA (0xFFFFFFFF86115700, 0xFFFFFFFF8607D720, 0xFFFFFFFFF7C56CB4, 0x1)
Error: THREAD_STUCK_IN_DEVICE_DRIVER_M
Bug check description: This indicates that a thread in a device driver is endlessly spinning.
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: nv4_disp.sys .
Google query: nv4_disp.sys THREAD_STUCK_IN_DEVICE_DRIVER_M

Conclusion

22 crash dumps have been found and analyzed. Only 15 are included in this report. 4 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:

nv4_mini.sys (NVIDIA Compatible Windows 2000 Miniport Driver, Version 175.19 , NVIDIA Corporation)

avipbb.sys (Avira Driver for Security Enhancement, Avira GmbH)

sptd.sys (SCSI Pass Through Direct Host, Duplex Secure Ltd.)

nv4_disp.sys

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.

Bonsoir 77chris70

Nenette58

Merci Nenette58 pour le lien....

Re: 77chris70

Merci pour le rapport. Je l'ai survolé rapi8dement. Il m'a confirmé ce que j'ai pensé. Mais je vais le regarder en détail. Il va falloir intervenir au niveau du driver d'Envidia.

Je vais revenir avec la marche à suivre.

merci mac peter

Bonsoir 77chris70




On va procéder en deux étapes. Tout d'abord il faudra, malheureusement, désinstaller le driver de ta carte graphique mais en utilisant ce petit logiciel:

http://www.clubic.com/telecharger-fiche18788-driver-cleaner-pe.html

Puis il faudra réinstaller le driver après...

Bonjour Mac peter,

ok pour le petit logiciel afin de desinstaller le driver mais ensuite j'installe lequel celui de mon cd ou 175.16 ou 195.19 ou 285.......

Bonsoir 77chris70

Il faudrait réinstaller 175.16...

bonjour mac peter

j'ai desinstaller le driver actuel avec votre petit logiciel et reinstaller le driver 175.16 de votre lien du 13/12 tout ça en mode sans echec car en mode normal c impossible j'espère que j'ai bien fait

que dois je faire maintenant ??

merci à vous et bon reveillon de noel