ah merci monk521, ce logiciel est merveilleux meme pas besoin de tester, il analyse les crashes precedents, voila le rapport:
computer name: NONO-AMD
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
Hardware: ASRock, 990FX Killer
CPU: AuthenticAMD AMD FX(tm)-8350 Eight-Core Processor AMD586, level: 21
8 logical processors, active mask: 255
RAM: 8544194560 total
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Mon 13/10/2014 14:56:07 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: Unknown (0xFFFFF800022E3438)
Bugcheck code: 0xA (0x8, 0x2, 0x1, 0xFFFFF800022E3438)
Error: IRQL_NOT_LESS_OR_EQUAL
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
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.
Google query: IRQL_NOT_LESS_OR_EQUAL
On Thu 09/10/2014 17:17:53 GMT your computer crashed
crash dump file: C:\Windows\Minidump\101014-13743-01.dmp
This was probably caused by the following module: usbport.sys (USBPORT+0x15BB3)
Bugcheck code: 0xD1 (0x26179, 0x2, 0x1, 0xFFFFF88008015BB3)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\usbport.sys
product: MicrosoftR WindowsR Operating System
company: Microsoft Corporation
description: USB 1.1 & 2.0 Port Driver
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.
On Thu 09/10/2014 14:10:18 GMT your computer crashed
crash dump file: C:\Windows\Minidump\100914-13556-01.dmp
This was probably caused by the following module: tcpip.sys (tcpip+0x62745)
Bugcheck code: 0xD1 (0x54, 0x2, 0x1, 0xFFFFF88001863745)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\tcpip.sys
product: MicrosoftR WindowsR Operating System
company: Microsoft Corporation
description: TCP/IP Driver
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.
On Thu 18/09/2014 13:16:02 GMT your computer crashed
crash dump file: C:\Windows\Minidump\091814-14149-01.dmp
This was probably caused by the following module: ndis.sys (ndis+0x1584)
Bugcheck code: 0xD1 (0x2A, 0x2, 0x1, 0xFFFFF8800164E584)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\ndis.sys
product: MicrosoftR WindowsR Operating System
company: Microsoft Corporation
description: NDIS 6.20 driver
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.
On Mon 01/09/2014 14:47:24 GMT your computer crashed
crash dump file: C:\Windows\Minidump\090114-14508-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF800020F3622, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\ntoskrnl.exe
product: MicrosoftR WindowsR Operating System
company: Microsoft Corporation
description: NT Kernel & System
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.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Sun 31/08/2014 16:26:59 GMT your computer crashed
crash dump file: C:\Windows\Minidump\090114-14164-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75B90)
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\ntoskrnl.exe
product: MicrosoftR WindowsR Operating System
company: Microsoft Corporation
description: NT Kernel & System
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.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Tue 15/04/2014 13:50:09 GMT your computer crashed
crash dump file: C:\Windows\Minidump\041514-43461-01.dmp
This was probably caused by the following module: etronxhci.sys (0xFFFFF88005592A20)
Bugcheck code: 0xD1 (0xC, 0x2, 0x0, 0xFFFFF88005592A20)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\etronxhci.sys
product: Etron xHCI Driver.
company: Etron Technology Inc
description: Etron eXtensible Host Controller Driver.
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.
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: etronxhci.sys (Etron eXtensible Host Controller Driver., Etron Technology Inc).
Google query: Etron Technology Inc DRIVER_IRQL_NOT_LESS_OR_EQUAL
On Fri 21/03/2014 14:34:28 GMT your computer crashed
crash dump file: C:\Windows\Minidump\032114-53102-01.dmp
This was probably caused by the following module: etronxhci.sys (0xFFFFF880053A9A20)
Bugcheck code: 0xD1 (0xC, 0x2, 0x0, 0xFFFFF880053A9A20)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\etronxhci.sys
product: Etron xHCI Driver.
company: Etron Technology Inc
description: Etron eXtensible Host Controller Driver.
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.
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: etronxhci.sys (Etron eXtensible Host Controller Driver., Etron Technology Inc).
Google query: Etron Technology Inc DRIVER_IRQL_NOT_LESS_OR_EQUAL
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
8 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:
etronxhci.sys (Etron eXtensible Host Controller Driver., Etron Technology Inc)
If no updates for these drivers are available, try searching with Google on the names of these drivers in combination the errors that have been reported for these drivers and include the brand and model name of your computer as well in the query. This often yields interesting results from discussions from 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.
Donc du driver etron usb de merde apparemment...qu'en pensez vous ?
---------------
FX8350@4700, NH-D15 R9 fury Nitro, Asrock 990fx killer, 16go DDR3,
. La ram est overclockee aussi a cause du fsb a 220 donc a 1866 au lieu des 1600mhz de base.
Il faut effacer ton message précédent, la charte du forum interdit ce mode d'affichage, et poster le rapport selon le tuto suivant:
) en esperant un changement ds la gestion de l'usb merdique...
je préfère une statue...
Fais gaffe quand même avec ce procédé. Crée un point de restauration avant.