dalem29
Honorary Members-
Posts
36 -
Joined
-
Last visited
Reputation
0 Neutral-
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.
-
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?
-
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. .
-
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
-
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.
-
Will do. Don't have much time today, but will get back with you in few days
-
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.
-
MBAM PRO - How many computers?
dalem29 replied to mwalimu's topic in Malwarebytes for Windows Support Forum
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. -
Forgot to mention that it includes regular scans by MBAM, usually the quick one.
-
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.
-
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.
-
Won't Update. Error 732(0,0)
dalem29 replied to ctJosh's topic in Malwarebytes for Windows Support Forum
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. -
Error (732, 0,0) Woes Continue
dalem29 replied to dalem29's topic in Malwarebytes for Windows Support Forum
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. -
Error (732, 0,0) Woes Continue
dalem29 replied to dalem29's topic in Malwarebytes for Windows Support Forum
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. -
Error (732, 0,0) Woes Continue
dalem29 replied to dalem29's topic in Malwarebytes for Windows Support Forum
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?