Hagahan ayaa kaa caawin doona inaad fahanto, falanqayso, xalliso oo aad hagaajiso Windows Screen of Death^{(fix Windows Blue Screen of Death)} , Jooji khaladaadka^{(Stop Errors)} , Koodhadhka qaladka^{(Error Codes)} , Khaladaadka Hubinta Bug^{(Bug Check)} , khaladaadka nidaamka, qaladka nidaamka, khaladaadka kernel ee ku dhaca Windows 11/10/8/7 . Marka Windows ay la kulanto xaalad wax u dhimaysa hawlgalka nidaamka badbaadada ah (ie, “bug”), nidaamku wuu joogsadaa.

Shaashadda buluuga^{(Blue Screen)} ah ee dhimashada^(Death) gudaha Windows 11/10

Xaaladdan waxaa loo yaqaan ' baaritaanka cayayaanka^{(bug check)} '. Waxa kale oo caadi ahaan loo yaqaan shil nidaam, khalad kernel, cillad habaysan, ama Cilad Joojin^{(Stop Error)} .

Gudaha Windows XP , nidaamka Ka warbixinta Cilada Windows^{(Windows Error Reporting)} wuxuu ahaa aasaas ahaan gacanta laakiin hadda waa la wanaajiyey oo lagu hagaajiyay Windows 7 & Windows Vista . Iyadoo laga yaabo inay tani dhacdo, Shaashado buluug^{(Blue Screens)} ah kaliya ma lumin. Waxaad weli ku arki kartaa iyaga Windows 7/8 sidoo kale.

Caadi ahaan, marka BSOD dhacdo, waxay sii jirtaa ilbiriqsi ka hor inta uusan kombuyuutarku isla markiiba dib u bilaabin. Sidan ayaan u kari waynay in aan akhriyo waxa qoran. Si aad agagaarkeeda u hesho, mid waa inuu curyaamiyaa ikhtiyaarka dib u bilaabista PC-ga tooska ah ee StartUp & Nidaamka Soo kabashada^{(System Recovery)} . Ogaanshaha koodka khaladku wuxuu kaa caawin karaa in la aqoonsado dhibaatada/xalka. U samee sida soo socota:

Dami UAC _ Control Panel > System and Maintenance > System > Advanced System Settings > Advanced tab> Under Startup and Recovery > Click Settings > Clear Nadiifi sanduuqa calaamadaynta si toos ah^{(Automatically Restart)} dib u bilow > dhagsii OK. Daar UAC _

Daaqadaha ayaa isku dayi doona in ay iskii u xaliyaan dhibaatada inta badan, laakiin haddii aysan ka soo kaban karin iskeed, waxay keeni doontaa shaashad buluug ah.

Khaladaadka Shaashada Buluuga ee Windows 11/10

Isticmaalayaasha nidaamka Windows waa hubaal inay la kulmeen, hal mar ama mid kale, argagixsada "Ka reebista Dhimashada", oo caadi ahaan loo yaqaan "Shaashada Buluugga ee Dhimashada", ama BSOD . In kasta oo BSOD -gu inta badan lagu dhex tuuray tuubbada slag software-ka, gudaha Vista , shilalka si buuxda looma saarin. Marka Windows ay la kulanto xaalad wax u dhimaysa hawlgalka nidaamka badbaadada ah (ie, “bug”), nidaamku wuu joogsadaa. Xaaladdan waxaa loo yaqaan 'baaritaanka cayayaanka'. Waxa kale oo inta badan loo yaqaan shil nidaam, khalad kernel, cillad nidaamka, ama qalad Jooji^(Stop) . Marka Windows ay la kulanto qaladka halista ah ee ku qasbaya inuu joojiyo socodsiinta, waxay soo bandhigaysaa aShaashadda buluga^{(BLUE SCREEN OF DEATH)} ah ee dhimashada ama kaliya 'jacayl' loo yaqaan BSOD !

Gudaha Windows 11/10/8/7 , si ka duwan XP, halkaas oo nidaamku ahaa mid gacanta lagu hago, Warbixinta Cilada Windows^{(Windows Error Reporting)} waa la wanaajiyay oo lagu hagaajiyay Windows 7 & Vista . Qofku waa inuu dabagal ku sameeyo si uu u eego in xal la helay iyo in kale. Tani waxay ahayd nidaam aad u xanuun badan. Gudaha Windows 10/8/7/Vista , warbixintan oo dhan iyo habka dabagalka ayaa ah mid toos ah.

Maalmahan a Windows 11/10/8/7/Vista Isticmaalayaasha Vista waxay u badan tahay inay u badan tahay inay arkaan fariinta sida soo socota: " Nidaamka Operating System-ka Microsoft kama jawaabayo^{(Microsoft Windows Operating System is not responding)} ." Isticmaalayaashana waxaa la siiyaa laba fursadood. Waxay noqon karaan "xiri barnaamijka" ama " Sug^(Wait) inta barnaamijku ka jawaabayo. “Qofku^{(” One)} wuxuu sugaa isagoo rajaynaya in arrinta la xalin doono, haddii kale markaas uun baa barnaamijka xidha oo isu diyaariya inuu xog lumiyo. Ugu yaraan, fariimahani waxay u muuqdaan kuwo aan dhib badan lahayn.

BSOD^(BSODs) - yadu dhanka kale waxay ahaayeen/waa kuwo argagax leh oo niyad-jab leh, in la yiraahdo ugu yaraan!

Qoraalka saxda ah ee cilad^(Stop) - joojintu way kala duwan tahay, marka loo eego waxa sababay khaladka. Laakin qaabku waa la jaanqaadaya wuxuuna ka kooban yahay 3 qaybood^{(3 parts)} :

