Ecran bleu

Ton erreur est KERNEL_MODE_EXCEPTION_NOT_HANDLED

Il y a de nombreuses causes. la meilleure solution pour toi c'est d'envoyer ici les derniers fichiers .dmp qui se trouvent dans le dossier Windows\Minidump.

On a parle et utilisé la methode des centaines de fois sur ce forum.

le dernier date du 30 juin 2006. Donc a priori il n'y a rien ?

Tu as peut etre eu un plantage application. Regarde dans le dossier Drwatson. Il est cache dans Documents and Settings ton nom etc...
Dans drwatson il y a par contre un fichier .txt a lire.
Fais une recherche en decachant les fichiers systeme et tu vas le trouver.

sans rire je ne trouve pas de dossier drwatson ! je crois l'avoir supprimé un jour par mégarde...

Je n'ai que 3 fichiers intitulés comme tel situés dans: C/windows et C/windows/system32 et C/i386.

Pas de dossier...
Que faire ?

Ah bon ? Pas grave. Tu n'auras pas de notification d'erreurs d'applications.
Fais une recherche Google avec le nom de plantage que je t'ai donné. Moi j'ai toutes les explications mais en anglais. Si tu ne trouves pas sur Google je te mettrai en anglais ce que dit Microsoft sur le sujet.

je veux bien la solution microsoft. Merci de me la poster.

Lorsque je serai rentre chez moi.
En ce moment je suis dans la boutique informatique de mon assembleur prefere qui repare.....mon taille haie !

KERNEL_MODE_EXCEPTION_NOT_HANDLED

Bon courage

Cause
This is a very common bug check. To interpret it, you must identify which exception was generated.

Common exception codes include:

0x80000002: STATUS_DATATYPE_MISALIGNMENT
An unaligned data reference was encountered.

0x80000003: STATUS_BREAKPOINT
A breakpoint or ASSERT was encountered when no kernel debugger was attached to the system.

0xC0000005: STATUS_ACCESS_VIOLATION
A memory access violation occurred. (Parameter 4 of the bug check is the address that the driver attempted to access.)


For a complete list of exception codes, see the ntstatus.h file located in the inc directory of the Windows Driver Kit.

Resolving the Problem
If you are not equipped to debug this problem, you should use some basic troubleshooting techniques. If a driver is identified in the bug check message, disable the driver or check with the manufacturer for driver updates. Try changing video adapters. Check with your hardware vendor for any BIOS updates. Disable BIOS memory options such as caching or shadowing.

If you plan to debug this problem, you may find it difficult to obtain a stack trace. Parameter 2 (the exception address) should pinpoint the driver or function that caused this problem.

If exception code 0x80000003 occurs, this indicates that a hard-coded breakpoint or assertion was hit, but the system was started with the /NODEBUG switch. This problem should rarely occur. If it occurs repeatedly, make sure a kernel debugger is connected and the system is started with the /DEBUG switch.

If exception code 0x80000002 occurs, the trap frame will supply additional information.

If the specific cause of the exception is unknown, the following should be considered:

Hardware incompatibility. First, make sure that any new hardware installed is listed in the Microsoft Windows Marketplace Tested Products List.

Faulty device driver or system service. In addition, a faulty device driver or system service might be responsible for this error. Hardware issues, such as BIOS incompatibilities, memory conflicts, and IRQ conflicts can also generate this error.

If a driver is listed by name within the bug check message, disable or remove that driver. Disable or remove any drivers or services that were recently added. If the error occurs during the startup sequence and the system partition is formatted with NTFS file system, you might be able to use Safe Mode to rename or delete the faulty driver. If the driver is used as part of the system startup process in Safe Mode, you need to start the computer by using the Recovery Console to access the file.

If the problem is associated with Win32k.sys, the source of the error might be a third-party remote control program. If such software is installed, the service can be removed by starting the system using the Recovery Console and deleting the offending system service file.

Check the System Log in Event Viewer for additional error messages that might help pinpoint the device or driver that is causing bug check 0x1E. Disabling memory caching of the BIOS might also resolve the error. You should also run hardware diagnostics, especially the memory scanner, supplied by the system manufacturer. For details on these procedures, see the owner's manual for your computer.

The error that generates this message can occur after the first restart during Windows Setup, or after Setup is finished. A possible cause of the error is a system BIOS incompatibility. BIOS problems can be resolved by upgrading the system BIOS version.