Share via

Train a model in wsl caused blue screen, it seems like hyper-v caused it.

boris zhu 0 Reputation points
2023-08-07T04:52:53.14+00:00

I trained a model in wsl, it takes a long time to train. But it unfortunately caused blue screen. I ran !analyze -v to get debug info.

It seems like hyper-v caused it. I already have removed hyper-v.

Here are some dump files: KMODE_EXCEPTION_NOT_HANDLED KERNEL_SECURITY_CHECK_FAILURE MEMORY_MANAGEMENT PFN_LIST_CORRUPT

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

KERNEL_SECURITY_CHECK_FAILURE (139)
A kernel component has corrupted a critical data structure.  The corruption
could potentially allow a malicious user to gain control of this machine.
Arguments:
Arg1: 0000000000000002, Stack cookie instrumentation code detected a stack-based
	buffer overrun.
Arg2: fffffd08fd69e2f0, Address of the trap frame for the exception that caused the BugCheck
Arg3: fffffd08fd69e248, Address of the exception record for the exception that caused the BugCheck
Arg4: 0000000000000000, Reserved

Debugging Details:
------------------


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 2734

    Key  : Analysis.Elapsed.mSec
    Value: 9396

    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: 374

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

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

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0x139

    Key  : FailFast.Name
    Value: STACK_COOKIE_CHECK_FAILURE

    Key  : FailFast.Type
    Value: 2

    Key  : Failure.Bucket
    Value: 0x139_MISSING_GSFRAME_nt!KiFastFailDispatch

    Key  : Failure.Hash
    Value: {1971a9b0-b7ec-89bf-0a51-10ac52818da5}

    Key  : Hypervisor.Enlightenments.Value
    Value: 77057948

    Key  : Hypervisor.Enlightenments.ValueHex
    Value: 497cf9c

    Key  : Hypervisor.Flags.AnyHypervisorPresent
    Value: 1

    Key  : Hypervisor.Flags.ApicEnlightened
    Value: 1

    Key  : Hypervisor.Flags.ApicVirtualizationAvailable
    Value: 0

    Key  : Hypervisor.Flags.AsyncMemoryHint
    Value: 0

    Key  : Hypervisor.Flags.CoreSchedulerRequested
    Value: 0

    Key  : Hypervisor.Flags.CpuManager
    Value: 1

    Key  : Hypervisor.Flags.DeprecateAutoEoi
    Value: 0

    Key  : Hypervisor.Flags.DynamicCpuDisabled
    Value: 1

    Key  : Hypervisor.Flags.Epf
    Value: 0

    Key  : Hypervisor.Flags.ExtendedProcessorMasks
    Value: 1

    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: 1

    Key  : Hypervisor.Flags.Phase0InitDone
    Value: 1

    Key  : Hypervisor.Flags.PowerSchedulerQos
    Value: 0

    Key  : Hypervisor.Flags.RootScheduler
    Value: 0

    Key  : Hypervisor.Flags.SynicAvailable
    Value: 1

    Key  : Hypervisor.Flags.UseQpcBias
    Value: 0

    Key  : Hypervisor.Flags.Value
    Value: 4853999

    Key  : Hypervisor.Flags.ValueHex
    Value: 4a10ef

    Key  : Hypervisor.Flags.VpAssistPage
    Value: 1

    Key  : Hypervisor.Flags.VsmAvailable
    Value: 1

    Key  : Hypervisor.RootFlags.AccessStats
    Value: 1

    Key  : Hypervisor.RootFlags.CrashdumpEnlightened
    Value: 1

    Key  : Hypervisor.RootFlags.CreateVirtualProcessor
    Value: 1

    Key  : Hypervisor.RootFlags.DisableHyperthreading
    Value: 0

    Key  : Hypervisor.RootFlags.HostTimelineSync
    Value: 1

    Key  : Hypervisor.RootFlags.HypervisorDebuggingEnabled
    Value: 0

    Key  : Hypervisor.RootFlags.IsHyperV
    Value: 1

    Key  : Hypervisor.RootFlags.LivedumpEnlightened
    Value: 1

    Key  : Hypervisor.RootFlags.MapDeviceInterrupt
    Value: 1

    Key  : Hypervisor.RootFlags.MceEnlightened
    Value: 1

    Key  : Hypervisor.RootFlags.Nested
    Value: 0

    Key  : Hypervisor.RootFlags.StartLogicalProcessor
    Value: 1

    Key  : Hypervisor.RootFlags.Value
    Value: 1015

    Key  : Hypervisor.RootFlags.ValueHex
    Value: 3f7

    Key  : WER.OS.Branch
    Value: vb_release

    Key  : WER.OS.Version
    Value: 10.0.19041.1


