Blue screen on every startup...

[harry]

Something strange just happened to my XP...

At one point, I noticed strange changes in font sizes and some of the
graphical elements of the GUI (such as the "X" to close windows)
disappeared (I have various up to date spyware/virii scanners). I
thought an application caused this, so I wanted to close it from the
task manager... but pressing Ctrl-Alt-Del did not bring it up; instead,
a color window with various options ("Logged in as... bla bla bla")
appeared; there was an option to start Task manager, but when I tried,
the system informed me that taskmgr.exe "could not be properly
initialized".

I shut down and restarted... and now there is a blue screen every time
and the system freezes then. It's shortly after the XP logo with the
animation at the bottom.

The blue screen has the general "there was an error, bla bla bla"
message, with the only informative portion being:

"STOP: 0x0000007E (0xC0000005, 0xF8448174, 0xF7C89D44, 0xF7C89A40)"

I found no reference to an error with those addresses online...

I can boot into safe mode. (This is where I am now, in fact) I ran
the repairing procedure from XP's install CD; it changed nothing.

Any solutions out there?

Additionally (or alternatively...), is there any way I could pause the
booting procedure and check what is loaded, step by step? See the name
of every driver, DLL, executable, font, anything being loaded, to
pinpoint the possible culprit that got loaded just before the crash?
(The way one could do in DOS and older Windows...)

 

[Will Denny]

Hi

Please try the following link to Jim Eshelman's web page - left hand column
(7E)

http://aumha.org/win5/kbestop.htm

--


Will Denny
MS MVP Windows Shell/User
Please reply to the News Groups

 

[Guest]

You got a boot sector virus which wont be wiped away by simple reformatting
the drive.
Its a tuff thing though see if these can help

http://support.microsoft.com/default.aspx?scid=kb;en-us;122221

http://www.microsoft.com/resources/...all/reskit/en-us/prkd_tro_oxhc.asp?frame=true

http://antivirus.about.com/od/securitytips/a/bootsectorvirus.htm

 

[harry]

Please try the following link to Jim Eshelman's web page - left hand

column (7E)

http://aumha.org/win5/kbestop.htm

Nope, nothing...

 

[harry]

You got a boot sector virus

No, I don't. I do have a lousy excuse for an OS, though, one that does
not even allow step by step booting. Sadly, W98 does not work with all
of this hardware.

 

[Bob I]

You must have gotten a duff copy installed. Start over.

 

[S. Taylor]

In safemode run msconfig.exe and switch to its BOOT.INI tab
and put a check in the /BOOTLOG option.
I don't know where the file will be saved to, but it should be named
bootlog.txt

 

[Ron Martell]

Nope, nothing...

Did you read the MSDN article linked from Jim's web page?

"If the specific cause of the exception is unknown, the following
should be considered:

Hardware incompatibility. First, make sure that any new hardware
installed is listed on the Microsoft Windows Hardware Compatibility
List (HCL).

Faulty device driver or system service. In addition, a faulty device
driver or system service might be responsible for this error. Hardware
issues, such as BIOS incompatibilities, memory conflicts, and IRQ
conflicts can also generate this error.

If a driver is listed by name within the bug check message, disable or
remove that driver. Disable or remove any drivers or services that
were recently added. If the error occurs during the startup sequence
and the system partition is formatted with NTFS file system, you might
be able to use Safe Mode to rename or delete the faulty driver. If the
driver is used as part of the system startup process in Safe Mode, you
need to start the computer by using the Recovery Console to access the
file.

If the problem is associated with Win32k.sys, the source of the error
might be a third-party remote control program. If such software is
installed, the service can be removed by starting the system using the
Recovery Console and deleting the offending system service file.

Check the System Log in Event Viewer for additional error messages
that might help pinpoint the device or driver that is causing bug
check 0x1E. Disabling memory caching of the BIOS might also resolve
the error. You should also run hardware diagnostics, especially the
memory scanner, supplied by the system manufacturer. For details on
these procedures, see the owner's manual for your computer. "

Good luck



Ron Martell Duncan B.C. Canada
--
Microsoft MVP
On-Line Help Computer Service
http://onlinehelp.bc.ca

In memory of a dear friend Alex Nichol MVP
http://aumha.org/alex.htm