Solved BSOD Help! WhoCrashed Report

[FONT=Segoe UI, Arial]Please help! I have no clue what's going on TT-TT

computer name: AWESOMENESS-PC
windows version: Windows Vista Service Pack 2, 6.0, build: 6002
windows dir: C:\Windows
Hardware: VGN-CS26S_Q, Sony Corporation, VAIO
CPU: GenuineIntel Intel(R) Core(TM)2 Duo CPU P8600 @ 2.40GHz Intel586, level: 6
2 logical processors, active mask: 3
RAM: 3217084416 total
VM: 2147352576, free: 1996177408

[/FONT][FONT=Segoe UI, Arial]Crash dump directory: C:\Windows\Minidump[/FONT]
[FONT=Segoe UI, Arial][/FONT]
[FONT=Segoe UI, Arial]Crash dumps are enabled on your computer.
[/FONT]
[FONT=Segoe UI, Arial]On Sun 5/18/2014 6:59:06 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini051814-02.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntkrnlpa.exe[/FONT] (nt+0x87756)
Bugcheck code: 0x1000007E (0xFFFFFFFFC000001D, 0xFFFFFFFF81ECA756, 0xFFFFFFFF8AF93B6C, 0xFFFFFFFF8AF93868)
Error: [FONT=Segoe UI, Arial]SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M[/FONT]
file path: C:\Windows\system32\ntkrnlpa.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 system thread 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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.


[/FONT]
[FONT=Segoe UI, Arial]On Sun 5/18/2014 6:59:06 PM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntkrpamp.exe[/FONT] (nt!KeBugCheckEx+0x1E)
Bugcheck code: 0x7E (0xFFFFFFFFC000001D, 0xFFFFFFFF81ECA756, 0xFFFFFFFF8AF93B6C, 0xFFFFFFFF8AF93868)
Error: [FONT=Segoe UI, Arial]SYSTEM_THREAD_EXCEPTION_NOT_HANDLED[/FONT]
Bug check description: This bug check indicates that a system thread generated an exception that the error handler did not catch.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: ntkrpamp.exe .
Google query: [FONT=Segoe UI, Arial]ntkrpamp.exe SYSTEM_THREAD_EXCEPTION_NOT_HANDLED[/FONT]


[/FONT]
[FONT=Segoe UI, Arial]On Sun 5/18/2014 3:01:59 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini051814-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntkrnlpa.exe[/FONT] (nt+0x4E643)
Bugcheck code: 0x7F (0xD, 0x0, 0x0, 0x0)
Error: [FONT=Segoe UI, Arial]UNEXPECTED_KERNEL_MODE_TRAP[/FONT]
file path: C:\Windows\system32\ntkrnlpa.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 bug check indicates that the Intel CPU generated a trap and the kernel failed to catch this trap.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.


[/FONT]
[FONT=Segoe UI, Arial]On Sun 5/18/2014 12:32:47 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini051714-04.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]win32k.sys[/FONT] (win32k+0xC8DA4)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF943A8DA4, 0xFFFFFFFF9CB22BB4, 0x0)
Error: [FONT=Segoe UI, Arial]KERNEL_MODE_EXCEPTION_NOT_HANDLED_M[/FONT]
file path: C:\Windows\system32\win32k.sys
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: Multi-User Win32 Driver
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 that cannot be identified at this time.


[/FONT]
[FONT=Segoe UI, Arial]On Sat 5/17/2014 11:30:11 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini051714-03.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntkrnlpa.exe[/FONT] (nt+0x4E643)
Bugcheck code: 0x7F (0xD, 0x0, 0x0, 0x0)
Error: [FONT=Segoe UI, Arial]UNEXPECTED_KERNEL_MODE_TRAP[/FONT]
file path: C:\Windows\system32\ntkrnlpa.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 bug check indicates that the Intel CPU generated a trap and the kernel failed to catch this trap.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.


[/FONT]
[FONT=Segoe UI, Arial]On Sat 5/17/2014 1:58:10 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini051714-02.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntkrnlpa.exe[/FONT] (nt+0x4DECD)
Bugcheck code: 0xA (0x3495FBFF, 0xFF, 0x0, 0xFFFFFFFF81E905D3)
Error: [FONT=Segoe UI, Arial]IRQL_NOT_LESS_OR_EQUAL[/FONT]
file path: C:\Windows\system32\ntkrnlpa.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 that cannot be identified at this time.


[/FONT]
[FONT=Segoe UI, Arial]On Sat 5/17/2014 1:45:16 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini051714-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntkrnlpa.exe[/FONT] (nt+0x4DECD)
Bugcheck code: 0xA (0x3EA20BFF, 0xFF, 0x0, 0xFFFFFFFF81E6C5D3)
Error: [FONT=Segoe UI, Arial]IRQL_NOT_LESS_OR_EQUAL[/FONT]
file path: C:\Windows\system32\ntkrnlpa.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 that cannot be identified at this time.


[/FONT]
[FONT=Segoe UI, Arial]On Sat 5/17/2014 3:44:53 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini051614-03.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntkrnlpa.exe[/FONT] (nt+0x9182E)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF81EAF82E, 0xFFFFFFFFA04A3B24, 0x0)
Error: [FONT=Segoe UI, Arial]KERNEL_MODE_EXCEPTION_NOT_HANDLED_M[/FONT]
file path: C:\Windows\system32\ntkrnlpa.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 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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.


[/FONT]
[FONT=Segoe UI, Arial]On Sat 5/17/2014 3:40:34 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini051614-02.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntkrnlpa.exe[/FONT] (nt+0x4DECD)
Bugcheck code: 0xA (0x3E9A6BFF, 0xFF, 0x0, 0xFFFFFFFF81E535D3)
Error: [FONT=Segoe UI, Arial]IRQL_NOT_LESS_OR_EQUAL[/FONT]
file path: C:\Windows\system32\ntkrnlpa.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 that cannot be identified at this time.


[/FONT]
[FONT=Segoe UI, Arial]On Fri 5/16/2014 7:17:46 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini051614-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]Unknown[/FONT] (0x018A27A1)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0x18A27A1, 0xFFFFFFFF803ECC49, 0x0)
Error: [FONT=Segoe UI, Arial]KERNEL_MODE_EXCEPTION_NOT_HANDLED_M[/FONT]
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.
A third party driver was identified as the probable root cause of this system error.

[/FONT]

The general gist of the problem is that my computer is randomly BSOD-ing when I'm online and I'm pretty sure it's completely my fault. I installed a new software that's not the cause of the problem because I've had it before, but in order to run it I had to temporarily turn off my Firewall... and I forgot to turn it back on...

so anyway, six weeks later, bam BSOD
and it happens frequently, as shown by the numerous crash reports
but I can never read what's on the screen because it flashes too fast
the WhoCrashed program tells me ntkrpamp.exe is the issue but idk what to do from there

If you would follow our posting instructions, someone will come by to help
http://www.vistax64.com/crashes-debugging/282419-blue-screen-death-bsod-posting-instructions.html

I came here because I thought this forum had nice people who could give a non-techie some tips on a problem, not to be ignored until I'm forced to download a useless "Seven Forums Diagnostic Tool". My WhoCrashed report essentially contains the exact same information - I fail to see why the format matters so much. It makes me sad that this website is really about self promotion. I'll pay for a repair, thank you very much.