The Blue Screen Of Death

Status
Not open for further replies.

karansthink

Broken In
:mad: When I turned off my computer I got this:

STOP: c000021a {Fatal System Error}
The Windows Sub-system process terminated unexpectedly with a status of c0000005 (0x7c91888f 0x005cc64).
The system has been shutdown.


System specs:
Laptop
Core2Duo T5500
Win xp prof sp2
1 GB RAM
100 GB HDD
945 intel motherboard
DVD-RAM drive

Softwares:
Avast antivirus
Zone Alarm Pro
Vista transformation pack 6.0
Windowsblinds 5
MS office 2003
Yahoo Widgets
Cyberlink Power dvd
VLC Player
WMP 11
Internet explorer 7
Mozilla Firefox 2
7 zip
yahoo messenger
Foxit pdf reader
Tweak ui etc.
 

shantanu

Technomancer
LAPTOPS ArE CORE DUO i think..
UNINSTAll all THE UNNECESARY SOFTWARES AND LEAN UP YOUR REGISTRY With a reg. cleaner tool.
 

anandk

Distinguished Member
refer the bsod primer or get it auto-analysed on-line
more here *www.thinkdigit.com/forum/showthread.php?t=38732&highlight=blue+screen
or
*www.aumha.org/win5/kbestop.php
 

azhararmar

Broken In
Blue Screen of Death mainly Causes Due to the Following Reasons...

If you Can Boot in Safe Mode..then the Reasons are the following....

1.Grapics Driver(Try to Uninstall it in Safe Mode)
2.Any other Drivers or Software Installed...

If you Cannot Boot In Safe Mode then the Reasons are the Following...

1.It is Mainly Caused to the Problem of Ram(Try Changing the RAM)
2.It may be other also Like Hard Disk..(Try Changing the Device)...
 

gary4gar

GaurishSharma.com
To resolve this issue:
1. Create a parallel installation of Windows NT.For additional information how to do so, click the article number below to view the article in the Microsoft Knowledge Base:
259003 (*support.microsoft.com/kb/259003/EN-US/) How and Why to Perform a Parallel Installation of Windows NT 4.0
2. Start your computer to the parallel installation of Windows NT, and then start Registry Editor.
3. On the Window menu, click HKEY_LOCAL_MACHINE on Local Machine.
4. On the Registry menu, click Load Hive.
5. Type the path to the System hive of the prior installation, typically %systemroot%\system32\config\system, and then click Open.
6. When you are prompted for the name of the key, type TEST, and then view the following registry entry:
HKEY_LOCAL_MACHINE\TEST\Select
7. Note the setting for the Current DWord value in the preceding registry key. This is typically 0x1, and is represented as CURRENT:Reg_Dword:0x1. This value indicates that the "CurrentControlSet" for your original Windows NT installation corresponds to ControlSet001 in this window. A value of 2 would indicate that the "CurrentControlSet" for your original Windows NT installation would correspond to ControlSet002, and so on.
8. Locate the following registry key
HKEY_LOCAL_MACHINE\TEST\ControlSetXXX\Control\Session Manager
where XXX is the CurrentControlSet that you identified in the preceding step.
9. Under the Session Manager key, note and then delete any PendingFileRenameOperations entries.
10. Click the TEST hive, and then click Unload Hive on the Registry menu.
11. On the Registry menu, click Load Hive.
12. Type the path to the Software hive of the prior installation, typically %systemroot%\system32\config\Software, and then click Open.
13. When you are prompted for the name of the key, type TEST2.
14. Remove any PendingFileRenameOperations entries in the following registry keys:
HKEY_LOCAL_MACHINE\TEST2\Microsoft\Windows\CurrentVersion\RunOnce

HKEY_LOCAL_MACHINE\TEST2\Microsoft\Windows\CurrentVersion\RunOnceEx
15. Click the TEST2 hive, and then click Unload Hive on the Registry menu.
16. Quit Registry Editor, and then restart your original installation.


source
 

Chetan1991

Youngling
You can use regestry cleaning softwares like TuneUp to check any fault in your registry structure.If it doesn't works,backup your imp. data to a removable media(CD etc...) and reinstall your OS.
 
Status
Not open for further replies.
Top Bottom