• QAYBTA 1^{(PART 1)} : Magaca qaladka calaamada ah: Kani waa fariinta Stop Error ee la siiyo OS oo u dhiganta Stop Error nambarka soo muuqda.
• QAYBTA 2^{(PART 2)} : Talooyinka xallinta dhibaatada: Qoraalkani wuxuu khuseeyaa dhammaan Joojinta^(Stop) Khaladaadka noocaas gaarka ah.
• QAYBTA 3^{(PART 3)} : Nambarka qaladka iyo cabbiraadaha: Waa macluumaadka hubinta cayayaanka. Qoraalka raacaya kelmadda STOP waxaa ku jira lambarka qaladka, xarafka hexadecimal, iyo ilaa afar cabbir kuwaas oo ah nooca qaladka.

Guud ahaan, ma jiraan doorashooyin aad u badan oo ah nooc ka mid ah soo kabashada. Caadi ahaan, qofku wuxuu isku dayaa inuu "dib u kiciyo" PC-ga iyadoo la rajeynayo in BSOD ay u dhacday sababtoo ah xaalad naadir ah oo darawalka qaar ah kaas oo la iska indho-tiray codeynta iyo tijaabinta. Laakiin haddii BSOD -gu sii jiro, waxaa jira xeelado laga yaabo in la isticmaalo si loo hagaajiyo nidaamka waxaa jira in ka badan 250 codes BSOD ah^{(250 documented BSOD codes)} .

Qaado, tusaale ahaan, BSOD-da ugu caansan:

Bugcode 0xA - IRQL_NOT_LESS_OR_EQUAL

Tani waa BSOD^(BSOD) caadi ah oo caadi ah oo dhacda marka darawalku si sharci darro ah u galo goobta xusuusta halka NT uu ka shaqaynayo IRQL gaar ah . Kani waa khalad codeing darawalka, oo la mid ah isku dayga inuu galo meel xusuusta aan ansax ahayn.

Halbeegyada:
1 - goobta xusuusta ee la tixraacay
2 - IRQL wakhtiga tixraaca
3 - 0 == akhrin, 1 == qor
4 - kood ku qoran oo tixraacaya
Soo kabashada/Meelaha shaqada:
Ma jiro. Kani waa khalad dilaa ah waana khalad codeing darawalka.

Waa maxay tallaabada ugu horreysa ee la qaado si loo xalliyo qaladka Shaashada Buluugga^{(Blue Screen)} ah ee Dhimashada^(Death)

BSOD-yada ama Joojinta Khaladaadka gudaha Windows 10 waxay u muuqdaan inay ka fiican yihiin oo ka saaxiibtinimo badan yihiin oo indhaha ku fudud yihiin. Laakiin ma bixiyaan tafaasiil badan. Waa inaad ku qasbeysaa OS-gaaga inuu soo bandhigo Jooji macluumaadka qaladka Windows 10 .

Sida loo Debuxiyo Tuuboyinka Xusuusta

Si aad u ogaato sida loo tirtiro qashinka xusuusta^{(Memory Dumps)} si aad u ogaato sababta BSOD kaaga , soo deji oo rakib Qalabka Debugging Microsoft^{(Microsoft Debugging Tools)} . Hubi in faylkaaga bogga uu wali ku jiro qaybta nidaamka. Haddii kale, Windows ma awoodo inay kaydiso faylalka qaladka.

Waxaad isticmaali kartaa softiweerka Falanqeeyaha Qashinka Qulqulka^{(Crash Dump Analyzer software)} si aad u falanqeyso warbixinada qashinka.

TROUBLESHOOT WINDOWS STOP ERRORS/BSODs

1. Marka hore^(First) & Ugu horrayn^(Foremost) , eeg haddii System Restore uu xallin karo arrintan.
2. Haddii kale, dabadeed socodsii anti-virus-kaaga iyo anti-spyware iyo PC-gaaga Junk/Registry Cleaner .
3. Taas ka dib, socodsii Windows Check Utility Disk^{(Windows Check Disk Utility)} .
4. Ka dib isku day inaad aqoonsato inaad samaysay wax software ama hardware wax ka beddel ah ama wax ka beddel ah.
5. Inta badan, software-ku waa dhibbanaha ee maaha sababta BSOD's. Markaa ha ka saarin dhibaatooyinka qalabka. Waxaa dhaawacmi kara disk-yada adag, RAM -ka jirka oo cilladaysan, chips-yada ^(RAM)CPU -da ee kulaylka badan ama wax kale!
6. Hubi haddii aad ku arki karto magaca darawalka faahfaahinta khaladka. Haddii aad awooddo, ka dib si fudud u curyaaminta, ka saarista, ama dib ugu celinta darawalka nuqul hore waxay kaa caawin kartaa xalinta dhibaatadaas. Kaararka is-dhexgalka shabakada^(Network) , kontaroolayaasha diskooga, iyo Adapters-ka Fiidiyowga^{(Video Adapters)} ayaa ah dambiilayaasha, inta badan.
7. Hubi xusuustaada. Isticmaal qalabka ogaanshaha xusuusta^{(Memory Diagnostic Tool)} Windows . Tag Control Panel oo ku qor "xasuusta" sanduuqa raadinta^(Search) . Hoosta Aaladaha^(Tools) Maamulka , dhagsii Cilad-sheeg Dhibaatooyinka Xusuusta^{(Memory Problems)} Kumbuyuutarkaaga . Qalabka Cilad-baadhista Xusuus^{(Windows Memory Diagnostics Tool)} -qorka ee Windows , oo halkan lagu muujiyey, dooro mid ka mid ah xulashooyinka.
8. Si taxadar leh u hubi nidaamkaaga BIOS Cusbooneysii ma laga heli karaa soo saaraha nidaamka ama Motherboard-ka? Si taxadar leh u hubi dukumeentiyada BIOS ; Dib u dejinta dhammaan xulashooyinka BIOS ee khaladaadkooda ayaa mararka qaarkood xallin kara arrin ay sababtay tweaking xad-dhaaf ah.
9. Hubi haddii aad ku yar tahay ilaha nidaamka? Mararka qaarkood yaraanta adag ee Space Space^{(Disk Space)} ama RAM waxay keeni kartaa BSOD's.
10. Hubi haddii faylka nidaamka uu dhaawacmay? Ku Shaqeyso Qaab Badbaado^{(Safe Mode)} leh , maadaama darawallada iyo adeegyada kaliya ee muhiimka ah ay shaqeeyaan. Haddi nidaamkaagu ku bilaamayo qaab badbaado^{(Safe Mode)} leh balse aanu caadiyan ahayn, waxa ay u badantahay in aad dhibaato kala kulanto darawalka. Isku day in aad Maamulaha Aaladda^{(Device Manager)} ku socodsiiso Qaab Badbaado^{(Safe Mode)} leh oo aad ka saarto tuhmanaha ay u badan tahay. Ama ku socodsii Nidaamka Soo Celinta^{(System Restore)} ee Habka Badbaadada^{(Safe Mode)} ah .
11. Samee Windows 10 Dhibbanaha Shaashada Buluugga ah .