BUGCHECK_CODE:  139

BUGCHECK_P1: 2

BUGCHECK_P2: fffffd08fd69e2f0

BUGCHECK_P3: fffffd08fd69e248

BUGCHECK_P4: 0

FILE_IN_CAB:  073023-16812-01.dmp

TRAP_FRAME:  ffff800000000000 -- (.trap 0xffff800000000000)
Unable to read trap frame at ffff8000`00000000

EXCEPTION_RECORD:  fffffd08fd69e248 -- (.exr 0xfffffd08fd69e248)
ExceptionAddress: fffff80005af2e75 (Ntfs!_report_gsfailure+0x0000000000000005)
   ExceptionCode: c0000409 (Security check failure or stack buffer overrun)
  ExceptionFlags: 00000001
NumberParameters: 1
   Parameter[0]: 0000000000000002
Subcode: 0x2 FAST_FAIL_STACK_COOKIE_CHECK_FAILURE 

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  svchost.exe

ERROR_CODE: (NTSTATUS) 0xc0000409 - The system detected an overrun of a stack-based buffer in this application. This overrun could potentially allow a malicious user to gain control of this application.

EXCEPTION_CODE_STR:  c0000409

EXCEPTION_PARAMETER1:  0000000000000002

EXCEPTION_STR:  0xc0000409

STACK_TEXT:  
fffffd08`fd69dfc8 fffff800`09e10129     : 00000000`00000139 00000000`00000002 fffffd08`fd69e2f0 fffffd08`fd69e248 : nt!KeBugCheckEx
fffffd08`fd69dfd0 fffff800`09e10690     : ffff9c04`50ce06b0 00000000`00000784 ffffac8f`c6684030 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffffd08`fd69e110 fffff800`09e0e65d     : ffffbf08`470d54b0 fffffd08`00000000 ffffbf08`55bec040 00000000`00000000 : nt!KiFastFailDispatch+0xd0
fffffd08`fd69e2f0 fffff800`05af2e75     : fffff800`05af3f96 fffffd08`fd69ea60 fffff800`09ce5d4f fffff800`05b7cf1c : nt!KiRaiseSecurityCheckFailure+0x31d
fffffd08`fd69e488 fffff800`05af3f96     : fffffd08`fd69ea60 fffff800`09ce5d4f fffff800`05b7cf1c fffffd08`00000000 : Ntfs!_report_gsfailure+0x5
fffffd08`fd69e490 fffff800`05af3fe6     : fffffd08`fd69e560 00000000`00000000 fffffd08`fd69ea98 fffffd08`fd69ea70 : Ntfs!_GSHandlerCheckCommon+0x5a
fffffd08`fd69e4c0 fffff800`09e067b2     : fffff800`05b7cf1c fffffd08`fd69ea60 fffff800`05af3fa4 fffff800`05cd25b7 : Ntfs!_GSHandlerCheck_SEH+0x42
fffffd08`fd69e4f0 fffff800`09ce5b37     : fffffd08`fd69ea60 00000000`00000000 fffffd08`fd69ec70 fffff800`05cd25b7 : nt!RtlpExecuteHandlerForException+0x12
fffffd08`fd69e520 fffff800`09ce7b06     : fffffd08`fd69f438 fffffd08`fd69f170 fffffd08`fd69f438 00000000`00000000 : nt!RtlDispatchException+0x297
fffffd08`fd69ec40 fffff800`09e1026c     : 00000000`00001000 fffffd08`fd69f4e0 ffff8000`00000000 00000000`00000000 : nt!KiDispatchException+0x186
fffffd08`fd69f300 fffff800`09e0bcbd     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiExceptionDispatch+0x12c
fffffd08`fd69f4e0 fffff800`05cd25b7     : fffff800`0a0cf352 ffffac8f`9e4fc9d0 ffffac8f`9e4fc9d0 ffffac8f`9e4fc9d0 : nt!KiPageFault+0x43d
fffffd08`fd69f678 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 ffffe422`8fe4ff20 : Ntfs!NtfsChangeVolumeSize+0x269f


