Marka codsiga Windows ee socda uu u istaago ama u shil galo si lama filaan ah, nidaamkaagu waxa uu abuuraa 'faylka qashinka daadinta' si uu u kaydiyo macluumaadka jira ka hor inta aanay shilku dhicin. Akhrinta faylalkan daadinta shilalka ayaa laga yaabaa inay kaa caawiyaan inaad hesho oo aad cilad bixiso sababta qaladka. Soo hel sida aad u akhrin karto faylka xusuusta^{(memory dump file)} yar ee ay samaysay Windows.

Akhrinta faylalka Xasuusta Yaryar^{(Small Memory Dump)} ( DMP ).

Faylka qashinka yar ee xusuusta ayaa diiwaangeliya xogta ugu yar ee faa'iidada leh ee kaa caawin karta inaad qeexdo sababta codsigu u shilmay ama u istaagay si lama filaan ah. Nooca cusub ee Windows wuxuu si toos ah u abuuraa fayl cusub mar kasta oo kombuyuutarku si lama filaan ah u istaago. Taariikhda la xidhiidha faylashaas waxa lagu kaydiyaa %SystemRoot%Minidumpgalka Nooca faylka qashinka waxaa ku jira macluumaadka soo socda:

1. Fariinta Joojinta^(Stop) iyo cabbirkeeda iyo xogta kale
2. Liiska darawallada la raray
3. Macnaha processor-ka ( PRCB ) ee processor-ka istaagay
4. Macluumaadka habka iyo macnaha guud ee kernel ( EPROCESS ) ee habka joogsaday
5. Xogta habka iyo macnaha kernel ( ETHREAD ) ee dunta joogsatay
6. Qaabka Kernel-ka xidhmada xidhmada^{(Kernel-mode)} dunta joogsatay

Isticmaalayaashu waxay isticmaali karaan qalabka Windows Debugger (WinDbg.exe) si ay u akhriyaan faylasha xusuusta yar yar. It ( WinDbg ) waxay ku timaadaa qayb ka mid ah nooca ugu dambeeyay ee Tools Debugging^{(Debugging Tools)} ee xirmada Windows .

Waxa aad ku rakibi kartaa qalabka wax-ka-darida sida qayb gooni-gooni ah oo ka socota Qalabka Horumarinta Software-ka ee Windows^{(Windows Software Development Kit)} ( SDK ).

Inta lagu jiro habaynta, marka saxaraha rakibaadda SDK uu soo baxo, calaamadee sanduuqa ka soo horjeeda Qalabka Debugging ee Windows^{(Debugging Tools for Windows)} . Tallaabadani waxay awood kuu siinaysaa inaad ku rakibto qalabka wax-ka-hortagga sida qayb kaligiis ah oo ka socda Qalabka Horumarinta Software-ka ee Windows^{(Windows Software Development Kit)} ( SDK ).

Markaad dejiso Debugger-ka Windows^{(Windows Debugger)} , fur qashin-qubka adiga oo dooranaya ikhtiyaarka daadinta Shilalka Furan ee menu-ka ^{(Open Crash Dump)}Faylka^(File) ama adigoo riixaya CTRL+D.

Marka sanduuqa wada hadalka furan ee Qashin qubka^{(Open Crash Dump)} uu ka soo baxo shaashadda kombiyuutarkaaga, geli dariiqa buuxda iyo magaca faylka qashinka ee sanduuqa magaca faylka^{(File name)} , ama isticmaal sanduuqa wada hadalka si aad u dooratid wadada saxda ah iyo magaca faylka.

Hadda, marka faylka saxda ah la doorto, dooro Fur^(Open) .

Sug^(Wait) dhowr ilbiriqsi si aad ugu ogolaato in faylka la shubo uu ku shubo marka uu ku xidho intarneedka^(Internet) oo uu soo dejiyo calaamadaha loo baahan yahay si uu ugu muujiyo akhrinta.

Waa inaad aragto fariin, akhrinaysa - Debugee kuma xidhna^{(Debugee not connected)} .

Ka dib marka dhammaan calaamadaha si guul leh loo soo dejiyo, farriintan soo socota waa inay ka muuqataa xagga hoose ee qoraalka qashinka - Dabagalka: Mulkiilaha Mashiinka.^{(Followup: MachineOwner.)}

Geli amar gudaha bar taliska ee hoose ee daaqada qashinka si aad u falanqeyso faylka qashinka. Waa in aad aragto isku-xidhaha ku !analyze -vhoos qoran Falanqaynta Bugcheck^{(Bugcheck Analysis)} .