MSDN print-link BlueScreenView

Maxaa la sameeyaa haddii aad ka shakisan tahay in darawalku^(Driver) uu keeno BSOD's

Haddii aad ka shakisan tahay in darawalka qalabka buggy uu khalad u yahay BSOD's, wac qalab cilad-yar oo la yaqaan laakiin awood leh oo loo yaqaan Maareeyaha Xaqiijinta Darawalka^{(Driver Verifier Manager)} . Geli xaqiijinta^(verifier) bar raadinta oo ku dhufo gal si aad u soo qaadato Verifier.exe . U Orod^(Run) sidii Maamule^{(Administrator)} . Qalabkani wuxuu kaa caawinayaa inaad si dhab ah u aqoonsato darawalka cilladaysan.

Hadda dooro "Create Standard Settings". Marka xigta^(Next) , dooro nooca darawallada aad rabto inaad xaqiijiso. Darawalada aan saxeexin waxay u badan tahay inay sabab u yihiin dhibaatooyinka, maadaama loo abuuray noocyadii hore ee Windows . Guji Xiga^{(Click Next)} , ilaa la dhammeeyo.

Maamulaha Xaqiijiye Darawalku^{(Driver Verifier Manager)} wuxuu u shaqeeyaa habkan soo socda. Halkii uu mashiinkaagu ku tuuri lahaa BSOD aan la garan karin , wakhti kasta, waxaad ka dhigi kartaa Hubiyaha Darawalka^{(Driver Verifier)} inuu joojiyo kombiyuutarkaaga marka uu bilaabayo, oo leh BSOD kaas oo sharxi doona dhibaatada dhabta ah, halkii saxda ah! Kadib waxaad dooran kartaa inaad xalliso dhibaatada adoo cusboonaysiiya, dib u rogaya ama ka saaraya darawalka dembiilaha ah.

Fadlan ogow in ay dhacdo naadir ah Maareeyaha Xaqiijinta Darawalku^{(Driver Verifier Manager)} uu helo darawal aan waafaqsanayn; waxaa dhici karta in aysan ahayn midda dembiilaha ah. Markaa samee taxadar aad u daran. Driver/s dareewalada la aqoonsaday mid shaki leh oo samee xukunkaaga ugu fiican kiiskan oo kale.

Markaad hoos u dhigto darawalka^(Driver) dhibaatada leh , waxaad haysataa saddex doorasho: Cusbooneysii^(Update) , Dib-u- celinta^{(Roll Back)} ama Uninstall Driver Device^{(Device Driver)} .

Si taas loo sameeyo, fur Maareeyaha Aaladda^{(Device Manager)} . Fur sanduuqa wada-hadalka guryaha ee qalabka, oo isticmaal badhamada soo socda ee tab darawalka^(Driver) si aad u qabato hawlaha dayactirka:

• Cusboonaysii Darawalka^{(Update Driver)} : Tani waxay bilaabi doontaa Wizard Cusboonaysiinta Hardware^{(Hardware Update Wizard)} .
• Roll Back Driver : Tani waxay tirtiri doontaa darawalkii ugu dambeeyay ee la cusboonaysiiyay waxayna dib ugu celin doontaa qaabayntaada, noocii hore.
• Uninstall Driver : Tani waxay gebi ahaanba tirtiraysaa faylalka darawalka iyo goobaha diiwaangelinta ee qalabka la doortay.

Akhri^(Read) : Sidee lagu ogaan karaa darawalka keenaya shaashadda buluuga ah ee Windows?

Liiska Khaladaadka Shaashadda Buluugga ah ee Daaqadaha Guud^{(Common Windows Blue Screen Errors)} & xalalka

JOOJI 0x000000D1 ama DRIVER_IRQL_NOT_OR_EQUAL

Malaha BSOD-ga ugu caansan! Tani waxay dhacdaa marka darawalku si sharci darro ah u galo goobta xusuusta halka NT uu ka shaqaynayo IRQL gaar ah . Kani waa khalad codeing darawalka, oo la mid ah isku dayga inuu galo meel xusuusta aan ansax ahayn. Soo kabashada/Xarun-shaqeedka: Caadiyan midna. Laakin kuwaani waxaa laga yaabaa inay caawiyaan KB810093 , KB316208 & KB810980 .

JOOJI 0x0000000A^{(STOP 0x0000000A)} ama IRQL_NOT_LESS_OR_EQUAL

Habka kernel-ka ama darawalku wuxuu isku dayay inuu galo goobta xusuusta amar la'aan. Ciladan Joogsiga^(Stop) ah waxaa sida caadiga ah sababa cillad ama qalab ama software aan ku haboonayn Magaca dareewalka aaladaha dembiilaha ayaa inta badan ka muuqda qaladka Joojinta^(Stop) wuxuuna ku siin karaa tilmaam muhiim ah oo lagu xallinayo dhibaatada. Haddii fariinta khaladku ay tilmaamto qalab gaar ah ama qaybta qalabka, isku day inaad ka saarto ama badasho qalabka qaybtaas. Haddii cilad^(Stop) -joojintu soo baxdo inta lagu jiro Setup , ka shaki darawal aan ku habboonayn, adeegga nidaamka, iskaanka fayraska, ama barnaamijka kaydinta. KB314063 waxa laga yaabaa inuu ku tuso jihada.

