Bluescreens pour mes premiers pas en traitement video

Bonjour,
J'ai une machine plutôt fiable avec laquelle je fais régulièrement de la PAO en jonglant avec les log de la suite Adobe, du traitement de musique, tout un tas de choses et je ne l'ai jamais vraiment prise en défaut. Aujourd'hui, pour la première fois je me suis attaqué à un petit montage vidéo et là ... une vraie cata, pas moins de 4 bluescreens dans l'après midi. Je ne comprends pas pourquoi. Le soucis c'est que je devrais être amené à traiter de la vidéo de plus en plus souvent...
Si quelqun pouvait me dire ce qu'il en est?

le rapport WhoCrashed:


windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
Hardware: ASUSTeK COMPUTER INC., M5A97 R2.0
CPU: AuthenticAMD AMD Phenom(tm) II X4 965 Processor AMD586, level: 16
4 logical processors, active mask: 15
RAM: 8531673088 total




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

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Thu 01/10/2015 17:19:47 GMT your computer crashed
crash dump file: C:\Windows\Minidump\100115-24242-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x735C0)
Bugcheck code: 0x1A (0x41287, 0x30, 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 that cannot be identified at this time.



On Thu 01/10/2015 17:09:35 GMT your computer crashed
crash dump file: C:\Windows\Minidump\100115-15459-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x735C0)
Bugcheck code: 0xC4 (0x91, 0x2, 0xFFFFFA80095F9060, 0x0)
Error: DRIVER_VERIFIER_DETECTED_VIOLATION
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This is the general bug check code for fatal errors found by Driver Verifier.
The driver switched stacks using a method that is not supported by the operating system. The only supported way to extend a kernel mode stack is by using KeExpandKernelStackAndCallout. 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 Thu 01/10/2015 14:38:29 GMT your computer crashed
crash dump file: C:\Windows\Minidump\100115-14944-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x735C0)
Bugcheck code: 0x1A (0x61940, 0x48C3000, 0x268BAAAC0ECDD09E, 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 Thu 01/10/2015 13:16:41 GMT your computer crashed
crash dump file: C:\Windows\Minidump\100115-17425-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x735C0)
Bugcheck code: 0x4E (0x99, 0x130A90, 0x0, 0x151090)
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 that cannot be identified at this time.