lolom7 : Profil et derniers messages sur le Forum Informatique

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.

Merci beaucoup

lolom7

Contacter lolom7

Statistiques de l’utilisateur

Les derniers messages de lolom7