Bonjour,
 
J'ai un problème d'écran bleu avec un asus. En effet au démarrage du pc il recherche à corriger des erreurs après ayant l'écran bleu ci dessous :
 

 
Alors je tiens à préciser que j'ai déjà fait un formatage complet sans CD ET avec CD win 7 pour la partition cachée. Je ne vois pas trop ce que je peux faire maintenant... Pourriez vous m'aider ?
 
Cordialement.
 
PS : précision au démarrage du pc apres cet écran bleu j'ai le systeme de reparation de windows et ca peut redemarrer le PC plusieurs apres pendant 30 mn avant que le PC s'allume. Parfois mais rarement tout fonctionne bien.

salut,
installe Whocrashed ( http://www.resplendence.com/downlo [...] dSetup.exe ), lance-le et clic sur le bouton Analyze en haut à gauche de l'écran. Ensuite copie-colle dans ta prochaine réponse ce qu'il y a sous les rubriques Analyze et Conclusion.
 
+

Bonjour,
 
Je vous remercie pour votre aide. Voici le rapport :
 
System Information (local)
--------------------------------------------------------------------------------
 
computer name: EMILIE-PC
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
CPU: AuthenticAMD AMD Athlon(tm) II Dual-Core M320 AMD586, level: 16
2 logical processors, active mask: 3
RAM: 4294041600 total
VM: 2147352576, free: 1924472832
 
 
 
 
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
 
Crash dump directory: C:\Windows\Minidump
 
Crash dumps are enabled on your computer.
 
On Tue 21/05/2013 10:22:57 GMT your computer crashed
crash dump file: C:\Windows\Minidump\052113-27970-01.dmp
This was probably caused by the following module: hal.dll (hal+0x12A3B)  
Bugcheck code: 0x124 (0x0, 0xFFFFFA8003EE9038, 0xF607A000, 0x136)
Error: WHEA_UNCORRECTABLE_ERROR
file path: C:\Windows\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).  
This is likely to be caused by a hardware problem problem. This problem might be caused by a thermal issue.  
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 Tue 21/05/2013 10:22:57 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: aswmonflt.sys (aswMonFlt+0x1AEA)  
Bugcheck code: 0x124 (0x0, 0xFFFFFA8003EE9038, 0xF607A000, 0x136)
Error: WHEA_UNCORRECTABLE_ERROR
file path: C:\Windows\system32\drivers\aswmonflt.sys
product: avast! Antivirus
company: AVAST Software
description: avast! File System Minifilter for Windows 2003/Vista
Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).  
This is likely to be caused by a hardware problem problem. This problem might be caused by a thermal issue.  
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: aswmonflt.sys (avast! File System Minifilter for Windows 2003/Vista, AVAST Software).  
Google query: AVAST Software WHEA_UNCORRECTABLE_ERROR
 
 
 
On Tue 21/05/2013 10:20:38 GMT your computer crashed
crash dump file: C:\Windows\Minidump\052113-29390-01.dmp
This was probably caused by the following module: hal.dll (hal+0x12A3B)  
Bugcheck code: 0x124 (0x0, 0xFFFFFA80040FA038, 0xF6462000, 0x3000136)
Error: WHEA_UNCORRECTABLE_ERROR
file path: C:\Windows\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).  
This is likely to be caused by a hardware problem problem. This problem might be caused by a thermal issue.  
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 20/05/2013 09:27:11 GMT your computer crashed
crash dump file: C:\Windows\Minidump\052013-33914-01.dmp
This was probably caused by the following module: hal.dll (hal+0x12A3B)  
Bugcheck code: 0x124 (0x0, 0xFFFFFA80040F2038, 0xF64DA000, 0xEE000136)
Error: WHEA_UNCORRECTABLE_ERROR
file path: C:\Windows\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).  
This is likely to be caused by a hardware problem problem. This problem might be caused by a thermal issue.  
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 Sun 19/05/2013 09:36:37 GMT your computer crashed
crash dump file: C:\Windows\Minidump\051913-33633-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C00)  
Bugcheck code: 0x1A (0x41287, 0xA8401080480, 0x0, 0x0)
Error: MEMORY_MANAGEMENT
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.  
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.  
 
 
 
On Sat 18/05/2013 10:18:16 GMT your computer crashed
crash dump file: C:\Windows\Minidump\051813-31434-01.dmp
This was probably caused by the following module: hal.dll (hal+0x12903)  
Bugcheck code: 0x124 (0x0, 0xFFFFFA80040FA038, 0xB6002000, 0x3000136)
Error: WHEA_UNCORRECTABLE_ERROR
file path: C:\Windows\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).  
This is likely to be caused by a hardware problem problem. This problem might be caused by a thermal issue.  
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
--------------------------------------------------------------------------------
 
6 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:  
 
aswmonflt.sys (avast! File System Minifilter for Windows 2003/Vista, 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.
 
 
 
 
 
 
 
PS : J'ai pas tout compris mais je lis du "avast" mais je pense pas que ça soit la cause du problème quand même..surtout j'ai déjà fait des formatages..et de la partition cachée avec les cd de restauration aussi. Et niveau thermique j'ai dépoussiéré en démontant et j'ai un cooling pad.
 
Merci encore.

Salut,
à la lecture du rapport on peut en effet voir que avast peut être une cause de problème. Je te conseille de la désinstaller au moins pour voir si cela fonctionne sans. Tu le réinstallera après...
 
Sinon tu as peut êtrre un problème de mémoire, essaie d'executer le programme memtest ( http://www.memtest86.com/ ).

Re,
 
Alors j'ai lancé un memtest en laissant 20mn pour une pass et il m'a détecté 0 erreur. J'ai désinstallé Avast et je te dirais demain si ça me refait le coup de l'écran bleu et réparation windows car en redemarrant le PC ca me le fait pas et c'est "normal" ça me le fais pas en redémarrant. Mais ce serait bizarre que ce serait à cause d'avast... tu penses que sans avast tout marchera niquel ? J'aimais bien cet antivirus gratuit..Je dois zapper cet antivirus ?  
Encore merci.

Eh ben si c'est à cause d'avast que tu plantes il va falloir effectivement s'en passer au moins jusqu'à la prochaine mise à jour...

En rallumant le PC ce matin il y a eu la même erreur que celle signalée dans le premier post, et j'avais désinstallé avast la veille :s

demarre en mode sans echec , touche F8
si tu peux acceder au systeme , alors le driver qui fait crasher le systeme n'a pas été chargé au demarrage , alors execute msconfig et cherche dans services et démarrage le programme qui fait crasher

Donc si j'arrive à démarrer en mode sans échec c'est good et si  comment je repère ce programme qui fait crasher ? le msconfig je le fais dans "executer" c'est ça ? et quand je suis en mode sans échec ?
 

oui , executer ou dans accessoires , puis msconfig
alors ensuite pour trouver le programme qui fait crasher , chercher un driver suspect ou un antivirus
pour trouver le coupable , coche un par un les programmes , en redemarrant à chaque fois , après chaque programme coché
si tu as un ecran bleu après avoir coché un programme , tu peux ensuite le decocher et activer le reste pour savoir si c'est bien le programme coupable
j'espere que c'est clair

oui c'est clair mais le soucis c'est que ça me le fait que lors du premier démarrage du PC de la journée, genre par exemple si la je le redemarre ben y aura pas de problème.

J'ai toujours ce soucis de recherche d'erreur qui dure au moin 20 mn à l'allumage du PC... merci