Se connecter / S'enregistrer
Votre question

recherche aide pour crash et blue screen svp

Tags :
  • Jeux
  • Windows
  • Kernel
  • Système d'exploitation
  • Écrans
Dernière réponse : dans Systèmes d'exploitation
31 Mars 2012 04:58:21

bonjour j`ai un grave probleme et j'espère que quelqun poura m'aider
depuis très longtemps jai des crash et des ecran bleues seulement lorsque je joue a des jeux videos
tout le reste fonctionne très bien

voici les copie de mes crash de bluescreenview


123111-12671-01.dmp 2011-12-31 16:04:18 SYSTEM_SERVICE_EXCEPTION 0x0000003b 00000000`c0000005 fffff880`0f0307b3 fffff880`05eab5d0 00000000`00000000 dxgmms1.sys dxgmms1.sys+307b3 C:\Windows\Minidump\123111-12671-01.dmp 3 15 7601 291 216


123011-14281-01.dmp 2011-12-30 18:44:29 IRQL_NOT_LESS_OR_EQUAL 0x0000000a ffffffff`ffffffff 00000000`00000002 00000000`00000000 fffff800`028ddbb6 ntoskrnl.exe ntoskrnl.exe+7cc40 C:\Windows\Minidump\123011-14281-01.dmp 3 15 7601 291 232


122311-14250-01.dmp 2011-12-23 16:51:08 PAGE_FAULT_IN_NONPAGED_AREA 0x00000050 fffff8a0`0be69a00 00000000`00000001 fffff880`0fdc3ca1 00000000`00000002 ntoskrnl.exe ntoskrnl.exe+7cc40 C:\Windows\Minidump\122311-14250-01.dmp 3 15 7601 291 224


122111-18171-01.dmp 2011-12-21 21:03:49 UNEXPECTED_KERNEL_MODE_TRAP 0x0000007f 00000000`00000008 00000000`80050031 00000000`000006f8 fffff880`045d4fd7 nvmf6264.sys nvmf6264.sys+29fd7 C:\Windows\Minidump\122111-18171-01.dmp 3 15 7601 291 224


121911-18000-01.dmp 2011-12-20 00:33:17 PFN_LIST_CORRUPT 0x0000004e 00000000`00000099 00000000`00028a28 00000000`00000001 00000000`00028828 ntoskrnl.exe ntoskrnl.exe+7cc40 C:\Windows\Minidump\121911-18000-01.dmp 3 15 7601 291 160


121711-15468-01.dmp 2011-12-17 18:49:46 CACHE_MANAGER 0x00000034 00000000`0000055f ffffffff`c0000420 00000000`00000000 00000000`00000000 Ntfs.sys Ntfs.sys+aca17 C:\Windows\Minidump\121711-15468-01.dmp 3 15 7601 291 024


120911-17656-01.dmp 2011-12-09 17:46:06 MEMORY_MANAGEMENT 0x0000001a 00000000`00041287 00000000`05420018 00000000`00000000 00000000`00000000 dxgkrnl.sys dxgkrnl.sys+313f C:\Windows\Minidump\120911-17656-01.dmp 3 15 7601 291 216



120811-20859-01.dmp 2011-12-08 22:57:13 SYSTEM_SERVICE_EXCEPTION 0x0000003b 00000000`c0000005 fffff800`028c1c81 fffff880`076c6e30 00000000`00000000 ntoskrnl.exe ntoskrnl.exe+7cc40 C:\Windows\Minidump\120811-20859-01.dmp 3 15 7601 290 776




120811-18312-01.dmp 2011-12-08 19:28:32 SYSTEM_SERVICE_EXCEPTION 0x0000003b 00000000`c0000005 fffff800`028fe957 fffff880`060d10d0 00000000`00000000 ntoskrnl.exe ntoskrnl.exe+7cc40 C:\Windows\Minidump\120811-18312-01.dmp 3 15 7601 286 416






merci beaucoup

Autres pages sur : recherche aide crash blue screen svp

31 Mars 2012 05:16:34

voici ce que dit who crashed





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

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.


On Sat 2011-12-31 20:03:26 GMT your computer crashed
crash dump file: C:\Windows\Minidump\123111-12671-01.dmp
This was probably caused by the following module: dxgmms1.sys (dxgmms1+0x307B3)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8800F0307B3, 0xFFFFF88005EAB5D0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 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 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 Sat 2011-12-31 20:03:26 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: dxgmms1.sys (dxgmms1!VidMmInterface+0x1EEF3)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8800F0307B3, 0xFFFFF88005EAB5D0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 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 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 Fri 2011-12-30 22:43:35 GMT your computer crashed
crash dump file: C:\Windows\Minidump\123011-14281-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0xA (0xFFFFFFFFFFFFFFFF, 0x2, 0x0, 0xFFFFF800028DDBB6)
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 Fri 2011-12-23 20:49:52 GMT your computer crashed
crash dump file: C:\Windows\Minidump\122311-14250-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0x50 (0xFFFFF8A00BE69A00, 0x1, 0xFFFFF8800FDC3CA1, 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 Thu 2011-12-22 01:02:31 GMT your computer crashed
crash dump file: C:\Windows\Minidump\122111-18171-01.dmp
This was probably caused by the following module: nvmf6264.sys (nvmf6264+0x29FD7)
Bugcheck code: 0x7F (0x8, 0x80050031, 0x6F8, 0xFFFFF880045D4FD7)
Error: UNEXPECTED_KERNEL_MODE_TRAP
file path: C:\Windows\system32\drivers\nvmf6264.sys
product: NVIDIA Networking Driver
company: NVIDIA Corporation
description: NVIDIA MCP Networking Function Driver.
Bug check description: This bug check indicates that the Intel CPU generated a trap and the kernel failed to catch this trap.
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: nvmf6264.sys (NVIDIA MCP Networking Function Driver., NVIDIA Corporation).
Google query: nvmf6264.sys NVIDIA Corporation UNEXPECTED_KERNEL_MODE_TRAP




On Tue 2011-12-20 04:33:03 GMT your computer crashed
crash dump file: C:\Windows\Minidump\121911-18000-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0x4E (0x99, 0x28A28, 0x1, 0x28828)
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 Sat 2011-12-17 22:48:35 GMT your computer crashed
crash dump file: C:\Windows\Minidump\121711-15468-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0x34 (0x55F, 0xFFFFFFFFC0000420, 0x0, 0x0)
Error: CACHE_MANAGER
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 problem occurred in the file system's cache manager.
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 Fri 2011-12-09 21:45:12 GMT your computer crashed
crash dump file: C:\Windows\Minidump\120911-17656-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0x1A (0x41287, 0x5420018, 0x0, 0x0)
Error: MEMORY_MANAGEMENT
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 severe memory management error occurred.
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 Fri 2011-12-09 02:55:31 GMT your computer crashed
crash dump file: C:\Windows\Minidump\120811-20859-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF800028C1C81, 0xFFFFF880076C6E30, 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 Thu 2011-12-08 21:13:34 GMT your computer crashed
crash dump file: C:\Windows\Minidump\120811-18312-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF800028FE957, 0xFFFFF880060D10D0, 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.



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

10 crash dumps have been found and analyzed. A third party driver has been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers:

nvmf6264.sys (NVIDIA MCP Networking Function Driver., NVIDIA Corporation)

If no updates for these drivers are available, try searching with Google on the names of these drivers in combination the errors that have been reported for these drivers and include the brand and model name of your computer as well in the query. This often yields interesting results from discussions from users who have been experiencing similar problems.


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.
Tom's guide dans le monde
  • Allemagne
  • Italie
  • Irlande
  • Royaume Uni
  • Etats Unis
Suivre Tom's Guide
Inscrivez-vous à la Newsletter
  • ajouter à twitter
  • ajouter à facebook
  • ajouter un flux RSS