Windows 10: BSOD seems to happen when attaching and removing external devices

Dear Sir/Madame,
I have been having an intermittent problem with my Acer Aspire 5251-1805 running Windows 10 and it was not a problem previously. I noticed that when I was attaching an external drive or wi-fi booster on my computer it will crash and restart. I get a message saying it is collecting data and will restart -- it does restart without any problems but it is frustrating because I will sometimes lose data within a program especially the voice recorder. I now have many voice recorder files that are unreadable because of the BSOD but the apps themselves are crashing too.

Many times I will find that the computer has crashed and restarted because of an app that has restarted and needs me to take some type of action that occurs only at startup. Because some apps do not restart they will no longer be running so I cannot say for certain if the app is crashing or it is the BSOD that has caused the app to no longer be running. I am attaching the zip file per the instructions and I will await a response to my problem.

:)

 

unrecognized device when removing and re-attaching sync cable without rebootingcomupter

No. If I shut off active sync, I still get the same problem.

 

unrecognized device when removing and re-attaching sync cable without rebootingcomupter

Verify that Activesync is not running in the background before reconnecting your device. Run the Memory applet in Start - Settings - System.

 

The .zip file you attached is empty. Please re-run the log collector.

 

Spectrum,
I ran it again but I see it is the same size as the other file so probably the same result of an empty file. If I cannot get the collector to provide you with the information you need is there another option?

 

Do any errors occur when you attempt to run it? Have you tried running it as an administrator?

If the collector isn't working for you, the basics will be getting the minidumps and a system information report.

1. Create a folder on your desktop, ideally titled using your computer's name and the date
2. The minidumps should be in C:\Windows\MiniDump, copy the files over to the newly created folder
3. You can generate a system information report by launching an elevated PowerShell prompt and entering:
Code: msinfo32 /nfo "$home\Desktop\info.nfo"[/quote] This will place info.nfo on your desktop, move it to your folder
4. Compress the folder to a .zip and upload it here

 

There is an error-- "The system cannot find the file specified. 0 files copied." Apparently, it cannot find the "C:\windowa\minidump\*dmp". This is the message I got even after running it as Administrator.

 

I just went to that folder and it is empty.

 

The minidump folder says it was modified on 12/19/16. I did not modify it or delete any files from it so clearly there is something that caused it to be deleted.

 

Follow this guide to make sure you have crashdumps enabled.

https://www.tenforums.com/tutorials/...dows-10-a.html

 

I just enabled small memory dumps -- it was set to kernel memory dumps so I guess that is the default since I had not changed that previously.

 

The Kernel memory dump setting should still produce a minidump alongside a MEMORY.dmp file. Do you see a MEMORY.dmp file in "C:\Windows"? If so, feel free to use dropbox or some other service to share the file with us.

Regardless, let's hope minidumps will be generated if your system crashes again.

 

There is no .dmp folder or file in C:\Windows but there is a dmp folder and it too is empty. In looking at the minidump folder it says it was created on 10/3/16 at 8:29pm and was modified as I stated on 12/19/16 at 11:33am -- however it is empty.

I will await another crash to see if I can get some data....

 

I do not know if this is important but the Windows voice recorder app that I have been using for nearly a year now was not in the system apps. I went to the Ask me anything to search for it and I received a message that it needed to be repaired so the system downloaded it for reinstall. It has downloaded and I am running it now -- I will let you know if there are any additional problems associated with it.

 

Try running the following commands from an elevated PowerShell or CMD prompt:

sfc /scannow
dism /Online /Cleanup-image /Scanhealth
dism /Online /Cleanup-image /RestoreHealth
sfc /scannow

After they are finished, note any messages about corruption being detected and then reboot.