Questions

Taskmanger crash - bad checksum

Tags:
+
0 Votes
Locked

Taskmanger crash - bad checksum

jdclyde
Greetings,

Working on WinXPsp3.

System had several dozen infections, they have been removed.

Only problem I still have is when you do the CTRL-ALT-DEL, I get the following error.

"taskmgr.exe has encountered a problem and needs to close. We are sorry for the inconvenience."

The dump file is not helpful to me, just listing checksums and such.

Any suggestions on how to fix this without having to do a wipe/reload? I will eventually do just that, but for now it has software on it that I can't replace that is needed, so not a short term option.

Thanks!

jd
  • +
    0 Votes
    santeewelding

    No matter what I did, CTRL-ALT-DEL was history. So was msconfig. But, then, there was no "software" I couldn't do without. Made sure of that going in. That is still the case.

    I wiped with abandon.

    +
    0 Votes
    jdclyde

    but that isn't an option at this time.

    In a few months, I will get it back and do a wipe/load, but have to "make do" for now.

    When I first got it to work on, it was ungodly slow, between the 256M of SHARED memory and the infections..... Bumped it up by dropping another gig in.

    +
    0 Votes
    seanferd

    If it is the correct file, you can always try profiling it with Dependency Walker to find missing/bad files/reg entries.

    You may also want try Autoruns and see if anything looks wrong, especially in Winlogon.

    Or Process Monitor, which may reveal something.

    +
    0 Votes
    jdclyde

    Never heard of Dependency Walker, so have not tried it. Training is in networking/servers, not systems.

    Process monitor. One more thing I have never used/heard of. Always used TaskManager to do that.

    Thanks!

    +
    0 Votes
    seanferd

    Proc Mon will profile file/process/reg activity. Process Explorer is more of the Task Manager replacement.
    http://technet.microsoft.com/en-us/sysinternals/bb545027.aspx

    Dependency Walker used to come with a variety of MS software.
    http://www.dependencywalker.com/

    Good luck and happy hunting, whatever path you take.

    +
    0 Votes
    OH Smeg

    You can perform a Repair/Upgrade/In Place install as per method 2 here

    http://support.microsoft.com/kb/978788

    Col

    +
    0 Votes
    jdclyde

    one, if recovery console would fix this, and two, how to use the recovery console....

    Google, here I come!

    +
    0 Votes
    makkh

    I try not to be too techy, but here goes:

    1. Make sure you have enable the system to boot from CD/DVD ROM 1st. To do this, you need to do some setting in BIOS. Observe the screen when you power up the PC where they mention something like "PRESS DEL TO ENTER BIOS" which is what you need to do (press the Delete key on your keyboard). In BIOS, look for the Tab named BOOT (use <- & -> key on keyboard to navigate), look for one option mentioning boot device priority, adjust the setting until the CD/DVD is place as 1st boot device (to do this, read the instructions text place at bottom screen). Once done, navigate to the last Tab and select Save the setting & restart the system, press enter.

    2. Insert the XP installation CD into the CD/DVD ROM drive.

    3. The Black screen appear with line of text "Press any key to boot from CD/DVD", press Enter.

    4. Let the XP installation file load by itself. The process usually should be fine if there is no hardware damage.

    5. When all files loaded, a simple intro screen appear, press Enter to proceed install XP.

    6. A long list of agreement appear, just press F8 on keyboard to proceed.

    7. 3 options available, press R on keyboard to select the Recovery Console.

    8. Black DOS screen appear, when asked for which WINDOWS system to attend, press 1 on keyboard to select Drive C.

    9. When ask for Administrator password, usually just press Enter on keyboard if you're sure no password assign before. Be careful as it only allows max 3 fail attempts, then you need to start the entire process again from step 3.

    10. When the console is ready (C:/ ), type chkdsk to run a simple check disk process.

    11. Once check disk is done, type fixboot as the console will generate a new startup file.

    12. Just press the restart button on the CPU to reboot the system. Remember to remove the XP CD from the drive.

  • +
    0 Votes
    santeewelding

    No matter what I did, CTRL-ALT-DEL was history. So was msconfig. But, then, there was no "software" I couldn't do without. Made sure of that going in. That is still the case.

    I wiped with abandon.

    +
    0 Votes
    jdclyde

    but that isn't an option at this time.

    In a few months, I will get it back and do a wipe/load, but have to "make do" for now.

    When I first got it to work on, it was ungodly slow, between the 256M of SHARED memory and the infections..... Bumped it up by dropping another gig in.

    +
    0 Votes
    seanferd

    If it is the correct file, you can always try profiling it with Dependency Walker to find missing/bad files/reg entries.

    You may also want try Autoruns and see if anything looks wrong, especially in Winlogon.

    Or Process Monitor, which may reveal something.

    +
    0 Votes
    jdclyde

    Never heard of Dependency Walker, so have not tried it. Training is in networking/servers, not systems.

    Process monitor. One more thing I have never used/heard of. Always used TaskManager to do that.

    Thanks!

    +
    0 Votes
    seanferd

    Proc Mon will profile file/process/reg activity. Process Explorer is more of the Task Manager replacement.
    http://technet.microsoft.com/en-us/sysinternals/bb545027.aspx

    Dependency Walker used to come with a variety of MS software.
    http://www.dependencywalker.com/

    Good luck and happy hunting, whatever path you take.

    +
    0 Votes
    OH Smeg

    You can perform a Repair/Upgrade/In Place install as per method 2 here

    http://support.microsoft.com/kb/978788

    Col

    +
    0 Votes
    jdclyde

    one, if recovery console would fix this, and two, how to use the recovery console....

    Google, here I come!

    +
    0 Votes
    makkh

    I try not to be too techy, but here goes:

    1. Make sure you have enable the system to boot from CD/DVD ROM 1st. To do this, you need to do some setting in BIOS. Observe the screen when you power up the PC where they mention something like "PRESS DEL TO ENTER BIOS" which is what you need to do (press the Delete key on your keyboard). In BIOS, look for the Tab named BOOT (use <- & -> key on keyboard to navigate), look for one option mentioning boot device priority, adjust the setting until the CD/DVD is place as 1st boot device (to do this, read the instructions text place at bottom screen). Once done, navigate to the last Tab and select Save the setting & restart the system, press enter.

    2. Insert the XP installation CD into the CD/DVD ROM drive.

    3. The Black screen appear with line of text "Press any key to boot from CD/DVD", press Enter.

    4. Let the XP installation file load by itself. The process usually should be fine if there is no hardware damage.

    5. When all files loaded, a simple intro screen appear, press Enter to proceed install XP.

    6. A long list of agreement appear, just press F8 on keyboard to proceed.

    7. 3 options available, press R on keyboard to select the Recovery Console.

    8. Black DOS screen appear, when asked for which WINDOWS system to attend, press 1 on keyboard to select Drive C.

    9. When ask for Administrator password, usually just press Enter on keyboard if you're sure no password assign before. Be careful as it only allows max 3 fail attempts, then you need to start the entire process again from step 3.

    10. When the console is ready (C:/ ), type chkdsk to run a simple check disk process.

    11. Once check disk is done, type fixboot as the console will generate a new startup file.

    12. Just press the restart button on the CPU to reboot the system. Remember to remove the XP CD from the drive.