Ecran bleu rapport whocrashed

Bonjour,

Mon pc ne peut pas rester en mode normal car il reboote irrégulièrement.

j'ai trouvée l'idée de whocrashed mais ne sais que faire ensuite.
Pouvez-vous m'aider? Merci.

Rapport:
--------------------------------------------------------------------------------
System Information (local)
--------------------------------------------------------------------------------

computer name: DELL-OPTIPLEX
windows version: Windows XP Service Pack 3, 5.1, build: 2600
windows dir: C:\WINDOWS
Hardware: OptiPlex GX520 , Dell Inc. , Dell Inc. , 0UG982
CPU: GenuineIntel Intel(R) Celeron(R) CPU 2.66GHz Intel586, level: 15
1 logical processors, active mask: 1
RAM: 1063329792 total
VM: 2147352576, free: 2047336448




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

Crash dump directory: C:\WINDOWS\Minidump

Crash dumps are enabled on your computer.

On Mon 10/02/2014 01:48:58 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini021014-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x69810)
Bugcheck code: 0xA (0x4, 0x2, 0x0, 0xFFFFFFFF804F8FE3)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\WINDOWS\system32\ntkrnlpa.exe
product: Système d'exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Noyau et système NT
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 11/01/2014 22:42:36 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini011114-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x69810)
Bugcheck code: 0xA (0x4, 0x2, 0x0, 0xFFFFFFFF804F8FE3)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\WINDOWS\system32\ntkrnlpa.exe
product: Système d'exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Noyau et système NT
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 30/11/2013 07:34:11 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini113013-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x69810)
Bugcheck code: 0xA (0x4, 0x2, 0x0, 0xFFFFFFFF804F8FE3)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\WINDOWS\system32\ntkrnlpa.exe
product: Système d'exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Noyau et système NT
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
--------------------------------------------------------------------------------

3 crash dumps have been found and analyzed. No offending third party drivers have been found. Consider using WhoCrashed Professional which offers more detailed analysis using symbol resolution. Also configuring your system to produce a full memory dump may help you.


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.