Freeze on startup script, PLEASE HELP

DBarber

Honorable
Oct 10, 2013
10
0
10,510
Hello, I work for a high security data center as an IT technician. Obviously due to the nature of my work, there are many cameras scattered throughout the building. All of these cameras are connected to one machine which seems to be an "all-in-one" solution to camera security functions. This machine is running Windows XP, and upon startup makes it to the "running startup scripts" step and freezes. Doesn't hang, literally freezes. Now, being that my job is what it is, it is expected that I would proceed to check on all scripts set to run on startup, which was the first thing I thought of, but there's only one problem. Not only did I just start working here two weeks ago, but the security system and the machine it is connected to were here long before we were. Even my boss, the CEO, has no clue what the problem is, and we can't just reinstall. This system wasn't set up by us, so if we reinstall we will be lost. It was working fine, and then one day it froze upon startup, and has been doing it ever since. Any ideas would be MUCH appreciated.

Dylan.
 

DBarber

Honorable
Oct 10, 2013
10
0
10,510
Also, the machine is not connected to the internet. It is a single machine, keyboard, monitor, and mouse, connected to a network of local cameras, but there is no LAN or WAN, therefore it couldn't have been a network related update. Just found out that when the company first moved here, the system was not working. One of the technicians got it functioning properly to meet our needs, however he is no longer with the company. Like I said, it just quit out of nowhere. We literally have no clue why it would be doing this. I've done my googleing and other research, and so far have not found anyone with the same problem, or a solution. Only hang solutions are out there. If this is a hang, it's a 48+ hour hang. The mouse still moves, but it wont procede with startup.

Dylan
 

c3h8

Distinguished
Aug 8, 2008
185
0
18,710
My first four guesses would be: Windows Update(s).
----
The Basics (I presume you know these) [Lengthy/Intended for General Re-Use]

