Myanmar IT Resource Forum
Myanmar IT Resource Forum
Myanmar IT Resource Forum

You are not connected. Please login or register

View previous topic View next topic Go down  Message [Page 1 of 1]

solakoko

solakoko
Moderator



Moderator
Using
Last Known Good Configuration


Hardware ေတြ၊ System Configuration ေတြ ေျပာင္းလိုက္လို႔ Windows က boot
မလုပ္ေတာ့တာမ်ိဳး၊ အရင္လိုေကာင္းေကာင္း အလုပ္မလုပ္ေတာ့တာမ်ိဳးဆိုရင္….

1. Computer ကို restart လုပ္ၿပီး Power On Self Test လုပ္အၿပီး၊ OS ကို load
မလုပ္ခင္မွာ F8 key ကို ႏွိပ္ပါ။ Windows Advanced Startup Option page
ေပၚလာပါလိမ့္မယ္။


2. Last Known Good Configuration option
ကိုေရြးၿပီး Windows တက္ပါ။

(မရရင္ Safe Mode ကိုသံုးပါ။)
Using Safe Mode
Windows
ဟာ hang သြားတယ္၊ သူ႔ဟာသူ restart က်က်သြားတယ္၊ blue screen error
တက္ၿပီးရပ္သြားတယ္၊ screen မွာ ဇင္းေၾကာင္းေတြ၊ အေျပာက္ေတြေပၚၿပီး
ရပ္သြားတယ္၊ Last Known Good Configuration လဲ လုပ္ၿပီးလို႔လဲ
မရေသးဘူးဆိုရင္….

1. Computer ကို restart လုပ္ၿပီး Power
On Self Test လုပ္အၿပီး၊ OS ကို load မလုပ္ခင္မွာ F8 key ကို ႏွိပ္ပါ။

2. Safe Mode option ကို ေရြးၿပီး Enter
ကို ႏွိပ္ပါ။

3. Admin right ရွိတဲ့ User account
တခုခုနဲ႔ Logon လုပ္ပါ။ (မေသခ်ာရင္ Administrator နဲ႔ Logon လုပ္ပါ။)

4. ‘Running in safe mode’ dialog box
မွာ Yes သို႔ OK ကို click ပါ။

5.မၾကာေသးခင္က အေျပာင္းအလဲ လုပ္ထားတဲ့ system configuration ေတြကို
မူလအတိုင္း ျပန္ေျပာင္းပါ၊ hardware အသစ္တပ္မိရင္လဲ ျဖဳတ္ၿပီး ျပန္စမ္းပါ၊
ဒါမွမရေသးရင္ System Restore ကို သံုးၿပီး နဂိုေကာင္းေကာင္းအလုပ္လုပ္တဲ့
State ကို ျပန္ Restore လုပ္ပါ။

(အဲဒါမွ မရေသးရင္ေတာ့ Recover Console
ကိုသံုးၿပီးေျဖရွင္းရပါမယ္၊ အဲဒီေခါင္စဥ္မွာ ဆက္ဖတ္ပါ။)

Using Boot Log to Trace Problem
ဘယ္ driver ေတြ၊ service ေတြက Windows
မတက္ႏိုင္ေအာင္ ျပႆနာေပးေနလဲသိရေအာင္ဆိုရင္ေတာ့…..

1. Windows Advanced Startup Menu
ကိုဝင္ပါ။

2. Enable Boot Logging option နဲ႔
Windows တက္ပါ။

3.တကယ္လို႔ Windows တက္သြားရင္၊ Windows folder ထဲက NTBLOG.TXT file
ကိုဖြင့္ၿပီး ဘယ္ driver or service ေတြ load မလုပ္သလဲ၊
ျပႆနာတက္ေနလဲၾကည့္ပါ။ (စာရြက္မွာခ်ေရးထားရင္ ပိုေကာင္းပါတယ္။)

Using Recovery Console
Windows
က Normal ေရာ၊ Safe Mode ေရာ မတက္ေတာဘူး (သို႔) missing or corrupt error
ျပေနၿပီဆိုရင္ေတာ့ Recovery Console ကို သံုးရပါေတာ့မယ္။ (Recovery
Console ထဲကို ဝင္နည္းကိုေတာ့ Troubleshooting Windows XP post
မွာပဲသြားဖတ္လိုက္ပါ။ အဲ့ post ကို အေသးစိတ္ေရးခ်င္လို႔ အခ်ိန္ယူေနတာပါ။
ဒီမွာေတာ့ Console ကို သံုးၿပီး Common Startup Error ေတြ
အလြယ္ေျဖရွင္းနည္းကိုပဲေရးမွာပါ။)

