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.

[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!

[AdamBraden]

The WSL team is working through issues with WSL & DevDrive. See - https://github.com/microsoft/WSL/issues?q=is%3Aissue+is%3Aopen+%22dev+drive%22

@craigloewen-msft - can you confirm if this is a known issue, or transfer to the WSL repo?

[craigloewen-msft]

@Patrick-Herzog are you using the Windows Subsystem for Linux for this? Or is this running using the Windows version of Python?

[Patrick-Herzog]

@craigloewen-msft I don't use the WSL for this. It runs under Windows, more precisely in a virtual environment of a project in dev drive. The blue screen is also only generated by Python in the virtual environment. I haven't tested it in the WSL.

@adrastogi I had created a feedback in the feedback hub. Unfortunately, your colleague rejected the feedback due to a lack of diagnostic data. I opened a new feedback

[AdamBraden]

@Patrick-Herzog - Thanks for the information. The WSL question was because in the repro steps above you mentioned BASH.

Will need to take a look at the fbhub issue. Can you share the link to the issue?

[adrastogi]

@AdamBraden found the issue on the backend here (I'll figure out how to get it converted to an internal bug): https://aka.ms/AAr02ll

[adrastogi]

@Patrick-Herzog just to clarify, the device you filed the feedback from is the same device that is encountering the bluescreen?

[Patrick-Herzog]

@adrastogi yes, and my first feedback (https://aka.ms/AAqqwy2) has a dmp file as an attachment, created by Windows at Crash.

[craigmccauley]

Hi @Patrick-Herzog, unfortunately the attachment and the diagnostics on the Feedback didn't make it through. Are you able to create another Feedback? Preferably with Settings (Windows Key + I) -> Privacy & Security -> Diagnostics & Feedback -> Send optional diagnostics data switched on and logged into Feedback Hub.

[Patrick-Herzog]

Hi, I tried uploading it again via the Feedback Hub. I hope that all the necessary data has been collected, but I am not sure whether the steps here worked, as I was no longer able to see the data after the crash.

I was able to find out some other information from the memory dump:

Loading Dump File [C:\Users\patri\OneDrive\Documents\MEMORY.DMP]
Kernel Bitmap Dump File: Kernel address space is available, User address space may not be available.

Primary dump contents written successfully

************* Path validation summary **************
Response Time (ms) Location
Deferred srv*
Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 22621 MP (20 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Edition build lab: 22621.1.amd64fre.ni_release.220506-1250
Kernel base = 0xfffff80710a00000 PsLoadedModuleList = 0xfffff80711613530
Debug session time: Tue Jul 9 19:05:27.099 2024 (UTC + 2:00)
System Uptime: 0 days 0:05:41.891
Loading Kernel Symbols
...............................................................
................................................................
................................................................
...........................................
Loading User Symbols
PEB is paged out (Peb.Ldr = 0000000000802018). Type ".hh dbgerr001" for details Loading unloaded module list ............. For analysis of this file, run !analyze -v nt!KeBugCheckEx: fffff80710e15ea0 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffff9083`08b008a0=0000000000000001
2: kd> !analyze -v

---

•                                                                         *
  

•                    Bugcheck Analysis                                    *
  

•                                                                         *
  

---

APC_INDEX_MISMATCH (1)
This is a kernel internal error. The most common reason to see this
BugCheck is when a filesystem or a driver has a mismatched number of
calls to disable and re-enable APCs. The key data item is the
Thread->CombinedApcDisable field. This consists of two separate 16-bit
fields, the SpecialApcDisable and the KernelApcDisable. A negative value
of either indicates that a driver has disabled special or normal APCs
(respectively) without re-enabling them; a positive value indicates that
a driver has enabled special or normal APCs (respectively) too many times.
Arguments:
Arg1: 00007ffdc0df01e4, Address of system call function or worker routine
Arg2: 0000000000000000, Thread->ApcStateIndex
Arg3: 000000000000fffe, (Thread->SpecialApcDisable << 16) | Thread->KernelApcDisable
Arg4: ffff908308b00a60, Call type (0 - system call, 1 - worker routine)

Debugging Details:

KEY_VALUES_STRING: 1

Key  : Analysis.CPU.mSec
Value: 3187

Key  : Analysis.Elapsed.mSec
Value: 3482

Key  : Analysis.IO.Other.Mb
Value: 0

Key  : Analysis.IO.Read.Mb
Value: 0

Key  : Analysis.IO.Write.Mb
Value: 0

Key  : Analysis.Init.CPU.mSec
Value: 312

Key  : Analysis.Init.Elapsed.mSec
Value: 4750

Key  : Analysis.Memory.CommitPeak.Mb
Value: 92

Key  : Bugcheck.Code.KiBugCheckData
Value: 0x1

Key  : Bugcheck.Code.LegacyAPI
Value: 0x1

Key  : Bugcheck.Code.TargetModel
Value: 0x1

Key  : Dump.Attributes.AsUlong
Value: 1000

Key  : Dump.Attributes.DiagDataWrittenToHeader
Value: 1

Key  : Dump.Attributes.ErrorCode
Value: 0

Key  : Dump.Attributes.LastLine
Value: Dump completed successfully.

Key  : Dump.Attributes.ProgressPercentage
Value: 100

Key  : Failure.Bucket
Value: 0x1_SysCallNum_12_nt!KiSystemServiceExitPico

Key  : Failure.Hash
Value: {1122a8f7-e1f7-da41-6eae-e5addcfc5641}

Key  : Hypervisor.Enlightenments.Value
Value: 0

Key  : Hypervisor.Enlightenments.ValueHex
Value: 0

Key  : Hypervisor.Flags.AnyHypervisorPresent
Value: 0

Key  : Hypervisor.Flags.ApicEnlightened
Value: 0

Key  : Hypervisor.Flags.ApicVirtualizationAvailable
Value: 1

Key  : Hypervisor.Flags.AsyncMemoryHint
Value: 0

Key  : Hypervisor.Flags.CoreSchedulerRequested
Value: 0

Key  : Hypervisor.Flags.CpuManager
Value: 0

Key  : Hypervisor.Flags.DeprecateAutoEoi
Value: 0

Key  : Hypervisor.Flags.DynamicCpuDisabled
Value: 0

Key  : Hypervisor.Flags.Epf
Value: 0

Key  : Hypervisor.Flags.ExtendedProcessorMasks
Value: 0

Key  : Hypervisor.Flags.HardwareMbecAvailable
Value: 1

Key  : Hypervisor.Flags.MaxBankNumber
Value: 0

Key  : Hypervisor.Flags.MemoryZeroingControl
Value: 0

Key  : Hypervisor.Flags.NoExtendedRangeFlush
Value: 0

Key  : Hypervisor.Flags.NoNonArchCoreSharing
Value: 0

Key  : Hypervisor.Flags.Phase0InitDone
Value: 0

Key  : Hypervisor.Flags.PowerSchedulerQos
Value: 0

Key  : Hypervisor.Flags.RootScheduler
Value: 0

Key  : Hypervisor.Flags.SynicAvailable
Value: 0

Key  : Hypervisor.Flags.UseQpcBias
Value: 0

Key  : Hypervisor.Flags.Value
Value: 16908288

Key  : Hypervisor.Flags.ValueHex
Value: 1020000

Key  : Hypervisor.Flags.VpAssistPage
Value: 0

Key  : Hypervisor.Flags.VsmAvailable
Value: 0

Key  : Hypervisor.RootFlags.AccessStats
Value: 0

Key  : Hypervisor.RootFlags.CrashdumpEnlightened
Value: 0

Key  : Hypervisor.RootFlags.CreateVirtualProcessor
Value: 0

Key  : Hypervisor.RootFlags.DisableHyperthreading
Value: 0

Key  : Hypervisor.RootFlags.HostTimelineSync
Value: 0

Key  : Hypervisor.RootFlags.HypervisorDebuggingEnabled
Value: 0

Key  : Hypervisor.RootFlags.IsHyperV
Value: 0

Key  : Hypervisor.RootFlags.LivedumpEnlightened
Value: 0

Key  : Hypervisor.RootFlags.MapDeviceInterrupt
Value: 0

Key  : Hypervisor.RootFlags.MceEnlightened
Value: 0

Key  : Hypervisor.RootFlags.Nested
Value: 0

Key  : Hypervisor.RootFlags.StartLogicalProcessor
Value: 0

Key  : Hypervisor.RootFlags.Value
Value: 0

Key  : Hypervisor.RootFlags.ValueHex
Value: 0

Key  : SecureKernel.HalpHvciEnabled
Value: 0

Key  : WER.OS.Branch
Value: ni_release

Key  : WER.OS.Version
Value: 10.0.22621.1

BUGCHECK_CODE: 1

BUGCHECK_P1: 7ffdc0df01e4

BUGCHECK_P2: 0

BUGCHECK_P3: fffe

BUGCHECK_P4: ffff908308b00a60

FILE_IN_CAB: MEMORY.DMP

DUMP_FILE_ATTRIBUTES: 0x1000

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXPNP: 1 (!blackboxpnp)

BLACKBOXWINLOGON: 1

PROCESS_NAME: pip.exe

STACK_TEXT:
ffff908308b00898 fffff80710e2be29 : 0000000000000001 00007ffdc0df01e4 0000000000000000 000000000000fffe : nt!KeBugCheckEx
ffff908308b008a0 fffff80710e2bce9 : ffffbb0e1ddc0000 0000000000000000 000000000000003f ffffbb0e00000000 : nt!KiBugCheckDispatch+0x69
ffff908308b009e0 00007ffdc0df01e4 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiSystemServiceExitPico+0x3ad
0000000000afeaa8 0000000000000000 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : 0x00007ffd`c0df01e4

SYMBOL_NAME: nt!KiSystemServiceExitPico+3ad

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

STACK_COMMAND: .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET: 3ad

FAILURE_BUCKET_ID: 0x1_SysCallNum_12_nt!KiSystemServiceExitPico

OS_VERSION: 10.0.22621.1

BUILDLAB_STR: ni_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {1122a8f7-e1f7-da41-6eae-e5addcfc5641}

Followup: MachineOwner