Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - XDamian

Pages: [1]
I guess I can leave this as solved but the solution has come as strangely as the problem had. I did and do have the Premium version of Malwarebytes and do use the scheduling mechanism. But this time I uninstalled using their application on their website as opposed to the uninstall app that comes with the bundle. I also have had, as I indicated before, no problems with the BSOD for a week now. SO I am declaring it GONE FOR GOOD!> But if you ask me how come, I can't answer you. I do not know what solved what. But I appreciate the support.

SO far it seems the clean-up of my registry has eliminated the BSOD.  I imagine that is possible since I do not know what sort of conflicts were created by the registry's condition. As to disabling java, I did  but found I really need it for the websites I frequent.  As to re-installing Malwarebyte, I have done that 3 times now. It still hangs and takes up a great deal of memory over time so when I see that happening I simply END it and start it up again.While this is only the third day I have not suffered a BSOD, I am hoping it will stay away from now on.

I would like to disable java but your instructions do not seem to apply to Chrome. Chrome does show how to disable java Script, but that I understand is not the Java which pertains to the update I just installed. (Or is it?)

I guess I am still awaiting Shane's reply. While waiting I loaded an app I used to use (although I stopped using it because McAfee Adviser told me the site has issues). System Mechanics has indicated (and fixed) the 795 registry errors. I understand that THAT is quite a lot. I did not have any when I was using SYSTEM MECHANIC. I have reinstalled it, for certainly among all that mess a BSOD could have been generated, YES? (or no??). SO far, with my fingers crossed, Its now 46 hours since I have seen a BSOD. I am knocking on wood vehemently because in the pit of my gut I sense I am walking a tightrope about 200 feet in the air with my eyes closed.
 However, while you do have the list of drivers I have re-installed as per your suggestion (see the NEW Add/remove list I attached), I would hope I could get some feedback on the former messages which indicated what the app "WhoCrashed" returned.

Thanks for the  Java tip. I have both uninstalled old and installed new Java. However both took a rather long time. Is that usual? AND are you suggesting that a BSOD could be due to this seemingly minor faux pas on my behalf?

And as you can tell from the ADD/'Remove page I did replace existing drivers as per the recommendation above.

I thought maybe a list of the latest ADD/Remove installations might be helpful also:(see attach)  The reason I am doing this is because once after uninstalling the latest program, I had a 28 hour respite from the BSOD and figured that was not a coincidence, so I try to eliminate  even the diagnostic programs if I am getting BS's more than previously.

The reason I took so long to reply is that the computer just went through the full diagnostics about 36 hours worth in one of the f keys. Of course any assistance with the info below would be appreciated.  (When I check this out , one article says its a registry error and suggests I use  Ntoskrnl Exe Repair Tool  for free, but since I keep DIskeeper running constantly I have my doubts about the registry  being disrupted. But if you have a suggestion where a trusted reg tool will help, I am all ears.) The attachment is simply a picture of what I posted here.

On Mon 11/24/2014 5:01:35 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\112514-19749-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x7F (0x8, 0x80050031, 0x6F8, 0xFFFFF80003C9BE08)
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that the Intel CPU generated a trap and the kernel failed to catch this trap.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

The mwac points to possibly when I tried turning malwarebytes to disabled on the advice of the Dell Specialist because he said it would not run correctly with McAfeee, however I never got that message till I turned it off so I think his advice is wrong since I have been using MWAREB for 2 years without ever seeing that message so I enabled it again.

On Mon 11/24/2014 5:01:35 AM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: mwac.sys (mwac+0x61B0)
Bugcheck code: 0x7F (0x8, 0x80050031, 0x6F8, 0xFFFFF80003C9BE08)
file path: C:\Windows\system32\drivers\mwac.sys
product: Malwarebytes Web Access Control
company: Malwarebytes Corporation
description: Malwarebytes Web Access Control
Bug check description: This bug check indicates that the Intel CPU generated a trap and the kernel failed to catch this trap.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: mwac.sys (Malwarebytes Web Access Control, Malwarebytes Corporation).
Google query: Malwarebytes Corporation UNEXPECTED_KERNEL_MODE_TRAP

I forgot to add I ran the Dell OS disk (re-installation) which has a partition to do diagnostics also and to run without doing a complete re-image but indicates it can help repair certain issues without being very specific.

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 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.

Windows 7 I am the admin, it is an XPS L701X which is my fav. I tried opening the DMP file but could not locate the proper app to do so. Please help here. I did send the Screen of the error I usually get. Perhaps you can help

Pages: [1]