The DM log collector .exe does not download from your link in zip form (nothing to extract), and I definitely saw the whole thing complete in command prompt. I'll run it again and copy-paste what I'm seeing.
There are 2 log collectors, DM and beta.
The DM log collector you were using earlier in the thread.
The method of use for the DM log collector has not been changed.
Are you now having problems with the DM log collector?
A link with text and images was posted for the beta log collector.
This was followed with additional text and images in the thread.
See if you can run and post the beta log collector so that it collects the files.
Didn't see it this time; last time it paused to ask about a couple overwrites. The file is larger, so maybe?
The link that was posted was the DM log collector.
See if you are able to follow the text and images in this link to run the beta log collector so that it collects log files:
Post #5:
DM Log tool problem Solved - Windows 10 Forums
Also see the added text and images in post #110
log collector v2-beta08.zip
(extract > open)
My computer is now telling me I need administrative privileges to extract the files, and no window appears to give permission, so all that happens is a couple empty folders are created. Huh?
For the users on the computer are you able to sign on as the administrator?
If so do you have the same problem clicking on extract?
Were you able to match the images to what you are doing on the computer?
If possible using the snipping tool and post images of the before and after as you follow the steps in the the text and images.
I am the only user on the computer, and I've never had a problem extracting files before.
Please close this thread and open a new thread in the applicable forum to address any remaining issues.
The issue that you are having is puzzling.
Consider opening a new thread in the General forum: problem extracting files: especially beta log collector
I'm back. For some reason I didn't see your last post, but I'm assuming the issues I'm now dealing with are related. If you still think I should start a new thread, I will.
My laptop was usable, and I managed to get rid of those pesky update attempts by setting my home connection to "metered" and then disabling the relevant triggers. No problems since. But yesterday, right in the middle of the day, I found myself unable to connect to particular websites; Google, Facebook, and most other usual websites worked fine, but .edu websites and Wikipedia, among others, were all inaccessible. I tried a bunch of things, ran a virus scan, and eventually restarted the laptop, and everything seemed back to normal.
Then today I had a sudden restart (bug check 0x00000124). When I got back in, I could connect to my network, but I could not access any websites (others in my household still can). I ran the troubleshooter several times; a few times it claimed to have fixed the issue (something to do with DNS), but I still had no access. I restarted the router, restarted the computer again, refreshed the IP, but nothing is working. One of the weird things is that I get a split-second of connection when I reconnect to the internet; pages will start to load, but then nothing. I did yesterday ensure my network drivers were up-to-date; but what else could be causing this?
...Just now, the internet connection came back for about three seconds, and then was gone again.... I'm very confused.
Whenever there is a BSOD please post a new BETA log collector zip:
https://www.tenforums.com/attachment...-v2-beta10.zip
(extract > open)
The bugcheck 0x124 is typically a hardware malfunctioning problem.
Sometimes though hardware and software drivers can produce this bugcheck.
The dump files and logs will need to be reviewed.
Multiple dump files are needed for debugging so whenever there is a dump run the BETA log collector and post a new zip.
For the first few dumps also look for the memory dump:
file explorer > this PC > C: > in the right upper corner search for: C:\Windows\memory.dmp
Then zip it > upload to one drive or drop box > post a share link into the thread.
Quote
