basskozz
asked on
Bad Image Checksum - My System Files are Corrupt, PLZ HELP
I've been having some problems with my computer for the past couple of days, it all started with it hanging at bootup on "Preparing Network Connections..."
See Here: https://www.experts-exchange.com/questions/21697246/URGENT-Boot-Hangs-on-Preparing-Network-Connections.html
So I've been trying to correct that issue by removing drivers and startup services, well I think I screwed up bigtime because now I am getting the blue screen of death and it's saying the following error message on boot:
Stop: c0000221 {Bad Image Checksum}
The image gdi32.dll is possibly corrupt. The header checksum does not match the computed checksum.
...
It then goes on to say makesure hardware is properly connected, etc..., etc...
I have a copy of ERD Commander 2005 that I've been using as a LiveBOOTCD to edit the registry etc..., and I tried using the "System File Repair" utility, and it recognizes the following two files are corrupt:
C:\WinNT\System32\ntkrnlpa
C:\WinNT\System32\ntoskrnl
But when I select repair i get the following error message from ERD commander:
"Error Repairing: The system cannot find the path specified"
Abort | Retry | Ignore
I tried hitting "retry" numrous times but that does nothing, it keeps bringing up the same error message... I can only Ignore or Abort.
I think I've seriously F'ed up my machine now... Please help
p.s. I've run CHKDSK and all my HD's seem to be fine, I've also run Virus Scanners and Spyware scanners using BartPE/Ultimate BootCD Windows (http://www.ubcd4win.com/)
-BassKozz
See Here: https://www.experts-exchange.com/questions/21697246/URGENT-Boot-Hangs-on-Preparing-Network-Connections.html
So I've been trying to correct that issue by removing drivers and startup services, well I think I screwed up bigtime because now I am getting the blue screen of death and it's saying the following error message on boot:
Stop: c0000221 {Bad Image Checksum}
The image gdi32.dll is possibly corrupt. The header checksum does not match the computed checksum.
...
It then goes on to say makesure hardware is properly connected, etc..., etc...
I have a copy of ERD Commander 2005 that I've been using as a LiveBOOTCD to edit the registry etc..., and I tried using the "System File Repair" utility, and it recognizes the following two files are corrupt:
C:\WinNT\System32\ntkrnlpa
C:\WinNT\System32\ntoskrnl
But when I select repair i get the following error message from ERD commander:
"Error Repairing: The system cannot find the path specified"
Abort | Retry | Ignore
I tried hitting "retry" numrous times but that does nothing, it keeps bringing up the same error message... I can only Ignore or Abort.
I think I've seriously F'ed up my machine now... Please help
p.s. I've run CHKDSK and all my HD's seem to be fine, I've also run Virus Scanners and Spyware scanners using BartPE/Ultimate BootCD Windows (http://www.ubcd4win.com/)
-BassKozz
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
carrzkiss,
Ok... I've already tried the W2k disk "Repair" w/ no luck :(
Miguel,
ERD Commander's built in network support isn't working, I think my on-board NIC might be fried, or ERD doesn't have the correct drivers...
Suggestions ?
-BassKozz
Ok... I've already tried the W2k disk "Repair" w/ no luck :(
Miguel,
ERD Commander's built in network support isn't working, I think my on-board NIC might be fried, or ERD doesn't have the correct drivers...
Suggestions ?
-BassKozz
Miguel
The [R]epair "should" get the system Bootable. With (or) Without SP4 installed.
I know from experiance, As I have done it.
I am not suggested that the Repair will fix this issue.
If he is able to boot to his Desktop, then he can then Backup everything.
If the Repair does not work, and the ERD Commander does not work.
Then the best thing if to remove the HD and put it in another Win2k system
Backup everything, then put the HD back into the computer and
Format/Install
The [R]epair "should" get the system Bootable. With (or) Without SP4 installed.
I know from experiance, As I have done it.
I am not suggested that the Repair will fix this issue.
If he is able to boot to his Desktop, then he can then Backup everything.
If the Repair does not work, and the ERD Commander does not work.
Then the best thing if to remove the HD and put it in another Win2k system
Backup everything, then put the HD back into the computer and
Format/Install
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
HI,
Like carrzkiss says, do you have the option to take the HD out and put it in the other computer ?
If so .. go ahead ...
Miguel
Like carrzkiss says, do you have the option to take the HD out and put it in the other computer ?
If so .. go ahead ...
Miguel
Hi basskozz,
What is your NIC Card ?
Miguel
What is your NIC Card ?
Miguel
Hi basskozz,
And if the nic has built what's the computer brand and model ....
Miguel
And if the nic has built what's the computer brand and model ....
Miguel
ASKER
The NIC is built into my MoBo: Intel D865GBF.
http://www.intel.com/products/motherboard/d865gbf/
http://www.intel.com/products/motherboard/d865gbf/
ASKER
I think I found the problem, although it is too late as I had to re-format and re-install windows...
The On-Board NIC (ethernet adaptor) seems to be fried, I've downloaded the drivers from Intel's site and tried to install them, and they don't seem to be working at all... I am pretty sure it's fried. It all makes sence now, because ERD Commander and BartPE/Ultimate BootCD 4 windows was unable to connect to the network w/ the ethernet adaptor.
Look's like I have to make a trip out to my local compUSA and pickup a new NIC card. :(
two questions:
1. Is there anyway to diagnos the On-Board NIC (ethernet adaptor) to ensure that it is indeed fried ?
2. When I purchase and install the new NIC card will it conflict at all with the built in ethernet adaptor?
Thanks for all the help, if I had only had tried using a new card in the first place... oh well, you live you learn.
-BassKozz
The On-Board NIC (ethernet adaptor) seems to be fried, I've downloaded the drivers from Intel's site and tried to install them, and they don't seem to be working at all... I am pretty sure it's fried. It all makes sence now, because ERD Commander and BartPE/Ultimate BootCD 4 windows was unable to connect to the network w/ the ethernet adaptor.
Look's like I have to make a trip out to my local compUSA and pickup a new NIC card. :(
two questions:
1. Is there anyway to diagnos the On-Board NIC (ethernet adaptor) to ensure that it is indeed fried ?
2. When I purchase and install the new NIC card will it conflict at all with the built in ethernet adaptor?
Thanks for all the help, if I had only had tried using a new card in the first place... oh well, you live you learn.
-BassKozz
)Posted this on the other post as well)
#2 - Make sure that you do not install the drivers for the on-board card. And you should not have no problems.
(Personally, myself, I hate On-Baord "Anything", I like everything Plug-n-PLay)
#1 - Not really sure about?
#2 - Make sure that you do not install the drivers for the on-board card. And you should not have no problems.
(Personally, myself, I hate On-Baord "Anything", I like everything Plug-n-PLay)
#1 - Not really sure about?
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thanks for all the help guys.
Hi basskozz,
Glad to help and good luck to you :)
Miguel
Glad to help and good luck to you :)
Miguel
Choose the [R]epair option, see if this will at least get you back up and runing
So you can do a Backup of your system.
--------
Once this is done and you successfully do your Backup, then I strongly recommend that you do
A complete Format/Reinstall of your system.
You are receiving too many errors on your computer not to do a reinstall of it.
There is no use in prolonging this issue to much longer.
Good Luck on the [R]epair.