Il y a actuellement 43 visiteurs
Mardi 11 Décembre 2018
accueilactualitésdossierscomparer les prixtélécharger gratuitement vos logicielsoffres d'emploiforum informatique
Connexion
Créer un compte

lolom7

Ce membre n'a pas encore choisi d'avatar
Visiteur Confirmé
Visiteur Confirmé
Nom d'utilisateur:
lolom7
Groupes:

Contacter lolom7

Statistiques de l’utilisateur

Inscription:
30 Sep 2012 14:03
Dernière visite:
10 Mar 2013 23:50
Messages:
13 (0.00% de tous les messages / 0.01 messages par jour)
Forum le plus actif:
Forum Composants & Ordinateurs assemblés
(12 Messages / 92.31% des messages de l'utilisateur)
Sujet le plus actif:
Ecran Bleu -> branchement cable réseau
(12 Messages / 92.31% des messages de l'utilisateur)

Les derniers messages de lolom7

Message Ecran Bleu -> branchement cable réseau
Bonsoir,

Tout d'abord, cela a commencé par un crash de mon PC : écran Bleu

J'ai fait venir un informaticien, diagnostique : DD MORT. Il a récupéré le maximum de mes données et m'a conseillé d'acheter un autre DD. (pour ça, il m'a pris 100 €).

J'achète un nouveau DD, j'ai pris un Seagate Barracuda 1To 64Mo 3.5". J'ai réinstallé Windows 7 grâce à mes CD de restauration.

Tout fonctionne correcte jusqu'au moment ou je branche le cable réseau. => écran bleu... :evil:
Je fais plusieurs essai, démarrage avec, sans, bref le problème vient du moment ou le cable est branché.

J'ai trouvé quelques articles qui parlaient de la mise à jour de driver.
- carte réseau : Realtek PCIe GBE Family Controller : 2010-12-15 , Version:7.26.902.2010

J'ai télécharger (via un autre PC) la mise a jour puis installé sur mon PC : maintenant je suis en 2012-10-25 , Version:7.65.1025.2012. redémarrage du PC ... et toujours le même problème ... :evil:

Afin que vous puissiez me donner un coup de main pour résoudre mon problème j'ai télécharger WhoCrashed (vu sur un autre poste similaire).

Voici le rapport :

Code: Tout sélectionner
[i][color=#4040BF]System Information (local)
--------------------------------------------------------------------------------

computer name:
windows version: Windows 7 , 6.1, build: 7600
windows dir: C:\Windows
CPU: GenuineIntel Intel(R) Core(TM) i3 CPU 550 @ 3.20GHz Intel586, level: 6
4 logical processors, active mask: 15
RAM: 4151394304 total
VM: 2147352576, free: 1958531072




--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Sat 19/01/2013 17:38:16 GMT your computer crashed
crash dump file: C:\Windows\Minidump\011913-17004-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70040)
Bugcheck code: 0xA (0x10, 0x2, 0x1, 0xFFFFF80002C83BF5)
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 Sat 19/01/2013 17:37:17 GMT your computer crashed
crash dump file: C:\Windows\Minidump\011913-16894-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70040)
Bugcheck code: 0xA (0x10, 0x2, 0x1, 0xFFFFF80002CC7BF5)
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 18/01/2013 21:43:06 GMT your computer crashed
crash dump file: C:\Windows\Minidump\011813-18470-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70040)
Bugcheck code: 0xA (0x10, 0x2, 0x1, 0xFFFFF80002CD3BF5)
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 18/01/2013 21:41:14 GMT your computer crashed
crash dump file: C:\Windows\Minidump\011813-18205-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70040)
Bugcheck code: 0xA (0x10, 0x2, 0x1, 0xFFFFF80002C8EBF5)
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 Mon 17/12/2012 13:11:03 GMT your computer crashed
crash dump file: C:\Windows\Minidump\011813-29172-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70740)
Bugcheck code: 0xA (0x10, 0x2, 0x1, 0xFFFFF80002C82365)
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 Mon 17/12/2012 09:00:26 GMT your computer crashed
crash dump file: C:\Windows\Minidump\121712-17035-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70740)
Bugcheck code: 0xA (0x10, 0x2, 0x1, 0xFFFFF80002C96365)
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 Mon 17/12/2012 08:56:57 GMT your computer crashed
crash dump file: C:\Windows\Minidump\121712-23899-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70740)
Bugcheck code: 0xA (0x10, 0x2, 0x1, 0xFFFFF80002A95365)
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.




--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------

7 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. [/color][/i]


Je n'arrive pas a décrypter mon problème avec ces infos.

Est ce que quelqu'un peu m'aider. :D

Merci beaucoup

Message Choisir une webcam
Bonjour a tous,

Je suis à la recherche d'un système qui me permettrai de "skyper" depuis mon canapé.

Alors j'ai un pc fixe HP. Je l'ai branché à ma TV (samsung détail) du salon grâce à un câble HDMI de 15m (oui oui ca marche nikel).

Suite a l'arrivé du bébé et à de la famille à l'étranger, il serai agréable de pouvoir skyper depuis le canapé.

Je cherche donc une webcam que je pourrai poser sur la TV.

J'ai fait beaucoup de recherche mais j'ai trouvé que peux de solution.
Si j'ai bien compris un webcam IP sans fil n'ai pas compatible avec skype.

donc il reste les webcams USB:

Sans fil, j'ai trouvé uniquement celle ci :
WEBCAM PEARL elle est sans fil avec récepteur USB. cependant la qualité me semble médiocre et le sigle est optimal à 2 m (il m'en faudrait au mois 4)

Autrement il me faudrait une Webcam USB avec une rallonge USB de 15m. Je me demande si avec une telle longueur, l'alimentation électrique de la cam sera suffisante. (exemple)
et un webcam de ce type ici

[edit] Ou je viens d'avoir une autre idée : est il possible de bancher la cam sur un petit émetteur USB et brancher le récepteur USB sur le PC - je sais pas si cela existe


Voila en faite j'ai un budget dans les 80 €.

Pouvez vous me donner quelques conseil et me donner les avantages et inconvénient des différentes solutions possible.

Je vous remercie d'avance pour votre aide.

A bientot



.: Nous contacter :: Flux RSS :: Données personnelles :.
cron