bonjour
j'ai un pc portable asustek sous windows 7 familial, et soudainement il ma fais le fameux écran bleu de ce type http://www.presse-citron.net/wordpress_prod/wp-content/uploads/Windows_XP_BSOD.png
comment faire pour réparer ce soucis .. J'ai essayer de mettre le CD d'installation de Windows 7 mais ne se lance pas.. J'arrive meme pas a démarrer en mode sans échec. Même accéder au bureau j'arrive pas l'écran bleu me hante ! J'ai éssayer la restauration de systeme antérieur, les sauvegardes, mais sa bug quand même donc la je suis perdue !

Cordialement

Bon alors dl ce petit log il analyse les écrans bleus :

http://www.resplendence.com/download/whocrashedSetup.exe

Une fois lancé tu cliques sur analyses en haut , une fois fini tu vas recevoir le message suivant :

Please scroll down .....

Et tu vas me copier/coller tout ce qui est indiqué en dessous de Crash Dump Analysis ds le logiciel en allant voir vers le bas

Merci mais je fais comment pour le lancé ? L'ordi il a pas assez d'endurance pour atteindre le bureau !

Merde j'avais pas tout lu

tu peux prendre en photo l'écran bleu ?

Ou nous dire au moins l'erreur stop :

Et le gros message qui est marqué en haut en majuscule style ici :

PAGE_FAULT etc...

STOP:...... ect.... ecrit tout

ce qui est marqué en dessous

http://imageshack.com/a/img841/836/0djd.jpg

ça ira plus vite

T'as pas changé de matos récemment ou installer de nouveau pilotes/log ?

Pr démarrer sous le cd de 7 faut que t'aille ds le bios pr lui indiquer de booter sur le lecteur cd

Je sais pas surement ...Et j'ai fais mais sa marche quand même pas

T'es sur que t'as bien régler ton bios au niveau du boot device ?

Possible une photo ?

Je vais manger

Je reviens plus tard

Bonne ap'!

J'ai fais mais ça marche pas .. Le CD c'est pas celui du PC ..

Et c'est pas un CD Original .......... :oops:

re

c'est quoi le modele exact de ton asustek ça doit être marqué à l'arrière de ta machine, confond pas avec la cle windows

Salut ,;)

C'est un notebook aspire one D257

System Information (local)
--------------------------------------------------
------------------------------

computer name: ASUS-PC
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
Hardware: F5SL , ASUSTeK Computer Inc. , PEGATRON CORPORATION , F5SL
CPU: GenuineIntel Intel(R) Pentium(R) Dual CPU T3200 @ 2.00GHz Intel586, level: 6
2 logical processors, active mask: 3
RAM: 3220463616 total
VM: 2147352576, free: 1927708672

--------------------------------------------------
------------------------------

Crash Dump Analysis
--------------------------------------------------
------------------------------

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Sun 18/05/2014 15:03:49 GMT your computer crashed
crash dump file: C:\Windows\Minidump\052014-28516-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0xA (0x18000002C, 0x2, 0x0, 0xFFFFF8000208653D)
Error: IRQL_NOT_LESS_OR_EQUAL
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 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.
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 18/05/2014 15:01:03 GMT your computer crashed
crash dump file: C:\Windows\Minidump\051814-26535-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0xC4 (0x91, 0x0, 0xFFFFFA8003FE1B50, 0x0)
Error: DRIVER_VERIFIER_DETECTED_VIOLATION
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This is the general bug check code for fatal errors found by Driver Verifier.
The driver switched stacks using a method that is not supported by the operating system. The only supported way to extend a kernel mode stack is by using KeExpandKernelStackAndCallout. 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 18/05/2014 14:58:19 GMT your computer crashed
crash dump file: C:\Windows\Minidump\051814-24523-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x4211)
Bugcheck code: 0x24 (0x1904FB, 0xFFFFF880023CBAC8, 0xFFFFF880023CB320, 0xFFFFF880012F56C7)
Error: NTFS_FILE_SYSTEM
file path: C:\Windows\system32\drivers\ntfs.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote du système de fichiers NT
Bug check description: This indicates a problem occurred in the NTFS file system.
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 18/05/2014 13:49:40 GMT your computer crashed
crash dump file: C:\Windows\Minidump\051814-24258-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF800020F3451, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: KMODE_EXCEPTION_NOT_HANDLED
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 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 Wed 14/05/2014 19:13:43 GMT your computer crashed
crash dump file: C:\Windows\Minidump\051414-27939-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0xD1 (0xFFFFF8000000B5F2, 0x2, 0x8, 0xFFFFF8000000B5F2)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
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 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 that cannot be identified at this time.

