Crash répétitif windows 7

Fermé
jérémi - 14 juin 2011 à 17:06
cemkusprocess Messages postés 135 Date d'inscription samedi 30 avril 2011 Statut Membre Dernière intervention 1 juillet 2011 - 14 juin 2011 à 17:25
Bonjour, j'ai acheté mon nouvel ordi il y a 3 jours mais impossible d'y jouer. Par interval de 15-20 minutes l'ordinateur crash, un écran bleu apparait me disant que windoes a fermé mon ordinateur pour évité les bris ou quelque chose du genre. j'ai fait les analyse avec whocrashed et voici le rapport qu'il me donne.

On Tue 2011-06-14 14:49:06 GMT your computer crashed
crash dump file: C:\Windows\Minidump\061411-13852-01.dmp
This was probably caused by the following module: nvlddmkm.sys (nvlddmkm+0xCE7C7)
Bugcheck code: 0xA (0x28, 0x2, 0x1, 0xFFFFF80003104412)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\nvlddmkm.sys
product: NVIDIA Windows Kernel Mode Driver, Version 275.33
company: NVIDIA Corporation
description: NVIDIA Windows Kernel Mode Driver, Version 275.33
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.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 275.33 , NVIDIA Corporation).
Google query: nvlddmkm.sys NVIDIA Corporation IRQL_NOT_LESS_OR_EQUAL




On Tue 2011-06-14 14:49:06 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: tcpip.sys (tcpip+0x8E9B9)
Bugcheck code: 0xA (0x28, 0x2, 0x1, 0xFFFFF80003104412)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\tcpip.sys
product: Système d'exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote TCP/IP
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 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 Tue 2011-06-14 11:19:20 GMT your computer crashed
crash dump file: C:\Windows\Minidump\061411-15210-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7FD00)
Bugcheck code: 0x50 (0xFFFFF6FB7D3EBFF8, 0x0, 0xFFFFF800030E0C9C, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
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 invalid system memory has been referenced.
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 2011-06-13 19:25:37 GMT your computer crashed
crash dump file: C:\Windows\Minidump\061311-16005-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7FD00)
Bugcheck code: 0x4E (0x99, 0x111092, 0x2, 0x15A9C)
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 Mon 2011-06-13 16:51:52 GMT your computer crashed
crash dump file: C:\Windows\Minidump\061311-15490-01.dmp
This was probably caused by the following module: luafv.sys (luafv+0x121FF)
Bugcheck code: 0x7F (0x8, 0x80050031, 0x406F8, 0xFFFFF88003D071FF)
Error: UNEXPECTED_KERNEL_MODE_TRAP
file path: C:\Windows\system32\drivers\luafv.sys
product: Système d'exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote de filtre de virtualisation de fichier LUA
Bug check description: This bug check indicates that the Intel CPU generated a trap and the kernel failed to catch this trap.
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 Mon 2011-06-13 16:41:02 GMT your computer crashed
crash dump file: C:\Windows\Minidump\061311-15849-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7FD00)
Bugcheck code: 0x3B (0xC000001D, 0xFFFFF88000A0C501, 0xFFFFF880086F6DE0, 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 which cannot be identified at this time.


On Mon 2011-06-13 02:43:32 GMT your computer crashed
crash dump file: C:\Windows\Minidump\061211-14773-01.dmp
This was probably caused by the following module: dxgmms1.sys (dxgmms1+0x20CEE)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF88003C45CEE, 0xFFFFF88005A83668, 0xFFFFF88005A82EC0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\dxgmms1.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics MMS
Bug check description: This indicates that a system thread 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 Mon 2011-06-13 01:18:52 GMT your computer crashed
crash dump file: C:\Windows\Minidump\061211-13665-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7FD00)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80002DC2FF6, 0xFFFFF88006EC8DA0, 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 which cannot be identified at this time.


On Mon 2011-06-13 00:40:19 GMT your computer crashed
crash dump file: C:\Windows\Minidump\061211-16426-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7FD00)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80002DC70FD, 0xFFFFF88008032E00, 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 which cannot be identified at this time.


On Mon 2011-06-13 00:31:07 GMT your computer crashed
crash dump file: C:\Windows\Minidump\061211-16582-01.dmp
This was probably caused by the following module: ks.sys (ks+0x27BD)
Bugcheck code: 0x7F (0x8, 0x80050031, 0x406F8, 0xFFFFF8800444D7BD)
Error: UNEXPECTED_KERNEL_MODE_TRAP
file path: C:\Windows\system32\drivers\ks.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Kernel CSA Library
Bug check description: This bug check indicates that the Intel CPU generated a trap and the kernel failed to catch this trap.
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 Mon 2011-06-13 00:00:53 GMT your computer crashed
crash dump file: C:\Windows\Minidump\061211-21512-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7FD00)
Bugcheck code: 0xA (0x1, 0x2, 0x1, 0xFFFFF80002C9278C)
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.



j'attend votre aide avec impatiente, merci d'avance !

A voir également:

2 réponses

je-ne-sais-rien Messages postés 308 Date d'inscription lundi 21 février 2011 Statut Membre Dernière intervention 12 juillet 2013 50
14 juin 2011 à 17:22
bonjour, tu peux essayer de faire une réinstallation complète pour voir mais si l'ordinateur n'a que trois jours (et je suppose qu'il était livré avec windows 7 dessus) alors retourne-le au service après vente pour un échange.
0
cemkusprocess Messages postés 135 Date d'inscription samedi 30 avril 2011 Statut Membre Dernière intervention 1 juillet 2011 12
14 juin 2011 à 17:25
Bonjour

Si tu as la garantie,utilise la!Sinon formatage , en principe tu as une image dans ton système de ta machine(recovery)
0