First off thanks for the suggestion. However, every single incidence of the crash states it is possible another driver may have caused the crash. The latest crash left this in the Event viewer.
Service 'WMPNetworkSvc' did not start correctly because CoCreateInstance(CLSID_UPnPDeviceFinder) encountered error '0x80004005'.
I have seen this a number of times. Googling WIndows comes up with this:"Call CoCreateInstance when you want to create only one object on the local system. To create a single object on a remote system, call the CoCreateInstanceEx function. To create multiple objects based on a single CLSID, call the CoGetClassObject function"
HOWEVER i AM NOT CERTAIN WHAT objects I am trying to call simultaneously.
I have McAfee and MBAM (Malwarebytes) as well as Peerblock although of course the last two are quasi security. When I want to run more safely I have Firefox set up through 2/3 European jumps without being able to trace it back to me using JonDO but I have noticed these BSOF come on whether I turn JonDo on or not.
As far as RUNNING REPAIRS in TWeaking.com in SAFEMODE WITH NETWORKING AFTER FOLLOWING EACH AND EVERY option from start to finish, THIS I have done. However, I have never run my computer in Safe/NEtworking when I simply want to use it. so I can't answer that question. I hear you strongly suggesting it to ferret out my problem, yes? Is there a way to change the resolution once you are there, because in various apps the resolution in Safe mode becomes a real pain\
I will await SHANE and thanks again for your response. Much appreciated. I am wondering if a simple loose AC/Adapter could have caused this BUT when I checked the power icon on my battery I was at 100% charge when I returned home and found I had received a BSOD while I was away, and no I don't have any cats, or pets. It was simply on a browser page the whole time. And of course the reliability report was cryptic as ever:
WIndows shut down unexpectedly.
ANd yes I run virus scans full 3 times a week and this one I just ran came back clean, as usual.
MyDell which has a BlueScreen trouble shooter simply came back with this message:
"The PCI bus driver appears to have caused a system crash",so I will try and re-install that driver now, however, that is the message from last night (the last one posted on the BSOD troubleshooter), so it has nothing to do with the one I JUST got.
The two PCI bus' in the SYSTEM DEVICES are from 2006 but they are working normally. The PCI in the network adaptor is from 2011 (FAMILY CONTROLLER WHICH i NEVER USE ANYWAY).ANd of course there are no exclamation points anywhere in my device monitor.
SO I HAVE PRETTY MUCH HAVE REACHED THE END OF MY DIAGNOSTIC CAPABILITIES AFTER running the WIndows Diagnostics and the BIOS Diagnostics and the DELL diagnostics because they all come back clean, even the one I let run for 16 hours that was mostly checking out the memory. The dskchk from the tweak in safe mode also came back clean as did the system file check ,and as I mentioned all this done strictly from the point of draining my power completely with both AC and the battery pack out etc. (Please ignore caps. They have a tendency to do that themselves without any clear indication except for a very tiny "A" without a line through it which is very easy to miss situated above my keyboard .
Thanks for any help or clarity thrown on this situation. I am open to any ideas at all short of doing a re-image of my OS.