JOOJI 0x00000050 ama PAGE_FAULT_IN_NONPAGED_AREA

Darawalka qalabka ama adeegga nidaamka ayaa codsaday xog aan ku jirin xusuusta. Sababtu waxa ay noqon kartaa xusuusta jidhka oo cilladaysan ama software aan la jaan qaadi karin, gaar ahaan kuwa fog fog, iyo barnaamijyada ka hortagga. Haddii qaladku dhaco isla markaaba ka dib marka la rakibo darawalka qalabka ama codsiga, isku day inaad isticmaasho Mode Safe si aad uga saarto darawalka ama aad ka saarto barnaamijka. Wixii macluumaad dheeraad ah, eeg KB894278 & KB183169 .

JOOJI 0x000000C2 ama BAD_POOL_CALLER

Habka kernel-ka ama darawalku wuxuu isku dayay inuu sameeyo qoondaynta xusuusta sharci-darrada ah. Dhibka waxaa inta badan laga heli karaa cilad ku jirta darawalka ama software. Waxa kale oo mararka qaarkood sababa cillad ku timaadda qalabka qalabka. Wixii macluumaad dheeraad ah, eeg KB265879 .

JOOJI OX000000ED^{(STOP OX000000ED)} ama UNMOUNTABLE_BOOT_VOLUME

Tani waxay dhacdaa haddii Windows uusan awoodin inuu galo mugga ay ku jiraan faylasha boot. Laakiin haddii aad hesho fariintan markaad cusboonaysiinayso TO Vista , hubi inaad haysatid darawalo ku habboon kontaroolaha diskka iyo sidoo kale dib u hubi fiilada wadista, oo hubi in si habboon loo habeeyey. Haddii aad dib u isticmaalayso ATA-66 ama ATA-100 darawalada, iska hubi inaad haysato fiilo 80 ah, oo aanad haysan fiilada IDE ee caadiga ah ee 40-xidhiidhiyaha ah. Eeg KB297185 iyo KB315403 .

JOOJI 0x0000001E ama KMODE_EXCEPTION_NOT_HANDLED

Kernel- ka Windows -ku waxa uu ogaaday hab-raac sharci-darro ah ama aan la garanayn hab-raaca processor-ka, oo inta badan ka dhasha xusuusta khaldan iyo xadgudubyada gelitaanka ee ay sababaan darawallada khaldan ama qalabka qalabka. Fariinta qaladku waxay inta badan tilmaamtaa darawalka ama qalabka dembiga. Haddii qaladku isla markiiba dhacay ka dib markii la rakibay darawal ama adeeg, isku day inaad joojiso ama ka saarto ku-darka cusub.

JOOJI 0x00000024 ama NTFS_FILE_SYSTEM

Dhibaato ayaa ka dhex dhacday darawalka nidaamka faylka NTFS . Cilad Joojin^(Stop) la mid ah, 0x23, ayaa u jirta FAT32 . Sababta ugu badan ee ay u badan tahay waa hardware-ga oo ku xumaaday saxanka ama kontoroolka saxanka. Hubi dhammaan xidhiidhada jidheed ee dhammaan Hard Disk-yada ku jira nidaamka oo wad Check Disk^{(Check Disk)} -ga . KB228888 ayaa ku caawin doona.

JOOJI 0x0000002E ama DATA_BUS_ERROR

Xusuusta jireed ee fashilantay ama cilladaysan (ay ku jirto xusuusta loo isticmaalo adapters-ka muuqaalka) ayaa ah sababta ugu badan ee qaladkan Joojinta . ^(Stop)Waxa kale oo laga yaabaa in khaladku ka dhashay Hard Disk-gu xumaaday ama Motherboard-ka xumaaday.

JOOJI 0x0000003F^{(STOP 0x0000003F)} ama NO_MORE_SYSTEM_PTES

Nidaamkaagi waxa ka dhamaaday gelinta miiska bogga ( PTEs ). Sababta qaladkan aan caadiga ahayn waxa ay noqon kartaa barnaamij gurmad ah oo ka baxsan xakamaynta ama darawalka qalabka buggy. Wixii macluumaad dheeraad ah, eeg KB256004 .

JOOJI 0x00000077^{(STOP 0x00000077)} ama KERNEL_STACK_INPAGE_ERROR

Nidaamku waxa uu isku dayay in uu akhriyo xogta kernelka ee xusuusta dalwadda ah (faylka bogga) oo ku guuldareystay in uu helo xogta ciwaanka xusuusta ee la cayimay. Khaladka Joojintan^(Stop) waxaa sababi kara dhibaatooyin kala duwan, oo ay ku jiraan xusuusta cilladaysan, Hard Disk-gu oo xumaaday, kontaroolaha saxanka ama fiilada oo si khaldan loo habeeyey, xogta kharribtay, ama caabuq fayras ah. Wixii macluumaad dheeraad ah, guji KB228753 .

JOOJI 0x0000007F^{(STOP 0x0000007F)} ama UNEXPECTED_KERNEL_MODE_TRAP

Waxay u badan tahay inay ugu wacan tahay cilladda Hardware , sida chips-yada xusuusta cilladaysan, Qaybaha xusuusta oo khaldan , CPU -ga xumaaday , ama cillad ku timid taageerahaaga ama sahayda korontadu waa sababaha macquulka ah ee BSOD -kan . Waxa kale oo ay dhici kartaa haddii aad ka badan tahay CPU- gaaga^(CPU) . Fariinta ayaa bixinaysa tafaasiil dheeraad ah. Wixii kaalmo dheeraad ah eeg KB137539 .

JOOJI 0x000000D8^{(STOP 0x000000D8)} ama DRIVER_USED_EXCESSIVE_PTES

Tani waxay muujisay in darawalka si liidata u qoran uu keenayo in kombuyutarkaagu codsado qadar badan oo xusuusta kernelka ah. Talooyinka cilad-bixinta ayaa la mid ah kuwa laga helay fariinta STOP 0X3F . KB256004 ayaa ku caawin doonta

