Mon PC fait des écrans bleu à répétition Fermé

Question

Bonjour, 

Depuis un moment mon pc windows 7 acer ax 3400 me fait des ecran bleu et il redemare tout seul. Je n'ai pas le temps de tout relever. J'ai reussi a avoir quelque imformation écrite a l'écran : Driver_Irql_not_less_or_Equal arhrxusb.sys.

Quand mon ordinateur a redemarer il me met un rapport d'erreur où il est ecrit :


Signature du problème :
  Nom d'événement de problème:	BlueScreen
  Version du système:	6.1.7601.2.1.0.768.3
  Identificateur de paramètres régionaux:	1036

Informations supplémentaires sur le problème :
  BCCode:	1e
  BCP1:	0000000000000000
  BCP2:	0000000000000000
  BCP3:	0000000000000000
  BCP4:	0000000000000000
  OS Version:	6_1_7601
  Service Pack:	1_0
  Product:	768_1

Fichiers aidant à décrire le problème :
  C:\Windows\Minidump\052512-18735-01.dmp
  C:\Users\gaetan\AppData\Local\Temp\WER-48968-0.sysdata.xml

Lire notre déclaration de confidentialité en ligne :
  https://privacy.microsoft.com/fr-fr/windows-7-privacy-statement

Si la déclaration de confidentialité en ligne n'est pas disponible, lisez la version hors connexion :
  C:\Windows\system32\fr-FR\erofflps.txt

Merci de pouvoir m'aider

lilidurhone · Answer

Bienvenue sur CCM

Avant toute chose je souhaite éclaircir quelques points

Je vais te proposer deux logiciels sans danger qui permettront à ton helpeur d'y voir un peu plus clair

Sache que ça ne sera pas moi qui te désinfecterai car je n'ai pas l'autorisation

Reste zen et sois très patient car les helpeurs sont bénévoles et ont une vie en dehors de CCM

Dans un premier temps tu téléchargera le logiciel whocrashed qui permettra de savoir si ça vient d'un pilote https://www.commentcamarche.net/telecharger/utilitaires/23795-whocrashed-free-home-edition/
installe le et exécute le en tant qu'administrateur il analysera ton ordinateur et génèrera un  rapport colles le dans ta prochaine réponse

Dans un second temps je te propose un autre logiciel qui permettra de savoir si tout est à jour pilotes et logiciels
Rends toi à cette adresse https://www.getsysteminfo.com/
Cliques sur télécharger
Une fenêtre s'ouvrira pour commencer le téléchargement
Patientes jusqu'à que le téléchargement soit terminé
Double clic dessus
Acceptes la licence
Il te scannera l'ordinateur
Un rapport sera généré
Publie le dans ta prochaine réponse

Quelqu'un de plus compétent que moi prendra le relais

Bonne journée

psg6110 · Answer

Merci pour ta réponse très rapide lilidurhome. Je vais faire ces analyse le plus rapidement et je publierai les resultat dans le forum.

Bonne journée

psg6110 · Answer

System Information (local)
--------------------------------------------------------------------------------

computer name: GAETAN-PC
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
CPU: AuthenticAMD AMD Athlon(tm) II X2 220 Processor AMD586, level: 16
2 logical processors, active mask: 3
RAM: 4025729024 total
VM: 2147352576, free: 1885184000



--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.


On Fri 25/05/2012 20:54:08 GMT your computer crashed
crash dump file: C:\Windows\Minidump\052512-23758-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0) 
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80002EA5C3E, 0xFFFFF8800CB3A190, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32
toskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code. 
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 which cannot be identified at this time. 


On Fri 25/05/2012 20:54:08 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: aswsnx.sys (aswSnx+0x16319) 
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80002EA5C3E, 0xFFFFF8800CB3A190, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\drivers\aswsnx.sys
product: avast! Antivirus System
company: AVAST Software
description: avast! Virtualization Driver
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code. 
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: aswsnx.sys (avast! Virtualization Driver, AVAST Software). 
Google query: aswsnx.sys AVAST Software SYSTEM_SERVICE_EXCEPTION




On Fri 25/05/2012 19:59:06 GMT your computer crashed
crash dump file: C:\Windows\Minidump\052512-18735-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F190) 
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32
toskrnl.exe
product: Microsoft® Windows® 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 which cannot be identified at this time. 


On Thu 24/05/2012 22:12:01 GMT your computer crashed
crash dump file: C:\Windows\Minidump\052512-18408-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F190) 
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32
toskrnl.exe
product: Microsoft® Windows® 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 which cannot be identified at this time. 


On Thu 24/05/2012 10:59:10 GMT your computer crashed
crash dump file: C:\Windows\Minidump\052412-16442-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F190) 
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32
toskrnl.exe
product: Microsoft® Windows® 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 which cannot be identified at this time. 


