Jump to content

dalem29

Honorary Members
  • Posts

    36
  • Joined

  • Last visited

Everything posted by dalem29

  1. Rick on the Dell Forums suggested running this for your inspection. Crash dump directory: C:\Windows\Minidump Crash dumps are enabled on your computer. On Thu 10/30/2014 12:59:01 PM GMT your computer crashed crash dump file: C:\Windows\Minidump\Mini103014-01.dmp This was probably caused by the following module: ntfs.sys (Ntfs+0xEF268) Bugcheck code: 0x50 (0xFFFFFFFFC5DB4084, 0x1, 0xFFFFFFFF8E0F2268, 0x2) Error: PAGE_FAULT_IN_NONPAGED_AREA file path: C:\Windows\system32\drivers\ntfs.sys product: Microsoft® Windows® Operating System company: Microsoft Corporation description: NT File System Driver Bug check description: This indicates that invalid system memory has been referenced. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time. On Thu 10/30/2014 12:59:01 PM GMT your computer crashed crash dump file: C:\Windows\memory.dmp This was probably caused by the following module: ntfs.sys (Ntfs+0x1A4B0) Bugcheck code: 0x50 (0xFFFFFFFFC5DB4084, 0x1, 0xFFFFFFFF8E0F2268, 0x2) Error: PAGE_FAULT_IN_NONPAGED_AREA file path: C:\Windows\system32\drivers\ntfs.sys product: Microsoft® Windows® Operating System company: Microsoft Corporation description: NT File System Driver Bug check description: This indicates that invalid system memory has been referenced. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time. Conclusion 2 crash dumps have been found and analyzed. No offending third party drivers have been found. Connsider using WhoCrashed Professional which offers more detailed analysis using symbol resolution. Also configuring your system to produce a full memory dump may help you. Read the topic general suggestions for troubleshooting system crashes for more information. Note that it's not always possible to state with certainty whether a reported driver is responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further. Rick on the Dell Forums suggested running this to see if might offer any insights as what might have cause the blue screen.
  2. Now about a week later since the last post. Did a version update of Hitman Pro and then decided to do quik scans of the rest of my security programs. Started an MBAM scan and then went into another room for a minute. I heard some funny sounds from my computer speakers, and then my online radio program went off. I shortly discovered that the mouse and keyboard wouldn't do anything. I just let it sit for awhile and got a BSOD of PAGE FAULT IN NON-PAGED AREA Nothing I could do to get out of the screen, so had to do manual shutdown. These lockups and blue screens only seem to occur since I installed this latest version of MBAM. I submitted the requested logs above and wonder if they show anything that might be causing this problem. Otherwise, the program seems to be up and active and the protection functions are intact according to WinPatrol, Task Manager, and the Dashboard. Occasionally, the MBAM icon won't appear in the tray at start up or disappear later if it did display at first. Perhaps it is best to simply not do rountine scans unless a problem shows up. What is you opinion?
  3. Well...I tried a scan one more time...and this time it finished. No system freeze, no pounding of head or fist on table! Not sure what the glitch was, I guess we will wait and see how it goes from here. .
  4. Here are the log files as requested. This Vista computer is getting a little long in the tooth, so there is probably a bit junk in there. I have CryptoPrevent which might have caused all those restrictions. FRST.txt Addition.txt CheckResults.txt
  5. With the clean install, it still simply stops scanning about 2/3 of the way through the heuristic portion of the scan...and freezes the system. Happens whether or not the rootkit option is checked or not. Notice this option is unchecked by default. Will try get the Diagnostic Logs to you today or tomorrow.
  6. Will do. Don't have much time today, but will get back with you in few days
  7. I have MalwareBytes Premium. I recently downloaded and installed version 2.0.3.1025. I have had trouble doing scans. During the Threat Scan everything goes well until late in the heuristics portion of the scan...when the timer stops increasing and no more objects are scanned. This has happened three times now. The first time resulted in a BSOD...didn't get the Stop code, in the second attempt it ended up with a black screen, and once again awhile ago...but the online radio kept working while nothing else was happening! In all cases I had to resort to a hard shutdown since the mouse and keyboard didn't work. I had the system start normally in each case, but the last time it happened the system wanted me to run Check Disk. The results of the procedure scrolled by too quickly to read, but guess I don't have a problem, since the computer boots up and seems to work fine after each episode. According to David (ky331), Hernan (Iroc9555) has had similar problems at the same place in the heuristic scan, which he has posted here. Perhaps a small bug in the new version? Up to this point MBAM Pro has worked well and I have been very pleased with it. Any advice would be appreciated as to how to get beyond this minor glitch.
  8. Thanks for having this post up and easy to find. Found out what I needed to know. Lifetime license is the best bargain in town.
  9. Forgot to mention that it includes regular scans by MBAM, usually the quick one.
  10. Normally, MB is the first one to show up in the tray and it stays light gray for a just a little bit, then turns blue. Today this process took a good two minutes of more and didn't change until after my AV (Avira), which normally appears last, was up and showing. There doesn't appear to be any conflict between the programs and I was wondering if MB Pro is simply updating while it is gray? Regular scans by AntiVir, SAS, Windows Defender, and Hitman Pro continue to show no infections on my system.
  11. Just downloaded database version 2464 successfully. However, each time it it updates the size of the update as shown on the progress bar is a tad larger. Several days ago it was 2200+ KB and this latest was something like 2418 or so. Am I downloading the entire database with some new stuff attached to it, or all the definitions new in each update and the file size always being about the same size and growing just a coincidence. No problem with it, just curious.
  12. I wrote a few weeks ago about having this problem. I have an XP computer that simply won't update, so I quit trying on that one for the time being. On the XPS with Vista that I am writing this on I have had the same problem, except the error message is intermittent...most updates proceed normally. Most of the time if I try to update a few minutes later it works...no error message, so that has to rule out something on my machine causing the error. This Vista machine has Avast and Online Armor, the same programs I had on the XP computer.
  13. Been a few days. I changed out my AV from Avast to AntiVir. Just changed my firewall to Outpost from Online Armor. Before that, I installed MBAM again. MBAM was included in Outpost's allowed components...watched Outpost making rules for MBAM. Attempted to update MBAM...same story, same error message again. This is the XP computer. Vista computer has been updating well for several days, then this morning I got the error message there. Attempted another search for updates immediately, this time the update finished. So on this Vista machine I will baby it along even if it misses the mark once in awhile. Have given up on the XP machine. Vista has Avast and Online Armor and MBAM was trouble free and worked well on both computers until version 1.47 came along. I have never had a problem with security products, except Symantec several years ago, so I would say that whatever you did on these new versions, it seems your servers are at fault somehow. Whatever you did somehow changed the whole internal configuration and created a conflict where none existed before. I, or any other average user, should not have to go and add exclusions and exceptions and make changes in the registry to get a product to work. In my opinion this current product is buggy and I could not recommend it to anyone.
  14. Weekend Update: Well, lately the Vista computer has been updating OK and will keep using MBAM on it if it updates more or less regularly even if if the updates get cut off on occasion. Some Dell members think it might even be my dialup connection that is causing the time out. I have no idea how clean my connection is, how efficient my phone lines are, or what my true speed might be. Once I go back to work in a few weeks, I could try broadband for awhile and see how that affects my computing. Sorry if I have seemed a bit surly in my previous posts.
  15. Tried to update just a few minutes ago and it worked this time. Rather than getting the generic answer, can you tell me how I can get the error message on one occasion halfway through the update, and the second occasion a short time ago have it go through. My questions are: What would cause it to time out...as compared to the update completing. They are all fairly small...2200 KB or so? Why and how would my security products allow the update at one time and not others?
  16. Yeah...I hope a solution is in our future. Forgot to mention that today's update started fine and was about halfway through the usual 2200+/- KB, then the error message came up, like some connection was broken.
  17. Well...the saga carries on. On my computer with Vista, when I last wrote a few days ago, the error message had started on this computer, in addition to the one with XP. Then this one started to update normally again for the past several days. Then just awhile ago it did started giving me error messages again. I tried it again and the update got about halfway done, and then the error message. So I can't see how it can do this if it is somehow being blocked or if certain files are not allowed or not recognized...that idea just doesn't compute with me. I am describing these symptoms in case you might be able to see something on your end or some coding in the program that might be causing this. At any rate, on the recommendation fo joe53 of the Dell Forums, I am going to put the Outpost Firewall on the XP computer. Since I haven't used Avira for awhile I'll change to that AV instead of using Avast there. I will delete and clean MBAM first, then download and install it again first before I make this change so that the new programs will have to adapt to or accept MBAM. We'll see if that works...stay tuned.
  18. Been there and done all that. I must say that some change you made to the program created conflicts that cause MBAM to display this error message. I have nothing else to check because my firewall allows MBAM, and I can't see where Avast would block it. It might one of the following that is blocking but there is no way for me to tell: SAS Windows Defender Spybot S&D with its Hosts File and SD Helper, but not Tea Timer Spyware Blaster A Squared Antimalware And for good measure, Scotty guarding the gate...WinPatrol! I probably have too much stuff on here. Hoping a solution can be found soon.
  19. I was, and still am getting the error messages on a computer with XP. The computer I am writing on now, with Vista, has just started to have the same problem. The difference is...updating to version 1.38 had gone well until this morning. During this morning's update, it got halfway through the update, and then the (732,0,0) error message popped up. It happened again just a few minutes ago. My connection and settings are fine or I would not be able to write and send this message. Any solutions in sight? I really don't think this is our (the users in question) fault.
  20. I can get updates OK on a machine with Vista, but not this one with XP. The updating problem started with version 1.37 and continues with 1.38. I use the same AV and Firewall on both...Avast Free and Onliner Armor. I don't see anyway to tell if Avast is blocking something, and Online Armor shows several lines of items that are "Allowed". I couldn't find MBAM in the Start Up menu, and ky331 over at the Dell Forums had me check to make sure it is Run Once item. I can't think of any other program or setting that would cause this happen. I repeat, I did not change any settings or security programs between versions 1.36 and 1.37. If I knew where to look further, I would. So...the developers did something to the program to cause a conflict, and it would be nice if they could discover a fix to it. I think MBAM is a very good and useful program, but under the circumstances the best I can do with it, at least on this computer, is to wait until a new version comes out...which should be almost up to date...and do a full scan then. I have other products for scanning and fixing, but I would like to be able to use this one if I ever ran into trouble.
  21. I updated to the new version 1.38 and it also did not go seeking further updates. When I clicked on the icon, it said MBAM was already in use and nothing would come up. I went to update other things and then came back after a few minutes and MBAM had another update ready. This was on my other computer running Vista. On the XP computer I am on now 1.37 would not update after installing, kept getting an error message, so deleted it entirely for the time being. I will download the new version shortly and see what happen this time. Looking at the list of update feature it mentions that a minor update problem was fixed, so hopefully that little episode will be over with.
  22. I have tried the above with no luck. I doubt if it is my Avast AV doing this because I get no alerts from that program. I will check back occasionally and see what happens when you get another version done and up. You probably will eventually find the conflict that is causing this and do a fix. Up till now MBAM gave me no problem except the updating progress bar was erratic in operation, but no problem with the updates themselves. Really don't think the problem is on my end since other programs work fine. Just glad I didn't get the paid version.
  23. I wonder if this driver problem has anything to do with the updating problem some of us are having?
  24. Before I try the above I just want to run a few more things by you. I use Avast for my AV and from what I can see it is not stopping MBAM from updating. Online Armor firewall shows several entries for MBAM "allowed" Might be some conflict with other security products but there was no problems before. As far as my connections go, I still use dialup via MSN. When I go to Internet Options>>Connections on the XP machine under Dialup and Virtual Private Network Settings I show just MSN (default). Further down "Never dial a connection" is checked. On the computer with Vista, which does update, it shows Diaup Connectin (default) with MSN listed directly below it and further down "always dial my default connection" is checked. Not sure why the difference or if this has any bearing on the present problem, as I don't remember manually configuring the system this way, just let it do its own thing. Since others are having a similar problem there must be some minor conflict amongst certain programs on certain systems. I will try using the utility after hearing from you. Can't find an exclusion list in Avast.
  25. Still getting this error message since downloading free version 1.37 on 5/26. Using MSN through dialup on an XP computer. The problem doesn't happen on my Vista computer. Under "Fixes" it says to make sure that the Internet Explorer is not set to Offline Mode. Where would I go to check out this setting? Everything seemed to work fine until the latest version update and no settings were changed? As always, thank for any help. Finally, is there any way to edit a post...can't seem to find it?
Back to top
×
×
  • Create New...

Important Information

This site uses cookies - We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.