Thanks for explaining that, I'm still a little confused about "wireless networking adapter over wired onboard networking" but I'll get back to that one later.
I'm sure your aware that the little snips you posted about the crashes really don't give any useful information. I'm sure you just did that to save space from posting the entire output.
The warning appears to be because your trying to use a 32bit debugger on a 64bit driver and it's unable to read the timestamps. But thats not very important because you could always right click on the files and check the properties if the time stamp was important.
The error about not loading symbols is normal.
Third party programs almost never release the symbol packages for there files and even if they did they would not be available through the MS symbolic store or download packages.
The symbols would make it easier for people to reverse engineer the executables and drivers and most companies would not like that to happen.
Microsoft releases the symbols as a courtesy to software developers as a way to debug problems in development since they want programs to run smoothly on windows.
Besides that, no information pertaining to the crash is given or even the faulting module.
I have no doubt that a norton file may be listed as a faulting module but that doesn't necessarily mean that it caused the crash.
For example, a lot of crash files I have debugged will list "ntoskrnl" as the faulting module. That file is the brains of windows. it's the Windows "NT Operating System Kernel" Just because it's listed as the faulting module does not mean it is the problem. The windows kernal "crashed" because something else made it crash.
Every time I see drivers listed in the debug, the first step is to update those drivers.
360 is an easy one, make sure you are running the most recent version and the live updates are complete.
For your Nvidia card, I would go the other direction and update it to the newest driver version.
Graphic drivers are one of the most common causes of crashes because display drivers are in use for every program, they run all the time just like windows.
Leave that "TP Link" unistalled for a while if you can get along without it.
The way you describe it seems to me that your computer connects to the internet though a wired LAN cable and the adapter is used to provide wireless to another system?
Is that what it does?
I'm also more than happy to look at some of your dump files if they are minidumps and not full kernal dumps.
Please don't think I'm an expert at it but I have done it a lot and I happen to have a system here setup with windbg connected to the Microsoft symbol server.
If you want to take me up on that offer just let me know and I'll send you an email address in a private message.
Dave