Ku dhufo xiriirka si aad u geliso amarka !analyze -visla markiiba bogga hoose ee bogga.

Marka la sameeyo, falanqaynta hubinta cayayaanka ee faahfaahsan waa in ay qabsataa booska shaashadda.

Hoos^(Scroll) ugu dhaadhac qaybta ay ku qoran tahay STACK_TEXT . Goobta STACK_TEXT waxa^(STACK_TEXT) ay tusaysaa raxan raadka qaybta cilladaysan. Halkan, waxaad ka heli doontaa safaf tirooyin leh oo saf kastaa uu raacayo xiidan iyo xoogaa qoraal ah. Qoraalku waa inuu kaa caawiyaa inaad garato sababta shilka iyo haddii ay khusayso adeeggee baa burburaya.

Isticmaal !analyzeFidinta si aad u hesho tafaasiil dheeraad ah. Ha iloobin inaad isticmaasho -v, ikhtiyaarka si buuxda u muujinta xogta.

Akhri^(Read) : Sida gacanta loogu abuuro faylka Shilalka^{(manually create a Crash Dump file)} ee Windows 11/10.

Marka la fuliyo, taliska '!analyze' ayaa go'aamin doona tilmaamaha sababay khaladka oo ku tusi doona goobta FOLLOWUP_IP .

• SYMBOL_NAME - tus astaanta
• MODULE_NAME - waxa uu soo bandhigayaa cutubka
• IMAGE_NAME - wuxuu soo bandhigayaa magaca sawirka
• DEBUG_FLR_IMAGE_TIMESTAMP - waxay tusinaysaa shaabada sawirka oo u dhiganta tilmaantan

Qaado tallaabada lagama maarmaanka ah si arrinta loo xalliyo!

• Waxa kale oo aad isticmaali kartaa aaladda khadka taliska ^{(use the command-line tool)} Dumpchk.exe si aad u hubiso faylka kaydinta xusuusta.
• Waxaad isticmaali kartaa softiweerka Falanqeeyaha Qashinka Qulqulka^{(Crash Dump Analyzer software)} si aad u falanqeyso warbixinada qashinka.
• Haddii kale, waxaad isticmaali kartaa WhoCrashed Home Edition si aad u hubiso khaladaadka hal mar oo gujis ah. Qalabku wuxuu sameeyaa falanqaynta burburka dhimashada ka dib ee qashinka xusuusta Windows^{(Windows Memory Dumps)} wuxuuna soo bandhigayaa dhammaan macluumaadka la ururiyey si la fahmi karo.

Rajo in taasi ku caawiso!

Akhrinta la xidhiidha:^{(Related reads:)}

1. Dejinta Dajinta Xusuusta Daaqadaha
2. Xakamaynta xusuusta Jireed ee ku jirta faylalka Qashin-qubka^{(Physical Memory Limits in Crash Dump files)}
3. Habee Daaqadaha si aad u abuurto Faylasha Burburinta Shilalka Shaashada Buluuga ah
4. Xakamee tirada faylalka qashinka ee xusuusta, Windows ayaa abuurta oo kaydisa.

How to open and read Small Memory Dump (dmp) files in Windows 11/10

When a running Windows application stops or craѕhes υnexpectedly, your system generates a ‘crash dump file’ to saνe information present just before thе crashing event occurred. Reading these crash dump files may help you find and troubleshoot the cause of thе errоr. Find how you сan reаd a small memory dump file created by Windows.

Reading Small Memory Dump (DMP) files

A small memory dump file records the smallest set of useful information that may help you pinpoint why an application crashed or stopped unexpectedly. The newer version of Windows automatically creates a new file every time your computer stops unexpectedly. The history related to these files is stored in the %SystemRoot%\Minidumpfolder. The dump file type contains the following information:

1. The Stop message and its parameters and other data
2. A list of loaded drivers
3. The processor context (PRCB) for the processor that stopped
4. The process information and kernel context (EPROCESS) for the process that stopped
5. The process information and kernel context (ETHREAD) for the thread that stopped
6. The Kernel-mode call stack for the thread that stopped.

Users can use the Windows Debugger (WinDbg.exe) tool to read small memory dump files. It (WinDbg) comes as a part of the latest version of the Debugging Tools for Windows package.

You can install the debugging tools as a standalone component from the Windows Software Development Kit (SDK).

