A voir également:
- Message d'erreur au démarrage
- Message - Guide
- Erreur 0x80070643 - Accueil - Windows
- Pc lent au démarrage - Guide
- Reinitialiser pc au demarrage - Guide
- Forcer demarrage pc - Guide
5 réponses
intoxx62
Messages postés
361
Date d'inscription
lundi 3 janvier 2011
Statut
Membre
Dernière intervention
13 mars 2015
70
19 févr. 2013 à 09:33
19 févr. 2013 à 09:33
Salut, tu n'arrive plus à accéder à ta session ?
Et quand tu fais la récupération, cela fonctionne (tu peux aller sur ta session)?
Et quand tu fais la récupération, cela fonctionne (tu peux aller sur ta session)?
Utilisateur anonyme
19 févr. 2013 à 09:41
19 févr. 2013 à 09:41
salut
si une fois que je le fais ça refonctionne
ça a commencé hier après-midi
la 1ere fois, la j'ai du éteindre le pc après la récup
et ce matin, juste un redémarrage
mais apparemment, je dois passer par là
sinon oui, je récupère ma session
si une fois que je le fais ça refonctionne
ça a commencé hier après-midi
la 1ere fois, la j'ai du éteindre le pc après la récup
et ce matin, juste un redémarrage
mais apparemment, je dois passer par là
sinon oui, je récupère ma session
intoxx62
Messages postés
361
Date d'inscription
lundi 3 janvier 2011
Statut
Membre
Dernière intervention
13 mars 2015
70
19 févr. 2013 à 09:46
19 févr. 2013 à 09:46
Tu as installé des applications hier ou quelques jours avant ? Fais des tests avec ton matériel ? Sinon, d'après la page : https://docs.microsoft.com/en-us/windows-hardware/drivers/debugger/bug-check-0x7e--system-thread-exception-not-handled?redirectedfrom=MSDN , le message survient pour éviter justement des problèmes (soit de disques(mal formatés ou défaillants voir fichiers manquants), virus...
C'est quand même bizarre, je ne sais pas exactement mais si jamais tu ne trouve pas de solutions vois pour réinstaller Windows (a moins qu'un gars passe ici pour te help) car je ne vois pas trop comment le régler.
C'est quand même bizarre, je ne sais pas exactement mais si jamais tu ne trouve pas de solutions vois pour réinstaller Windows (a moins qu'un gars passe ici pour te help) car je ne vois pas trop comment le régler.
non justement, je n'ai rien installé depuis 2 semaines :/
mais merci pour le coup de main
j'espère ne pas devoir réinstaller windows
le pc n'a qu'un mois ^^
mais merci pour le coup de main
j'espère ne pas devoir réinstaller windows
le pc n'a qu'un mois ^^
Vous n’avez pas trouvé la réponse que vous recherchez ?
Posez votre question
Utilisateur anonyme
19 févr. 2013 à 10:46
19 févr. 2013 à 10:46
voici le rapport donné par le programme whocrashed
System Information (local)
--------------------------------------------------------------------------------
computer name: PC-MICA
windows version: Windows 8 , 6.2, build: 9200
windows dir: C:\Windows
CPU: AuthenticAMD AMD A6-4455M APU with Radeon(tm) HD Graphics AMD586, level: 21
2 logical processors, active mask: 3
RAM: 5849231360 total
VM: 2147352576, free: 1928658944
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Tue 19-02-13 08:06:49 GMT your computer crashed
crash dump file: C:\Windows\Minidump\021913-19063-01.dmp
This was probably caused by the following module: ndu.sys (Ndu+0x3D20)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF88019779D20, 0xFFFFF8800531E6E8, 0xFFFFF8800531DF20)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\ndu.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Windows Network Data Usage Monitoring Driver
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 that cannot be identified at this time.
On Thu 07-02-13 19:54:02 GMT your computer crashed
crash dump file: C:\Windows\Minidump\020713-21996-01.dmp
This was probably caused by the following module: watchdog.sys (watchdog+0x255D)
Bugcheck code: 0x119 (0x1, 0x4110, 0x4110, 0x410F)
Error: VIDEO_SCHEDULER_INTERNAL_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 video scheduler has detected a fatal 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 that cannot be identified at this time.
On Thu 17-01-13 04:31:32 GMT your computer crashed
crash dump file: C:\Windows\Minidump\011713-46051-01.dmp
This was probably caused by the following module: tcpip.sys (tcpip+0x137EC3)
Bugcheck code: 0xD1 (0x158, 0x2, 0x1, 0xFFFFF88001B63EC3)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\tcpip.sys
product: Système d'exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote TCP/IP
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
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.
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
3 crash dumps have been found and analyzed. No offending third party drivers have been found. Consider configuring your system to produce a full memory dump for better analysis.
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.
System Information (local)
--------------------------------------------------------------------------------
computer name: PC-MICA
windows version: Windows 8 , 6.2, build: 9200
windows dir: C:\Windows
CPU: AuthenticAMD AMD A6-4455M APU with Radeon(tm) HD Graphics AMD586, level: 21
2 logical processors, active mask: 3
RAM: 5849231360 total
VM: 2147352576, free: 1928658944
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Tue 19-02-13 08:06:49 GMT your computer crashed
crash dump file: C:\Windows\Minidump\021913-19063-01.dmp
This was probably caused by the following module: ndu.sys (Ndu+0x3D20)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF88019779D20, 0xFFFFF8800531E6E8, 0xFFFFF8800531DF20)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\ndu.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Windows Network Data Usage Monitoring Driver
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 that cannot be identified at this time.
On Thu 07-02-13 19:54:02 GMT your computer crashed
crash dump file: C:\Windows\Minidump\020713-21996-01.dmp
This was probably caused by the following module: watchdog.sys (watchdog+0x255D)
Bugcheck code: 0x119 (0x1, 0x4110, 0x4110, 0x410F)
Error: VIDEO_SCHEDULER_INTERNAL_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 video scheduler has detected a fatal 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 that cannot be identified at this time.
On Thu 17-01-13 04:31:32 GMT your computer crashed
crash dump file: C:\Windows\Minidump\011713-46051-01.dmp
This was probably caused by the following module: tcpip.sys (tcpip+0x137EC3)
Bugcheck code: 0xD1 (0x158, 0x2, 0x1, 0xFFFFF88001B63EC3)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\tcpip.sys
product: Système d'exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote TCP/IP
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
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.
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
3 crash dumps have been found and analyzed. No offending third party drivers have been found. Consider configuring your system to produce a full memory dump for better analysis.
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.