On Thu 17/04/2014 10:32:34 GMT your computer crashed
crash dump file: C:\Windows\Minidump\041714-28719-01.dmp
This was probably caused by the following module: rdyboost.sys (rdyboost+0x784D)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF8800186C84D, 0xFFFFF880033E7908, 0xFFFFF880033E7160)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\rdyboost.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: ReadyBoost 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.
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 11/03/2014 12:23:15 GMT your computer crashed
crash dump file: C:\Windows\Minidump\031114-24086-01.dmp
This was probably caused by the following module: wnmflt64.sys (0xFFFFF88005446960)
Bugcheck code: 0xD1 (0xD0, 0x2, 0x0, 0xFFFFF88005446960)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\wnmflt64.sys
product: Panda Network Manager
company: Panda Security, S.L.
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: wnmflt64.sys (Panda Security, S.L.).
Google query: Panda Security, S.L. DRIVER_IRQL_NOT_LESS_OR_EQUAL

On Fri 07/03/2014 20:10:33 GMT your computer crashed
crash dump file: C:\Windows\Minidump\030714-25022-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x78A8A)
Bugcheck code: 0x1000009F (0x4, 0x258, 0xFFFFFA80024CC040, 0xFFFFF80000B9C510)
Error: CUSTOM_ERROR
file path: C:\Windows\system32\ntoskrnl.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 that cannot be identified at this time.

On Tue 18/02/2014 12:53:51 GMT your computer crashed
crash dump file: C:\Windows\Minidump\021814-39062-01.dmp
This was probably caused by the following module: clgzifga.sys (Unloaded_clgzifga.SYS+0x5D000)
Bugcheck code: 0xD4 (0xFFFFF88006ACE000, 0x2, 0x1, 0xFFFFF80002C6CD4E)
Error: SYSTEM_SCAN_AT_RAISED_IRQL_CAUGHT_IMPROPER_DRIVER_
UNLOAD

Bug check description: This indicates that a driver did not cancel pending operations before unloading.
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: clgzifga.sys .
Google query: clgzifga.sys SYSTEM_SCAN_AT_RAISED_IRQL_CAUGHT_IMPROPER_DRIVER_
UNLOAD

On Fri 08/11/2013 12:43:38 GMT your computer crashed
crash dump file: C:\Windows\Minidump\110813-24055-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x7F (0x8, 0x80050031, 0x6F8, 0xFFFFF80002C79B8A)
Error: UNEXPECTED_KERNEL_MODE_TRAP
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that the Intel CPU generated a trap and the kernel failed to catch this trap.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

--------------------------------------------------
------------------------------

Conclusion
--------------------------------------------------
------------------------------

15 crash dumps have been found and analyzed. Only 10 are included in this report. 2 third party drivers have 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:

clgzifga.sys
wnmflt64.sys (Panda Security, S.L.)

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.

minidump c est la ou la memoire ram se vide

http://www.onlinespywareexpert.com/exe-errors/wnmflt64.sys.html

jai tenter une restauration de systeme. Lecran nest pas devenu bleu je prie pour que sa continue !!!

et au passage je fais fonctioner ton fichier comment ?