Solved BSOD when attaching files

[Garner]

BSOD occurs everytime when I try to attach files. No matter what program or file type.

Live Mail, net mail, third-party software where I try to add photo... nothing works. The most hilarious part: I tried to attach dump files and the computer info zip file to this thread but... you guessed it: BSOD.

Unfortunately, I don't have any rollbacks available. Don't know where they have disappeared.

I have run SFC scan. It couldn't repair everything but it's relatively clean now.

Computer works fine if I don't mess with attachments. The BSOD itself does not have any clue what might be wrong, just a bunch of hexes without description of the problem.

Any ideas? I guess I could copy/paste some content of the zip file here, I think it's still safe

 

[MrPepka]

How do you send files, e.g. to a cloud, BSOD also appears?

 

[Garner]

I tried WeTransfer just a moment ago. When I press "add file" I can see my folder structure for maybe one or two seconds, then the screen goes blue.


So the answer to your question is yes.


Last time this worked was March 9th. But I can't imagine any particular reason why this problem occurred.

Update: I just did memory check, no problems there. The error code I get is 0x0000001e, but no other information what might be the culprit.

 

[Snick]

I have run SFC scan. It couldn't repair everything but it's relatively clean now.

Computer works fine if I don't mess with attachments. The BSOD itself does not have any clue what might be wrong, just a bunch of hexes without description of the problem.

Any ideas? I guess I could copy/paste some content of the zip file here, I think it's still safe

You have computer problems sfc scan and BSOD say so.

SFCFix.exe is a more through tool and places a log on your desktop.
System Update Readiness Tool checks for missing cat/mum manifests, etc. I have most of them.
Would you like help finding/fixing your computer?
If so, please run the below tools and post logs please
Click Here to Download SFCFix v3.0.2.1 - Latest Version
My enhanced version of Microsoft System Update Readiness Tool
AutoSURTx64

If there are too many issues to manually correct, you can always Repair Install

 

[Garner]

As I cannot upload the whole file for obvious reasons this is what SFCfix found:


AutoAnalysis::
SFC verification failure on file NlsLexicons0019.dll of component Microsoft-Windows-NaturalLanguage6 (amd64, version 6.1.7601.17514). Permissions may be damaged - attempting automatic repair


All other lines were like this:


Successfully repaired permissions and ownership on file C:\Windows\winsxs\amd64_microsoft-windows-naturallanguage6_31bf3856ad364e35_6.1.7601.17514_none_fc00d9a9415b5f6e\NlsData0009.dll and all associated hardlinks.


SUMMARY: No corruptions were detected.
AutoAnalysis:: directive completed successfully.



Successfully processed all directives.


Failed to generate a complete zip file. Upload aborted.

SFCFix version 3.0.2.1 by niemiro has completed.
Currently storing 81 datablocks.
Finish time: 2020-03-18 07:19:11.242

 

[Garner]

Big thumbs-up to my friend who helped uploading the log-file!


Here are the results of running the AutoSURT:


WeTransfer


Hope you will find something helpful!

 

[MrPepka]

Maybe now we can send DMP files to WeTransfer? If not, read them in WinDbg and paste the screen as it looks (what is displayed in propably caused by)

 

[Garner]

Unfortunately, my friend is not available all the time. I also don't have WinDbg installed. Never used it and as I tried to install there was some error.
Maybe we just wait for Snick to check out what is already uploaded.

 

[Snick]

Garner
All you uploaded was CbsPersist_20200313225715.log which is not needed. After running AutoSURT64, a copy of the entire CBS folder should have appeared on your desktop. In its original location C:\Windows\Logs\CBS, the CheckSUR.log is temporary, that is why my program copies the folder to your desktop.
Run autosurt again please
do you still have the sfcfix.log?
Post logs please.

 

[Garner]

SFCfix report is above, post #5. It failed to generate a complete zip file so I don't know if there should be more.

CBS folder was created on my desktop but there were only three small txt-files beside what my friend uploaded.
In the original temp folder there is also CBS.txt which is much bigger file. You wanted CBS.txt?

It's 4.30 am here so I can't upload anything now unfortunately.

 

[Garner]

Here are the files you asked, thank again the courtesy of my friend:

WeTransfer

Let me know if there is still something missing. Thanks for your help!

 

[MrPepka]

1. Run Driver Verifier Manager through going to Start and typing "verifier"
2. Select "Create standard settings
3. Select "Select driver names from a list"
4. Tick all 3rd party drivers and 10 Microsoft drivers (ntoskrnl.exe, tcpip.sys, ndis.sys, afd.sys, ksecdd.sys, mrxsmb.sys, rdbss.sys, msrpc.sys, fvevol.sys and partmgr.sys)
5. Accept changes and reboot computer

 

[Snick]

Garner
read logs sfc was language pack permissions fixed as you indicated

 

[Garner]

Maybe it should include but it does not. Everything there was in that folder was uploaded except three tiny txt-files.
Is there any useful information in SFCfix.log you requested?

 

[Garner]

MrPepka, I ran the verifier. I don't see any other difference than my desktop running much slower now.

 

[MrPepka]

It's normal. Do you still have blue screens when sending files? If so, try to send some memory dumps

 

[Snick]

It's normal. Do you still have blue screens when sending files? If so, try to send some memory dumps

Agree!

 

[Snick]

MrPepka

dumps

View attachment 411405

 

[Garner]

It's normal. Do you still have blue screens when sending files? If so, try to send some memory dumps

Still not working. Tested with Live Mail.

 

[MrPepka]

Blue screens are still with the same bugcheck, and when you read DMP files in WinDbg is the problem still the same?