You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
First, I am not an experienced debugger or developer, just a user. I was trying to look at a bugcheck in memory.dmp and in the output of the analyze command below I noticed that it says Windows 10, but I am running an insider build of Windows 11. It does show the correct build number, but the OSNAME is wrong. I'm not sure if that affects anything, but I thought I would report it anyway. If you need anything else from me, I will be happy to provide it. Thank you.
PROCESS_NAME: System
First, I am not an experienced debugger or developer, just a user. I was trying to look at a bugcheck in memory.dmp and in the output of the analyze command below I noticed that it says Windows 10, but I am running an insider build of Windows 11. It does show the correct build number, but the OSNAME is wrong. I'm not sure if that affects anything, but I thought I would report it anyway. If you need anything else from me, I will be happy to provide it. Thank you.
PROCESS_NAME: System
SYMBOL_NAME: nt!KiDoubleFaultAbort+351
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
STACK_COMMAND: .cxr; .ecxr ; kb
BUCKET_ID_FUNC_OFFSET: 351
FAILURE_BUCKET_ID: 0x7f_8_VRF_nt!KiDoubleFaultAbort
OS_VERSION: 10.0.26227.5000
BUILDLAB_STR: ge_prerelease
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {2575f830-7dd8-52d7-e1be-20f8274db764}
The text was updated successfully, but these errors were encountered: