NeckTeck
Messages postés3Date d'inscriptionlundi 29 octobre 2012StatutMembreDernière intervention 2 novembre 2012
-
29 oct. 2012 à 07:00
NeckTeck
Messages postés3Date d'inscriptionlundi 29 octobre 2012StatutMembreDernière intervention 2 novembre 2012
-
2 nov. 2012 à 08:16
Bonjour,
-
-
-
-
Alors je vien vous demander de l'aide après plein de recherche sur internet, mise a jour de tout pilotes, netoyages avec "Ccleaner", mise a jour du Bios et tout via le logiciel de MSI "Live Update 5", mais j'ai toujour plein de crash du pc écran bleu avec plein de texte et code écrit en blanc donc je ne comprend pas un mot.
-
Voici ma config (Achetté et monté par matériel.net en chosisant chaque composant à la carte 'individuellement' mais j'ai installé windows seul et je n'ai pas fait de CD de restauration.) :
-
Zalman Z11 PLUS - DESTOCKAGE
Antec HCG - 520W
Seagate Barracuda SATA III 6 Gb/s - 2 To
Asus DRW-24B5ST - noir - OEM
Intel Core i5 3570K
MSI Z77A-G45
G.Skill Kit Extreme3 2 x 4 Go PC12800 ARES CAS9
MSI GeForce GTX 660 Twin Frozr 3 - OC - 2 Go
Materiel.net Montage
Materiel.net Extension de garantie à 3 ans atelier - B
Altec-Lansing BXR 1320
Microsoft Windows 7 Familial Premium 64 bits SP1 (oem)
-
et j'ai ensuite achetter le pack Clavier Black Widow Ultimate + Impérator 2012
branché mon ancien casque "sharkoon digital x tactic 5.1" qui va sur ps3/xbox360/pc
et tout sa sur mon écrant 16/10 synmaster T... 24 pouce
-
j'ai télécharger BlueScreenView et whocrashed donc voici les rapport des 9 crash via whocrashed (mais jen ai eu bien plus), je précise que j'ai le pc depuis moin d'un mois :
-
System Information (local)
--------------------------------------------------------------------------------
-
computer name: NECKTECK-PC
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
CPU: GenuineIntel Intel(R) Core(TM) i5-3570K CPU @ 3.40GHz Intel586, level: 6
4 logical processors, active mask: 15
RAM: 8531255296 total
VM: 2147352576, free: 1913921536
-
-
-
-
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
-
Crash dump directory: C:\Windows\Minidump
-
Crash dumps are enabled on your computer.
-
On Mon 29/10/2012 04:12:14 GMT your computer crashed
crash dump file: C:\Windows\Minidump\102912-15865-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x48D8)
Bugcheck code: 0x24 (0x1904FB, 0xFFFFF88007DCB748, 0xFFFFF88007DCAFA0, 0xFFFFF88001231285)
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 Mon 29/10/2012 04:12:14 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x48D8)
Bugcheck code: 0x24 (0x1904FB, 0xFFFFF88007DCB748, 0xFFFFF88007DCAFA0, 0xFFFFF88001231285)
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 Mon 29/10/2012 00:38:21 GMT your computer crashed
crash dump file: C:\Windows\Minidump\102912-14539-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80003158EC9, 0xFFFFF88002ACE8F0, 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.
-
-
-
On Sun 28/10/2012 23:32:21 GMT your computer crashed
crash dump file: C:\Windows\Minidump\102912-13899-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x48D8)
Bugcheck code: 0x24 (0x1904FB, 0xFFFFF8800377FA68, 0xFFFFF8800377F2C0, 0xFFFFF8800121AE3A)
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 Fri 26/10/2012 20:47:25 GMT your computer crashed
crash dump file: C:\Windows\Minidump\102612-14695-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0xC6051)
Bugcheck code: 0x19 (0x3, 0xFFFFF900C1F339F0, 0xFFFFF900C1B339F0, 0xFFFFF900C1F339F0)
Error: BAD_POOL_HEADER
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 a pool header is corrupt.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. 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 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 Fri 26/10/2012 19:59:57 GMT your computer crashed
crash dump file: C:\Windows\Minidump\102612-15178-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF800031AC93E, 0xFFFFF8800A80ABA0, 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.
-
-
-
On Fri 26/10/2012 18:56:12 GMT your computer crashed
crash dump file: C:\Windows\Minidump\102612-15022-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80003158EC9, 0xFFFFF88008A878F0, 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.
-
-
-
On Fri 26/10/2012 06:32:03 GMT your computer crashed
crash dump file: C:\Windows\Minidump\102612-15366-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8000319893E, 0xFFFFF88009DDA5E0, 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.
-
-
-
On Fri 26/10/2012 06:19:51 GMT your computer crashed
crash dump file: C:\Windows\Minidump\102612-13790-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0)
Bugcheck code: 0x1A (0x403, 0xFFFFF68000079000, 0xDD7000019165F867, 0xFFFFF68000206D52)
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.
-
-
-
-
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
-
9 crash dumps have been found and analyzed. No offending third party drivers have been found. Consider configuring your system to produce a full memory dump for better analysis.
-
-
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.
-
*******************************************************
-
Lors des rapport Blue screen view en rouge apparait dans la liste Ntfs.sys et un truck windows je sais plus exactement ce qu'il y avait d'écrit...
-
Voici auci quelques bugs j'ai :
-
lorsque ma session s'ouvre appres que j'ai tapper le pass :
-
messages d'erreurs dans des fenetres blanches (pas tous en même temp, et vraiment de façon aléatoires et spontanés) :
-
(celui ci lorsque avast ne veut pas se lancer, vue 3-4 fois)
********************************************************#
-AvastUI.exe - Erreur d'application
L'intruction à 0x01140727 emploie l'adresse mémoire 0xfffffff. La mémoire ne peut pas être en état 'read'.
-
Cliquez sur OK pour terminer le programme.
********************************************************
-
(celui ci lorsque skype ne veut pas se lancer, vue deux fois.)
********************************************************#
-Skype
access violation at address 774903F4 in module 'ntdll.dll'. Read of address 00100008.
********************************************************
-
(celui ci au démmarage de windows, sa me la fait q'une fois.)
********************************************************#
Windows à rencontré un problème critique et redémarrera dans une minute .Enregistrez votre travail maintenant.
********************************************************
-
(celui ci quasiment à chaque démmarage mais internet fonctionne quand même après.)
********************************************************#
Wifi Station for Livebox Utility a cessé de fonctioner.
********************************************************
-
Défois absolument aucune application ne veulent s'ouvrir hors internet via Mozila Firefox, aucun message d'erreur pourtant, quand je clique sur league of legend par exemple sa me fait le petit symbole qui tourne comme quoi sa lance le jeu ou charge un programme et puis sa revien au curseur de souris normale et puis rien ne se passe, y compris en lancement administrateur et compatibilité, je doit simplement redémarer mon pc et sa remarche.
-
J'ai un bug splat à chaque lancement de partie pendant le chargement quasiment et je doit quitté le jeux dans la barre des tache et relancé le jeu...
-
Voici quelque chose que j'ai trouvé étrange sur les correction d'erreur registre de CC cleaner qui me demande de sauvegardé les cles registres, je les ai toute sauvegardé quand sa voulais les effacé, voici deux screens :
-
https://www.casimages.com/i/12102906361645582.jpg.html -
https://www.casimages.com/i/121029064236643360.jpg.html -
-
Alors pour l'instant vue que le pc est flambant neuf je pense que sa pourais venir soit de la RAM qui serait défectieuse, windows mal installé, conflit avast avec anti virus/par feu windows ( à savoir Advanced SystèmeCare est aussi instalé mais ce n'est pas un anti virus je croit et de toute façon les problème étais la depuis l'achat du pc, apres que j'ai instalé windows et steam quand j'ai comencé à jouer les crash on comencé aussi d'ailleurs quand sa fait un écran bleu un deuxieme arrive aussi au redémarage assez souvent mais pas tout le temp.
-
J'oubliais skype se ferme tout seul d'un coup parfois et quand sa le fait sa le fait souvent encore 2-3 fois ensuite espacé de 5-20 minutes.
-
J'ai aussi des bug Adobe Air quand je lance league of legend parfois apres avoir taper mon pass et cliqué sur conexion:
***********************************************************#
Adobe Air Debug Laucher
Adobe Air Debug Lancher a cessé de fontionner
-
Un problème a fait que le programme a cessé de fonctionner correctement. Windows va fermer ce programme et vous indiquer si une solution est disponible.
Fermer le programme ( et quand je clique sur fermer le programme sa me quitte league of legend. )
**********************************************************
-
Voilà j'espère que toute ces information vous aideront pour m'aider :)
Merci d'avance.
A voir également:
Crash bleu aléatoire nouveau pc. scan whocrashed,etc...