bonjour a tous,
voila je vous écris car mon PC a un problème depuis un moment et j'aimerais le régler .
alors voila je vous met tout ce que m'indique le message d'erreur:
Je crois qu'à part le gars qu'a écrit le noyau, là...
Non, franchement, soit plus précis... Ca t'arrives quand ? T'as fait quoi avant le début des crashes ?
T'as quoi comme config ?
---------------
"This is like... everyone sees it, and everyone likes it, and I won't be the only geek in town anymore." - Pat Johnson, 5-25-77
C'est le signe d'un plantage kernel mais qui ne met pas seulement en cause ce driver systeme. C'est une sorte de ntoskrnl.....
Ces fichiers proteges ne peuvent pas etre bogues sur le HD car au reboot suivant le systeme les remettrait a neuf automatiquement.
Ca vient d'ailleurs.
Tu pourrais commencer par rebooter sur la console de recuperation puis taper chkdsk /p /r afin de controler l'integrite du HD.
Et je suppose que tu a fais un check de la ram avec Memtest ?
Message édité par bigbernie le 16-06-2006 à 09:48:08
Si ce n'est déjà fait, active l'event viewer pour les applications et le systeme (au moins!) et regarde si au moment du blue screen, il n'y a pas d'erreur detectée. Si oui, essaie de savoir ce qui cause cette erreur.
En analysant les dumps on peut connaitre la cause du break point mais c'est deja dans le message d'erreur. Je te signale aussi que Memtest a une version sur CD.
Tu peux mettre sur ce forum le contenu de ton dossier Minidump. Soit par ftp soit par YouSendit.
Je l'analyserai mais ça m'etonnerait que ça donne des indications sur un soft precis. Tu dois avoir un conflit hardware.
Il s'agit bien donc d'une erreur kernel. Mais comme le driver change ça vient d'autre chose.
Tu verras plus bas les explications.
Ton code d'erreur est
Bug Check 0x8E: KERNEL_MODE_EXCEPTION_NOT_HANDLED
The KERNEL_MODE_EXCEPTION_NOT_HANDLED bug check has a value of 0x0000008E. This indicates that a kernel-mode program generated an exception which the error handler did not catch.
Parameters
The following parameters are displayed on the blue screen.
Parameter Description 1 The exception code that was not handled 2 The address at which the exception occurred 3 The trap frame 4 Reserved
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.
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. Make sure you have enough disk space. 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 lack of disk space for installation and system BIOS incompatibilities. For problems during Windows installation that are associated with lack of disk space, reduce the number of files on the target hard disk. Check for and delete any unneeded temporary files, Internet cache files, application backup files, and .chk files containing saved file fragments from disk scans. You can also use another hard disk with more free space for the installation. BIOS problems can be resolved by upgrading the system BIOS version.
c'est bon je vous remercie j'ai détecter la source de mon problème, cela vient de ma carte mère (merci VIA) qui en fait foire et ne supporte pas la DDR noname ainsi que ma carte graphique (et comme ca cout moins chère d'acheter une carte mère que le reste ^^)
Dans 70% des ennuis c'est la ram. Soit par elle meme soit par ses implications.
Heureusement pour les ramasseurs de poubelles, trop peu de gens ne savent pas que les nonames sont des rams qui ne passent pas les certifications. Seules les A sont valables. Les B et encore plus les C sont des dechets. Ca ne devrait meme pas etre vendu mais heureusement pour les poubelleux il y a encore plein de fanatiques du prix le plus bas possible. Rien a dire commercialement. Le prix c'est comme la muletta que l'on agite devant el toro. L'animal (bipede) fonce dessus comme la verole sur un couvent de bonne soeur. Et apres on a des emmerdes tout le temps.
.