JOOJI 0X000000EA^{(STOP 0X000000EA)} ama THREAD_STUCK_IN_DEVICE_DRIVER

Waxay dhici kartaa ka dib markaad rakibto adabtarada fiidiyooga cusub ama darawal muuqaal ah oo la cusboonaysiiyay (oo si liidata u qoran) Beddelka adabtarada fiidyaha ama isticmaalka darawal fiidyow kale ayaa ku caawin kara. Eeg KB293078 .

JOOJI 0XC000021A^{(STOP 0XC000021A)} ama STATUS_SYSTEM_PROCESS_TERMINATED

Tani waxay dhacdaa haddii ay jirto dhibaato ammaan oo halis ah Windows . Nidaam hoose, sida Winlogon ama CSRSS waa la jabsaday; ama ay sabab u tahay is-maandhaafka faylalka nidaamka; ama haddii ogolaanshaha nidaamka si qaldan wax looga beddelay. Sababta caadiga ah ee dhibaatadan waa qaar ka mid ah barnaamijyada xisbiga 3aad. Isku day inaad aqoonsato barnaamij kasta oo cusub oo aad rakibtay oo ka saar.

JOOJI 0XC00000221^{(STOP 0XC00000221)} ama STATUS_IMAGE_CHECKSUM_MISMATCH

Tani waxay muujinaysaa faylka bogga dhaawacmay; ama disk ama fayl musuqmaasuq; ama qalab khaldan. Khaladka ayaa tilmaamaya nooca saxda ah iyo magaca faylka nidaamka dhaawacmay. Waxaa laga yaabaa inaad isticmaasho deegaanka^{(Environment)} soo kabashada ee Windows ama Nidaamka Soo Celinta ama ^{(System Restore)}Isku xidhka Wanaagsan^{(Known Good Configuration)} ee Ugu Danbeeyay si loo xalliyo arrintan.

REGISTRY_ERROR

Ciladan joogsigu waa naadir waxaana sabab u ah guuldarada in si sax ah loo akhriyo diiwaanka Hard Disk-ga. Waxa ugu fiican in la isku dayo oo dib loo soo celiyo diiwaanka kaydkaaga.

DIIVIDE_BY_ZERO_ERROR

Ciladan joogsiga waxaa keenay codsi isku dayaya inuu eber u qaybiyo. Haddii aad hesho ciladan oo aadan garanaynin codsiga sababay, waxaa laga yaabaa inaad rabto inaad tijaabiso oo aad baarto qashinka xusuusta.

KMODE_EXCEPTION_NOT_HANDLED

Dareewalka aaladda si khaldan loo habeeyey wuxuu badiyaa keena khaladkan. Way adag tahay in la go'doomiyo oo cilad-baadhis lagu sameeyo.

INVALID_PROCESS_ATTACH_ATTEMPT

Bugcode 0x5 waxa uu tusinayaa in habka kernel-ku uu isku dayay in uu ku xidho hannaan kale. Si aad u caawiso ogaanshaha, isticmaaluhu waa inuu ogaadaa dhammaan codsiyada fulinayay wakhtiga guuldarada. Ma jiro soo kabasho ama wax ka-kabasho.

HARDWARE_INTERRUPT_STORM

Ciladan oo kale waxaa badanaa keena darawal si liidata u qoran ama firmware. Way adag tahay in la cilad bixiyo, laakiin Maareeyaha Aaladda^{(Device Manager)} ama Qalabka Macluumaadka Nidaamka^{(System Information)} ayaa ku caawin kara.

INACCESSIBLE_BOOT_DEVICE

Ciladan joogsigu waxay dhacdaa marka Windows ay dhib kala kulanto wax ka akhrinta Hard Disk-ga. Khaladkan waxa sababi kara darawalka aaladda oo khaldan. Waxa kale oo aad isku dayi kartaa in aad isticmaasho antivirus-kaaga.

PFN_LIST_CORRUPT

Ciladan Bugcode 0x4E waxaa badanaa sababa RAM khaldan . Waxaa laga yaabaa inaad rabto in RAM- kaaga la hubiyo ama la beddelo. Haddii taasi shaqayn waydo, ma jirto soo kabasho kale oo la yaqaan

MACHINE_CHECK_EXCEPTION

Haddii aad dhaaftay CPU gaaga , tani waxay keeni kartaa. Sidoo kale hubi tamartaada.

MULTIPLE_IRP_COMPLETE_REQUESTS

Bugcode 0x44 wuxuu^{(Bugcode 0x44)} muujinayaa cilad ku timid macquulnimada darawalnimada. Tan waxaa loo arkay in ay ku dhacayso nidaam aad loo raray. Ma jiro soo kabasho ama wax ka-kabasho.

NMI_HARDWARE_FAILURE

Caadi ahaan waxaa sababa SIMMS xun . Waxa ugu fiican inaad wacdo iibiyahaaga qalabka.

Waxa kale oo laga yaabaa inaad rabto inaad qaadato caawinta BlueScreenView . Waa utility kaas oo daajiya dhammaan faylashaada minidump ee la sameeyay intii lagu jiray shilalka 'shashada buluuga ah ee dhimashada' oo muujisa macluumaadka ku saabsan dhammaan shilalka hal miis. Shil kasta, BlueScreenView waxay soo bandhigaysaa magaca faylka minidump, taariikhda/waqtiga shilka, macluumaadka shilalka aasaasiga ah ee lagu soo bandhigay shaashadda buluuga ah ( Koodhka Hubinta Bug^{(Bug Check Code)} -ga iyo 4 cabbirrada), iyo faahfaahinta darawalka ama moduleka suurtagalka ah ee sababay shilka ( Magaca faylka, magaca badeecada, sharraxaadda faylka, iyo nooca faylka). Shil kasta oo lagu soo bandhigo muraayadda sare, waxaad arki kartaa faahfaahinta wadayaasha aaladaha lagu soo raray inta lagu jiro shilka ee shayga hoose. BlueScreenViewsidoo kale waxay calaamadisaa darawalada ciwaanadooda laga helay shilka, si aad si fudud u heli karto darawaliinta laga shakisan yahay ee suurtogalka ah inay sababeen shilka.

