Boujour, mon Pc émet un Bip continue de moins de 2s de tps en tps, d’ou cela peut il venir? Problème de carte graphique? pb de mémoire?
Marque de la carte mère. :jap:
En fonction du BIOS [www.vulgarisation-informatique.com...](http://www.vulgarisation-informatique.com/bips-bios.php)
Carte mère: ASUS Rampage 2 GENE
Mémoire: OCZ XTC platinium PC12800 1600 Mhz
Tu as bien mis les barrettes sur les ports bleu ?
Vi, les 3 barettes sont bien sur les ports bleus, par contre, ce qui m’étonne, c’est qu’il est reconnais qu’en 1067 (DDR 533 Mhz).
Pr info, car je pense que ca pe aussi venir de la: DIMM = 1.51V
Merci pr vos réponses.
Met 1.65V
Donc faut que je trouve comment faire maintenant !!! lol
Salut !
Est ce que ce bip arrive quand tu laisse ton doigt appuyé sur une touche pendant un moment ??
Le bios est ton ami. 
Vi, je c que c ds le BIOS, ms c cho d’y toucher, pas l’habitude de faire ca!
Non, c alléatoire, le BIP arrive je c pas prkoi, surchauffe ou autre, aucune idée et je fais rien de spéciale en ce momment, rien ki demande bcp de ressource ou je ne c koi.
Un effort sur l’orthographe s’il te plait… Tu n’es pas en train de rédiger un texto mais un message lisible par ceux qui vont t’aider bénévolement, donc aies un minimum de respect pour eux et fais un petit effort. Merci :jap:
Edité le 28/03/2010 à 03:05
plaît*… aies un minimum*…
Pour le BIOS c’est pas dur tu appuies sur la touche ‘‘Del’’ (ou ‘‘Suppr’’) au démarrage ensuite tu te balades avec les flèches de ton clavier, les valeurs vont pas changer toutes seules si tu n’y touches pas…!
Pour l’orthographe il a raison, nous ne sommes pas décrypteurs et aimons le bon français donc fais un effort si tu veux nous solliciter.
Munis toi d’un logiciel, disons Hardware Monitor, pour nous montrer tes températures (tu nous fais un screen).
On veut bien t’aider mais il faut que tu y mettes du tien, on ne va pas pouvoir modifier tes voltages à ta place…Bref.
Edité le 28/03/2010 à 03:07
mouais, les accents c’est pas grave, il faut juste eviter de parler en langage SMS à la limite du compréhensible, un minimum d’efforts, c’est tout.
[/HS off]
Edité le 28/03/2010 à 03:07
Je plaisantais t’inquiètes ^^’
Bonsoir, j’ai changé mon BIOS (DRAM frequency: DDR3 1600mhz, DRAM timing control 7/7/7/24 et mis le DIMM à 1.65V), et ça n’a pas l’air d’étre mieux. En fait, au bout d’un certain temps, mon PC devient instable (écran bleu puis reboot)
La, jai remis le BIOS par défaut et voila ce que ça donne:
[Photo supprimée]
On espérent que ça peut vous aider.
Si ça peut encore plus aider quelqu’un, avec le logiciel Whocrashed 2.10, j’obtiens:
Welcome to WhoCrashed Home Edition 2.10
This program checks for drivers which have been crashing your computer.
Whenever a computer suddenly reboots without displaying any notice or blue screen of death, the first thing that is often though about is a hardware failure. In reality, on Windows most crashes are caused by malfunctioning device drivers and kernel modules. In case of a kernel error, most computers do not show a blue screen unless they are configured to do so. Instead these systems suddenly reboot without any notice.
This program does post-mortem crash dump analysis with the single click of a button.
To obtain technical support visit www.resplendence.com/support
To check if a newer version of this program is available, click here.
Just click the Analyze button for a comprehensible report …
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. The professional edition of WhoCrashed also allows analysis of crashdumps on remote drives and computers on the network and offers more detailed analysis.
Analysis
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Sat 03/04/2010 19:02:52 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x1A (0x5003, 0xFFFFF70001080000, 0x32B86, 0x202B63908065702)
Error: MEMORY_MANAGEMENT
Dump file: C:\Windows\Minidump\040310-21044-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.
On Sat 03/04/2010 18:10:36 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x1E (0xFFFFFFFFC000001D, 0xFFFFF80002C86A3D, 0x2, 0xFFFFF80002C18000)
Error: KMODE_EXCEPTION_NOT_HANDLED
Dump file: C:\Windows\Minidump\040310-20217-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.
On Sat 03/04/2010 16:04:56 your computer crashed
This was likely caused by the following module: tcpip.sys
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
Dump file: C:\Windows\Minidump\040310-21949-01.dmp
file path: C:\Windows\system32\drivers\tcpip.sys
product: Système dexploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote TCP/IP
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.
On Sat 03/04/2010 15:25:04 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
Dump file: C:\Windows\Minidump\040310-21091-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.
On Sat 03/04/2010 15:22:45 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x50 (0xFFFFF80003CDBC3B, 0x1, 0xFFFFFA80072F3623, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
Dump file: C:\Windows\Minidump\040310-21387-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.
Conclusion
5 crash dumps have been found and analyzed. Note that it’s not always possible to state with certainty whether a reported driver is really 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.
Désolé pour la longueure du post!