How to fix error code 0x490 in Windows 7 Enterprise
This morning I was getting a bad video display on my Dell Latitude D630 which I believe is a known issue.
To ensure I can keep working we swapped out my battery and HD to a Temp Dell.
Now when booting up I'm stuck in a loop.
I run the system repair and here is some information:
"If you have recently attached a device to this computer, such as a camera or portable music player, please remove it and restart your computer"
I did have this laptop in a docking station. I have removed it from the docking station and removed all devices connected and still produces the error message.
Click on 'View diagnostics and repair details'
Root cause found:
--------------------------
Boot sector for system disk partition is corrupt.
Repair action: Boot sector repair
Result: Failed: Error Code = 0x490
Time Taken = 183098ms
Please Help
To ensure I can keep working we swapped out my battery and HD to a Temp Dell.
Now when booting up I'm stuck in a loop.
I run the system repair and here is some information:
"If you have recently attached a device to this computer, such as a camera or portable music player, please remove it and restart your computer"
I did have this laptop in a docking station. I have removed it from the docking station and removed all devices connected and still produces the error message.
Click on 'View diagnostics and repair details'
Root cause found:
--------------------------
Boot sector for system disk partition is corrupt.
Repair action: Boot sector repair
Result: Failed: Error Code = 0x490
Time Taken = 183098ms
Please Help
Adam Leinss
Go into the BIOS and check the drive operation. If it's AHCI, try PATA or legacy to see if it boots. I assume it's another D630 laptop?
Use the Windows 7 Startup Repair tool.
To begin, you will need to boot from the Windows 7 DVD.
1.Watch for a Press any key to boot from CD or DVD... message.
2.Press a key to force the computer to boot from the Windows 7 DVD.
In Startup Repair, execute Boot Critical Disk Meta-data Repair (BCDMD).
The BCDMD repairs missing/corrupted MBR code, partition table, or boot sector (at least one must be intact), or missing/corrupted boot manager. These operations are non-reversible; therefore, prior to any repair, BCDMD ensures that the computer is indeed in an invalid state.
To begin, you will need to boot from the Windows 7 DVD.
1.Watch for a Press any key to boot from CD or DVD... message.
2.Press a key to force the computer to boot from the Windows 7 DVD.
In Startup Repair, execute Boot Critical Disk Meta-data Repair (BCDMD).
The BCDMD repairs missing/corrupted MBR code, partition table, or boot sector (at least one must be intact), or missing/corrupted boot manager. These operations are non-reversible; therefore, prior to any repair, BCDMD ensures that the computer is indeed in an invalid state.
ASKER
When booting in Safe Mode it stops at ClassPNP.sys and then BSOD
You run the Boot Critical Disk Meta-data Repair again?
ASKER
Is Boot Critical Disk Meta-data Repair different from the System Repair tool that runs?
Yes, is different. See step-by-step in http://pcsupport.about.com/od/toolsofthetrade/ss/windows-7-startup-repair.htm
To begin, you will need to boot from the Windows 7 DVD Installation.
To begin, you will need to boot from the Windows 7 DVD Installation.
ASKER
Please see pic
dd443489.5dc073f8-8d6c-4baa-91a6.jpg
dd443489.5dc073f8-8d6c-4baa-91a6.jpg
Yes. This option is correct. Startup Repair and not System Repair. The BCDMD routines are executed when choosing this option.
ASKER
I have executed this option to no such luck.
I have thoroughly researched the problem with this classpnp.sys file.
I was unable to copy a “Good” version of the file to the directory on the hard drive where the supposed corrupted one exists. This is due to the fact that there is a plug n play process that continually calls this file when the hard drive is attached. There is not an immediate fix to my knowledge, to be able to delete the old, and add the new file.
Endpoint encryption is not the problem with this machine. It is unknown what the true cause of this problem is, but definitely has something to do with swapping the hard drive from one machine to another. Normally it’s not a huge issue, but this time, for whatever reason, it caused a serious problem on the machine with this particular system file.
I can reviewed the various troubleshoot links I have found, but they all mostly point to reformatting or reimaging the machine, or trying to replace that file with a good one, which I have not found a way to do.
I have thoroughly researched the problem with this classpnp.sys file.
I was unable to copy a “Good” version of the file to the directory on the hard drive where the supposed corrupted one exists. This is due to the fact that there is a plug n play process that continually calls this file when the hard drive is attached. There is not an immediate fix to my knowledge, to be able to delete the old, and add the new file.
Endpoint encryption is not the problem with this machine. It is unknown what the true cause of this problem is, but definitely has something to do with swapping the hard drive from one machine to another. Normally it’s not a huge issue, but this time, for whatever reason, it caused a serious problem on the machine with this particular system file.
I can reviewed the various troubleshoot links I have found, but they all mostly point to reformatting or reimaging the machine, or trying to replace that file with a good one, which I have not found a way to do.
See http://social.answers.microsoft.com/Forums/en-US/w7repair/thread/2d3ba36c-33c8-4869-95ab-49fbbe7d6579 and try this suggestion:
OPTION 1:
"1. rename bootcat.cashe for bootcat.old from C:\windows\system32\codein
the file is 384 bytes when broken , is 2,344,056 when OK. is beeing recreated when booting.
2. restart."
OPTION 2:
"1. delete bootcat.cashe from C:\windows\system32\codein
the file is 384 bytes when broken , is 2,344,056 when OK. is beeing recreated when booting.
2. copy from a ok pc c:\windows\system32\catroo
3. restart."
OPTION 1:
"1. rename bootcat.cashe for bootcat.old from C:\windows\system32\codein
the file is 384 bytes when broken , is 2,344,056 when OK. is beeing recreated when booting.
2. restart."
OPTION 2:
"1. delete bootcat.cashe from C:\windows\system32\codein
the file is 384 bytes when broken , is 2,344,056 when OK. is beeing recreated when booting.
2. copy from a ok pc c:\windows\system32\catroo
3. restart."
ASKER
renaming bootcat.cashe to bootcat.old did not work
I'm still having BSOD and when in Safe Mode it stops at windows\systems 32\drivers\classpnp.sys
I'm still having BSOD and when in Safe Mode it stops at windows\systems 32\drivers\classpnp.sys
ASKER
renamed classpnp.sys to classpnp.old
rebooted LT and still BSOD
When in safe mode it now stops at windows\systems32\drivers\
rebooted LT and still BSOD
When in safe mode it now stops at windows\systems32\drivers\
Then, see if Windows has created a new file classpnp.sys. If you have created, try doing the same with the disk.sys.
According to a user named The_Real_Chris (http://social.answers.microsoft.com/forums/en-us/w7repair/thread/be922817-2bd7-414a-bda6-38d635bc2e7c) he managed to solve the problem by copying the file classpnp.sys from another machine and replacing the file with the problem.
It is also a good try. I suggest doing this with another machine Windows 7, but in his case, note that he used the file from XP.
If this sugestion also didn't work, I'll try to see if I find some other tip.
According to a user named The_Real_Chris (http://social.answers.microsoft.com/forums/en-us/w7repair/thread/be922817-2bd7-414a-bda6-38d635bc2e7c) he managed to solve the problem by copying the file classpnp.sys from another machine and replacing the file with the problem.
It is also a good try. I suggest doing this with another machine Windows 7, but in his case, note that he used the file from XP.
If this sugestion also didn't work, I'll try to see if I find some other tip.
ASKER
renamed classpnp.sys to classpnp.old
rebooted LT and still BSOD
When in safe mode it now stops at windows\systems32\drivers\
renamed disk.sys to disk.old
now Safe Mode stops at hwpolicy.sys...attempting to renamed file and trying again
rebooted LT and still BSOD
When in safe mode it now stops at windows\systems32\drivers\
renamed disk.sys to disk.old
now Safe Mode stops at hwpolicy.sys...attempting to renamed file and trying again
But you already confirmed that Windows creates the files again?
ASKER
Yes...as I'm renaming them and rebooting to Safe Mode...Windows is recreating those renamed files.
It just seems like an endless list of .sys files to rename
It just seems like an endless list of .sys files to rename
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Ok, I understand. Sorry not able to help you.
The change from AHCI to Legacy worked on my PC! Thanks a lot!