Ilaha Dheeraadka ah:^{(Additional Resources:)}

1. Ku falanqee qashinkaaga shilkaaga WhoCrashed^{(Analyze your crash dumps with WhoCrashed)}
2. Liiska hubinta kutaanta Windows ama Jooji Koodhadhka Khaladka .

Akhri^(Read) : Purple, Bunni, Jaalle, Casaan, Shaashadda Cagaaran ee Geerida ayaa la sharaxay .

Troubleshoot Windows Blue Screen of Death or Stop Errors

Thiѕ guide will help you understand, analyze, troubleshoot and fix Windows Blue Screen of Death, Stop Errors, Error Codes, Bug Check errors, system crash errors, system fault, kernel error crashes in Windows 11/10/8/7. When Windows encounters a condition that compromises safe system operation (i.e., a “bug”), the system halts.

Blue Screen of Death in Windows 11/10

This condition is called a ‘bug check‘. It is also commonly referred to as a system crash, a kernel error, a system fault, or a Stop Error.

In Windows XP, the Windows Error Reporting system was essentially manual but has now been improved & streamlined in Windows 7 & Windows Vista. While this may be the case, Blue Screens haven’t just vanished. You may still get to see them on Windows 7/8 too.

Usually, when a BSOD occurs, it stays for a second before the PC immediately restarts. This way we are unable to read what is written. To get around it, one has to disable the auto PC restart option from the StartUp & System Recovery settings. Knowing the error code can help identify the problem/solution. Do it as follows:

Disable UAC. Control Panel > System And Maintenance > System > Advanced System Settings > Advanced tab > Under Startup And Recovery > Click Settings > Clear the Automatically Restart check box > click OK. Enable UAC.

Windows will attempt to fix the problem on its own in most cases, but if it cannot recover on its own, it will cause a blue screen.

Blue Screen Errors in Windows 11/10

Users of the Windows system are sure to have experienced, at one point or another, the terrors of “The Fatal Exception”, commonly called the “Blue Screen Of Death”, or BSOD. Although the BSOD has largely been thrown onto the software slag heap, in Vista, crashes haven’t been totally banished. When Windows encounters a condition that compromises safe system operation (i.e., a “bug”), the system halts. This condition is called a ‘bug check’. It is also commonly referred to as a system crash, a kernel error, a system fault, or a Stop error. When Windows encounters such a serious error that forces it to stop running, it displays a BLUE SCREEN OF DEATH or just ‘lovingly’ called BSOD!

In Windows 11/10/8/7, unlike XP, where the system was essentially manual, the Windows Error Reporting has been improved & streamlined in Windows 7 & Vista. One had to follow-up to see if a solution had become available. This was a rather painful process. In Windows 10/8/7/Vista, this entire reporting and follow-up process is automated.

These days a Windows 11/10/8/7/Vista user is more often likely to see a message as follows: “Microsoft Windows Operating System is not responding.” And users are given two possibilities. They can either “Close the program” or “Wait for the program to respond.” One waits in the hope that the issue will be resolved, or else then one just closes the program and gets prepared to lose information. At least, these messages look less daunting.

The BSODs on the other hand were/are quite traumatic and frustrating, to say the least!

The exact text of a Stop error varies, according to what caused the error. But the format is standardized and is made up of 3 parts:

• PART 1: Symbolic error name: This is the Stop Error message that is given to the OS and corresponds to the Stop Error number that appears.
• PART 2: Troubleshooting recommendations: This text applies to all Stop Errors of that particular type.
• PART 3: Error number and parameters: Its the bug check information. The text following the word STOP includes the error number, in hexadecimal notation, and up to four parameters that are typical of this error type.

In general, there are not too many options for any type of recovery. Normally, one tries to just “reboot” the PC in the hope that the BSOD occurred because of a rare condition of some driver which was overlooked in coding and testing. But if the BSOD persists, there are some tactics that may be employed to repair the system there are over 250 documented BSOD codes.

Take, for example, the most common BSOD:

Bugcode 0xA – IRQL_NOT_LESS_OR_EQUAL

This is a fairly common BSOD that occurs when a driver has illegally accessed a memory location while NT is operating at a specific IRQL. This is a driver coding error, akin to trying to access an invalid memory location.

Parameters:
1 – memory location that was referenced
2 – IRQL at time of reference
3 – 0 == read, 1 == write
4 – code addressed which referenced memory
Recovery/Workaround:
There is none. This is a fatal error and is a driver coding error.

What is the first step to take to resolve a Blue Screen of Death error

The BSODs or Stop Errors in Windows 10 appear to be better and more user-friendly and easier on the eyes. But they don’t give many details. You have to force your OS to display Stop Error information in Windows 10.

How to Debug Memory Dumps

To know how to debug Memory Dumps so that you can find out the cause for your BSOD, download and install the Microsoft Debugging Tools. Make certain that your page file still resides on the system partition. Otherwise, Windows will not be able to save the debug files.

You can use Crash Dump Analyzer software to analyze crash dump reports.

TROUBLESHOOT WINDOWS STOP ERRORS/BSODs

