blue screen after pip install in venv on the devdrive

[Patrick-Herzog]

Dev Home version

0.1301.477.0

Windows build number

10.0.22631.3593

Other software

OS Build Version: 10.0.22631.3593.amd64fre.ni_release.220506-1250
.NET Version: .NET 8.0.4

Steps to reproduce the bug

1. create pythonprojekt, 2. create venv, 3. activate venv, 4. in venv on terminal install command "pip install keras" or same problem with "pip install --upgrade pip"

Expected result

Installation of the python package

Actual result

bluescreen, (BugCheck, Ereignis-ID 1001)
Der Computer wurde nach einem schwerwiegenden Fehler neu gestartet. Der Fehlercode war: 0x00000001 (0x00007ffd224cfb94, 0x0000000000000000, 0x000000000000fffe, 0xffffea8a2f949a60). Ein volles Abbild wurde gespeichert in: C:\WINDOWS\Minidump\051724-11406-01.dmp. Berichts-ID: de5d5162-afcc-4bb6-ab7d-a74c9b6a51b4.

on a normal drive there was no problem with te further steps

Included System Information

CPU: Intel(R) Core(TM) i9-10900F CPU @ 2.80GHz
Physischer Speicher: 31.8GB (16.42GB free)
Prozessorarchitektur: x64

Included Extensions Information

Erweiterungen:
Microsoft.Windows.DevHome_0.1301.477.0_x64__8wekyb3d8bbwe (Dev Home (Vorschau))
Microsoft.Windows.DevHome_0.1301.477.0_x64__8wekyb3d8bbwe (Dev Home (Vorschau))
Microsoft.Windows.DevHomeGitHubExtension_0.1300.477.0_x64__8wekyb3d8bbwe (Dev Home-GitHub-Erweiterung (Vorschau))

Widgetdienst:
MicrosoftWindows.Client.WebExperience_424.1301.450.0_x64__cw5n1h2txyewy

[krschau]

Bing Translate:

Steps to reproduce the bug

1. create pythonprojekt,
2. create venv,
3. activate venv,
4. in venv on terminal install command "pip install keras" or same problem with "pip install --upgrade pip"

Expected result
Installation of the python package

Actual result
bluescreen, (BugCheck, Event ID 1001)
The computer has restarted after a fatal error. The error code was: 0x00000001 (0x00007ffd224cfb94, 0x0000000000000000, 0x000000000000fffe, 0xffffea8a2f949a60). A full image has been saved in: C:WINDOWSMinidump051724-11406-01.dmp. Report ID: de5d5162-afcc-4bb6-ab7d-a74c9b6a51b4.

on a normal drive there was no problem with te further steps

[krschau]

Hi @Patrick-Herzog, can you explain more about what you did here? It doesn't seem like steps a user would take inside Dev Home, but I might just be getting a bad translation.
/needinfo

[Patrick-Herzog]

Hello,

The issue did not occur within Dev Home itself but within the Dev Drive that was created by Dev Home. Here are the exact steps and details:

• Created Dev Drive: I created a Dev Drive via Dev Home to use it for development.
• Cloned Repository: I cloned a Git repository onto the Dev Drive.
• Created Virtual Environment: Within the cloned repository, I created a Python virtual environment in pycharm:

bash:
python -m venv venv
venv\Scripts\activate (on Windows)

• Upgraded pip: I tried to upgrade pip within the virtual environment:

bash:
pip install --upgrade pip

This caused a bluescreen.

• Installed Keras: I tried to install Keras:

bash:
pip install keras

This also caused a bluescreen.

The problem seems specific to the Dev Drive, as the installation works fine on normal drives that are not virtually created by Dev Home. Here are the additional steps I took to troubleshoot the issue:

• Checked System Resources: There is sufficient memory and disk space available.
• Updated Drivers and Windows: All drivers and Windows updates are up to date.
• Checked System Files: Ran sfc /scannow, no issues found.
• Created New Virtual Environments: Tried creating new virtual environments both on the Dev Drive and on other drives multiple times.
• Conducted Memory Diagnostic: Used mdsched.exe, no issues found.
• Checked Event Viewer: Searched the system logs for relevant error messages.
  In the Event Viewer, I found the following information:

Event Type: Bluescreen (BugCheck, Event ID 1001)
Description: The computer has restarted after a fatal error. The error code was: 0x00000001 (0x00007ffd224cfb94, 0x0000000000000000, 0x000000000000fffe, 0xffffea8a2f949a60). A full image has been saved in: C:\WINDOWS\Minidump\051724-11406-01.dmp. Report ID: de5d5162-afcc-4bb6-ab7d-a74c9b6a51b4.

It is possible that this usage does not align with typical scenarios. This was my first time trying out Dev Home, and it led to a bluescreen in this configuration.

If it helps you, I could try to reproduce the error again and send you the .dmp file from windows.

Best regards,
Patrick Herzog

[krschau]

Thank you, @Patrick-Herzog, for all this information! Could you please open an issue in Feedback Hub with the information you have included here? Since this problem is more related to Dev Drive than Dev Home specifically, over there we can get more eyes on it, as well as possibly getting additional telemetry if your device is configured to send it. If you wanted to create that .dmp file, that would be the place to include it. We'll keep this issue open while we investigate further.
/feedbackhub

FYI @AdamBraden and @ChandKV, in case you guys have thoughts.

[microsoft-github-policy-service]

Hi @Patrick-Herzog. Please file this issue on Feedback Hub [Windows]+[f] and paste the link here so we can more easily find your information on the back end. The link can be found at the bottom of the feedback report. Please use "Apps" and "Dev Home" for the Category.

[adrastogi]

@Patrick-Herzog would you be able to open a Feedback Hub item for this issue? See the comment here for the steps on that. Thank you!