Ecran de la mort, redémarage récurant ! windows 8.1
Picsoux49
Messages postés
2
Statut
Membre
-
Picsoux49 Messages postés 2 Statut Membre -
Picsoux49 Messages postés 2 Statut Membre -
Voila toutes les 30 a 45 min mon PC crash et redémarre.
J'ai testé la ram mais il semble que ce n'est pas sa.
Il semblerais que sa serais peut être un driver Xbox wirless d'après des forum anglais mais mon niveau dans cette langue est faible.
Voici le code erreur : Kmode_Exeption_not_Handled mt7612US.syst
Si vous en savez plus; je suis preneur :)
J'ai testé la ram mais il semble que ce n'est pas sa.
Il semblerais que sa serais peut être un driver Xbox wirless d'après des forum anglais mais mon niveau dans cette langue est faible.
Voici le code erreur : Kmode_Exeption_not_Handled mt7612US.syst
Si vous en savez plus; je suis preneur :)
A voir également:
- Ecran de la mort, redémarage récurant ! windows 8.1
- Clé windows 8.1 - Guide
- Dupliquer ecran windows - Guide
- Retourner ecran windows - Guide
- Montage video gratuit windows - Guide
- Capture d'écran whatsapp - Accueil - Messagerie instantanée
1 réponse
Voici le rapport de WhoCrashed :
System Information (local)
--------------------------------------------------------------------------------
Computer name: NICOLAS
Windows version: Windows 8.1 , 6.3, build: 9600
Windows dir: C:\WINDOWS
Hardware: All Series, ASUS, ASUSTeK COMPUTER INC., H81I-PLUS
CPU: GenuineIntel Intel(R) Core(TM) i5-4590 CPU @ 3.30GHz Intel586, level: 6
4 logical processors, active mask: 15
RAM: 8523153408 bytes total
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\WINDOWS\Minidump
Crash dumps are enabled on your computer.
On Sun 24/04/2016 15:58:00 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\042416-14000-01.dmp
This was probably caused by the following module: mt7612us.sys (mt7612US+0x3262F)
Bugcheck code: 0x1E (0xFFFFFFFF80000003, 0xFFFFF8019D03262F, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\WINDOWS\system32\drivers\mt7612us.sys
product: MediaTek Inc. MT7612 Wireless LAN Adapter Driver
company: MediaTek Inc.
description: MT7612U Phoenix Driver
Bug check description: This indicates that a kernel-mode program 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: mt7612us.sys (MT7612U Phoenix Driver, MediaTek Inc.).
Google query: MediaTek Inc. KMODE_EXCEPTION_NOT_HANDLED
On Sun 24/04/2016 15:58:00 GMT your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: mt7612us.sys (mt7612US+0x32630)
Bugcheck code: 0x1E (0xFFFFFFFF80000003, 0xFFFFF8019D03262F, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\WINDOWS\system32\drivers\mt7612us.sys
product: MediaTek Inc. MT7612 Wireless LAN Adapter Driver
company: MediaTek Inc.
description: MT7612U Phoenix Driver
Bug check description: This indicates that a kernel-mode program 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: mt7612us.sys (MT7612U Phoenix Driver, MediaTek Inc.).
Google query: MediaTek Inc. KMODE_EXCEPTION_NOT_HANDLED
On Sun 24/04/2016 15:07:07 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\042416-13625-01.dmp
This was probably caused by the following module: mt7612us.sys (mt7612US+0x3262F)
Bugcheck code: 0x1E (0xFFFFFFFF80000003, 0xFFFFF80068F7F62F, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\WINDOWS\system32\drivers\mt7612us.sys
product: MediaTek Inc. MT7612 Wireless LAN Adapter Driver
company: MediaTek Inc.
description: MT7612U Phoenix Driver
Bug check description: This indicates that a kernel-mode program 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: mt7612us.sys (MT7612U Phoenix Driver, MediaTek Inc.).
Google query: MediaTek Inc. KMODE_EXCEPTION_NOT_HANDLED
On Sun 24/04/2016 14:18:28 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\042416-20796-01.dmp
This was probably caused by the following module: mt7612us.sys (mt7612US+0x3262F)
Bugcheck code: 0x1E (0xFFFFFFFF80000003, 0xFFFFF8008879162F, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\WINDOWS\system32\drivers\mt7612us.sys
product: MediaTek Inc. MT7612 Wireless LAN Adapter Driver
company: MediaTek Inc.
description: MT7612U Phoenix Driver
Bug check description: This indicates that a kernel-mode program 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: mt7612us.sys (MT7612U Phoenix Driver, MediaTek Inc.).
Google query: MediaTek Inc. KMODE_EXCEPTION_NOT_HANDLED
On Sat 23/04/2016 23:31:51 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\042416-15515-01.dmp
This was probably caused by the following module: mt7612us.sys (mt7612US+0x3262F)
Bugcheck code: 0x1E (0xFFFFFFFF80000003, 0xFFFFF800FA16562F, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\WINDOWS\system32\drivers\mt7612us.sys
product: MediaTek Inc. MT7612 Wireless LAN Adapter Driver
company: MediaTek Inc.
description: MT7612U Phoenix Driver
Bug check description: This indicates that a kernel-mode program 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: mt7612us.sys (MT7612U Phoenix Driver, MediaTek Inc.).
Google query: MediaTek Inc. KMODE_EXCEPTION_NOT_HANDLED
On Sat 23/04/2016 13:51:03 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\042316-17453-01.dmp
This was probably caused by the following module: mt7612us.sys (mt7612US+0x3262F)
Bugcheck code: 0x1E (0xFFFFFFFF80000003, 0xFFFFF8015250962F, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\WINDOWS\system32\drivers\mt7612us.sys
product: MediaTek Inc. MT7612 Wireless LAN Adapter Driver
company: MediaTek Inc.
description: MT7612U Phoenix Driver
Bug check description: This indicates that a kernel-mode program 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: mt7612us.sys (MT7612U Phoenix Driver, MediaTek Inc.).
Google query: MediaTek Inc. KMODE_EXCEPTION_NOT_HANDLED
On Sat 23/04/2016 13:44:48 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\042316-22078-01.dmp
This was probably caused by the following module: mt7612us.sys (mt7612US+0x3262F)
Bugcheck code: 0x1E (0xFFFFFFFF80000003, 0xFFFFF801AA54862F, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\WINDOWS\system32\drivers\mt7612us.sys
product: MediaTek Inc. MT7612 Wireless LAN Adapter Driver
company: MediaTek Inc.
description: MT7612U Phoenix Driver
Bug check description: This indicates that a kernel-mode program 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: mt7612us.sys (MT7612U Phoenix Driver, MediaTek Inc.).
Google query: MediaTek Inc. KMODE_EXCEPTION_NOT_HANDLED
On Fri 22/04/2016 23:28:10 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\042316-21375-01.dmp
This was probably caused by the following module: mt7612us.sys (mt7612US+0x3262F)
Bugcheck code: 0x1E (0xFFFFFFFF80000003, 0xFFFFF801E831062F, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\WINDOWS\system32\drivers\mt7612us.sys
product: MediaTek Inc. MT7612 Wireless LAN Adapter Driver
company: MediaTek Inc.
description: MT7612U Phoenix Driver
Bug check description: This indicates that a kernel-mode program 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: mt7612us.sys (MT7612U Phoenix Driver, MediaTek Inc.).
Google query: MediaTek Inc. KMODE_EXCEPTION_NOT_HANDLED
On Fri 22/04/2016 22:44:17 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\042316-11921-01.dmp
This was probably caused by the following module: mt7612us.sys (mt7612US+0x3262F)
Bugcheck code: 0x1E (0xFFFFFFFF80000003, 0xFFFFF8017E43262F, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\WINDOWS\system32\drivers\mt7612us.sys
product: MediaTek Inc. MT7612 Wireless LAN Adapter Driver
company: MediaTek Inc.
description: MT7612U Phoenix Driver
Bug check description: This indicates that a kernel-mode program 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: mt7612us.sys (MT7612U Phoenix Driver, MediaTek Inc.).
Google query: MediaTek Inc. KMODE_EXCEPTION_NOT_HANDLED
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
9 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:
mt7612us.sys (MT7612U Phoenix Driver, MediaTek Inc.)
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.
System Information (local)
--------------------------------------------------------------------------------
Computer name: NICOLAS
Windows version: Windows 8.1 , 6.3, build: 9600
Windows dir: C:\WINDOWS
Hardware: All Series, ASUS, ASUSTeK COMPUTER INC., H81I-PLUS
CPU: GenuineIntel Intel(R) Core(TM) i5-4590 CPU @ 3.30GHz Intel586, level: 6
4 logical processors, active mask: 15
RAM: 8523153408 bytes total
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\WINDOWS\Minidump
Crash dumps are enabled on your computer.
On Sun 24/04/2016 15:58:00 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\042416-14000-01.dmp
This was probably caused by the following module: mt7612us.sys (mt7612US+0x3262F)
Bugcheck code: 0x1E (0xFFFFFFFF80000003, 0xFFFFF8019D03262F, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\WINDOWS\system32\drivers\mt7612us.sys
product: MediaTek Inc. MT7612 Wireless LAN Adapter Driver
company: MediaTek Inc.
description: MT7612U Phoenix Driver
Bug check description: This indicates that a kernel-mode program 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: mt7612us.sys (MT7612U Phoenix Driver, MediaTek Inc.).
Google query: MediaTek Inc. KMODE_EXCEPTION_NOT_HANDLED
On Sun 24/04/2016 15:58:00 GMT your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: mt7612us.sys (mt7612US+0x32630)
Bugcheck code: 0x1E (0xFFFFFFFF80000003, 0xFFFFF8019D03262F, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\WINDOWS\system32\drivers\mt7612us.sys
product: MediaTek Inc. MT7612 Wireless LAN Adapter Driver
company: MediaTek Inc.
description: MT7612U Phoenix Driver
Bug check description: This indicates that a kernel-mode program 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: mt7612us.sys (MT7612U Phoenix Driver, MediaTek Inc.).
Google query: MediaTek Inc. KMODE_EXCEPTION_NOT_HANDLED
On Sun 24/04/2016 15:07:07 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\042416-13625-01.dmp
This was probably caused by the following module: mt7612us.sys (mt7612US+0x3262F)
Bugcheck code: 0x1E (0xFFFFFFFF80000003, 0xFFFFF80068F7F62F, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\WINDOWS\system32\drivers\mt7612us.sys
product: MediaTek Inc. MT7612 Wireless LAN Adapter Driver
company: MediaTek Inc.
description: MT7612U Phoenix Driver
Bug check description: This indicates that a kernel-mode program 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: mt7612us.sys (MT7612U Phoenix Driver, MediaTek Inc.).
Google query: MediaTek Inc. KMODE_EXCEPTION_NOT_HANDLED
On Sun 24/04/2016 14:18:28 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\042416-20796-01.dmp
This was probably caused by the following module: mt7612us.sys (mt7612US+0x3262F)
Bugcheck code: 0x1E (0xFFFFFFFF80000003, 0xFFFFF8008879162F, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\WINDOWS\system32\drivers\mt7612us.sys
product: MediaTek Inc. MT7612 Wireless LAN Adapter Driver
company: MediaTek Inc.
description: MT7612U Phoenix Driver
Bug check description: This indicates that a kernel-mode program 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: mt7612us.sys (MT7612U Phoenix Driver, MediaTek Inc.).
Google query: MediaTek Inc. KMODE_EXCEPTION_NOT_HANDLED
On Sat 23/04/2016 23:31:51 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\042416-15515-01.dmp
This was probably caused by the following module: mt7612us.sys (mt7612US+0x3262F)
Bugcheck code: 0x1E (0xFFFFFFFF80000003, 0xFFFFF800FA16562F, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\WINDOWS\system32\drivers\mt7612us.sys
product: MediaTek Inc. MT7612 Wireless LAN Adapter Driver
company: MediaTek Inc.
description: MT7612U Phoenix Driver
Bug check description: This indicates that a kernel-mode program 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: mt7612us.sys (MT7612U Phoenix Driver, MediaTek Inc.).
Google query: MediaTek Inc. KMODE_EXCEPTION_NOT_HANDLED
On Sat 23/04/2016 13:51:03 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\042316-17453-01.dmp
This was probably caused by the following module: mt7612us.sys (mt7612US+0x3262F)
Bugcheck code: 0x1E (0xFFFFFFFF80000003, 0xFFFFF8015250962F, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\WINDOWS\system32\drivers\mt7612us.sys
product: MediaTek Inc. MT7612 Wireless LAN Adapter Driver
company: MediaTek Inc.
description: MT7612U Phoenix Driver
Bug check description: This indicates that a kernel-mode program 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: mt7612us.sys (MT7612U Phoenix Driver, MediaTek Inc.).
Google query: MediaTek Inc. KMODE_EXCEPTION_NOT_HANDLED
On Sat 23/04/2016 13:44:48 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\042316-22078-01.dmp
This was probably caused by the following module: mt7612us.sys (mt7612US+0x3262F)
Bugcheck code: 0x1E (0xFFFFFFFF80000003, 0xFFFFF801AA54862F, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\WINDOWS\system32\drivers\mt7612us.sys
product: MediaTek Inc. MT7612 Wireless LAN Adapter Driver
company: MediaTek Inc.
description: MT7612U Phoenix Driver
Bug check description: This indicates that a kernel-mode program 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: mt7612us.sys (MT7612U Phoenix Driver, MediaTek Inc.).
Google query: MediaTek Inc. KMODE_EXCEPTION_NOT_HANDLED
On Fri 22/04/2016 23:28:10 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\042316-21375-01.dmp
This was probably caused by the following module: mt7612us.sys (mt7612US+0x3262F)
Bugcheck code: 0x1E (0xFFFFFFFF80000003, 0xFFFFF801E831062F, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\WINDOWS\system32\drivers\mt7612us.sys
product: MediaTek Inc. MT7612 Wireless LAN Adapter Driver
company: MediaTek Inc.
description: MT7612U Phoenix Driver
Bug check description: This indicates that a kernel-mode program 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: mt7612us.sys (MT7612U Phoenix Driver, MediaTek Inc.).
Google query: MediaTek Inc. KMODE_EXCEPTION_NOT_HANDLED
On Fri 22/04/2016 22:44:17 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\042316-11921-01.dmp
This was probably caused by the following module: mt7612us.sys (mt7612US+0x3262F)
Bugcheck code: 0x1E (0xFFFFFFFF80000003, 0xFFFFF8017E43262F, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\WINDOWS\system32\drivers\mt7612us.sys
product: MediaTek Inc. MT7612 Wireless LAN Adapter Driver
company: MediaTek Inc.
description: MT7612U Phoenix Driver
Bug check description: This indicates that a kernel-mode program 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: mt7612us.sys (MT7612U Phoenix Driver, MediaTek Inc.).
Google query: MediaTek Inc. KMODE_EXCEPTION_NOT_HANDLED
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
9 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:
mt7612us.sys (MT7612U Phoenix Driver, MediaTek Inc.)
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.
