Rapport Who Crashed :
Code : Tout sélectionner
System Information (local)
--------------------------------------------------------------------------------
computer name: MADRIDISTA-PC
windows version: Windows 7 , 6.1, build: 7600
windows dir: C:\Windows
CPU: GenuineIntel Intel(R) Core(TM)2 Duo CPU E8300 @ 2.83GHz Intel586, level: 6
2 logical processors, active mask: 3
RAM: 3219644416 total
VM: 2147352576, free: 1953058816
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Tue 18/09/2012 15:00:43 GMT your computer crashed
crash dump file: C:\Windows\Minidump\091812-19187-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70040)
Bugcheck code: 0xA (0xFFFFF6FB7E8000C0, 0x2, 0x0, 0xFFFFF8000338432B)
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 Tue 18/09/2012 15:00:43 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: 0xA (0xFFFFF6FB7E8000C0, 0x2, 0x0, 0xFFFFF8000338432B)
Error: IRQL_NOT_LESS_OR_EQUAL
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 Mon 17/09/2012 19:31:24 GMT your computer crashed
crash dump file: C:\Windows\Minidump\091712-25484-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70040)
Bugcheck code: 0xA (0x48, 0x2, 0x1, 0xFFFFF80003333F3F)
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 Mon 17/09/2012 17:59:23 GMT your computer crashed
crash dump file: C:\Windows\Minidump\091712-17953-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70040)
Bugcheck code: 0xA (0x48, 0x2, 0x1, 0xFFFFF8000333FF3F)
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 Mon 17/09/2012 15:06:54 GMT your computer crashed
crash dump file: C:\Windows\Minidump\091712-16750-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70040)
Bugcheck code: 0xA (0x18, 0x2, 0x0, 0xFFFFF80003326FE7)
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 Sun 16/09/2012 13:23:39 GMT your computer crashed
crash dump file: C:\Windows\Minidump\091612-23125-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70040)
Bugcheck code: 0x1A (0x411, 0xFFFFF6FC5001BF48, 0xEF200000218B8882, 0xFFFFF6FC1001BF49)
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 Sat 15/09/2012 12:42:14 GMT your computer crashed
crash dump file: C:\Windows\Minidump\091512-19765-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70040)
Bugcheck code: 0x1A (0x411, 0xFFFFF6FC50009AD8, 0xB4D0000048DB8882, 0xFFFFF6FC10009AD9)
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 Thu 16/08/2012 01:48:10 GMT your computer crashed
crash dump file: C:\Windows\Minidump\081612-24875-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70040)
Bugcheck code: 0x4E (0x99, 0x20C0B, 0x0, 0x4CF0B)
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 Tue 07/08/2012 18:36:37 GMT your computer crashed
crash dump file: C:\Windows\Minidump\080712-19656-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70040)
Bugcheck code: 0x4E (0x99, 0x144FC, 0x2, 0x65782)
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 Fri 27/07/2012 21:56:14 GMT your computer crashed
crash dump file: C:\Windows\Minidump\072712-19453-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70040)
Bugcheck code: 0xA (0xFFFFF680001250A8, 0x0, 0x0, 0xFFFFF80003298B62)
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 Sun 15/07/2012 09:15:24 GMT your computer crashed
crash dump file: C:\Windows\Minidump\071512-25406-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70040)
Bugcheck code: 0x4E (0x99, 0x19592, 0x1, 0x71812)
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 Sun 24/06/2012 23:13:56 GMT your computer crashed
crash dump file: C:\Windows\Minidump\062512-18218-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70040)
Bugcheck code: 0xA (0xFFFFF6800015CEC0, 0x0, 0x0, 0xFFFFF800032EAB62)
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. 
Il ne faut pas d'erreur dans le cadre en bas à droite.