Disable service or driver
ေစာေစာက NTBLOG.TXT file ထဲက
ျပႆနာေပးႏိုင္မယ္ထင္တဲ့ service/driver ေတြကို disable လုပ္ပါမယ္။


Console
မွာ listsvc လို႔ ႐ိုက္ထည့္ပါ။ computer မွာ ရွိတဲ့ service/driver name,
startup type, ျဖစ္ႏိုင္ရင္ friendly name ပါျပေပးပါမယ္။ ကိုယ္
enable/disable လုပ္ခ်င္တဲ့ name ကို မွတ္ထားပါ။

disable လုပ္ခ်င္ရင္ disable service/driver-name
enable လုပ္ခ်င္ရင္ enable service/driver-name
Fixing MBR
လြယ္ပါတယ္။ Console မွာ fixmbr
လို႔႐ိုက္ၿပီး Enter ေခါက္လိုက္႐ံုပါပဲ။ ၿပီးရင္ Ctrl + Alt + Del
ႏွိပ္ၿပီး restart လုပ္ပါ။

Fixing Boot Sector
ဒါလဲလြယ္ပါတယ္။ Command ရဲ႕ syntax က fixboot
driveletter:
ပါ။ မ်ားေသာအားျဖင့္ေတာ့ fixboot
C:
လို႔ပဲ႐ိုက္ရတာမ်ားပါတယ္။ restart လုပ္ပါ။

MBR
နဲ႔ Boot Sector ပ်က္လို႔ Windows မတက္တာဆိုရင္ေတာ့ အဲ command ႏွစ္ခုကို
တစ္ခါ run ၿပီး႐ံုနဲ႔ လံုေလာက္ပါၿပီ။ ထပ္ run ဖို႔ မလိုပါဘူး။
အခ်ိန္ရရင္ေတာ့ CheckDisk ပါ run ေပးပါ။ syntax က chkdsk driveletter:
/p /r
ပါ။ e.g: chkdsk c: /p /r

Fixing NTOSKRNL Errors
‘NTOSKRNL Missing or Corrupt’ error
ျပေနၿပီဆိုရင္ေတာ့….

1. Recovery Console ကိုဝင္ပါ။

2.i386 folder ထဲကိုဆက္ဝင္ပါ။ (i386 folder ကို drive D ထဲကို copy
ကူးထဲ့ထားမယ္ဆိုရင္ cd d:\i386 ေပါ့။ အဲလိုမဟုတ္ဘူး CD ထဲမွာဆိုရင္ေတာ့ cd
cd-driveletter:\i386 ေပါ့။)

3. ၿပီးရင္ expand ntkrnlmp.ex_
%systemroot%\system32\ntoskrnl.exe
လို႔ ႐ိုက္ၿပီး Enter။
Restart.

Fixing HAL Error
‘HAL.DLL Missing or Corrupt’ error
ဆိုရင္ေတာ့….

Recovery Console မွာ bootcfg
/rebuild
လို႔႐ိုက္ၿပီး Enter. Restart

Fixing Corrupted or Missing
\Windows\System32\Config errors

‘\Windows\System32\Config\System’ or
‘\Windows\System32\Config\Software’ erros ဆိုရင္ေတာ့…

System file အတြက္ဆိုရင္
cd %systemroot%\system32\config
ren system system.bad
copy %systemroot%\repair\system
Software file အတြက္ဆိုရင္
cd %systemroot%\system32\config
ren software software.bad
copy %systemroot%\repair\software
Fixing NTLDR or NTDETECT Not Found
Errors

‘NTLDR is Missing’ or ‘[You must be registered and logged in to see this link.]’ is missing’ error ဆိုရင္….
expand cd-driveletter:\i386\ntldr c:\
or
expand cd-driveletter:\i386\[You must be registered and logged in to see this link.] c:\
ကဲေတာ္ေတာ္ေလးစံုသေလာက္ရွိသြားပါၿပီ။
ကၽြန္ေတာ္သိတာလဲကုန္ၿပီ။ အဲဒါမွမရရင္ေတာ့ Windows ကို Repair သာလုပ္ေပေတာ့။