SYMBOL_NAME:  nt!KiFastFailDispatch+d0

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

IMAGE_VERSION:  10.0.19041.3208

STACK_COMMAND:  .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET:  d0

FAILURE_BUCKET_ID:  0x139_MISSING_GSFRAME_nt!KiFastFailDispatch

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {1971a9b0-b7ec-89bf-0a51-10ac52818da5}

Followup:     MachineOwner
---------

Here was another one. 


*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

KMODE_EXCEPTION_NOT_HANDLED (1e)
This is a very common BugCheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff80120c7242f, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: 0000000000001000, Parameter 1 of the exception

Debugging Details:
------------------

*************************************************************************
***                                                                   ***
***                                                                   ***
***    Either you specified an unqualified symbol, or your debugger   ***
***    doesn't have full symbol information.  Unqualified symbol      ***
***    resolution is turned off by default. Please either specify a   ***
***    fully qualified symbol module!symbolname, or enable resolution ***
***    of unqualified symbols by typing ".symopt- 100". Note that     ***
***    enabling unqualified symbol resolution with network symbol     ***
***    server shares in the symbol path may cause the debugger to     ***
***    appear to hang for long periods of time when an incorrect      ***
***    symbol name is typed or the network symbol server is down.     ***
***                                                                   ***
***    For some commands to work properly, your symbol path           ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: ExceptionRecord                               ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Either you specified an unqualified symbol, or your debugger   ***
***    doesn't have full symbol information.  Unqualified symbol      ***
***    resolution is turned off by default. Please either specify a   ***
***    fully qualified symbol module!symbolname, or enable resolution ***
***    of unqualified symbols by typing ".symopt- 100". Note that     ***
***    enabling unqualified symbol resolution with network symbol     ***
***    server shares in the symbol path may cause the debugger to     ***
***    appear to hang for long periods of time when an incorrect      ***
***    symbol name is typed or the network symbol server is down.     ***
***                                                                   ***
***    For some commands to work properly, your symbol path           ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: ContextRecord                                 ***
***                                                                   ***
*************************************************************************
*** WARNING: Check Image - Checksum mismatch - Dump: 0x18561b, File: 0x1857e3 - C:\ProgramData\Dbg\sym\BTHport.sys\70388B82185000\BTHport.sys

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 2671

    Key  : Analysis.Elapsed.mSec
    Value: 16473

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

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

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

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

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

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

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0x1e

    Key  : Failure.Bucket
    Value: AV_R_nt!RtlCompareUnicodeString

    Key  : Failure.Hash
    Value: {590f55a9-3f14-617c-fb39-78eaefcbb09a}

    Key  : Hypervisor.Enlightenments.Value
    Value: 77057948

    Key  : Hypervisor.Enlightenments.ValueHex
    Value: 497cf9c

    Key  : Hypervisor.Flags.AnyHypervisorPresent
    Value: 1

    Key  : Hypervisor.Flags.ApicEnlightened
    Value: 1

    Key  : Hypervisor.Flags.ApicVirtualizationAvailable
    Value: 0

    Key  : Hypervisor.Flags.AsyncMemoryHint
    Value: 0

    Key  : Hypervisor.Flags.CoreSchedulerRequested
    Value: 0

    Key  : Hypervisor.Flags.CpuManager
    Value: 1

    Key  : Hypervisor.Flags.DeprecateAutoEoi
    Value: 0

    Key  : Hypervisor.Flags.DynamicCpuDisabled
    Value: 1

    Key  : Hypervisor.Flags.Epf
    Value: 0

    Key  : Hypervisor.Flags.ExtendedProcessorMasks
    Value: 1

    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: 1

    Key  : Hypervisor.Flags.Phase0InitDone
    Value: 1

    Key  : Hypervisor.Flags.PowerSchedulerQos
    Value: 0

    Key  : Hypervisor.Flags.RootScheduler
    Value: 0

    Key  : Hypervisor.Flags.SynicAvailable
    Value: 1

    Key  : Hypervisor.Flags.UseQpcBias
    Value: 0

    Key  : Hypervisor.Flags.Value
    Value: 4853999

    Key  : Hypervisor.Flags.ValueHex
    Value: 4a10ef

    Key  : Hypervisor.Flags.VpAssistPage
    Value: 1

    Key  : Hypervisor.Flags.VsmAvailable
    Value: 1

    Key  : Hypervisor.RootFlags.AccessStats
    Value: 1

    Key  : Hypervisor.RootFlags.CrashdumpEnlightened
    Value: 1

    Key  : Hypervisor.RootFlags.CreateVirtualProcessor
    Value: 1

    Key  : Hypervisor.RootFlags.DisableHyperthreading
    Value: 0

    Key  : Hypervisor.RootFlags.HostTimelineSync
    Value: 1

    Key  : Hypervisor.RootFlags.HypervisorDebuggingEnabled
    Value: 0

    Key  : Hypervisor.RootFlags.IsHyperV
    Value: 1

    Key  : Hypervisor.RootFlags.LivedumpEnlightened
    Value: 1

    Key  : Hypervisor.RootFlags.MapDeviceInterrupt
    Value: 1

    Key  : Hypervisor.RootFlags.MceEnlightened
    Value: 1

    Key  : Hypervisor.RootFlags.Nested
    Value: 0

    Key  : Hypervisor.RootFlags.StartLogicalProcessor
    Value: 1

    Key  : Hypervisor.RootFlags.Value
    Value: 1015

    Key  : Hypervisor.RootFlags.ValueHex
    Value: 3f7

    Key  : WER.OS.Branch
    Value: vb_release

    Key  : WER.OS.Version
    Value: 10.0.19041.1


