jeffyz

Bonjour!

J'étais en réseau (domestique) avec le pc à mon frere et mon ps3(réseau avec fil). Mais la, mon pc ne détecte plus le réseau et il est maintenant en réseau(public). Je ne sait pas pourquoi il y a eu des changements et je ne sait pas plus comment revenir à un réseau domestique. Lorsque j'ouvre Centre Réseau et partage et que je click sur Connexion à un réseau Windows me dis qu'il ny a aucune connexion disponible.

OS : windows 7

Merci !

Bonjour à tous

J'ai acheté une carte-mere (ASUS P5G41T-M/CSM LGA775 mATX G41 DDR3) et de la Ram (Corsair CMV4GX3M2A1333C9 4GB DDR3 2X2GB DDR3-1333 CL9 Dual Channel) pour reconstruire mon ancien pc.

Dans les specs de la carte-mere c'est écrit : This motherboard supports DDR3 memory that features data transfer rates of 1333 (O.C.)/1066/800 MHz

Donc je dois O.C. le bios pour que ma CM détecte les 1333Mhz de ma Ram ?

Si oui, quelle est le moyen le plus simple pour y arriver ?

Merci de votre aide !

Bonjour à tous !

Depuis 2 mois jai un nouveau pc que j'ai assemblé moi-meme. Depuis le début jai des petits problemes : des pages bleu, lorsque que je démarre l'ordinateur windows analyse mes disques durs, l'ordinateur freeze sans raison, et j'ai limpression que parfois mes dd ne fond rien ou son lent. On dirait qu'il y a un décalage entre le moment ou je clique et le moment que mes DD se mettent en marche.

Specs du pc : Tous les pieces sont neuves auf ma carte graphique

Carte mère: ASUS P6X58D-E
Disque dur: Western Digital Caviar Black 640GB SATA3 6GB/S 7200RPM 64MB en RAID 0
Ram: Kingston HyperX 6GB
CG:GTX 280
CPU:Intel Core i7 950
OS: windows 7 64 bits

J'ai installé WHOCRASHED et voici ce quil dit :

Code: Tout sélectionner

Crash dumps are enabled on your computer.


On Wed 2011-01-05 02:33:46 GMT your computer crashed
crash dump file: C:\Windows\Minidump\010411-62587-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70710)
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
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 which cannot be identified at this time.


On Wed 2011-01-05 02:33:46 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: rdyboost.sys (rdyboost+0x15109)
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
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 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 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 Wed 2011-01-05 01:55:03 GMT your computer crashed
crash dump file: C:\Windows\Minidump\010411-112367-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70740)
Bugcheck code: 0xF4 (0x3, 0xFFFFFA8009743730, 0xFFFFFA8009743A10, 0xFFFFF80002F7B5D0)
Error: CRITICAL_OBJECT_TERMINATION
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 process or thread crucial to system operation has unexpectedly exited or been terminated. 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 2010-12-27 02:02:48 GMT your computer crashed
crash dump file: C:\Windows\Minidump\122610-54631-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70740)
Bugcheck code: 0xA (0x526F0, 0x2, 0x0, 0xFFFFF80002D97FD4)
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 which cannot be identified at this time.


On Sun 2010-12-26 20:33:56 GMT your computer crashed
crash dump file: C:\Windows\Minidump\122610-40591-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70740)
Bugcheck code: 0x4E (0x99, 0x8CA30, 0x2, 0x8BF30)
Error: PFN_LIST_CORRUPT
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 page frame number (PFN) list is corrupted.
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 the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Sun 2010-12-26 19:21:56 GMT your computer crashed
crash dump file: C:\Windows\Minidump\122610-56706-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70740)
Bugcheck code: 0xF4 (0x3, 0xFFFFFA8009747AD0, 0xFFFFFA8009747DB0, 0xFFFFF80002F865D0)
Error: CRITICAL_OBJECT_TERMINATION
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 process or thread crucial to system operation has unexpectedly exited or been terminated. 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 2010-12-25 18:35:10 GMT your computer crashed
crash dump file: C:\Windows\Minidump\122510-30919-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70740)
Bugcheck code: 0xA (0x1767AD, 0x2, 0x0, 0xFFFFF80002DA4FD4)
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 which cannot be identified at this time.


On Wed 2010-12-22 22:25:33 GMT your computer crashed
crash dump file: C:\Windows\Minidump\122210-20498-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70710)
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
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 which cannot be identified at this time.

J'ai installer tous les drivers, mais je n'ai pas formater mon pc depuis que je l'ai. serais-ce une solution ?
Merci de m'aider !!
Jeff

Bonjour à tous!

je voulais savoir si j'installe une carte graphique overclocker du fabricant, est-ce que je vais devoir aller jouer dans le bios ou je l'installe normalement?

carte graphique : MSI GeForce GTX 460 Fermi Hawk OC 780MHZ 1GB GDDR5 Dual DVI Mini-HDMI DX11 PCI-E

Merci de vos réponses !

Salut!

Depuis 3 jours j'ai uploader(pas téléchager) plus de 13 gig sans savoir pourquoi. J'ai un réseau local avec routeur (avec fil) je partage avec 1 ordinateur et mon PS3. J'ai changé mon pc il y a 3 jour serait-ce le probleme ?? Je ne partage rien sauf windows media pour la musique et les film.

Je n'ai rien dowloader sauf les mises à jour et quelques programmes essentiels.
Par contre mon frere c'est mis à jouer à un nouveau jeu ... League of legend. est-ce que ca pourrait etre la cause de 5 gig d'upload par jour ?

aider moi svp !

Merci

salut !

est-ce qu'une carte mere(asus p6x58d-e) qui supporte de la ddr5 (carte video) peut supporter une carte video ddr2 ?