1. First & Foremost, see if a System Restore can resolve this issue.
2. Else, then run your anti-virus and anti-spyware and your PC Junk/Registry Cleaner.
3. After this, Run the Windows Check Disk Utility.
4. Then try to identify if you’ve made any software or hardware change or modification.
5. In most cases, the software is the victim and not the cause of BSOD’s. So don’t rule out hardware problems. It could be damaged hard disks, defective physical RAM, overheated CPU chips or anything else!
6. Check if you can see a driver’s name in the error details. If you can, then simply disabling, removing, or rolling back that driver to an earlier version can help solve that problem. Network interface cards, disk controllers, and Video Adapters are the culprits, most often.
7. Check your memory. Use the Windows Memory Diagnostic Tool. Go to Control Panel and type “memory” in the Search box. Under Administrative Tools, click Diagnose Your Computer’s Memory Problems. In the Windows Memory Diagnostics Tool, shown here, select one of the options.
8. Check your system BIOS carefully Is an update available from the manufacturer of the system or motherboard? Check the BIOS documentation carefully; resetting all BIOS options to their defaults can sometimes resolve an issue caused by over tweaking.
9. Check if you are low on system resources? Sometimes a critical shortage of Disk Space or RAM can cause BSOD’s.
10. Check if a system file has been damaged? Work in Safe Mode, as only the core drivers and services are activated. If your system starts in Safe Mode but not normally, you very likely have a problem driver. Try running Device Manager in Safe Mode and uninstalling the most likely suspect. Or run System Restore in Safe Mode.
11. Run the Windows 10 Blue Screen Troubleshooter.

MSDN print-link BlueScreenView

What to do if you suspect that a Driver is causing BSOD’s

If you suspect that a buggy device driver is at fault for the BSOD’s, call upon a lesser-known but powerful troubleshooting tool called the Driver Verifier Manager. Enter verifier in the search bar and hit enter to bring up Verifier.exe. Run As Administrator. This tool helps you to actually identify the flawed driver.

Now select “Create Standard Settings”. Next, select the type of drivers you want to verify. Unsigned drivers are a likely cause of problems, as they are created for older versions of Windows. Click Next, till completion.

Driver Verifier Manager works in the following manner. Instead of your machine throwing up an undecipherable BSOD at you, at any time, you can make Driver Verifier stop your computer at startup, with a BSOD which will explain the actual problem, rather accurately! You can then choose to resolve the problem by either updating, rolling back or uninstalling the offending driver.

Please do note that in the rare eventuality the Driver Verifier Manager does find a non-conforming driver; there could be a possibility that it may not be the offending one. So do exercise extreme caution. Regard the identified Driver/s with suspicious and exercise your best judgment in such a case.

Having narrowed down to the problematic Driver, you have three options: Update, Roll Back or Uninstall the Device Driver.

To do that, open Device Manager. Open the properties dialog box for the device, and use the following buttons on the Driver tab to perform maintenance tasks:

• Update Driver: This will start the Hardware Update Wizard.
• Roll Back Driver: This will uninstall the most recently updated driver and will roll back your configuration, to the earlier version.
• Uninstall Driver: This will uninstall completely the driver’s files and registry settings for the selected hardware.

Read: How to find which Driver is causing the Blue Screen on Windows?

List of Common Windows Blue Screen Errors & solutions

STOP 0x000000D1 or DRIVER_IRQL_NOT_OR_EQUAL

Probably the most common BSOD! This occurs when a driver has illegally accessed a memory location while NT is operating at a specific IRQL. This is a driver coding error, akin to trying to access an invalid memory location. Recovery/Workaround: Usually none. But these may help KB810093 , KB316208 & KB810980.

STOP 0x0000000A or IRQL_NOT_LESS_OR_EQUAL

A kernel-mode process or driver attempted to access a memory location without authorization. This Stop error is typically caused by faulty or incompatible hardware or software. The name of the offending device driver often appears in the Stop error and can provide an important clue to solving the problem. If the error message points to a specific device or category of devices, try removing or replacing devices in that category. If this Stop error appears during Setup, suspect an incompatible driver, system service, virus scanner, or backup program. This KB314063 may show you the direction.

STOP 0x00000050 or PAGE_FAULT_IN_NONPAGED_AREA

A hardware driver or system service requested data that was not in memory. The cause may be defective physical memory or incompatible software, especially remote control, and antivirus programs. If the error occurs immediately after installing a device driver or application, try to use Safe Mode to remove the driver or uninstall the program. For more information, see KB894278 & KB183169.

STOP 0x000000C2 or BAD_POOL_CALLER

A kernel-mode process or driver attempted to perform an illegal memory allocation. The problem can often be traced to a bug in a driver or software. It is also occasionally caused by a failure in a hardware device. For more information, see KB265879.

STOP OX000000ED or UNMOUNTABLE_BOOT_VOLUME

This occurs if Windows if unable to access the volume containing the boot files. But if you get this message while updating TO Vista, check that you have compatible drivers for the disk controller and also re-check the drive cabling, and ensure that it is configured properly. If you’re reusing ATA-66 or ATA-100 drivers, make sure you have an 80-connector cable, and not the standard 40-connector IDE cable. See KB297185 and KB315403.

STOP 0x0000001E or KMODE_EXCEPTION_NOT_HANDLED

The Windows kernel detected an illegal or unknown processor instruction, often the result of invalid memory and access violations caused by faulty drivers or hardware devices. The error message often identifies the offending driver or device. If the error occurred immediately after installing a driver or service, try disabling or removing the new addition.

STOP 0x00000024 or NTFS_FILE_SYSTEM

A problem occurred within the NTFS file-system driver. A similar Stop error, 0x23, exists for FAT32 drives. The most likely cause is a hardware failure in a disk or disk controller. Check all physical connections to all hard disks in the system and run Check Disk. KB228888 will help you.

STOP 0x0000002E or DATA_BUS_ERROR

Failed or defective physical memory (including memory used in video adapters) is the most common cause of this Stop error. The error may also be the result of a corrupted hard disk or a damaged motherboard.

STOP 0x0000003F or NO_MORE_SYSTEM_PTES

Your system ran out of page table entries (PTEs). The cause of this relatively uncommon error may be an out-of-control backup program or a buggy device driver. For more information, see KB256004.

STOP 0x00000077 or KERNEL_STACK_INPAGE_ERROR

The system has attempted to read kernel data from virtual memory (the page file) and failed to find the data at the specified memory address. This Stop Error can be caused by a variety of problems, including defective memory, a malfunctioning hard disk, an improperly configured disk controller or cable, corrupted data, or a virus infection. For additional information, click KB228753.

STOP 0x0000007F or UNEXPECTED_KERNEL_MODE_TRAP

