# Julia 1.8.\* & VSCode & Ryzen CPU & Windows 10 64bit --\> crash

**URL:** <https://discourse.julialang.org/t/julia-1-8-vscode-ryzen-cpu-windows-10-64bit-crash/87283>\
**Category:** General Usage\
**Tags:** question, vscode, crash\
**Created:** [September 14, 2022, 6:22pm UTC](https://discourse.julialang.org/t/julia-1-8-vscode-ryzen-cpu-windows-10-64bit-crash/87283 "2022-09-14T18:22:45Z")\
**Posts on this page:** 1\
**Showing post:** 6

<div class="post-metadata">

**Author:** ![mkoculak](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/mkoculak/32/28310_2.png) [@mkoculak](https://discourse.julialang.org/u/mkoculak)\
**Post date:** [October 2, 2022, 6:59pm UTC](https://discourse.julialang.org/t/julia-1-8-vscode-ryzen-cpu-windows-10-64bit-crash/87283/6 "2022-10-02T18:59:12Z")

</div>

Great to hear that things started to work.

Yeah, there were actually no changes addressing the precompilation threads in Julia, but some developers think what actually caused trouble is the number of spawned openblas threads (you can find their comments and links to commits in the thread below).

> [@Julia 1.8.1 pkg.update() crashes OS / software during precompilation phase](https://discourse.julialang.org/t/julia-1-8-1-pkg-update-crashes-os-software-during-precompilation-phase/87979/15):
>
> Julia defaults to more BLAS threads if you have more cores, so given AMD has more cores than most it seems sensible AMD users had most problems, but otherwise memory use is strictly unrelated to CPUs at least their frequency etc.

Julia 1.8.2 also seemed to fix the issue for me. I experimented with higher number of precompile tasks and things look stable. You might want to give it also a go, since it speeds up the installation substantially.

---

_[View the full topic](https://discourse.julialang.org/t/julia-1-8-vscode-ryzen-cpu-windows-10-64bit-crash/87283)._