Vous diminuez les moyens dont nous disposons pour vous proposer des contenus de qualités gratuits.
SVP laissez les publicités s'afficher ou soutenez le site :
Faire un don - si vous ne voulez pas afficher les publicités
J'ai voulue faire un retour en arrière vers Windows 7 après l'installation Windows 10 qui n'a pas été géniale.
Depuis, plus rien ne démarre sauf, en mode sans échec. J'ai un écran bleu permanent avant le démarrage.
Nom d’événement de problème: BlueScreen
Version du système: 6.1.7601.2.1.0.256.1
Identificateur de paramètres régionaux: 1036
Informations supplémentaires sur le problème :
BCCode: 1000007e
BCP1: FFFFFFFF80000003
BCP2: FFFFF88003D4B02D
BCP3: FFFFF880009A9428
BCP4: FFFFF880009A8C80
OS Version: 6_1_7601
Service Pack: 1_0
Product: 256_1
Welcome to WhoCrashed (HOME EDITION) v 5.51
--------------------------------------------------------------------------------
This program checks for drivers which have been crashing your computer. If your computer has displayed a blue (or black) screen of death, suddenly rebooted or shut down then this program will help you find the root cause and possibly a solution.
Whenever a computer suddenly reboots without displaying any notice or blue (or black) screen of death, the first thing that is often thought about is a hardware failure. In reality, on Windows most crashes are caused by malfunctioning device drivers and kernel modules. In case of a kernel error, many computers do not show a blue screen unless they are configured for this. Instead these systems suddenly reboot without any notice.
This program will analyze your crash dumps with the single click of a button. It will tell you what drivers are likely to be responsible for crashing your computer. It will report a conclusion which offers suggestions on how to proceed in any situation while the analysis report will display internet links which will help you further troubleshoot any detected problems.
To obtain technical support visit http://www.resplendence.com/support
Click here to check if you have the latest version or if an update is available.
Just click the Analyze button for a comprehensible report ...
--------------------------------------------------------------------------------
Home Edition Notice
--------------------------------------------------------------------------------
This version of WhoCrashed is free for use at home only. If you would like to use this software at work or in a commercial environment you should get the professional edition of WhoCrashed which allows you to perform more thorough and detailed analysis. It also offers a range of additional features such as remote analysis on remote directories and remote computers on the network.
Click here for more information on the professional edition.
Click here to buy the the professional edition of WhoCrashed.
--------------------------------------------------------------------------------
System Information (local)
--------------------------------------------------------------------------------
Computer name: CAISSE-PC
Windows version: Windows 7 Service Pack 1, 6.1, build: 7601
Windows dir: C:\Windows
Hardware: HP Compaq 8000 Elite SFF PC, Hewlett-Packard, 3646h
CPU: GenuineIntel Pentium(R) Dual-Core CPU E5400 @ 2.70GHz Intel586, level: 6
2 logical processors, active mask: 3
RAM: 2073292800 bytes total
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Wed 06/01/2016 09:38:14 GMT your computer crashed
crash dump file: C:\Windows\Minidump\010616-36332-01.dmp
This was probably caused by the following module: avkmgr.sys (avkmgr+0x802D)
Bugcheck code: 0x1000007E (0xFFFFFFFF80000003, 0xFFFFF88003AD002D, 0xFFFFF880009A9428, 0xFFFFF880009A8C80)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\avkmgr.sys
product: Avira Product Family
company: Avira Operations GmbH & Co. KG
description: Avira Manager 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.
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: avkmgr.sys (Avira Manager Driver, Avira Operations GmbH & Co. KG).
Google query: Avira Operations GmbH & Co. KG SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
On Wed 06/01/2016 09:38:14 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: avkmgr.sys (avkmgr!funcd+0x2AAE)
Bugcheck code: 0x7E (0xFFFFFFFF80000003, 0xFFFFF88003AD002D, 0xFFFFF880009A9428, 0xFFFFF880009A8C80)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\drivers\avkmgr.sys
product: Avira Product Family
company: Avira Operations GmbH & Co. KG
description: Avira Manager Driver
Bug check description: This bug check indicates that a system thread generated an exception that the error handler did not catch.
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: avkmgr.sys (Avira Manager Driver, Avira Operations GmbH & Co. KG).
Google query: Avira Operations GmbH & Co. KG SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
2 crash dumps have been found and analyzed. A third party driver has 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:
avkmgr.sys (Avira Manager Driver, Avira Operations GmbH & Co. KG)
If no updates for these drivers are available, try searching with Google on the names of these drivers in combination with the errors that have been reported for these drivers. Include the brand and model name of your computer as well in the query. This often yields interesting results from discussions on the web by 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 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
Problème réglé, merci !!!!
J'ai changé d'antivirus comme tu m'as dit et ça fonctionne à nouveau.
Par contre j'ai l'impression qu'avec celui là il est plus lent qu'avant.