BSOD occurs after logging in to windows

Can you post it following the Blue Screen of Death (BSOD) Posting Instructions?

All your BSOD-s were caused by Norton/Symantec.

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

If the removal tool does not work uninstall using Revo uninstaller in Advanced Mode (Delete leftover registry of the programs):

• Download Revo Uninstaller Freeware - Free and Full Download - Uninstall software, remove programs, solve uninstall problems

Make scans with the following:

-Kaspersky TDSSKiller

• Anti-rootkit utility TDSSKiller

-ESET online scanner

• Free Online Virus Scanner | ESET

Microsoft Security Essentials.

Recommended from a strict BSOD perspective, compatibility & stability compared to other antiviruses/internet security software. It is free and lightweight:-

• Microsoft Security Essentials, Free antivirus for windows.
• Malwarebytes Anti-Malware Free
• Good and Free system security combination
• 
  

   Warning

Do not start the free trial of Malware Bytes; remember to deselect that option when prompted.

Run a full scan with both (separately) once downloaded, installed and updated.

Perform a System File Check to check the integrity of all protected Windows 7 :

1. Click on the start
2. Type CMD on Search
3. Left click and Run as Administrator
4. Type
   Code:

   SFC /scannow

Full tutorial here:

• SFC /Scannow Command - System File Checker

Disk Check on your hard drive for file system errors and bad sectors on it.

• How to run Disk Check on Windows 7

Reduce items at start-up. Nothing except anti-virus.

• Startup Programs - Change
• Troubleshoot Application Conflicts by Performing a Clean Startup

Let us know the results.

BSOD BUGCHECK SUMMARY

Code:

Built by: 7601.17944.x86fre.win7sp1_gdr.120830-0333
Debug session time: Tue Feb 19 19:48:44.550 2013 (UTC + 6:00)
System Uptime: 0 days 0:01:27.160
*** WARNING: Unable to verify timestamp for SYMEVENT.SYS
*** ERROR: Module load completed but symbols could not be loaded for SYMEVENT.SYS
----- ETW minidump data unavailable-----
Probably caused by : csrss.exe
BUGCHECK_STR:  0xF4_c00000fd
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME:  csrss.exe
FAILURE_BUCKET_ID:  0xF4_c00000fd_IMAGE_csrss.exe
CPUID:        "Intel(R) Core(TM)2 Duo CPU     P8600  @ 2.40GHz"
MaxSpeed:     2400
CurrentSpeed: 2394
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17944.x86fre.win7sp1_gdr.120830-0333
Debug session time: Tue Feb 19 17:08:50.533 2013 (UTC + 6:00)
System Uptime: 0 days 0:01:56.156
*** WARNING: Unable to verify timestamp for SYMEVENT.SYS
*** ERROR: Module load completed but symbols could not be loaded for SYMEVENT.SYS
----- ETW minidump data unavailable-----
Probably caused by : csrss.exe
BUGCHECK_STR: 0xF4_c00000fd
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME: csrss.exe
FAILURE_BUCKET_ID:  0xF4_c00000fd
CPUID:        "Intel(R) Core(TM)2 Duo CPU     P8600  @ 2.40GHz"
MaxSpeed:     2400
CurrentSpeed: 2394

Perform the clean boot in safe mode.

Good news.

Yes, go ahead. Post back when you've completed all the steps on my post :)

It may be a software causing the BSOD.

Follow the troubleshooting applications link again and try finding out which software is giving you the BSOD