အဲ… Blue Screen of Death (BSOD) Stop
Error ေတြ နည္းနည္းေျပာဦးမယ္။ translate ေတာ့မလုပ္ေတာ့ဘူး။ အိပ္ခ်င္ၿပီ။

Troubleshooting
Tips for Stop Errors

Error message

Troubleshooting recommendation

Stop 0×0000000A

Replace/remove hardware, roll back,
or update driver.


Stop 0×0000001E

Recently installed or defective
software crashed the OS. Report the error and update or remove the
software.




Stop 0×00000024

Probable disk or file system error.
Run CHKDSK to determine disk problems.


Stop 0×0000002E

Defective
or mismatched memory, including motherboard, Level 2 cache, or video
RAM. Replace memory or system board. May also be caused by pagefile or
disk error. Run CHKDSK to determine disk/file system problems.


Stop 0×0000003F

Removing or reinstalling upgraded
software may solve this problem.


Stop 0×00000050

Replacing
RAM memory, L2 RAM cache, video RAM, or incompatible software,
including remote control and antivirus software, are possible fixes.


Stop 0×00000077

Run
a virus protection scan to locate and remove any possible virus
infections. Run CHKDSK or other disk-repair diagnostic or replacing the
hard drive may resolve this problem.


Stop 0×00000079

This
error most often occurs when ACPI firmware settings are changed. For
example, you might install Windows XP Professional on an x86-based
computer with the firmware ACPI enable option enabled and later decide
to disable it.


This error can also result when
mismatched single and multiprocessor configuration files are copied to
the system.



Re-enable ACPI or run Windows
installation to repair the installation to match the present hardware
configuration.



Stop 0×0000007A

Run CHKDSK or other disk-repair
diagnostic or replacing the hard drive or controller may resolve this
problem.




Stop 0×0000007B

Installing
incorrect device drivers when installing or upgrading storage adapter
hardware typically causes stop 0×7B errors. Stop 0×7B errors could also
indicate possible virus infection.


Run
a virus protection scan to locate and remove any possible virus
infections. Run CHKDSK or other disk-repair diagnostic or replacing the
hard drive may resolve this problem.


Stop 0×0000007F

This
could be caused by software problems or hardware failures. Removing and
reinstalling updated drivers, software, or hardware may solve this
problem.


Stop 0×0000009F

The
Stop 0×9F message indicates that a driver is in an inconsistent or
invalid power state. Restarting the PC may resolve this problem.


Stop 0xBE

Removing and reinstalling updated
drivers may solve this problem.


Stop 0xC2

This message is typically due to a
faulty driver or software. Removing and reinstalling updated drivers may
solve this problem.




Stop 0×000000CE

This
message indicates that a driver failed to cancel pending operations
before exiting. Restarting the PC may resolve this problem.


Stop 0×000000D1

Drivers
that have used improper addresses typically cause this error. Removing
and reinstalling updated drivers may solve this problem.


Stop 0×000000D8

Drivers
that have used improper addresses typically cause this error. Removing
and reinstalling updated drivers may solve this problem.


Stop 0×000000EA

Removing and reinstalling updated
drivers, software, or hardware may solve this problem.


Stop 0×000000ED

This
error might also occur during an upgrade to Windows XP Professional on
systems that use higher throughput ATA disks or controllers with
incorrect cabling. In some cases, your system might appear to work
normally after you restart. Installing an 80-wire IDE cable may solve
this problem.


Stop 0×000000F2

Edge-level
and level-interrupt-triggered devices are incorrectly assigned the same
IRQ (for example, a serial port and a peripheral component interconnect
(PCI) SCSI controller). Resetting Plug and Play/ESCD values in BIOS may
solve this problem.


Stop 0xC000021A

Windows security system is unable to
function. Running Windows setup to reinstall/repair may solve this
problem.




Stop 0xC0000221

Indicates
driver, system file, or disk corruption problems (such as a damaged
paging file). Faulty memory hardware can also cause this Stop message
to appear. Replacing memory or resetting the pagefile may solve this
problem.



Ref:
Windows XP Cookbook
itmen blog မွ ကူးယူေဖာ္ျပပါသည္

View previous topic View next topic Back to top  Message [Page 1 of 1]

Permissions in this forum:
You cannot reply to topics in this forum

 

Free forum | ©phpBB | Free forum support | Report an abuse | Forumotion.com