Try generating this report instead:
Please run this report collecting tool so that we can provide a complete analysis: http://omgdebugging.com/bsod-inspector/
When done a Notepad document will open with the name of the file and it's location. (By default it'll be a .zip file located on your Desktop)
Simply upload the .zip file with your next post and we'll move on from there.
If that doesn't work, then do this:
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.
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.
A BSOD problem from Norton isn't a criticism of the Norton program. It's a statement that the memory dumps have pointed to Norton drivers as being to blame.
For example, one of the memory dumps stated:
Probably caused by :EX64.SYS ( EX64+12d996 )
This is a driver that belongs to Norton.
If you look for the "Probably caused by" string in the memory dumps concealed by the Show/Hide tags, you'll see that at least 6 of them blame Norton drivers.
All programs have the potential to become corrupted (which is what I suspect here). There's also many other possible reasons for why this would happen - but we don't often get into discovering why it happened (as long as we fix it).
Uninstalling your Norton will tell you if that is the problem.
While testing, you should have an antivirus installed (to keep from getting infected). I recommend using a free one during testing (for W7, I suggest Microsoft Security Essentials).
Then, when finished testing, feel free to download a fresh copy of the Norton and reinstall it (and uninstall the Microsoft Security Essentials).
Again, this is a testing procedure - it is not a criticism of the Norton product.
Finally, in BSOD analysis there's different types of BSOD events.
Most are simple and the debugger points to the faulting driver.
Some are more complex, and involve different drivers working against each other, faulting drivers exiting before the crash - so no info is available for them, hardware problems, compatibility issues, etc.
On average it takes about 2 pages of posts to fix a simple BSOD problem, the more complicated take 4-6 or more pages.