Most likely due to a Hardware failure, like defective memory chips, mismatched memory modules, a malfunctioning CPU, or a failure in your fan or power supply are the probable reasons for this BSOD. It can also occur if you have overclocked your CPU. The message gives more details. For more help see KB137539.

STOP 0x000000D8 or DRIVER_USED_EXCESSIVE_PTES

This indicated that a poorly written driver is causing your computer to request large amounts of kernel memory. Troubleshooting suggestions are identical to those found in the STOP 0X3F message. KB256004 will help you

STOP 0X000000EA or THREAD_STUCK_IN_DEVICE_DRIVER

It could occur after you install a new video adapter or an updated (and poorly written) video driver. Replacing the video adapter or using a different video driver could help. See KB293078.

STOP 0XC000021A or STATUS_SYSTEM_PROCESS_TERMINATED

This occurs if there is a serious security problem with Windows. A subsystem, such as Winlogon or the CSRSS is compromised; or due to a mismatch in system files; or if system permissions have been incorrectly modified. A common cause of this problem is some 3rd-party programs. Try to identify any new program which you have installed and uninstall it.

STOP 0XC00000221 or STATUS_IMAGE_CHECKSUM_MISMATCH

This indicates a damaged page file; or disk or file corruption; or faulty hardware. The error will indicate the exact nature and the name of the damaged system file. You may have to use the Windows recovery Environment or a System Restore or Last Known Good Configuration to resolve this issue.

REGISTRY_ERROR

This stop error is rare and is caused due to failure to read the registry properly from the hard disk. Best to try and restore the registry from your backup.

DIVIDE_BY_ZERO_ERROR

This stop error is caused by an application trying to divide by zero. If you receive this error & don’t know which application caused it, you might want to try & examine memory dump.

KMODE_EXCEPTION_NOT_HANDLED

An incorrectly configured device driver usually causes this type of error. Difficult to isolate and troubleshoot.

INVALID_PROCESS_ATTACH_ATTEMPT

This Bugcode 0x5 indicates that a kernel process was making an attempt to attach to another process. To aid in the diagnosis, the user should note all applications that were executing at the time of the failure. There is no recovery or workaround.

HARDWARE_INTERRUPT_STORM

Such an error is usually caused by a poorly written driver or firmware. Difficult to troubleshoot, but Device Manager or System Information tool can help you.

INACCESSIBLE_BOOT_DEVICE

This stop error occurs when Windows has trouble reading from the hard disk. This error can be caused by a faulty device driver. You may also try running your antivirus.

PFN_LIST_CORRUPT

This Bugcode 0x4E error is usually caused by faulty RAM. You may want to get your RAM checked or replaced. If that doesn’t work, there is no other known recovery or workaround

MACHINE_CHECK_EXCEPTION

If you have overclocked your CPU, this could result. Also check your power supply.

MULTIPLE_IRP_COMPLETE_REQUESTS

This Bugcode 0x44 indicates a fault in driver logic. This has been seen to occur on a heavily loaded system. There is no recovery or workaround.

NMI_HARDWARE_FAILURE

Usually caused by bad SIMMS. Best to call your hardware vendor.

You may also want to take the help of BlueScreenView. It is a utility that cans all your minidump files created during ‘blue screen of death’ crashes and displays the information about all crashes in one table. For each crash, BlueScreenView displays the minidump filename, the date/time of the crash, the basic crash information displayed in the blue screen (Bug Check Code and 4 parameters), and the details of the driver or module that possibly caused the crash (filename, product name, file description, and file version). For each crash displayed in the upper pane, you can view the details of the device drivers loaded during the crash in the lower pane. BlueScreenView also marks the drivers that their addresses found in the crash stack, so you can easily locate the suspected drivers that possibly caused the crash.

Additional Resources:

1. Analyze your crash dumps with WhoCrashed
2. List of Windows Bug Check or Stop Error Codes.

Read: Purple, Brown, Yellow, Red, Green Screen of Death explained.

Related posts

• Sida loo hagaajiyo muraayadda Orange ee dhimashada gudaha Windows 11/10

• Barnaamijyada dhaliyaha Shaashadda buluuga ah ee been abuurka ah ee bilaashka ah ee Windows 10

• Hagaaji hardlock.sys Screen Blue of Death qaladka gudaha Windows 11/10

• Sida loo saxo qaladka Shaashadda Buluugga ah ee dhimashada gudaha Windows 11/10

• Hagaaji aksdf.sys Screen Blue of Death qaladka gudaha Windows 11/10

• Hagaaji Koodhka Cilada Cusboonaysiinta Windows 0x8007025D-0x2000C

• Ku hagaaji CACHE_MANAGER Shaasha buluugga ah ee Windows 10

• Waa maxay macnaha Fariintan Cilada Windows?

• Aaway faylka log ee BSOD gudaha Windows 11/10?

• Hagaaji WDF_VIOLATION Cilada Shaashada Buluuga ee Windows 11/10

• Hagaaji win32kfull.sys khaladka shaashadda buluuga ah ee gudaha Windows 10

• Hagaaji rtf64x64.sys Screen Blue of Death qaladka Windows 11/10

• Ugu Fiican Falanqeeyaha Qashin qubka Bilaashka ah ee loogu talagalay Windows 11/10

• Isku-dubarid Windows 10 si aad u abuurto faylal daadsan shaashadda buluuga ah ee dhimashada

• Xalka NIDAAMKA AAN LAGA REEBAYN (ldiagio.sys) BSOD

• Hagaaji HYPERVISOR_ERROR Shaashada buluuga ah ee Windows 11/10

• Hagaaji habraaca muhiimka ah ee dhintay, 0x000000EF khaladka gudaha Windows 11/10

• Hagaaji Cillada galka Xogta KerNEL (Msis.SYS) gudaha Windows 11/10

• Hagaaji shaashadda buluuga ah ee khaladka dhimashada Windows 10

• Khaladaadka dabinka KernEL-ka ee aan la fileyn ee gudaha Windows 11/10