Can Only Boot WinXP SP2 with "Last Known Good Configuration"

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I am at a real loss here, and could use some serious help. I have a PC that
everytime it is restarted, does not get past the Windows XP splash screen
before restarting itself, at which point the user receives the prompt to use
"last known good configuration", "start windows normally", or safe mode
(regular, with networking, or with command prompt). Anytime the user tries
to start normally, the same thing happens. If the user chooses "last known
good configuration" the machine will start up, but the next time the user
restarts the entire process repeats itself.

The machine is a ThinkCentre M50 (type: 8189-d8u) running XP SP2 on a
domain. The following are the error messages in the system event log:
- PlugPlayManager : The device Root\LEGACY_DRMTION\0000 disappeared from the
system without first being prepared for removal.
- Service Control Manager : The following boot-start or system-start
driver(s) failed to load:
d347bus
SAVRT
- Service Control Manager : The PMEM service failed to start due to the
following error: The system cannot find the file specified.
- SAVRT : Unable to initialize the virus scanning engine database files.

The following are the error messages in the application event log:
- WinVNC4 : MsgWindow: untrapped: Unable to open Input desktop: The
requested resource is in use. (170)
- WinVNC4 : MsgWindow: untrapped: Unable to open Input desktop: The
requested resource is in use. (170)
- WinVNC4 : MsgWindow: untrapped: Unable to open Input desktop: The
requested resource is in use. (170)
- Userenv : Windows saved user <DOMAIN NAME REMOVED>\<NAME REMOVED> registry
while an application or service was still using the registry during log off.
The memory used by the user's registry has not been freed. The registry will
be unloaded when it is no longer in use. This is often caused by services
running as a user account, try configuring the services to run in either the
LocalService or NetworkService account.

We do use Symantec AntiVirus Corporate Edition and RealVNC.

Under Device Manager, under System Devices, the following devices have
yellow exclamation points:
- PnP BIOS Extension : Windows cannot load the device driver for this
hardware. The driver may be corrupted or missing. (Code 39)

Under Device Manager, under Non-Plug and Play Drivers (View : Show Hidden
Devices), the following devices have yellow exclamation points:
- NAVEX15 : This device is not present, is not working properly, or does not
have all its drivers installed. (Code 24)
- PMEM : This device is not present, is not working properly, or does not
have all its drivers installed. (Code 24)
- SAVRT : This device is not present, is not working properly, or does not
have all its drivers installed. (Code 24)

The machine did have DAEMON Tools installed but I have since removed it in
an attempt to rectify the problem with no success. The machine also has the
following installed (among other things):
- IBM System Update
- Symantec Ghost Console and Standard Tools
- Exchange System Manager
- Microsoft Exchange Best Practices Analyzer Tool
- Windows Server 2003 Administration Tools Pack
- RealVNC Deployment Tool
- RealVNC Viewer - Enterprise Edition

I have been unsuccesful using System Restore to go back to any previous
restore points, and all attempts to use System Restore fail. I have tried to
run sfc /scannow but it doesn't seem to do anything.

Any help or advice regarding this issue is GREATLY APPRECIATED! I have been
pulling my hair out on this problem for a while now. Thanks!

- Marc
 
I receievd some suggestions from another board I posted on, so below are the
suggestions and my responses to them...Hopefully it will provide some more
useful diagnostic information for my problem:


* Remove & Reinstall your Symantec Antivirus (SAVNRT is related) *

- I tried this already with no success

* Do a repair install of Win XP. To do this, pop in your XP disc before boot
up and boot from the CD (this may require you to modify some BIOS settings
beforehand). Choose "Set Up Win XP Now" at the first menu, then when the
setup prgram detects that a previous installation is already there, press "R"
for repair. *

- I'd prefer not to do this as I imagine it will cause me more headaches
down the line, since all my settings, etc. will be lost and as I've
understood, doing a repair install is a second-to-last resort (the last being
blowing away the system and starting from scratch)

* If all else fails, Disable automatic restart. This will allow you to
gather more information about the error to post here (because a blue STOP
screen will be displayed, instead of the system automatically restarting). *

- Here is the information that I pulled from the BSOD:
DRIVER_IRQL_NOT_LESS_OR_EQUAL

Technical Information:
*** STOP: 0x000000D1 (0x00000307, 0x000000FF, 0x00000000, 0x00000307)

- Here is some further information that might be useful in diagnosing and
resolving this issue:

- it seems I am able to get into Safe Mode
- when attempting to use MSCONFIG to start in diagnostic startup mode, I
received the same Blue Screen of Death
- when booting back up using Last Known Good Configuration from my attempt
to restart the system using MSCONFIG : diagnostic startup mode, the System
Configuration Utility automatically restarted after I had logged in (as it
should have), but instead of it still showing me in diagnostic mode, it had
moved me into Selective Startup because somehow a startup item (under the
Startup tab) had become checked: ICO.EXE located at
HKLM\Software\Microsoft\Windows\CurrentVersion\Run
- This file seems to related to the IBM mouse I'm using, so I attempted to
start in normal startup mode but unplugged the mouse, and the BIOS gave me
some sort of error (not sure if this is related to my issue at all or not):
Error
System Configuration Data Updated
8603: Pointing Device Error
* Error Boot Sequence will be taken if no selection is made
(I then chose to launch BIOS Setup Utility, saved changed, and rebooted
and it started up again without this error but then gave me the BSOD again -
not really unexpected though)

Once more, I am completely at a loss, and this issue is driving me insane,
not to mention making this system entirely unstable. Any further help or
advice is GREATLY appreciated! Thanks again!

- Marc
 
Back
Top