Tweet
I like to bill by the JOB, that way I do not feel hounded to get it done yesterday. I will let them know how long it will take and what I want for the work up front after I have a look around.
SO I returned today with both arms swinging.
I found out that ENABLE bootlogging did not really help any. I think if it stops on bootup with a 7E error that there is no log written. I might be wrong because I had to hit RESET and then boot up with enable VGA and I tried to review the log but I found nothing out of the ordinary. It seemed that the error was NTKRNLA.EXE or somethign that was the error. Which made no sense, so I tried to log several times, but I think I should have booted up with the HIREN disk instead of back into windows and then tried to view the log. I did end up booting into a recovery console and viewing services and then disabled several like agp440 and intelide and intelppm (which were mostly already disabled). No change
I put in a graphics card that I had the driver CD to and booted into vga mode but even with the proper drivers (Nvidia 285) it failed to boot.
I figured it was something else for some reason, SO After trying to get the proper drivers installed, then finally installing them, then having to reboot several times, I decided to perform another repair install on this. (The first one happened when it had its initial failure a few days ago.) No change...
The repair install copied over the files, then wanted to reboot the computer, SO I obliged and it hit that STOP 7E ONCe again. I rebooted it and was not sure of what to make, so I had it go back to enable VGA mode again. It went into the setup. I had to go back and forth with the new NVIDIA driver disk and the XP SP3 disk a few times and in the end it finalized and rebooted. To yet another STOP 7E error... No change...
SO nothing has really changed and I booted into the VGA only mode again and went online and started looking for ALL STOP 7E fixes. I happened across this page: http://support.microsoft.com/kb/316434 And I thought that this HAD to be from drivers that were leftover and trying to be loaded. I spent another 20 minutes following the unsigned driver portion and ran the program and then removed all 15 or so unsigned drivers (minus 3 that would NOT move) to a different folder. I also noticed the intelide.sys and the intelppm.sys back in there. I removed those as well. Upon reboot I was waiting to see the STOP BSOD and it blew right past and into windows NORMAL mode. I about pissed myself so I rebooted again and same thing. I think removing those last drivers has solved the problem.
For good measure I should go into the system again and have that utility remove all unused drivers and then button it up. But I wanted to get home so I made a System Restore point and rebooted again in disbelief and all booted up fine. I set the boot options to only give options for 2 seconds for recovery console/xp pro and set automatic updates to run and locked it and I went home.
SO, I took this computer from Dell optiplex P4 3.0ghz single core whatever that was running an AGP Quadro video card to a NEW AMD based FX4130 quad core cpu running at around 3.8ghz and instead of 2GB of RAM they now have 4GB of RAM (yeah I know 4GB limitations on xp...) and they have a PCIE video card and new case and dvd burner (all sata) and the ONLY part of the old computer is their HD. Funny too that windows activated with no issues over the net. They are on a network with the NAS4Free box that I setup and the login script for the user/network drives is still going strong. No issues at all.
And the COOLEST thing is that I found a cable management system that took their 9+ cords and wrapped them into 1 -2 large cords so that their desk looks NICE instead of wires and cables running all over the place. So that is how you do it I guess... Now I will get a copy of those files (oh wait, I have a copy already) and I will look them up and see what they belong to and see which ones would cause the issue. When I duplicate it at home in my lab then I will have a closer look and when things like this pop up in the future then hopefully it will only take a few more minutes to fix...
Enable VGA mode with Windows XP IS BULL**** though. It appears that it was NOT a graphics issue. Asshats at MS need to get trout-slapped for that one.
SO I returned today with both arms swinging.
I found out that ENABLE bootlogging did not really help any. I think if it stops on bootup with a 7E error that there is no log written. I might be wrong because I had to hit RESET and then boot up with enable VGA and I tried to review the log but I found nothing out of the ordinary. It seemed that the error was NTKRNLA.EXE or somethign that was the error. Which made no sense, so I tried to log several times, but I think I should have booted up with the HIREN disk instead of back into windows and then tried to view the log. I did end up booting into a recovery console and viewing services and then disabled several like agp440 and intelide and intelppm (which were mostly already disabled). No change
I put in a graphics card that I had the driver CD to and booted into vga mode but even with the proper drivers (Nvidia 285) it failed to boot.
I figured it was something else for some reason, SO After trying to get the proper drivers installed, then finally installing them, then having to reboot several times, I decided to perform another repair install on this. (The first one happened when it had its initial failure a few days ago.) No change...
The repair install copied over the files, then wanted to reboot the computer, SO I obliged and it hit that STOP 7E ONCe again. I rebooted it and was not sure of what to make, so I had it go back to enable VGA mode again. It went into the setup. I had to go back and forth with the new NVIDIA driver disk and the XP SP3 disk a few times and in the end it finalized and rebooted. To yet another STOP 7E error... No change...
SO nothing has really changed and I booted into the VGA only mode again and went online and started looking for ALL STOP 7E fixes. I happened across this page: http://support.microsoft.com/kb/316434 And I thought that this HAD to be from drivers that were leftover and trying to be loaded. I spent another 20 minutes following the unsigned driver portion and ran the program and then removed all 15 or so unsigned drivers (minus 3 that would NOT move) to a different folder. I also noticed the intelide.sys and the intelppm.sys back in there. I removed those as well. Upon reboot I was waiting to see the STOP BSOD and it blew right past and into windows NORMAL mode. I about pissed myself so I rebooted again and same thing. I think removing those last drivers has solved the problem.
For good measure I should go into the system again and have that utility remove all unused drivers and then button it up. But I wanted to get home so I made a System Restore point and rebooted again in disbelief and all booted up fine. I set the boot options to only give options for 2 seconds for recovery console/xp pro and set automatic updates to run and locked it and I went home.
SO, I took this computer from Dell optiplex P4 3.0ghz single core whatever that was running an AGP Quadro video card to a NEW AMD based FX4130 quad core cpu running at around 3.8ghz and instead of 2GB of RAM they now have 4GB of RAM (yeah I know 4GB limitations on xp...) and they have a PCIE video card and new case and dvd burner (all sata) and the ONLY part of the old computer is their HD. Funny too that windows activated with no issues over the net. They are on a network with the NAS4Free box that I setup and the login script for the user/network drives is still going strong. No issues at all.
And the COOLEST thing is that I found a cable management system that took their 9+ cords and wrapped them into 1 -2 large cords so that their desk looks NICE instead of wires and cables running all over the place. So that is how you do it I guess... Now I will get a copy of those files (oh wait, I have a copy already) and I will look them up and see what they belong to and see which ones would cause the issue. When I duplicate it at home in my lab then I will have a closer look and when things like this pop up in the future then hopefully it will only take a few more minutes to fix...
Enable VGA mode with Windows XP IS BULL**** though. It appears that it was NOT a graphics issue. Asshats at MS need to get trout-slapped for that one.
Comment