(I) Can you get to Safe Mode? Spam F8 during boot, boot into safemode (with networking).
(I.a) Have you checked the system error log (assuming it wasn't disabled)?
(I.b) Have you checked Windows update history?
(I.c) Have you done a system file integrity check? (pop a WinXP install disk in; CMD: sfc /scannow)
(I.d) For good measure have windows schedule a chkdisk on your OS drive on reboot.

(II) Alternatively, Can you confirm the hardware is good?
(II.a) Memtest x86 (A few passes can be enough to spot major errors)
(II.b) Try booting into a Linux Live CD, I like Fedora or Mint- though that's just familiarity.

(III) If Safemode Works
(III.a) Check drivers.
(III.b) Check your scripts (I know this can be miserable, DO IT ANYWAY).
(III.c) Do a Virus Scan (Use whatever you are licensed with or search for a free alternative*).
(III.d) Do a Spyware Check (Use whatever you are licensed with or search for a free alternative*).
(III.e) Attempt to boot into Windows.

(IV) If repairs in safe mode fail
(IV.a) Consider digging in the registry. If you don't know what you're doing, DON'T.
(IV.b) Consider a System Repair

(V) If the hardware appears bad attempt to isolate the problem.
---
PS. It's recommended you have a migration strategy before April 8, 2014. Windows XP End of Support/End of Life is fast approaching.
 

DBarber

Honorable
Oct 10, 2013
10
0
10,510
Little bit of updated info, It is a Lenel running Windows XP Professional. It has three HDD's, all of which have a green light for the light bulb symbol, (on the HDD itself) however only the first two have the green light on the cylindrical icon, which I assume is the access symbol. There are two main lights on the front of the machine, a green power light and a red HDD light. The red light seems to be non color associated, that is I do not believe that the red can be changed to green by any means other than replacing it with a green bulb. Still no clue as to the problem. looking into the third hdd light being off right now. Running an sfc command, afterward a chkdsk. Will post results.
 

DBarber

Honorable
Oct 10, 2013
10
0
10,510
Haven't tried safe mode, as my boss has a bootable cd she has been asking me to use... going to try that shortly. Would not could not be windows update, as I've said it has literally 0 network connectivity and no one has applied any updates via physical media. The machine is on it's own isolated network apart from anything and everything else.
 

c3h8

Distinguished
Aug 8, 2008
185
0
18,710
(Just read your update)
I still recommend sections (I) and (III). Step (II.a) and (I.d) are always good ideas. Though for giggles, check power management.

To clarify, check both the BIOS and Windows settings regarding power management. Power supply may also be at fault. I had a cheap Pentium Dual Core build with specific incompatibilities with the low-power modes. Windows would lock-up transitioning from a S3 state and you could only reset it.
 

DBarber

Honorable
Oct 10, 2013
10
0
10,510
Also updating/migrating OS is a problem because this is a legacy machine that is slow on xp, you can forget 7. Only option would be Linux, and the higher ups aren't too fond of our flightless friend.
 

DBarber

Honorable
Oct 10, 2013
10
0
10,510
UPDATE: Tried safe mode, and safe with command prompt... Both same issue. It shows all of the drivers loading, but every time stops at one called mup. not sure if that is the last one to load, and it wont proceed to the next stage of boot, or if it is the driver itself causing the boot to stop. any ideas?
 

c3h8

Distinguished
Aug 8, 2008
185
0
18,710
Allegedly, Win8 is genuinely useful as an upgrade to XP. Offering even performance boosts to legacy hardware over XP. I hate the OS for it's changes from 7 into Metro, but the undated kernel it's built on is fantastically quick.
 

c3h8

Distinguished
Aug 8, 2008
185
0
18,710
Definitely corrupted drivers. Windows, indeed, list drivers only after successfully loading them. Video drivers are the likely culprit.

Consider pulling the capture card (for your cameras), then try to boot into safe mode. If your luck that's the corrupted driver and you can reinstall/repair it from there.
 

DBarber

Honorable
Oct 10, 2013
10
0
10,510
UPDATE: Found out the 3rd HDD has failed. Running chkdsk on the others now. will post results. Finally, pulling an internal card would be difficult as this is a rack mounted machine, and if at all possible I would like to resolve the issue without a dismount/internal operation.
 

c3h8

Distinguished
Aug 8, 2008
185
0
18,710
Ok, don't pull the internal card unless you have to. The diagnostician in me is curious how the system will behave if you disable the failed drives and attempt to boot.

You might not have the answer, but was windows installed with all the drives attached? Xp has an amazingly retarded habit of putting the MBR and PBR on non OS drives when they are attached. "BootICE" is a very nice (freeware) utility for fixing such problems. It's a windows executable, that can be ran from a PE environment with desktop access. It's standard with "Hiren's Boot CD".

If boot errors persist, and they might, identifying the corrupted driver preventing safe mode should be the focus.
 

DBarber

Honorable
Oct 10, 2013
10
0
10,510
Actually, it's funny that you mention HBCD. That is one of my favorite tools, and I am bringing it tomorrow. After a little more research I have found a few files on the root of C: that are blank (0Kb) but seemingly shouldn't be. i.e. autoexec.bat, config.ini, etc. This leads me to believe that possibly some of the startup files are corrupted, however I am curious as to why these files are located at the root of C: instead of within the Windows folder... Boot.ini is also located at the root of C: and it is a measly 1Kb. Only 4 lines, 2 of which actually affect the startup. This situation just keeps going from bad to worse. As any IT guy would, I love a computer related challenge, but this has so many stipulations... If it were me, I would wipe it. Install a new OS, find a new software to run the cams, and viola. Thing is boss lady wants to keep the software and settings we already have implemented, which introduces a massive hurdle in this fix up. Definitely know 3rd drive in the array is bad, but the whole point of raid is redundancy. One drive going out isn't going to stop the op. Planning on replacing that tomorrow with one of the 60 something drives just laying in a drawer, however that wont solve the problem. Also that won't be as easy as it sounds. All the drives are in locking enclosures that take a special kind of barrel key, not the generic ones that most use. Like I mentioned earlier, the thing was here way before we were, in a way we kind of inherited it... and we don't have a key... :( So basically I have to remove a drive that no one has a key for, replace it, and still figure out what the hell is going on with this old thing. Not to mention no one seems to know the bios password. guess i'm just going to have to use a BCD to reset it ;) Darn though, this whole situation is a headache.
 

DBarber

Honorable
Oct 10, 2013
10
0
10,510
Oh yeah, the chkdsk found nothing. 0 problems. isn't that nice. Also, keep in mind that it does get past the Windows XP loading page, makes it to "loading startup scripts" and thats where it stops... Doubt its the mbr or pbr or the bios wouldn't be able to find windows anyways.
 

c3h8

Distinguished
Aug 8, 2008
185
0
18,710
True, though with XP I don't trust anything it does automatically involving the boot order. That driver corruption made evident by the failed safe mode boot looks ever more your culprit. From what I've read, sfc added support for external hives with Vista.

From the XP recovery console "listsvc" can be called on to list drivers and services, then "disable" can be invoked to render them inert. [If About.com is to be trusted]

Haven't tried this technique myself, but it looks potentially useful under the given circumstances.
 

DBarber

Honorable
Oct 10, 2013
10
0
10,510
Certainly. I have had a stroke of luck on this matter though... I found a hidden system volume information folder on the root of C: This folder contains recovery files and information, and just so happens to have a recovery folder with files dated 07/2013. Perfect! Now I just have to get the recovery console to work... Hopefully HBCD will assist in that endeavor. If I can replace the malfunctioning drive, and restore to july's state, all will be well. Hopefully I can accomplish this tomorrow. I appreciate all the help, and will post once more tomorrow letting you know how everything goes. I get off work in 4 mins haha ;)