WSL: Having trouble saving minidumps with bugchecks in LXCore

I had a bugcheck recently using WSL, but when I checked the C:\Windows\minidump directory, and C:\Windows\Memory.DMP, I couldn’t find them to submit to secure@microsoft.com

I’d really like to submit these dumps to improve the project, but they aren’t saving properly. Are there logs anywhere that I can use to troubleshoot why my memdumps aren’t saving?

This isn’t necessarily a WSL problem, but since it’s crucial to get the data to the team (and since some bugchecks are intermittent and hard to reproduce), could someone help me out? I tried reading the documentation, and everything seems fine. All the memdump settings are correct, and I only have one pagefile, size managed by Windows, on C:.

The main Windows event viewer only shows an unexpected shutdown at the time it occurred, with no other details about which logs were saved where or whatever.

It does have this message attached under the details tab (doesn’t seem like much to go on):

- System 

  - Provider 

   [ Name]  Microsoft-Windows-Kernel-Power 
   [ Guid]  {331C3B3A-2005-44C2-AC5E-77220C37D6B4} 
 
   EventID 41 
 
   Version 4 
 
   Level 1 
 
   Task 63 
 
   Opcode 0 
 
   Keywords 0x8000400000000002 
 
  - TimeCreated 

   [ SystemTime]  2017-01-01T10:34:23.587306400Z 
 
   EventRecordID 3567 
 
   Correlation 
 
  - Execution 

   [ ProcessID]  4 
   [ ThreadID]  8 
 
   Channel System 
 
   Computer FPQC-PC 
 
  - Security 

   [ UserID]  S-1-5-18 
 

- EventData 

  BugcheckCode 0 
  BugcheckParameter1 0x0 
  BugcheckParameter2 0x0 
  BugcheckParameter3 0x0 
  BugcheckParameter4 0x0 
  SleepInProgress 0 
  PowerButtonTimestamp 0 
  BootAppStatus 0 
  Checkpoint 0 
  ConnectedStandbyInProgress false 
  SystemSleepTransitionsToOn 0 
  CsEntryScenarioInstanceId 0 

About this issue

  • Original URL
  • State: closed
  • Created 10 years ago
  • Comments: 19 (7 by maintainers)

Most upvoted comments

That would normally be a strange bug – the kernel crashes through direct volume manager access, not file names. You may want to try enabling support for a ‘dedicated dump file’ to see if that changes anything.