During the setup, when the SDK installation wizard appears, check the box marked against Debugging Tools for Windows. This action will enable you to install the debugging tools as a standalone component from the Windows Software Development Kit (SDK).

Once you have set up the Windows Debugger, open a dump by choosing Open Crash Dump option from the File menu or by pressing CTRL+D.

When the Open Crash Dump dialog box pops up on your computer screen, enter the full path and name of the crash dump file in the File name box, or use the dialog box to select the proper path and file name.

Now, when the proper file has been chosen, select Open.

Wait for a few seconds to allow the dump file to load as it connects to the Internet and downloads the required symbols to display in the readout.

You should see a message, reading – Debugee not connected.

After all the symbols have been successfully downloaded, the following message should be visible at the bottom of the dump text – Followup: MachineOwner.

Enter a command into the command bar at the bottom of the dump window to analyze the dump file. You should see a link that says !analyze -v under Bugcheck Analysis.

Hit the link to enter the command !analyze -vin the prompt at the bottom of the page.

Once done, a detailed bug check analysis should occupy the screen space.

Scroll down to the section where it says STACK_TEXT . The STACK_TEXT field shows a stack trace of the faulting component. Here, you will find be rows of numbers with each row followed by a colon and some text. The text should help you identify the cause of the crash and if applicable what service is crashing it.

Use the !analyzeExtension to get more details. Do not forget to use the-v, option for a fully verbose display of data.

Read: How to manually create a Crash Dump file in Windows 11/10.

Upon execution, the ‘!analyze’ command will determine the instruction that has probably caused the error and display it in the FOLLOWUP_IP field.

• The SYMBOL_NAME – show the symbol
• MODULE_NAME – displays the module
• IMAGE_NAME – displays image name
• DEBUG_FLR_IMAGE_TIMESTAMP – shows image timestamp corresponding to this instruction

Take the necessary action to get the issue resolved!

• You can also use the command-line tool Dumpchk.exe to check a memory dump file.
• You can use Crash Dump Analyzer software to analyze crash dump reports.
• Alternatively, you can use WhoCrashed Home Edition to check for errors in a single click. The tool does a post-mortem crash-dump analysis of the Windows Memory Dumps and presents all gathered information in a comprehensible way.

Hope that helps!

Related reads:

1. Windows Memory Dump Settings
2. Physical Memory Limits in Crash Dump files
3. Configure Windows to create Crash Dump Files on Blue Screen
4. Control the number of Memory Dump Files, Windows creates and saves.

Related posts

• Hagaaji WerMgr.exe ama WerFault.exe Qaladka Codsiga gudaha Windows 11/10

• Sida gacanta loogu abuuro faylka Shilalka Burburinta gudaha Windows 11/10

• Habka fog-fog ayaa wacaya khalad markii la isticmaalayo DISM gudaha Windows 11/10

• Adeegga wareejinta garaadka ee asalka ah oo aan shaqaynayn Windows 11/10

• Hagaaji sirta aaladda si ku-meel-gaar ah ayaa loo hakiyay qalad gudaha Windows 11/10

• PC-gaagu kuma taageerayo qaladka Miracast gudaha Windows 11/10

• Cilad kaadhka fiidiyoowga ah ee aan socon karin inta lagu jiro rakibida Windows 11/10

• Dib u dhiska Tokens.dat ama Faylka Tokens Activation gudaha Windows 11/10

• Qalab wax diliddu way xidhan yihiin, barafayaan, ama ku burburayaan gudaha Windows 11/10

• Ma jiro iskaan-qaadayaal lagu arkay cilad ku jirta Windows 11/10 kumbuyuutarka

• Adeegga Maqalka Windows kuma shaqeeyo Windows 11/10

• Bixiyaha WMI (WmiPrvSE.exe) Isticmaalka CPU sare ee Windows 11/10

• Goobta Desktop lagama heli karo gudaha Windows 11/10

• Start Menu ma furna ama badhanka bilawga kuma shaqeeyo Windows 11/10

• Hel app Help oo aan shaqaynayn Windows 11/10

• Adeegyada maqalka ee aan ka jawaabin khaladaadka gudaha Windows 11/10

• Daaqadaha ma heli karaan Settings Network router-ka gudaha Windows 11/10

• Sida loo xaliyo arrimaha waxqabadka gudaha Windows 11/10

• App-ka sawirada ku burburaya qaladka nidaamka faylka Windows 11/10

• Sida loo xaliyo khaladaadka faylalka DLL ee maqan Windows 11/10 PC