Sunday, November 2, 2008

Windows XP - System failure

Last month, My home PC did not boot at all. I searched the solutions on Internet and tried many things. Even Microsoft's knowledge base articles were not solved my problem.

Problem 1: winlogon.exe - Application Error
Initially I got the WinLogon.exe error dialog box and then it was restarted automatically again and again. The dialog box message was like below:
-----------------------------------------
winlogon.exe - Application Error
------------------------------------------
The instructions at "0x759723ee" referenced memory
at "0x00000000". The memory could not be "read".

Click on OK to terminate the program
Click on CANCEL to debug the program
-------------------------------------------

System was restarted, if I click OK butto or Cancel Button. Then I restarted the system by all startup modes. I have explained all these modes in my previous post - Strange behavior with Service Pack . None of the modes helped me. I got blue screen, while I was trying by startup mode - Disable Automatic restart on system failure. I searched on net and applied many solutions. None of them worked out...

Solution 1
From softwaretipsandtricks.com

  1. Boot with winxp cd
  2. Log in to recovery console
  3. chkdsk /r


Solution 2
This is a problem with virtual RAM, I've had it before with various steam games, try lowering the size of the paging file (I'm pretty sure you can do that from the recovery console) or deleting it completely just so you can log on, then set the paging file back up again, with a lower size. This problem also arises if you have page files on more than one hard disk, its better to have 1 3GB page than 2 1.5GB ones on separate hard disks.

Solution 3
It's simple, just download hijack.exe and killbox.exe. Run Hijack. Look for these types of process in the hijack log:
O20 - Winlogon Notify: arergiti - arergiti.dll
O20 - Winlogon Notify: bdicjulx - bdicjulx.dll (this is only an example, it will not be the same dll files in your case, just put the types of these trojans for your understanding) kill all these dll files comes under the heading "Winlogon notify" using killbox (use the option 'delete on reboot')..and it is simple as that...nothing to worry..Just check for Winlogon nofify errors and delete all these dlls which fall under this category (i.e. "winlogon notify")

Solution 4
mbrando.com
We’ve had 15-20 machines suddenly start doing this in the last month. I’ve narrowed it down to an issue with the RPC and DCOM services; by default they are both set to “Restart the computer” if they can’t start.
We’re still working with Microsoft to determine why this suddenly started, but we have at least figured out that after several reboots and if you let it sit at the logon screen for a while before attempting to logon, you can sometimes get it to boot all the way into Explorer. If you get that lucky, go into your services and set the recovery options for both services to “Restart the service” instead of “Restart the computer”.

Solution 5
I had the same issue and I was able to hit CTRL+ALT+DEL before the error message popped up and then login and do a system restore. Not sure if that will work for anybody else, but just thought I’d throw this out there (problem happened after the Monday update from MS Update).

Solution 6
I was getting the same error message. But used the click here underlined for details. Stated the problem was with the uxtheme.dll file. So from msconfig, I uncheck the theme services. Rebooted with no errors. Realized that it turned off my XP Theme. So went into Services from Admin Tools, and set disable to automatic and click the Start button, to start the service. Then rebooted. Have not received the error since.

UXTheme is the XP Theme package, but was recently updated in a patch. So maybe chalk it up as a bad install. Now repaired.

Another option is to go to c:\windows\system32 and find the uxtheme.dll file. Rename it to uxtheme.dll.old. Then restart. Should repair, reinstall itself.

Problem 2: Stop 0x000000B4 The Video Driver Failed to Initialize
After doing Chkdsk command, I was getting the blue screen. After this stage, I didn't get Winlogon.exe - Application Error. I did Google search for this system error and I got few solutions for that.

Solution 7
From forums.techguy.org
It may be the built in VGA driver is corrupt. You could try replacing it in Recovery Console from the CD. I've attached a screen shot of the commands.

To do this boot into the Recovery Console. This should leave you at a C:\Windows prompt. Enter the following commands:

cd system32
ren vga.dll vga.dllold
ren vga.drv vga.drvold
cd drivers
ren vga.sys vga.sysold
expand d:\i386\vga.sy_
cd ..
expand d:\i386\vga.dl_
expand d:\i386\vga.dr_


Exit, and then try Safe Mode and/or Enable VGA Mode.

Solution 8
From forums.cnet.com
To anyone with this same problem - here's how I recovered my files:

Changed my Bios to boot from Windows XP DVD-ROM.
Installed XP to the SAME PARTITION as my corrupt one, only I created a new folder entitled XP_2.
It did get stuck once on the "34-min left" but I just re-tried and it worked the second time.
When it was done installing, it asked me for an account name - DO NOT NAME THE PROFILE ACCOUNT THE SAME AS ANY OF YOUR ALREADY EXISTING ACCOUNTS. I made a generic account name.
When it was done installing, go into your hard drive, documents and settings and voila! There you will see your other user accounts along with their desktops and my document folders. Also, you will be able to see your Program Files and any other hard drive folders you need.

Solution 9
One other thing Microsoft help says may cause the B4 STOP is a port conflict. If your laptop has a parallel port, disable in BIOS or change I/O address to 0378 from 03BC.

Solution 10 - From Microsoft Knowledge base
Solution - STOP: 0x000000B4 The video driver failed to initialize.
Solution - STOP: 0x000000B4 The video driver failed to initialize
SYMPTOMS
When you try to start Windows 2000, you may receive the following error message (on a blue screen):
*** STOP: 0x000000B4
The video driver failed to initialize.

Additionally, you cannot start Windows in Safe mode.

Solution 11 - Virus Infection
None of these solutions were worked for me. microsoft.public.windowsxp.customize. I got a idea from this post. I did following steps.

  • Removed the hard-disk from my PC.

  • Have connected the my PC through external drive to my Laptop. Both systems are having Windows XP SP2

  • Ran the anti-virus program for G drive, which is C Drive for my home PC.

  • 2 DLLs (under C:\Windows\System32) got infected. Removed those files.

  • Deleted 2 files under C:\Windows\System32, which are created on that day (based on the time-stamp).

  • Connected the hard-disk to my home PC again. Started my PC through WinXP setup CD.

  • Automatically Upgrade workstation was executed from Windows CD (Repair Windows Installation).

  • Rebooted System successfully and did not get any system errors..

3 comments:

Logan said...

I face the same problems sometimes too. What I did is to run my computer through a computer check up and it was all fixed. If you are interested you can do the same at http://www.pcaholic.com. Apparantly they provide alot of free tools to help in speeding up the computer.

Microsoft Help Canada said...

Thanks for Sharing this usefull info.

Palani Selvam said...

Welcome and Thanks for the comments. Now the PC is alright..