Kernel Replacement (XP Pro SP1)

Topic

New Reply

To make a long story short, does anyone know the exact procedure and syntax to replace the “kernel” ? Approx. twice a week I get a blue screen either on a shut down or on a resume from hibernation that puts a “KernelFaultCheck” in start-up. If I delete the mini-dump that was created and remove the reg entry I am OK for 2-4 days. This all started after adding a D-Link DWL-AB650 wireless card which works flawlessly in 2 other Win2K Pro laptops. Yes they are the latest drivers and yes I did an uninstall-reinstall. If I did a “system repair” is there any downside to it and would it replace the “kernel”? I already did the basic remedies, CHKDSK, SFC/scannow and SFC/purgecache. This installation is still the Dell factory image (with SP1+ added) approx. 10 months old. Thanks in advance.

Reply | Quote

Replies

Have you tried re-installing SP1 ?

Reply | Quote

No I have not. I installed SP1 approx. 2 weeks after the release, whenever that was last year. Would there be any negative to re-installing SP1? Would the updates that were released after it need to be reinstalled?

Reply | Quote

Leif,
I took your suggestion and did an SP1 refresh the next day. Everything was running better until today. The refresh lasted 6 days then the same Blue screen error when it was sitting all by its’ lonesome and was going into hibernation from being inactive for 2 hours. I spoke with a friend in QC at HP (the offending laptop is a Dell) and she said that last year they had trouble with XP and Norton at startup and had NAV delay their startup to eliminate the conflict (Too many programs wanting the same memory IRQ range at the same time). I noticed that NAV 2003 has this delay and NAV 2002 does not. I think this is what causes the minute plus delay preventing the wireless card from connecting. I am going to change to NAV 2003 when I return from a trip in two weeks as my subscription is up in 6 weeks anyway. I am hoping that will fix this headache. If it doesn’t do the job I am tossing XP Pro out the window and putting Win2K on the laptop. The only thing that I will miss is the Cleartype function.

Reply | Quote

I think you problem is “hibernation”, my suggestion is to turn if OFF. Hibernation is a memory HOG, and needs to save ALL information of ALL programs that are open.

I turn off hibernation ASAP on all systems. Remember that hibernation was designed for laptops and some USB devices and NIC’s have problems after hibernation has been activated.

DaveA I am so far behind, I think I am First
Genealogy....confusing the dead and annoying the living

Reply | Quote

As you stated hibernation is for laptops and this laptop is the only one that runs XP Pro and NAV 2002. The other 2 have Win2K and NAV 2003. If I remove the wireless card and boot up then put the card in it will connect in 7-10 seconds. If I leave the card in and boot up it takes 60-80 seconds to connect. The sequence of re-initializing the system and open apps is in a different order on the XP laptop in comparison to the Win2K laptops. I am still leanning towards NAV 2002 being the problem. I let you know in 2-3 weeks when I change to NAV 2003 and have run it for a while.

Reply | Quote

Just to prove your suspicions about NAV, have you tried disabling NAV and then booting? There are several programs around that will allow you to control the sequence and timing of your startup (no matter where the start origin is) items. One is Startup Delay.

Joe

--Joe

Reply | Quote

XP has its own builtin startup control. Also, the hibernation comments earlier also apply to LPT1 which goes to sleep and print jobs stick around until a reboot. Turn off hibernation no matter what the end result of the original issue.

-Jester

Reply | Quote

Except as usual with many MS tools MSconfig is a rather blunt instrument. It only allows you to say yeah or nay to any item. XP & all MS OSes since 95 will try to start all the programs in each startup area in the order in which they are specified (usually alphabetical unless the user does something) and starts them one immediately after the other. Some of the start up managers allow the user to specify the order of items and a delay between each module thus there is a more orderly startup with consideration to what should first, second, etc. and the resources each takes to start. The overall effect is a faster startup.

Joe

--Joe

Reply | Quote

After my trip I checked the D-link support site and they had posted new drivers for my wireless card while I was away. After the driver upgrade, which was faster than me typing this post, the wireless connection was put in an earlier start-up position. My connection now starts instantly on the XP Pro laptop. It has been almost two weeks without a problem. Thanks for all your suggestions. I still believe changing to NAV2003 which would have changed the start-up order of things would have fixed things as well.

Reply | Quote