blue screen several times a day

hello i have been getting a blue screen several times a day please help this is the report from who crashed. i really dont know what to do to fix it any help would be greatly appreciated. System Information (local) ——————————————————————————– computer name: ALMA-PC windows version: Windows 7 Service Pack 1, 6.1, build: 7601 windows dir: C:\Windows CPU: GenuineIntel Intel® Pentium® CPU G630 @ 2.70GHz Intel586, level: 6 2 logical processors, active mask: 3 RAM: 4167213056 total VM: 2147352576, free: 1978179584 ——————————————————————————– Crash Dump Analysis ——————————————————————————– Crash dump directory: C:\Windows\Minidump Crash dumps are enabled on your computer. On Tue 1/15/2013 7:43:19 PM GMT your computer crashed crash dump file: C:\Windows\Minidump\011513-59732-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0) Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80002FFC617, 0xFFFFF88008578E70, 0x0) Error: SYSTEM_SERVICE_EXCEPTION 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 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 that cannot be identified at this time. On Tue 1/15/2013 7:43:19 PM GMT your computer crashed crash dump file: C:\Windows\memory.dmp This was probably caused by the following module: usbprint.sys (usbprint+0x3C99) Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80002FFC617, 0xFFFFF88008578E70, 0x0) Error: SYSTEM_SERVICE_EXCEPTION file path: C:\Windows\system32\drivers\usbprint.sys product: Microsoft® Windows® Operating System company: Microsoft Corporation description: USB Printer driver 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 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. On Tue 1/15/2013 7:34:27 PM GMT your computer crashed crash dump file: C:\Windows\Minidump\011513-54959-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0) Bugcheck code: 0x19 (0x3, 0xFFFFF80003019740, 0xFFFFF80003019740, 0xC001000003019740) Error: BAD_POOL_HEADER 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 pool header is corrupt. 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. On Tue 1/15/2013 7:32:13 PM GMT your computer crashed crash dump file: C:\Windows\Minidump\011513-53789-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0) Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80002FF7617, 0xFFFFF880076DFE60, 0x0) Error: SYSTEM_SERVICE_EXCEPTION 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 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 that cannot be identified at this time. On Tue 1/15/2013 3:17:01 AM GMT your computer crashed crash dump file: C:\Windows\Minidump\011413-25381-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x7EF90) Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0) Error: KMODE_EXCEPTION_NOT_HANDLED 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 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. On Tue 1/15/2013 2:58:30 AM GMT your computer crashed crash dump file: C:\Windows\Minidump\011413-26145-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x1AB9BC) Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF800030109BC, 0xFFFFF8800331D828, 0xFFFFF8800331D080) Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M 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 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. On Tue 1/15/2013 2:56:42 AM GMT your computer crashed crash dump file: C:\Windows\Minidump\011413-32729-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0) Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80002E78EC5, 0xFFFFF8800917FAC0, 0x0) Error: SYSTEM_SERVICE_EXCEPTION 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 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 that cannot be identified at this time. On Tue 1/15/2013 1:20:56 AM GMT your computer crashed crash dump file: C:\Windows\Minidump\011413-39655-01.dmp This was probably caused by the following module: tcpip.sys (tcpip+0x9D0D8) Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0) Error: KMODE_EXCEPTION_NOT_HANDLED file path: C:\Windows\system32\drivers\tcpip.sys product: Microsoft® Windows® Operating System company: Microsoft Corporation description: TCP/IP 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. On Mon 1/14/2013 10:17:52 PM GMT your computer crashed crash dump file: C:\Windows\Minidump\011413-25443-01.dmp This was probably caused by the following module: netio.sys (NETIO+0x4E358) Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0) Error: KMODE_EXCEPTION_NOT_HANDLED file path: C:\Windows\system32\drivers\netio.sys product: Microsoft® Windows® Operating System company: Microsoft Corporation description: Network I/O Subsystem 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. On Mon 1/14/2013 8:52:40 PM GMT your computer crashed crash dump file: C:\Windows\Minidump\011413-57829-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0) Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80002E93EC5, 0xFFFFF8800806ADF0, 0x0) Error: SYSTEM_SERVICE_EXCEPTION 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 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 that cannot be identified at this time. On Mon 1/14/2013 8:44:11 PM GMT your computer crashed crash dump file: C:\Windows\Minidump\011413-69498-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0) Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80002E8FEC5, 0xFFFFF88008B62D80, 0x0) Error: SYSTEM_SERVICE_EXCEPTION 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 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 that cannot be identified at this time. On Mon 1/14/2013 2:48:16 AM GMT your computer crashed crash dump file: C:\Windows\Minidump\011313-30856-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x705C0) Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80002E8B7A5, 0xFFFFF88007A30D80, 0x0) Error: SYSTEM_SERVICE_EXCEPTION 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 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 that cannot be identified at this time. On Mon 1/14/2013 1:41:17 AM GMT your computer crashed crash dump file: C:\Windows\Minidump\011313-27222-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x70590) Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0) Error: KMODE_EXCEPTION_NOT_HANDLED 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 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. On Mon 1/14/2013 1:17:17 AM GMT your computer crashed crash dump file: C:\Windows\Minidump\011313-24507-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x705C0) Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80002EBD7A5, 0xFFFFF88006AF1B40, 0x0) Error: SYSTEM_SERVICE_EXCEPTION 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 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 that cannot be identified at this time. On Sun 1/13/2013 9:36:17 PM GMT your computer crashed crash dump file: C:\Windows\Minidump\011313-36488-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x70590) Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0) Error: KMODE_EXCEPTION_NOT_HANDLED 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 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.

Well although that looks a lot of issues, there are only 3 or 4 that are repeated, from looking at a couple of quick searches it suggests it may be a video driver issue, so lets make sure you have the latest driver available, and if needed the old driver cleansed (removed totally), do you know what card you have and are OK in getting the latest driver from the makers from it ?

Now if it's an Nvidia card\driver, the latest file has a check box on it, at least that's what mine offered a few weeks back, anyway the box you tick, what this does it make the new install a clean install, ticking the box tells it to remove previous drivers before it adds the new ones, which when problems are possible it's advised to do this, some will say do it for every instance, kind of belt and braces approach, but it needs doing when probable drivers are behind it.

Should you have a different driver, you can use Driver Fusion to clean any previous drivers before installing new ones, you simply tell it from it's list what you want to find (which specific hardware driver), do this by clicking on the relevant part, then click analyse, once finished it lists them all (what it's found), then if needed check the boxes, then click Clean to remove them all, see if this helps at all.