Jump to content

d_m_burkus

Members
  • Posts

    13
  • Joined

  • Last visited

Reputation

0 Neutral
  1. The PC had been running well since I ran the VEW scan. This morning while watching a news video, the problem started again (and I have not been able to run the machine in Regular Mode -- I am using SafeMode now). I prepared a new VEW scan (data for 1 June to 18 June 2018), and as close to a detailed description of the history of the incident, both of which .txt files I am enclosing in the attached .zip archive. -- Daniel M. Burkus VEW (1 June to 18 June, 2018).zip
  2. Here is the VEW log. (Creating it made the PC shut down several times, so I let the machine cool down for a while before trying again.) -- Daniel M. Burkus VEW.zip
  3. Sorry, I have had problems saving the critical events (continually get errors, so the saved files have no data). Attached is a .zip containing what I hope is a valid file. For some reason the event viewer no longer groups the errors by type (I was trying to send only the critical errors, since they are the ones where the PC shut down), so this file contains all errors. In one of the MalwareBytes forum articles (replies) there was a suggestion to run ComboFix. I did that, and it seems to have helped (though I have not tried to run MalwareBytes because the last time the shut-down that it precipitated really messed up my PC). I have the logs, if you would like to review them. -- Daniel M. Burkus Events.zip
  4. Can you tell me how to export the entire system event log (other than making a separate .txt file for each event, or manually adding a number of events to a single file, I can not see how that can be done)? There have been 169 instances since March 30 (which is as far back as the records go -- though the event began to occur long before then). I reviewed a number of the events individually, and the contents (when pasted to a .txt file such as I sent) were absolutely identical, with the exception of the Event Record ID (which naturally would change, in sequence). Indeed, it is the case that the PC overheats and shuts down, as I have said all along. The point, though, is that it is usually a malware scan (or its aftermath -- the effects seem to linger for varying lengths of time) that precipitates this overheating, and always when it arrives at a specific point in the scan series. The point at which the PC overheats and shuts down, insofar as I can tell, is always very precisely the same. Too clearly so that this is simply a matter of random overheating, because then it should occur at a different time or point each time a scan is run. I have been running MalwareBytes at least once per week since this machine was set up, and can recall only one or two occasions -- quite some time ago -- when any malware was detected. So primarily I am using it prophylactically. Nevertheless, I think it is important to do this, and I would prefer to continue to do so in the future. The shutting down when caused by MalwareBytes has been happening since sometime in May; and, as with other scans that cause this to happen, once it starts, it continues to happen every time that program is run. -- Daniel M. Burkus
  5. The only thing I could find was in the Event viewer. The entire history is exactly the same -- only the event's number is different. I am attaching a log from there -- I tried to run MalwareBytes again and this time it froze 51 seconds into the scan (while performing "pre-scan operations"), and after a while the PC shut down. The file Event.zip contains the event log, which probably will not be much help. I compared the logs from a number of events, and the details in all of them were identical (all the way back to the first time this happened, when I tried to run a scan with Dr. Web). Also, I looked again (including looking through the Windows folder), but there is no "memory.dmp" file anywhere in this PC (according to "search programs and files"). -- Daniel M. Burkus Event.zip
  6. I should add that every time I run MalwareBytes since this started to happen, it causes certain issues: for example, when I start the PC again after it shuts down, after the Windows "Welcome" screen, the monitor goes white. It takes several minutes before it starts to load the desktop (and sometimes shuts down during the process). Also, thereafter it seems to shut down randomly, for example when the browser is open. I do not have to be doing anything, it just suddenly shuts down. I mention this because shortly after I posted the previous message the PC shut down. I could not get it to load the desktop in ordinary mode, so I am adding this from "Safe Mode with Networking." -- Daniel M. Burkus
  7. It is not so much trouble, and, yes, I imagined that it might be of help, too. This is happening with other scans, too, and seems to be including more of them as time goes by. Always the PC shutting down happens at the same point in the scan, and this suggests some sort of file issue. I tried to run MalwareBytes and, as usual (recently), the PC shut down. Since it is very annoying to be present when that happens, I was not in the room. Nevertheless, when I left I noticed that it was progressing through the series of scans, and so probably shut down at the same place. I came back and turned on the PC again, but I cannot find the dump file. According to my understanding (from "Startup and Recovery" --> Dump file) it should be %SystemRoot%\MEMORY.DMP. Sorry, but do you have any suggestions as to where the file might be? (Searching for both "%SystemRoot%\MEMORY.DMP" and "MEMORY.DMP" yielded no results.) -- Daniel M. Burkus
  8. Thank you. I was thinking about it, and concluded that that was what I might try -- if I did not hear back from you soon. Will do (as soon as I finish a couple of things I am working on), and will post the results in a .zip then. -- Daniel M. Burkus
  9. Thank you for your reply. I did the above as far as step 7. However, I do not understand how to run a kernel memory dump scan (and have not found anything on line other than by using third party software -- which I would prefer not to do at this time). -- Daniel M. Burkus
  10. Attached please find the "mbst-grab-results" file that was generated just now. And, thank you for your help. -- Daniel M. Burkus
  11. Attached please find the "mbst-grab-results" file that was generated just now. And, thank you for your help. -- Daniel M. Burkus mbst-grab-results.zip
  12. Hello. I was referred to MalwareBytes Forum by Broni at TechSpot Forum, who also suggested that I post the URL to the topic I created there, since it contains the logs for the various scans (the conclusion was that my PC is clean). That URL is: https://www.techspot.com/community/topics/pc-shutting-down-during-malware-scans-presumed-malware-infection-windows-7.246891/#post-1687693 I will repeat the description of the situation that prompted me to search for help, since that may give you some clues regarding my situation: This issue has been happening for a while -- even though my PC has been scanned on several occasions and found "clean" -- and it seems to be getting much worse of late. Whenever I try to run certain malware scans (originally Dr. Web, a year or so ago, and more recently MalwareBytes), the scan progresses to a certain point (in both Dr. Web and MalwareBytes this occurred near the end of the scan -- in the case of MalwareBytes, either at the end of the "scan file system," or the beginning of the "heuristics analysis" part of the scan, though since the PC shuts down without warning, I can not report precisely where) and then the PC shuts down (apparently the processor is overheating). The reason I am posting in the (TechSpot) Malware Forum is because it appears to be an issue with infected file(s), that, when the scan comes to the file in question, the file initiates a burst of activity (my guess as to what is happening, since I know no way to document precisely what is going on) that overheats the processor -- this is the best way I can explain it, from my careful observations. The shut-downs always occur at precisely the same point in the scan. Recently it has become increasingly difficult to run malware scans. Yesterday it appeared that GomPlayer had become infected or corrupted (videos were playing strangely, or crashing; and the uninstall file "Uninstall.exe" was missing, and GomPlayer not listed in the Add/Remove Programs list). The only thing I could think to do was redownload the install file, reinstall the program over top of the corrupted one, and then use the newly created "Uninstall.exe" file to remove the program from my PC. This has helped a little (I was able to keep the machine from shutting down while I scheduled the Boot Scan), but not really solved the problem. Earlier today, after removing the GomPlayer, I managed to keep Avast! open long enough to schedule a boot-time scan (and get the additional definitions downloaded and installed as well), and the scan found two issues (I can not find a way to get the results after the fact when running a boot-time scan, so perhaps they are not saved; and, knowing that from past experience, I copied these things down while the scan was running): 1) EICAR TEST-NOT VIRUS!!! (sic) [This item was moved from C:...\AppData\Local\temp to Avast!'s Virus Vault. This item, in a file named "AV-test.txt", was detected early in the scan, at the same point where some scans have failed when run after Windows had loaded.] 2) C:hiberfk.sys Win32:ISOM "Delete error 0xC0000043 {A file can not be opened because the share access flags are incompatible}." [Apparently nothing was done, since the file remained in situ in C:. This item was listed quite late in the scan, when it was around 97% complete, and this point corresponds to the failure of other scans -- notably Dr. Web and MalwareBytes.] I am running Windows 7 Ultimate (with SP1), 32-bit O/S. If other details are needed, please tell me what to list. And as for MalwareBytes, circumstances dictate that I use the free version: after Broni indicated that my PC was "clean" I uninstalled the MalwareBytes program and deleted the install file, and then redownloaded a fresh install file and went on from there, and when I tried to run the scan, the same thing happened -- PC shut down. I am going to do a system restore because, subsequent to this issue, when I turn on my PC, after signing in and the Windows "Welcome" screen, the monitor goes white, and either shuts down a minute or so later (while still showing a white screen), or begins to load the desktop and then shuts down. (Even now, writing in Safe Mode, the overheating alarms just went off, so I had better close here, and then do the system restore before it shuts down again and I loose this -- actually, the PC shut down when I tried to submit this; fortunately the text was saved and I can try to submit it again now). Thank you very much for your time, and for any help you can give. -- Daniel M. Burkus
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.