On Tue 22/05/2012 09:13:33 GMT your computer crashed
crash dump file: C:\Windows\Minidump\052212-20061-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F190) 
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32
toskrnl.exe
product: Microsoft® Windows® 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 which cannot be identified at this time. 


On Mon 21/05/2012 05:19:39 GMT your computer crashed
crash dump file: C:\Windows\Minidump\052112-23025-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0) 
Bugcheck code: 0xD1 (0x5BA8D29, 0x2, 0x0, 0xFFFFF880078C20E1)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32
toskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
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 the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time. 


On Tue 15/05/2012 21:41:10 GMT your computer crashed
crash dump file: C:\Windows\Minidump\051512-18408-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F190) 
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32
toskrnl.exe
product: Microsoft® Windows® 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 which cannot be identified at this time. 


On Mon 14/05/2012 20:31:29 GMT your computer crashed
crash dump file: C:\Windows\Minidump\051412-16146-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F190) 
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32
toskrnl.exe
product: Microsoft® Windows® 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 which cannot be identified at this time. 


On Sun 13/05/2012 19:46:32 GMT your computer crashed
crash dump file: C:\Windows\Minidump\051412-22635-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F190) 
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32
toskrnl.exe
product: Microsoft® Windows® 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 which cannot be identified at this time. 


On Thu 10/05/2012 18:01:29 GMT your computer crashed
crash dump file: C:\Windows\Minidump\051012-19936-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F190) 
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32
toskrnl.exe
product: Microsoft® Windows® 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 which cannot be identified at this time. 


On Thu 10/05/2012 13:12:41 GMT your computer crashed
crash dump file: C:\Windows\Minidump\051012-15615-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC80) 
Bugcheck code: 0xD1 (0x8005B8554E, 0x2, 0x0, 0xFFFFF880078B10E1)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32
toskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
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 the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time. 


On Thu 10/05/2012 12:09:13 GMT your computer crashed
crash dump file: C:\Windows\Minidump\051012-27190-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC80) 
Bugcheck code: 0xD1 (0x550B993, 0x2, 0x0, 0xFFFFF880075250E1)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32
toskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
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 the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time. 


On Thu 10/05/2012 05:37:34 GMT your computer crashed
crash dump file: C:\Windows\Minidump\051012-19312-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC50) 
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32
toskrnl.exe
product: Microsoft® Windows® 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 which cannot be identified at this time. 


On Wed 09/05/2012 12:31:14 GMT your computer crashed
crash dump file: C:\Windows\Minidump\050912-22183-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7FB7A) 
Bugcheck code: 0x1000009F (0x4, 0x258, 0xFFFFFA80036F5B60, 0xFFFFF80000B9C510)
Error: CUSTOM_ERROR
file path: C:\Windows\system32
toskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time. 



--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------

16 crash dumps have been found and analyzed. Only 15 are included in this report. 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: 

aswsnx.sys (avast! Virtualization Driver, AVAST Software)

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 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.

psg6110 · Answer

Code rouge:

Pilote(s) à mettre à jour :	[0]
Programme(s) à mettre à jour :	[0]
Inconnu trouvé :	[12]
Fichier(s) non fiable(s) :	[0]
Logiciel(s) potentiellement incompatible(s) :	[46]
Hosts :	original
Fichier(s) potentiellement infecté(s) :	[0]

Inconnu


Pilotes démarrés dans ...

chrome.exe [4]
=> C:\Users\gaetan\AppData\Local\Google\Chrome\Application\19.0.1084.52\ppgooglenaclpluginchrome.dll
=> C:\Users\gaetan\AppData\Local\Google\Chrome\Application\19.0.1084.52\avcodec-54.dll
=> C:\Users\gaetan\AppData\Local\Google\Chrome\Application\19.0.1084.52\avutil-51.dll
=> C:\Users\gaetan\AppData\Local\Google\Chrome\Application\19.0.1084.52\avformat-54.dll


Dossiers analysés

 C:\Users\gaetan\AppData\Local\Temp\ [1]
=> C:\Users\gaetan\AppData\Local\Temp\utt1DB0.tmp.exe

 C:\Users\gaetan\AppData\Local\Temp\CCIS\ [1]
=> C:\Users\gaetan\AppData\Local\Temp\CCIS\ccsqlh.exe

 C:\Users\gaetan\AppData\Local\Temp\DX6D24.tmp\ [2]
=> C:\Users\gaetan\AppData\Local\Temp\DX6D24.tmp\d3dx9_36.dll
=> C:\Users\gaetan\AppData\Local\Temp\DX6D24.tmp\infinst.exe

Incompatible 


Programmes installés [1]

=> avast! Free Antivirus

