Écran bleu, whoCrashed

[Louzo_1_1]

Le PCxxxx exprime la fréquence à laquelle tourne la mémoire.

Pour les AMD et les Core 2 de chez Intel, la fréquence du processeur et celui de la ram sont liés par un coef., donc si tu veux overclocker ton processeur (augmenter sa fréquence) tu as intérêt à avoir une ram avec une fréquence la plus élevée possible (dans certaines limites bien entendu). Mes explications sont raccourcies, mais c’est à peu près ça.

Si tu n’est pas un adapte de l’OC, aucun intérêt d’aller chercher une mémoire ultra-rapide, la PC6400 est parfaite (elle permet aussi l’OC ceci dit).

[razorback27]

Merci pour toute c’est information :super:

Je vien de passer commande de cella materiel.net

Hâte d’essayer pour voir si mon ordinateur deviens plus stable.

Merci a tous

[Tijo35]

Tiens nous au courant, en espérant que ça résolvera ton problème (j’en suis quasiment certain )

[ray4c]

Bonjour,
Je suis un peu désemparé, depuis peu j’ai un redémarrage alléatoire juste aprés avoir allumé mon PC, le temps d’ouvrir la première appli. Ecran bleu etc…Je ne me souviens pas avoir installé quoique ce soit récemment. Je ne peux pas faire de restore (oui je sais c’est ma faute, je me suis déjà auto flagellé!) J’ai contrôlé mes drivers, mises à jours, testé la mémoire vive avec memtest et a priori tout est ok, nettoyé et tout et tout mais rien n’y fait.
Avec Whocrashed j’ai ces rapports d’erreurs , pouvez-vous s’il vous plait m’aider à interpréter tout ça ?

On Sat 11/02/2012 12:38:39 GMT your computer crashed
crash dump file: C:\Windows\Minidump\021112-21387-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80002CD8B65, 0xFFFFF88006EFF060, 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 which cannot be identified at this time.

On Sat 11/02/2012 12:38:39 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: win32k.sys (win32k!EngSetLastError+0x1009D)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80002CD8B65, 0xFFFFF88006EFF060, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\win32k.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote Win32 multi-utilisateurs
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 a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.

On Tue 07/02/2012 12:38:03 GMT your computer crashed
crash dump file: C:\Windows\Minidump\020712-17472-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3453C7)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF80002FAC3C7, 0xFFFFF880031CB9B8, 0xFFFFF880031CB210)
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 which cannot be identified at this time.

On Tue 07/02/2012 06:06:42 GMT your computer crashed
crash dump file: C:\Windows\Minidump\020712-20342-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80002F8AE78, 0xFFFFF880073A6CE0, 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 which cannot be identified at this time.

On Mon 06/02/2012 18:21:27 GMT your computer crashed
crash dump file: C:\Windows\Minidump\020612-19484-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0xC2 (0x7, 0x109B, 0x102, 0xFFFFF8A004E52E60)
Error: BAD_POOL_CALLER
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 the current thread is making a bad pool request.
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 06/02/2012 06:04:50 GMT your computer crashed
crash dump file: C:\Windows\Minidump\020612-21091-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0x1A (0x41287, 0x10, 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 which cannot be identified at this time.

[Blackalf]

Le processus qui semble planter le plus souvent est “ntoskrnl.exe”,tu aurais donc bien un souci de démarrage de Windows

www.commentcamarche.net…

Infection de Windows ou pas je ne sais pas (à tout hasard et si c’est possible,vérifies s’il apparaît dans le gestionnaire de tâches)…mais perso et en l’absence de points de restauration je formaterais :neutre:
Edité le 12/02/2012 à 18:26

[Akma]

Salut,

J’ai le même soucis que toi et je pense savoir d’ou ça viens, en effet j’ai les même carte graphique que toi 4850 X2, et cela dois venir des pilote ressent essaye d’installer un ancien pilote ou même désinstalle les redémarre cela remettra ceux de Windows 7 de base depuis que j’ai fais ça et j’ai déjà MOINS de problème.

"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.
"

Dans cette partie il est bien indiqué que cela viens d’un pilote, et je me suis renseigner et je suis souvant tombé sur un problème de pilote des ces fameuse carte graphique en crossfire (il y en a 2).

==

2 solutions trouver les bon pilotes qui ne plante pas, en regardant les anciens ou ceux de base de windows ou change de carte graphique c’est ce que je compte faire j’en peux plus de jouer sur un pc instable.

Les pilotes rescent de la 4850 sont instable apparemment !

J’espère t’avoir aidé toi et d’autre !