BUGCHECK_CODE:  1e

BUGCHECK_P1: ffffffffc0000005

BUGCHECK_P2: fffff80120c7242f

BUGCHECK_P3: 0

BUGCHECK_P4: 1000

FILE_IN_CAB:  073023-13437-01.dmp

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  0000000000001000

READ_ADDRESS: fffff801212fb390: Unable to get MiVisibleState
Unable to get NonPagedPoolStart
Unable to get NonPagedPoolEnd
Unable to get PagedPoolStart
Unable to get PagedPoolEnd
unable to get nt!MmSpecialPagesInUse
 0000000000001000 

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  services.exe

TRAP_FRAME:  ffff800000000000 -- (.trap 0xffff800000000000)
Unable to read trap frame at ffff8000`00000000

STACK_TEXT:  
fffff405`2389c1c8 fffff801`20a60d23     : 00000000`0000001e ffffffff`c0000005 fffff801`20c7242f 00000000`00000000 : nt!KeBugCheckEx
fffff405`2389c1d0 fffff801`20a1026c     : 00000000`00001000 fffff405`2389ca70 ffff8000`00000000 00000000`00000000 : nt!KiDispatchException+0x1793a3
fffff405`2389c890 fffff801`20a0bcbd     : 00000000`00000002 00000000`00000001 00000001`00000000 ffff9406`7da87000 : nt!KiExceptionDispatch+0x12c
fffff405`2389ca70 fffff801`20c7242f     : ffff8381`a63cb840 ffffcf86`f919d300 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x43d
fffff405`2389cc00 fffff801`20ccb747     : ffff9406`786e9bd0 fffff405`2389ccc0 00000000`00000000 fffff801`21245280 : nt!RtlCompareUnicodeString+0x1f
fffff405`2389cc40 fffff801`2083f753     : ffff8381`00000102 fffff801`21244a80 00000000`53706e50 00000000`00000000 : nt!PnpCompareInstancePath+0x17
fffff405`2389cc70 fffff801`20d1fbe1     : 00000000`00000000 fffff405`2389cd50 00000000`00000000 fffff405`2389cf01 : nt!RtlLookupElementGenericTableAvl+0x43
fffff405`2389cca0 fffff801`20d1f96d     : fffff405`2389cf90 00000000`00000000 00000000`00000000 00000000`00000000 : nt!PnpDeviceObjectFromDeviceInstanceWithTag+0x35
fffff405`2389cce0 fffff801`20c3df8e     : fffff801`206013c0 00000000`00000000 fffff405`2389d000 00000000`0000000e : nt!PiControlGetSetDeviceStatus+0xad
fffff405`2389cd80 fffff801`20a0f8f8     : ffffcf86`f982b0c0 fffff405`2389cf90 00000000`00000000 fffff405`2389cf90 : nt!NtPlugPlayControl+0xbe
fffff405`2389cdd0 fffff801`20a00ca0     : fffff801`20cce63c fffff801`2124f1c0 fffff801`20870b16 ffff8000`00000000 : nt!KiSystemServiceCopyEnd+0x28
fffff405`2389cf68 fffff801`20cce63c     : fffff801`2124f1c0 fffff801`20870b16 ffff8000`00000000 00000000`00000000 : nt!KiServiceLinkage
fffff405`2389cf70 fffff801`20cce5c7     : fffff405`2389d0a0 ffff9406`787359c0 00000000`00000000 00000000`00000014 : nt!PlugPlayGetDeviceStatus+0x68
fffff405`2389cfd0 fffff801`20cec0f8     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!PiPnpRtlGetDeviceStatus+0x27
fffff405`2389d010 fffff801`20ce8db0     : fffff405`2389d138 00000000`00000002 fffff405`2389d150 ffff82ca`033ed438 : nt!NtPlugPlayGetDeviceStatus+0x5c
fffff405`2389d070 fffff801`20ce8d0b     : fffff405`2389d3e0 00000000`00000000 00000000`00000000 00000000`00000000 : nt!CmIsDevicePresent+0x58
fffff405`2389d0d0 fffff801`20cc94c9     : fffff405`2389d1c8 fffff801`20820d00 ffff9406`787ff300 00000000`00000000 : nt!PiPnpRtlEnumeratorFilterCallback+0x8b
fffff405`2389d130 fffff801`20ce55db     : fffff801`20ce55a0 fffff405`2389d279 00000000`00000001 fffff801`20c4009e : nt!PiDmCmObjectMatchCallback+0x29
fffff405`2389d170 fffff801`20c3db25     : ffff9406`787ff300 00000000`00000000 fffff405`2389d279 00000000`00000000 : nt!PiDmGetObjectListCallback+0x3b
fffff405`2389d1c0 fffff801`20ced8ff     : 00000000`00008000 00000000`00000008 00000000`00000004 ffffcf86`00000001 : nt!PiDmEnumObjectsWithCallback+0x10d
fffff405`2389d2e0 fffff801`20ced8a2     : fffff405`2389d630 fffff405`2389d3f9 00000000`00000000 00000000`00000000 : nt!PiDmGetObjectList+0x4f
fffff405`2389d330 fffff801`20ced474     : 00000000`00000000 00000212`b68dc000 00000000`00000029 00000000`00000000 : nt!PiDmGetCmObjectListFromCache+0x46
fffff405`2389d390 fffff801`20c3e44f     : 00000000`00000000 00000000`00000000 fffff405`2389d630 00000000`c0000002 : nt!PiPnpRtlGetFilteredDeviceList+0x1e8
fffff405`2389d460 fffff801`20cca0db     : 00000000`00000001 00000000`00000000 00000000`00000102 fffff405`2389d760 : nt!PiPnpRtlCmActionCallback+0x1ff
fffff405`2389d5d0 fffff801`20cc9f9f     : 00000000`00000000 fffff405`2389d700 00000000`00000000 fffff405`2389d759 : nt!_CmGetMatchingFilteredDeviceList+0xc3
fffff405`2389d6f0 fffff801`20c3d2ac     : fffff405`2389d918 000000a7`a8fff078 00000212`b68d4050 00000000`00000000 : nt!PiCMGetDeviceIdList+0x30b
fffff405`2389d7b0 fffff801`20c3d163     : fffff405`2389d8f8 00000000`00000003 00000000`00000098 fffff801`20c11fee : nt!PiCMHandleIoctl+0x12c
fffff405`2389d7f0 fffff801`20cc27aa     : 00000000`00000000 fffff801`20cc2740 fffff405`2389dac0 fffff801`2081eada : nt!PiCMFastIoDeviceDispatch+0x53
fffff405`2389d840 fffff801`20c10906     : 00000000`00000098 00000000`00000000 00000000`00000000 ffffcf86`f91ae660 : nt!PiDaFastIoDispatch+0x6a
fffff405`2389d8a0 fffff801`20c101e6     : 00000212`b68dc070 00000000`00000000 00000000`00000000 00000000`00000000 : nt!IopXxxControlFile+0x706
fffff405`2389d9e0 fffff801`20a0f8f8     : 00000000`00000000 00000000`00000000 00000000`00000000 000000a7`a8fff458 : nt!NtDeviceIoControlFile+0x56
fffff405`2389da50 00007ffe`f5e6d0c4     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x28
000000a7`a8ffef68 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffe`f5e6d0c4


SYMBOL_NAME:  nt!RtlCompareUnicodeString+1f

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

IMAGE_VERSION:  10.0.19041.3208

STACK_COMMAND:  .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET:  1f

FAILURE_BUCKET_ID:  AV_R_nt!RtlCompareUnicodeString

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {590f55a9-3f14-617c-fb39-78eaefcbb09a}

Followup:     MachineOwner
---------
Windows 10
Windows 10
A Microsoft operating system that runs on personal computers and tablets.
12,075 questions
Hyper-V
Hyper-V
A Windows technology providing a hypervisor-based virtualization solution enabling customers to consolidate workloads onto a single server.
2,852 questions
0 comments

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Limitless Technology 44,681 Reputation points
    2023-08-07T10:53:59.37+00:00

    Hello there,

    If you experienced a Blue Screen of Death (BSOD) while training a machine learning model in Windows Subsystem for Linux (WSL) and suspect that Hyper-V might be the cause, there are several factors to consider and steps you can take to diagnose and resolve the issue:

    Hardware Virtualization and Hyper-V: Hyper-V is a hypervisor technology that enables virtualization on Windows systems. To use Hyper-V, hardware virtualization features need to be enabled in your computer's BIOS/UEFI settings. However, running Hyper-V alongside other virtualization technologies (like those used by WSL 2) can lead to compatibility issues and system instability.

    Check Event Logs: After the BSOD, check the Windows Event Viewer for any error messages or codes that might provide insights into the cause of the crash. Look for events related to Hyper-V or virtualization.

    WSL 2 and Hyper-V: WSL 2 uses Hyper-V technology for its virtualization, which might lead to conflicts if you're also running Hyper-V for other purposes. Consider temporarily disabling Hyper-V to see if the BSOD issue is resolved.

    BIOS/UEFI Settings: Ensure that your computer's BIOS/UEFI settings are configured correctly for virtualization. If you're using Hyper-V, make sure it's configured to coexist with other virtualization technologies.

    Update Drivers: Outdated or incompatible hardware drivers can lead to system instability and crashes. Make sure you're using the latest drivers for your hardware components.

    Check for Updates: Ensure that your Windows system is up to date with the latest updates and patches. Sometimes, updates include bug fixes and stability improvements.

    Resource Utilization: Training machine learning models can be resource-intensive. Ensure that your system has adequate resources (CPU, RAM, disk space) available for both Hyper-V and WSL 2.

    Memory and Disk Space: Lack of memory or disk space can lead to system crashes. Make sure you have enough free memory and disk space before running resource-intensive tasks.

    I used AI provided by ChatGPT to formulate part of this response. I have verified that the information is accurate before sharing it with you.

    Hope this resolves your Query !!

    --If the reply is helpful, please Upvote and Accept it as an answer–

    Senthil K

    0 comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.