BSOD dont know what to do

[Chestersx]

Today i got 8 Blue Screen and i m getting really angry and i really dont know what to do, to fix it.
Can anyone help me?
Gonna show the report

[FONT=Segoe UI, Arial]On Tue 21-08-2012 17:20:02 GMT your computer crashed
crash dump file: C:\Windows\Minidump\082112-15225-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x7F1C0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF800032A2FB6, 0xFFFFF8800A040F40, 0x0)
Error: [FONT=Segoe UI, Arial]SYSTEM_SERVICE_EXCEPTION[/FONT]
file path: C:\Windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: NT Kernel & System
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
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.
[/FONT]

[FONT=Segoe UI, Arial]On Tue 21-08-2012 17:20:02 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntkrnlmp.exe[/FONT] (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF800032A2FB6, 0xFFFFF8800A040F40, 0x0)
Error: [FONT=Segoe UI, Arial]SYSTEM_SERVICE_EXCEPTION[/FONT]
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
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.
[/FONT]

[FONT=Segoe UI, Arial]On Tue 21-08-2012 16:40:03 GMT your computer crashed
crash dump file: C:\Windows\Minidump\082112-15288-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x7F1C0)
Bugcheck code: 0x109 (0xA3A039D898F18510, 0x0, 0x3A7B481C67A13354, 0x101)
Error: [FONT=Segoe UI, Arial]CRITICAL_STRUCTURE_CORRUPTION[/FONT]
file path: C:\Windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: NT Kernel & System
Bug check description: This indicates that the kernel has detected critical kernel code or data corruption.
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.
[/FONT]

[FONT=Segoe UI, Arial]On Tue 21-08-2012 16:06:10 GMT your computer crashed
crash dump file: C:\Windows\Minidump\082112-16738-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x7F1C0)
Bugcheck code: 0xA (0xFFFFF28007071DA0, 0x2, 0x1, 0xFFFFF80003308186)
Error: [FONT=Segoe UI, Arial]IRQL_NOT_LESS_OR_EQUAL[/FONT]
file path: C:\Windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
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.
[/FONT]

[FONT=Segoe UI, Arial]On Tue 21-08-2012 15:53:33 GMT your computer crashed
crash dump file: C:\Windows\Minidump\082112-20077-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x7F1C0)
Bugcheck code: 0xA (0xFFFFBA80099B9A98, 0x2, 0x0, 0xFFFFF80003310D3F)
Error: [FONT=Segoe UI, Arial]IRQL_NOT_LESS_OR_EQUAL[/FONT]
file path: C:\Windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
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.
[/FONT]

[FONT=Segoe UI, Arial]On Tue 21-08-2012 15:30:20 GMT your computer crashed
crash dump file: C:\Windows\Minidump\082112-17784-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x7F1C0)
Bugcheck code: 0xA (0x28, 0x2, 0x0, 0xFFFFF800032D03D8)
Error: [FONT=Segoe UI, Arial]IRQL_NOT_LESS_OR_EQUAL[/FONT]
file path: C:\Windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
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.
[/FONT]

[FONT=Segoe UI, Arial]On Tue 21-08-2012 15:25:25 GMT your computer crashed
crash dump file: C:\Windows\Minidump\082112-16832-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x7F1C0)
Bugcheck code: 0xD1 (0x80000000018, 0x2, 0x0, 0xFFFFF880016F7CA3)
Error: [FONT=Segoe UI, Arial]DRIVER_IRQL_NOT_LESS_OR_EQUAL[/FONT]
file path: C:\Windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: NT Kernel & System
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 the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
[/FONT]

[FONT=Segoe UI, Arial]On Tue 21-08-2012 01:11:29 GMT your computer crashed
crash dump file: C:\Windows\Minidump\082112-19718-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]fltmgr.sys[/FONT] (fltmgr+0x3B77)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF88000E72B77, 0x0, 0x80000000028)
Error: [FONT=Segoe UI, Arial]KMODE_EXCEPTION_NOT_HANDLED[/FONT]
file path: C:\Windows\system32\drivers\fltmgr.sys
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: Microsoft Filesystem Filter Manager
Bug check description: This indicates that a kernel-mode program 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 which cannot be identified at this time.
[/FONT]

 

[KSoD]

You have a multitude of problems. Starting with Drivers, moving onto RAM and then finally the system itself. With that many errors in a row and given the range, I would say you need to backup right now and reinstall to save yourself a whole bunch of time.

 

[wilsonfrank]

I'd agree with Mak, you have a multitude of problems on that machine!!!
First things first, I'd be interested to know the OS ver n the config on that machine to be able to suggest some fixes.
A complete back-up, format and reinstall is something that is done as a last resort! And if its a hardware issue, and there's no guarantee that'd actually fix the issue.

Do remember to post the OS ver n the config, I'll see if there is something that I can help with.