BSOD IRQL_NOT_LESS_OR_EQUAL ntoskrnl.exe when starting up

When I start my computer up (I have Windows 7 Home Premium 64 Bit) and log into my user account, I will either get a BSOD saying IRQL_NOT_LESS_OR_EQUAL ntoskrnl.exe or something to do with ntosknl.exe or it will load up, and then display the message Logging off, then it would shut down. I grabbed all with the SF Diagnostic Tool and that is attached. I am writing this from safe mode (I am doing everything with safe mode) because I can't access my computer normally.

With BlueScreenViewer, this is what I get:
052613-54241-01.dmp 5/26/2013 8:17:19 AM IRQL_NOT_LESS_OR_EQUAL 0x0000000a fffffa00`04456690 00000000`00000002 00000000`00000001 fffff800`02c9913d ntoskrnl.exe ntoskrnl.exe+7cc40 NT Kernel & System Microsoft® Windows® Operating System Microsoft Corporation 6.1.7601.17640 (win7sp1_gdr.110622-1506) x64 ntoskrnl.exe+7cc40 C:\Windows\Minidump\052613-54241-01.dmp 2 15 7601 277,208

With WhoCrashed, I get this:
Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Sun 5/26/2013 3:15:14 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\052613-54241-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0xA (0xFFFFFA0004456690, 0x2, 0x1, 0xFFFFF80002C9913D)
Error: IRQL_NOT_LESS_OR_EQUAL
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 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.



On Sun 5/26/2013 3:15:14 PM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: netio.sys (NETIO!KfdAleRemoveFlowContextTable+0xBF)
Bugcheck code: 0xA (0xFFFFFA0004456690, 0x2, 0x1, 0xFFFFF80002C9913D)
Error: IRQL_NOT_LESS_OR_EQUAL
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 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 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 Sat 5/25/2013 6:09:12 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\052513-97516-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF80002C6EF6B, 0x0, 0x7EFA0000)
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 Sat 5/25/2013 4:41:10 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\052513-44803-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0x1E (0xFFFFFFFFC0000096, 0xFFFFF80002CB6B5A, 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 Sun 4/14/2013 3:04:14 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\052513-89934-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0x8F087)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF960000FF087, 0xFFFFF88005B65D30, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\win32k.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Multi-User Win32 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.

Anybody have an idea what is happening?
Looks like WhoCrashed says that it is a software bug...
Recent Software I have used:
Firefox (in safe mode)
BlueScreenViewer (in safe mode)
WhoCrashed (in safe mode)
And maybe a few others that I don't remember...
My computer has been broken for a few weeks now...I was planning on calling a computer technician but then I decided to try to do safe mode.
Safe mode, system restore, and others did not work before. I'm glad safe mode works now.
Thanks if you can help!

Norton
Norton tends to cause BSOD-s and seen it create several issues for users. Recommend uninstalling it with the Norton Removal Tool and replace with Microsoft Security Essentials. See if this stops the BSOD-s. Download and run the Norton Removal Tool to remove the Norton Product and Uninstallers (removal tools) for common antivirus software

Microsoft Security Essentials and Malwarebytes are recommended from a strict BSOD perspective. They do not cause blue screens on the system as other AV products do.

Microsoft Security Essentials, Free antivirus for windows

Malwarebytes Anti-Malware Free

   Warning

DO NOT start the free trial of MalwareBytes, unselect that option when prompted.

   Tip

Make full scans with both separately.

MSINFO32:
Please go to Start and type in "msinfo32.exe" (without the quotes) and press Enter
Save the report as an .nfo file, then zip up the .nfo file and upload/attach the .zip file with your next post.
Also, save a copy as a .txt file and include it also (it's much more difficult to read, but we have greater success in getting the info from it).

If you're having difficulties with the format, please open an elevated (Run as administrator) Command Prompt and type (or copy/paste) "msinfo32 /nfo %USERPROFILE%\Desktop\TEST.NFO" (without the quotes) and press Enter. Then navigate to Desktop to retrieve the TEST.NFO file. If you have difficulties with making this work, please post back. Then zip up the .nfo file and upload/attach the .zip file with your next post.

systeminfo:
Please open an elevated (Run as administrator) Command Prompt and type (or copy/paste) "systeminfo.exe >%USERPROFILE%\Desktop\systeminfo.txt" (without the quotes) and press Enter. Then navigate to Desktop to retrieve the syteminfo.txt file. If you have difficulties with making this work, please post back. Then zip up the .txt file and upload/attach the .zip file with your next post.

Basic checks:
Please run these tests and report back the results

1. SFC /scannow to check windows for corruption - SFC /SCANNOW Command - System File Checker
2. Disk check for errors on the hard drive - How to Run Disk Check in Windows 7
3. Troubleshoot applications by a clean boot - Troubleshoot Application Conflicts by Performing a Clean Startup
4. Memtest86+ paying close attention to part 3 - RAM - Test with Memtest86+
5. Hard drive test from HDD mfg website - Hard Drive Diagnostic Procedure

Okay what about the nfo files?

You should either then just do a Clean Install Windows 7 or Repair Install

Good luck. Be sure to post an update.