BSOD windows Serveur 2008 R2

[Ouhlala]

Bonjour

J'ai des soucis avec mon serveur qui me fait des BSOD régulièrement (tout les jours, à heures non régulières), toujours à cause de "ntoskrnl". J'ai vérifié la ram (et même complètement changé les barettes), les disques durs, desinstallé les logiciels qui ne me servent pas, mis à jour tout ce qui devait l'être . J'ai aussi fait un coup d'antimalware, de ccleaner, et d'antivirus.

A priori, il faudrait que je teste tout les drivers un par un, mais ça risque d'être fastidieux, sans compter que je n'ai pas forcément envie de tout réinstaller non plus.

Des idées d'où çà pourrait venir?

Voici le dernier log who crashed :

-----------------

System Information (local)
--------------------------------------------------------------------------------

windows version: Windows Server 2008 R2 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
CPU: GenuineIntel Intel(R) Core(TM) i3-2100 CPU @ 3.10GHz Intel586, level: 6
4 logical processors, active mask: 15
RAM: 8589934592 total
VM: 2147352576, free: 1968934912



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

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.


On Sun 17/06/2012 01:48:06 GMT your computer crashed
crash dump file: C:\Windows\Minidump\061712-41948-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0xF4 (0x3, 0xFFFFFA8009B9DB30, 0xFFFFFA8009B9DE10, 0xFFFFF8000278A510)
Error: CRITICAL_OBJECT_TERMINATION
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 process or thread crucial to system operation has unexpectedly exited or been terminated.
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 17/06/2012 01:48:06 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: 0xF4 (0x3, 0xFFFFFA8009B9DB30, 0xFFFFFA8009B9DE10, 0xFFFFF8000278A510)
Error: CRITICAL_OBJECT_TERMINATION
Bug check description: This indicates that a process or thread crucial to system operation has unexpectedly exited or been terminated.
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 15/06/2012 03:42:04 GMT your computer crashed
crash dump file: C:\Windows\Minidump\061512-131524-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0x7A (0xFFFFF6FC501D8290, 0xFFFFFFFFC0000185, 0x7859C880, 0xFFFFF8A03B052000)
Error: KERNEL_DATA_INPAGE_ERROR
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 requested page of kernel data from the paging file could not be read into memory.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.

[Wobak]

T'as quelque chose juste avant dans l'event viewer ou pas du tout ?

J'ajoute 2 pistes :
-Supprimer la mémoire virtuelle
-Flusher le fichier d'échange

[Ouhlala]

nope j'ai rien dans l'event viewer avant ces bsods

J'ai mis en place le vidage automatique à chaque arret du fichier d'echange (rallonge de beaucoup l'arret du serveur), je vais voir si ça continue à bsod dans les prochains jours

Merci pour ton aide =)