Problème de page Bleu recurrent

[eklectik]

Salut salut j'ai installé windows 8.1 et je ne cesse d'avoir des ecrans bleu.

 

J'étais sur 7 et ca faisait pareil mais beaucoup moins souvent je me dis que c'est surement un problème hardware.

 

L'erreur est IRQL not less or equal.

 

Voici le rapport sous WhoCrashed :

 

Crash Dump Analysis

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

 

Crash dump directory: C:\WINDOWS\Minidump

 

Crash dumps are enabled on your computer.

 

On Fri 11/15/2013 11:02:27 AM GMT your computer crashed

crash dump file: C:\WINDOWS\Minidump\111513-13765-01.dmp

This was probably caused by the following module: ntoskrnl.exe (nt+0x14DCA0)

Bugcheck code: 0xA (0x5A790C0, 0x2, 0x0, 0xFFFFF802D1EBA9F9)

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 Fri 11/15/2013 5:26:07 AM GMT your computer crashed

crash dump file: C:\WINDOWS\Minidump\111513-28984-01.dmp

This was probably caused by the following module: ntoskrnl.exe (nt+0x10E686)

Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF8011AD8A686, 0xFFFFD000207B0638, 0xFFFFD000207AFE40)

Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M

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 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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

 

 

 

On Thu 11/14/2013 10:24:11 PM GMT your computer crashed

crash dump file: C:\WINDOWS\Minidump\111513-40312-01.dmp

This was probably caused by the following module: ntoskrnl.exe (nt+0x14DCA0)

Bugcheck code: 0xA (0xFFFFD000214CE7BB, 0x0, 0x1, 0xFFFFF8010D95ED10)

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 Thu 11/14/2013 12:40:42 PM GMT your computer crashed

crash dump file: C:\WINDOWS\Minidump\111413-13968-01.dmp

This was probably caused by the following module: ntoskrnl.exe (nt+0x14DCA0)

Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80325FC7929, 0xFFFFD00026AE6900, 0x0)

Error: SYSTEM_SERVICE_EXCEPTION

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 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 that cannot be identified at this time.

 

 

 

 

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

Conclusion

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

 

4 crash dumps have been found and analyzed. No offending third party drivers have been found. Consider using WhoCrashed Professional which offers more detailed analysis using symbol resolution. Also configuring your system to produce a full memory dump may help you.

 

 

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.

[Snake1628567281]

télécharge: Télécharger WhoCrashed Free Home Edition - 01net.com - Telecharger.com

 

Au prochain écran bleu, il te donnera des infos plus compréhensibles.

[eklectik]

Voila

 

 

Home Edition Notice

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

 

This version of WhoCrashed is free for use at home only. If you would like to use this software at work or in a commercial environment you should get the professional edition of WhoCrashed which allows you to perform more thorough and detailed analysis. It also offers a range of additional features such as remote analysis on remote directories and remote computers on the network.

 

Click here for more information on the professional edition.

Click here to buy the the professional edition of WhoCrashed.

 

 

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

System Information (local)

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

 

computer name: ARRETEAVECCA-PC

windows version: Windows 7 Service Pack 1, 6.1, build: 7601

windows dir: C:\Windows

Hardware: GL322AA-ABF m8190.fr, HP-Pavilion, ASUSTeK Computer INC., Berkeley

CPU: GenuineIntel Intel® Core2 Quad CPU @ 2.40GHz Intel586, level: 6

4 logical processors, active mask: 15

RAM: 6441717760 total

VM: 2147352576, free: 1954156544

 

 

 

 

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

Crash Dump Analysis

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

 

Crash dump directory: C:\Windows\Minidump

 

Crash dumps are enabled on your computer.

 

On Sun 17/11/2013 19:07:11 GMT your computer crashed

crash dump file: C:\Windows\Minidump\111713-23852-01.dmp

This was probably caused by the following module: ntfs.sys (Ntfs+0x1F15)

Bugcheck code: 0x24 (0xC08A5, 0x0, 0x0, 0x0)

Error: NTFS_FILE_SYSTEM

file path: C:\Windows\system32\drivers\ntfs.sys

product: Microsoft® Windows® Operating System

company: Microsoft Corporation

description: NT File System Driver

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.

 

 

 

 

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

Conclusion

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

 

One crash dump has been found and analyzed. No offending third party drivers have been found. Consider using WhoCrashed Professional which offers more detailed analysis using symbol resolution. Also configuring your system to produce a full memory dump may help you.

 

 

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.

[Snake1628567281]

Donc pas de blême de drivers apparemment...

 

Teste avec memtest l'état des tes RAM.

 

Met à jour le firmware de ton SSD.

 

Sinon re scanne tous tes disques dur et clé usb avec ton AV, et malwarebytes. L'AV comme malwarebytes réglé en mode scan minutieux.

[eklectik]

d'accord je fait ca je te remercie Snake je te tiens au courant

[eklectik]

Salut je penses avoir trouver le souci j'ai ma cg hd 6870 qui me sort le son par défaut aussi alors que j'ai le driver de ma carte son realtek hd installé prêt mais j'ai mis par defaut celle de la cg.

 

Quoique je fasses si je met par défaut la realtek aucun son ne sort. Et j'ai bien l'impression que ca vient de la. J'ai lancé le gestionnaire realtek et quand j'ai cliqué sur un bouton pour mettre par defaut le meme son strident est sorti que quand mon ordinateur plante. SI ca peut aider. Comment je fait pour que ma cg gère pas le son c'est pas logique quelques part....

[Snake1628567281]

J'ai jamais eu à faire qq chose pour que le son sorte sur l'analogique. J'ai jamais utilisé la CG pour le son d’ailleurs.

 

Teste le PC sans carte graphique pour voir. Perso c'est ce je ferais.

Si la carte mère n'a pas de sortie vidéo, essayer de gratter une CG toute pourrie pour tester.

 

C'est à se demander si la carte son de la CM n'est pas le problème. Bref je dis ça je dis rien. Là on peut qu'essayer tout et n'importe quoi pour essayer de trouver le problème.

 

Je viens de penser à un truc. Télécharge et grave un live cd de linux (ubuntu par exemple). Lance le, et regarde si le son fonctionne. Pour moi, si le son fonctionne avec linux, c'est que c'est bien un problème de drivers. Si sur linux ça ne fonctionne pas, je dirais que qq chose est en panne.

 

 

Et pourquoi pas regarder dans le bios si la puce audio est bien activée.

[eklectik]

Disons que quand je reinsatlle le pc il me demande de dl le driver de la cg et de ma carte son mais jarrive vraimetn pas a mettre le son par defaut sur celel de la carte mere .

 

Aucun son ne sort et je pense vraimetn que le irql was not sent etc ca vient de la