WSL: Running NPM causes non-deterministic BSOD
- VSCode Version: 1.38.1 (user setup)
- Local OS Version: Windows 10 Pro 18362.356
- Remote OS Version: Ubuntu 18.04.3 LTS
- Remote Extension/Connection Type: WSL
Steps to Reproduce:
- Restart computer
- Clear cache/node_modules
Does this issue occur when you try this locally?: No
npm install --save core-js@3
I’m running this command in integrated terminal of vscode which is connected to wsl and get BSoD with this error

About this issue
- Original URL
- State: closed
- Created 7 years ago
- Reactions: 5
- Comments: 21 (1 by maintainers)
I figured out a workaround for the time being for VS Code in
settings.json"remote.WSL.fileWatcher.polling": truehttps://code.visualstudio.com/docs/remote/wsl#_i-see-eaccess-permission-denied-error-trying-to-rename-a-folder-in-the-open-workspace
Microsoft in the link above explains why VS Code has such trouble in WSL with renaming folders. Which isn’t a direct answer for this issue, but after using polling I haven’t had a single issue yet.
Downside is that depending on the polling interval you may have to reopen files to see updates, package.json for example, and they point out could slow down larger projects considerably. They go on to say there not going to fix it in WSL 1 and that its fixed in WSL 2.
WSL 2 is actually slower than WSL 1 if you need to access files and folders outside of virtual drive it creates. (Which I do) So its kinda a mixed bag depending on your situation.
Hope this helps people coming to this issue.
I’m getting the same issue as OP with coincidentally the exact same setup down to the version # and it’s only BSOD when using integrated terminal. Sometimes I’ll also get a BSOD with
KERNEL_SYSTEM_CHECK_FAILURE, again on the integrated terminalUsing WSL in external terminal I don’t have any permission or BSOD issues. *Unless I’ve tried to run something like
npm i webpackin the integrated terminal and when that throws a permission error. I’ll try to do it from external and that is where I got theKERNEL_SYSTEM_CHECK_FAILUREAfter this I guess I’m not going to be using the integrated terminal again in VSCode. I’ve run into so many issues, both with Bash in WSL and Powershell.
Well, it seems that a month passed and I am still having the exact same issue here.
I am running WSL1 on
WIndows 10.0.19041.1, and BSOD (KERNEL_SECURITY_CHECK_FAILURE (139)) when I executenpm test. From Windbg it tells meLXCORE!LxpInotifyAddWatchis where the Exception is.Any suggestions but sent minidump to
secure@microsoft.com?