On Fri 15/05/2015 13:47:53 GMT your computer crashed crash dump file: C:\Windows\Minidump\051515-49609-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x150CA0) Bugcheck code: 0x1A (0x41793, 0xFFFFF6BFFFA8C400, 0x1, 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 that cannot be identified at this time.
On Fri 15/05/2015 13:47:53 GMT your computer crashed crash dump file: C:\Windows\memory.dmp This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0) Bugcheck code: 0x1A (0x41793, 0xFFFFF6BFFFA8C400, 0x1, 0x0) Error: MEMORY_MANAGEMENT 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 that cannot be identified at this time.
On Fri 15/05/2015 13:44:16 GMT your computer crashed crash dump file: C:\Windows\Minidump\051515-39281-01.dmp This was probably caused by the following module: Unknown () Bugcheck code: 0x0 (0x0, 0x0, 0x0, 0x0) Error: CUSTOM_ERROR A third party driver was identified as the probable root cause of this system error. Google query: CUSTOM_ERROR
On Fri 15/05/2015 13:01:03 GMT your computer crashed crash dump file: C:\Windows\Minidump\051515-27796-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x150CA0) Bugcheck code: 0xA (0xFFFFFC00036688F0, 0x2, 0x1, 0xFFFFF800F5EC28B8) 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 15/05/2015 12:26:23 GMT your computer crashed crash dump file: C:\Windows\Minidump\051515-29609-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x150CA0) Bugcheck code: 0xA (0xFFFFD0012D596074, 0xA, 0x1, 0xFFFFF803C5B4F0A3) 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 15/05/2015 12:18:27 GMT your computer crashed crash dump file: C:\Windows\Minidump\051515-20609-01.dmp This was probably caused by the following module: ndis.sys (ndis+0xA7E19) Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF801780D6E19, 0xFFFFD000219B4A48, 0xFFFFD000219B4250) Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M file path: C:\Windows\system32\drivers\ndis.sys product: Système d'exploitation Microsoft® Windows® company: Microsoft Corporation description: NDIS (Network Driver Interface Specification) 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 that cannot be identified at this time.
On Fri 15/05/2015 09:13:39 GMT your computer crashed crash dump file: C:\Windows\Minidump\051515-26718-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x150CA0) Bugcheck code: 0x7F (0x8, 0xFFFFF80307518E70, 0xFFFFD000DAA1F7A0, 0xFFFFF80305C3F8CE) Error: UNEXPECTED_KERNEL_MODE_TRAP file path: C:\Windows\system32\ntoskrnl.exe product: Microsoft® Windows® Operating System company: Microsoft Corporation description: NT Kernel & System 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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Fri 15/05/2015 07:04:43 GMT your computer crashed crash dump file: C:\Windows\Minidump\051515-18281-01.dmp This was probably caused by the following module: usbuhci.sys (usbuhci+0x149F) Bugcheck code: 0xD1 (0xFFFFE0001C8E759F, 0x2, 0x1, 0xFFFFF80142B9449F) Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL file path: C:\Windows\system32\drivers\usbuhci.sys product: Microsoft® Windows® Operating System company: Microsoft Corporation description: UHCI USB Miniport Driver Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high. 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 that cannot be identified at this time.
On Fri 15/05/2015 06:54:37 GMT your computer crashed crash dump file: C:\Windows\Minidump\051515-19000-01.dmp This was probably caused by the following module: scsiport.sys (0xFFFFF8007411005E) Bugcheck code: 0xD1 (0x368, 0xA, 0x0, 0xFFFFF8007411005E) Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL file path: C:\Windows\system32\drivers\scsiport.sys product: Microsoft® Windows® Operating System company: Microsoft Corporation description: SCSI Port Driver Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high. 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 that cannot be identified at this time.
On Fri 15/05/2015 06:47:50 GMT your computer crashed crash dump file: C:\Windows\Minidump\051515-19250-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x150CA0) Bugcheck code: 0xA (0xFFFFE00000BB8B58, 0x2, 0x0, 0xFFFFF802F78C4620) 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.
51 crash dumps have been found and analyzed. Only 10 are included in this report. 3 third party drivers have 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:
athwnx.sys (Qualcomm Atheros Extensible Wireless LAN device driver, Qualcomm Atheros Communications, Inc.) cdrom.sys (SCSI CD-ROM Driver, Microsoft Corporation) nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 341.44 , 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 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.
Je suis sous windows 8.1
J'ai le CD pour réparer mais le pc plante dès la réparation ou formatage
Trouvez des réponses à vos questions sur l'exploitation du système d'exploitation Windows, les astuces, et les résolutions de problèmes. Rejoignez une communauté de passionnés de Windows pour une utilisation efficace et productive de votre PC.