Processus démarrés

=> Nom C:\Program Files\Alwil Software\Avast5\AvastUI.exe" /nogui - avast! Antivirus

Pilotes démarrés dans ...

jusched.exe [1]
=> Nom C:\Program Files\Alwil Software\Avast5\snxhk.dll - avast! Antivirus

RIMBBLaunchAgent.exe [1]
=> Nom C:\Program Files\Alwil Software\Avast5\snxhk.dll - avast! Antivirus

DTShellHlp.exe [1]
=> Nom C:\Program Files\Alwil Software\Avast5\snxhk.dll - avast! Antivirus

EgisUpdate.exe [1]
=> Nom C:\Program Files\Alwil Software\Avast5\snxhk.dll - avast! Antivirus

PmmUpdate.exe [1]
=> Nom C:\Program Files\Alwil Software\Avast5\snxhk.dll - avast! Antivirus

mwlDaemon.exe [1]
=> Nom C:\Program Files\Alwil Software\Avast5\snxhk.dll - avast! Antivirus

EEventManager.exe [1]
=> Nom C:\Program Files\Alwil Software\Avast5\snxhk.dll - avast! Antivirus

GoogleToolbarNotifier.exe [1]
=> Nom C:\Program Files\Alwil Software\Avast5\snxhk.dll - avast! Antivirus

9props.exe [1]
=> Nom C:\Program Files\Alwil Software\Avast5\snxhk.dll - avast! Antivirus

msnmsgr.exe [1]
=> Nom C:\Program Files\Alwil Software\Avast5\snxhk.dll - avast! Antivirus

AvastUI.exe [19]
=> Nom C:\Program Files\Alwil Software\Avast5\aswUtil.dll - avast! Antivirus
=> Nom C:\Program Files\Alwil Software\Avast5\ashBase.dll - avast! Antivirus
=> Nom C:\Program Files\Alwil Software\Avast5\aswEngLdr.dll - avast! Antivirus
=> Nom C:\Program Files\Alwil Software\Avast5\aswCmnOS.dll - avast! Antivirus
=> Nom C:\Program Files\Alwil Software\Avast5\aswCmnIS.dll - avast! Antivirus
=> Nom C:\Program Files\Alwil Software\Avast5\aswCmnBS.dll - avast! Antivirus
=> Nom C:\Program Files\Alwil Software\Avast5\ashTask.dll - avast! Antivirus
=> Nom C:\Program Files\Alwil Software\Avast5\aswAux.dll - avast! Antivirus
=> Nom C:\Program Files\Alwil Software\Avast5\aswLog.dll - avast! Antivirus
=> Nom C:\Program Files\Alwil Software\Avast5\aswSqLt.dll - avast! Antivirus
=> Nom C:\Program Files\Alwil Software\Avast5\aswProperty.dll - avast! Antivirus
=> Nom C:\Program Files\Alwil Software\Avast5\AavmRpch.dll - avast! Antivirus
=> Nom C:\Program Files\Alwil Software\Avast5\1036\Base.dll - avast! Antivirus
=> Nom C:\Program Files\Alwil Software\Avast5\aswData.dll - avast! Antivirus
=> Nom C:\Program Files\Alwil Software\Avast5\ashTaskEx.dll - avast! Antivirus
=> Nom C:\Program Files\Alwil Software\Avast5\Aavm4h.dll - avast! Antivirus
=> Nom C:\Program Files\Alwil Software\Avast5\1036\uiLangRes.dll - avast! Antivirus
=> Nom C:\Program Files\Alwil Software\Avast5\CommonRes.dll - avast! Antivirus
=> Nom C:\Program Files\Alwil Software\Avast5\defs\12052600\uiext.dll - avast! Antivirus

chrome.exe [2]
=> Nom C:\Program Files\Alwil Software\Avast5\snxhk.dll - avast! Antivirus
=> Nom C:\Program Files\Alwil Software\Avast5\aswJsFlt.dll - avast! Antivirus

GoogleCrashHandler.exe [1]
=> Nom C:\Program Files\Alwil Software\Avast5\snxhk.dll - avast! Antivirus

GetSystemInfo.exe [1]
=> Nom C:\Program Files\Alwil Software\Avast5\snxhk.dll - avast! Antivirus

rundll32.exe [1]
=> Nom C:\Program Files\Alwil Software\Avast5\snxhk.dll - avast! Antivirus


Service démarrés

=> Nom C:\Program Files\Alwil Software\Avast5\AvastSvc.exe - avast! Antivirus

Registre

 _LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Run [1]
=> Nom C:\Program Files\Alwil Software\Avast5\AvastUI.exe - avast! Antivirus

psg6110 · Answer

Et voila les scan sont fait en esperant trouver une solution, le problème est récurent.