F
Frank
Hi All,
Background of the problem:
In the process of trying to upgrade from a P2 to a P3 processor I was not
able to boot into Windows XP Pro, and got a blue screen with the error
message:
***Hardware Malfunction
Call you hardware vendor for support
***The system has halted
I made several attempts at running in-place Repair Installations, but they
all failed and they all resulted in the same blue screen and error message,
they also occurred at unpredictable times during the Repair routine. While
the P3 did work fine in W98 (I have a multi-boot machine) I gave up on the
P3, put the P2 back in, and was now able to boot into XP Pro but was left
with these problems........
-Several errors started appearing in Event Viewer System log
-XP's firewall was inoperable
-Several services were unable to start
-I lost all control over Display Properties (no tabs, etc)
Please see this screen shot of the Display Properties dialog window I was
left with, it's worth 1000 words. http://shycatwebs.com/displayprops.jpg
Where I'm at now:
I believe I've straightened out the Event Viewer System error messages, and
have XPs firewall working again. There are now no more Event Viewer System
errors messages at boot up, and the System Information entries I get now
are the same as I had before trying to upgrade the processor. I was able
to do this after reviewing an Event Viewer Application log entry I came
across, the entry is shown at the bottom of this post. This log entry is
from a disk check that was performed by XP during the first successful boot
I made into XP after giving up on the Repair Installation and reinstalling
the original P2 processor.
It seems the volume was dirty as a result of all the failed attempts at
running Repair Installations, especially the ***Hardware Malfunction
blue screens that halted the system abruptly. Two of those blue screens
occurred while Setup was copying files (at appx the 5% mark on the progress
bar), so I assume some corruption had occurred because of it.
If you look at the errors noted next to the paths shown on the below log,
they all say "first allocation unit is not valid. The entry will be
truncated." Can somebody please explain what that error means? The reason
I ask is that after checking the paths, 22 of the 24 files/folders don't
exist at the locations shown. Could it be that the error is telling me
that the FAT had a reference for a file that didn't exist, and that
truncating the entry means it was removed from the FAT?
14 of the 22 missing files/folders I was able to find elsewhere in Windows
(10 of them in the \windows\system32\dllcache folder). So what I did was
copy the 14 matching filenames from their alternate locations to the
locations shown in the paths from the log. After booting into XP I was
pleased to find the EV errors gone, services that couldn't start were now
running, and I was able to enable the firewall.
I still have two things (that I know of) that need to be addressed.
- The total loss of Display Properties control
- The 8 files/folders I couldn't find anywhere in XP
Since two of the lost files/folders have ".cpl." in their names I'm
focusing on the files/folders first, because I assume they have something
to do with the Control Panel and may relate to the Display Properties
problem. Does that sound right? Here's the 8 files/folders I couldn't
find anywhere in, or under, the \windows folder:
\WINDOWS\WindowsShell.Manifest
\WINDOWS\WinSxS\InstallTemp
\WINDOWS\system32\logonui.exe.manifest
\WINDOWS\system32\ncpa.cpl.manifest
\WINDOWS\system32\nwc.cpl.manifest
\WINDOWS\Help\ieeula.chm
\WINDOWS\Help\printing.chm
\WINDOWS\Driver Cache\i386
Since none of those files/folders were on my disk I checked on the XP CD,
the only file I could find was the ieeula.chm file. I also referenced the
\windows\repair\setup.log file to see what else I could find out about
these files/folders. It showed that the sp1.cab and driver.cab files were
copied to the \WINDOWS\Driver Cache\i386 folder when XP was first
installed, and both of those files were on the CD. So I created a
\WINDOWS\Driver Cache\i386 folder and copied those files there, I also
extracted the ieeula.chm file to \WINDOWS\Help\. Doing so didn't help the
Display Properties problem, so I ended up removing them.
Can anybody offer any advice on the best way to go about finding or
recreating those files/folders? Which tools should I focus on? In other
words, would running a Repair Installation recreate them, as well as
restore my Display Properties? And though I'm a little apprehensive about
Repair Installations, it should work now that the P3 isn't an issue
anymore, but I'd like to explore other avenues first before resorting to a
Repair Installation again. Any suggestions or pointers would be
appreciated.
Thanks,
Frank
Event Type: Information
Event Source: Winlogon
Event Category: None
Event ID: 1001
Date: 10/7/2003
Time: 2:30:36 PM
User: N/A
Computer: CC494569-A
Description:
Checking file system on \Device\Harddisk1\Partition1
The type of the file system is FAT32.
The volume is dirty.
Volume Serial Number is 3E8F-0823
\WINDOWS\Prefetch first allocation unit is not valid. The entry will be
truncated.
\WINDOWS\WindowsShell.Manifest first allocation unit is not valid. The
entry will be truncated.
\WINDOWS\WinSxS\InstallTemp first allocation unit is not valid. The entry
will be truncated.
\WINDOWS\system32\asr_fmt.exe first allocation unit is not valid. The
entry will be truncated.
\WINDOWS\system32\d3dim700.dll first allocation unit is not valid. The
entry will be truncated.
\WINDOWS\system32\diskperf.exe first allocation unit is not valid. The
entry will be truncated.
\WINDOWS\system32\dxdllreg.exe first allocation unit is not valid. The
entry will be truncated.
\WINDOWS\system32\logonui.exe.manifest first allocation unit is not valid.
The entry will be truncated.
\WINDOWS\system32\ncpa.cpl.manifest first allocation unit is not valid.
The entry will be truncated.
\WINDOWS\system32\ntdsbcli.dll first allocation unit is not valid. The
entry will be truncated.
\WINDOWS\system32\nwc.cpl.manifest first allocation unit is not valid. The
entry will be truncated.
\WINDOWS\system32\oakley.dll first allocation unit is not valid. The entry
will be truncated.
\WINDOWS\system32\odfox32.dll first allocation unit is not valid. The
entry will be truncated.
\WINDOWS\system32\raschap.dll first allocation unit is not valid. The
entry will be truncated.
\WINDOWS\system32\rasppp.dll first allocation unit is not valid. The entry
will be truncated.
\WINDOWS\system32\spxcoins.dll first allocation unit is not valid. The
entry will be truncated.
\WINDOWS\system32\dllcache\SHLWAPI.DLL first allocation unit is not valid.
The entry will be truncated.
\WINDOWS\system32\dllcache\URLMON.DLL first allocation unit is not valid.
The entry will be truncated.
\WINDOWS\inf\LAYOUT.PNF first allocation unit is not valid. The entry will
be truncated.
\WINDOWS\inf\netoc.inf first allocation unit is not valid. The entry will
be truncated.
\WINDOWS\Help\ieeula.chm first allocation unit is not valid. The entry
will be truncated.
\WINDOWS\Help\printing.chm first allocation unit is not valid. The entry
will be truncated.
\WINDOWS\Fonts\micross.ttf first allocation unit is not valid. The entry
will be truncated.
\WINDOWS\Driver Cache\i386 first allocation unit is not valid. The entry
will be truncated.
Bad links in lost chain at cluster 1118100 corrected.
Convert lost chains to files (Y/N)? 43896 KB in 70 recovered files.
Windows has made corrections to the file system.
8177128 KB total disk space.
103112 KB in 769 hidden files.
16068 KB in 3649 folders.
4463864 KB in 44211 files.
3594080 KB are available.
4096 bytes in each allocation unit.
2044282 total allocation units on disk.
898520 allocation units available on disk.
Checking file system on D:
The type of the file system is FAT32.
One of your disks needs to be checked for consistency. You
may cancel the disk check, but it is strongly recommended
that you continue.
Windows will now check the disk.
Volume Serial Number is 3E8F-0823
Windows has checked the file system and found no problems.
8177128 KB total disk space.
103116 KB in 770 hidden files.
16064 KB in 3648 folders.
4463872 KB in 44212 files.
3594072 KB are available.
4096 bytes in each allocation unit.
2044282 total allocation units on disk.
898518 allocation units available on disk.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Background of the problem:
In the process of trying to upgrade from a P2 to a P3 processor I was not
able to boot into Windows XP Pro, and got a blue screen with the error
message:
***Hardware Malfunction
Call you hardware vendor for support
***The system has halted
I made several attempts at running in-place Repair Installations, but they
all failed and they all resulted in the same blue screen and error message,
they also occurred at unpredictable times during the Repair routine. While
the P3 did work fine in W98 (I have a multi-boot machine) I gave up on the
P3, put the P2 back in, and was now able to boot into XP Pro but was left
with these problems........
-Several errors started appearing in Event Viewer System log
-XP's firewall was inoperable
-Several services were unable to start
-I lost all control over Display Properties (no tabs, etc)
Please see this screen shot of the Display Properties dialog window I was
left with, it's worth 1000 words. http://shycatwebs.com/displayprops.jpg
Where I'm at now:
I believe I've straightened out the Event Viewer System error messages, and
have XPs firewall working again. There are now no more Event Viewer System
errors messages at boot up, and the System Information entries I get now
are the same as I had before trying to upgrade the processor. I was able
to do this after reviewing an Event Viewer Application log entry I came
across, the entry is shown at the bottom of this post. This log entry is
from a disk check that was performed by XP during the first successful boot
I made into XP after giving up on the Repair Installation and reinstalling
the original P2 processor.
It seems the volume was dirty as a result of all the failed attempts at
running Repair Installations, especially the ***Hardware Malfunction
blue screens that halted the system abruptly. Two of those blue screens
occurred while Setup was copying files (at appx the 5% mark on the progress
bar), so I assume some corruption had occurred because of it.
If you look at the errors noted next to the paths shown on the below log,
they all say "first allocation unit is not valid. The entry will be
truncated." Can somebody please explain what that error means? The reason
I ask is that after checking the paths, 22 of the 24 files/folders don't
exist at the locations shown. Could it be that the error is telling me
that the FAT had a reference for a file that didn't exist, and that
truncating the entry means it was removed from the FAT?
14 of the 22 missing files/folders I was able to find elsewhere in Windows
(10 of them in the \windows\system32\dllcache folder). So what I did was
copy the 14 matching filenames from their alternate locations to the
locations shown in the paths from the log. After booting into XP I was
pleased to find the EV errors gone, services that couldn't start were now
running, and I was able to enable the firewall.
I still have two things (that I know of) that need to be addressed.
- The total loss of Display Properties control
- The 8 files/folders I couldn't find anywhere in XP
Since two of the lost files/folders have ".cpl." in their names I'm
focusing on the files/folders first, because I assume they have something
to do with the Control Panel and may relate to the Display Properties
problem. Does that sound right? Here's the 8 files/folders I couldn't
find anywhere in, or under, the \windows folder:
\WINDOWS\WindowsShell.Manifest
\WINDOWS\WinSxS\InstallTemp
\WINDOWS\system32\logonui.exe.manifest
\WINDOWS\system32\ncpa.cpl.manifest
\WINDOWS\system32\nwc.cpl.manifest
\WINDOWS\Help\ieeula.chm
\WINDOWS\Help\printing.chm
\WINDOWS\Driver Cache\i386
Since none of those files/folders were on my disk I checked on the XP CD,
the only file I could find was the ieeula.chm file. I also referenced the
\windows\repair\setup.log file to see what else I could find out about
these files/folders. It showed that the sp1.cab and driver.cab files were
copied to the \WINDOWS\Driver Cache\i386 folder when XP was first
installed, and both of those files were on the CD. So I created a
\WINDOWS\Driver Cache\i386 folder and copied those files there, I also
extracted the ieeula.chm file to \WINDOWS\Help\. Doing so didn't help the
Display Properties problem, so I ended up removing them.
Can anybody offer any advice on the best way to go about finding or
recreating those files/folders? Which tools should I focus on? In other
words, would running a Repair Installation recreate them, as well as
restore my Display Properties? And though I'm a little apprehensive about
Repair Installations, it should work now that the P3 isn't an issue
anymore, but I'd like to explore other avenues first before resorting to a
Repair Installation again. Any suggestions or pointers would be
appreciated.
Thanks,
Frank
Event Type: Information
Event Source: Winlogon
Event Category: None
Event ID: 1001
Date: 10/7/2003
Time: 2:30:36 PM
User: N/A
Computer: CC494569-A
Description:
Checking file system on \Device\Harddisk1\Partition1
The type of the file system is FAT32.
The volume is dirty.
Volume Serial Number is 3E8F-0823
\WINDOWS\Prefetch first allocation unit is not valid. The entry will be
truncated.
\WINDOWS\WindowsShell.Manifest first allocation unit is not valid. The
entry will be truncated.
\WINDOWS\WinSxS\InstallTemp first allocation unit is not valid. The entry
will be truncated.
\WINDOWS\system32\asr_fmt.exe first allocation unit is not valid. The
entry will be truncated.
\WINDOWS\system32\d3dim700.dll first allocation unit is not valid. The
entry will be truncated.
\WINDOWS\system32\diskperf.exe first allocation unit is not valid. The
entry will be truncated.
\WINDOWS\system32\dxdllreg.exe first allocation unit is not valid. The
entry will be truncated.
\WINDOWS\system32\logonui.exe.manifest first allocation unit is not valid.
The entry will be truncated.
\WINDOWS\system32\ncpa.cpl.manifest first allocation unit is not valid.
The entry will be truncated.
\WINDOWS\system32\ntdsbcli.dll first allocation unit is not valid. The
entry will be truncated.
\WINDOWS\system32\nwc.cpl.manifest first allocation unit is not valid. The
entry will be truncated.
\WINDOWS\system32\oakley.dll first allocation unit is not valid. The entry
will be truncated.
\WINDOWS\system32\odfox32.dll first allocation unit is not valid. The
entry will be truncated.
\WINDOWS\system32\raschap.dll first allocation unit is not valid. The
entry will be truncated.
\WINDOWS\system32\rasppp.dll first allocation unit is not valid. The entry
will be truncated.
\WINDOWS\system32\spxcoins.dll first allocation unit is not valid. The
entry will be truncated.
\WINDOWS\system32\dllcache\SHLWAPI.DLL first allocation unit is not valid.
The entry will be truncated.
\WINDOWS\system32\dllcache\URLMON.DLL first allocation unit is not valid.
The entry will be truncated.
\WINDOWS\inf\LAYOUT.PNF first allocation unit is not valid. The entry will
be truncated.
\WINDOWS\inf\netoc.inf first allocation unit is not valid. The entry will
be truncated.
\WINDOWS\Help\ieeula.chm first allocation unit is not valid. The entry
will be truncated.
\WINDOWS\Help\printing.chm first allocation unit is not valid. The entry
will be truncated.
\WINDOWS\Fonts\micross.ttf first allocation unit is not valid. The entry
will be truncated.
\WINDOWS\Driver Cache\i386 first allocation unit is not valid. The entry
will be truncated.
Bad links in lost chain at cluster 1118100 corrected.
Convert lost chains to files (Y/N)? 43896 KB in 70 recovered files.
Windows has made corrections to the file system.
8177128 KB total disk space.
103112 KB in 769 hidden files.
16068 KB in 3649 folders.
4463864 KB in 44211 files.
3594080 KB are available.
4096 bytes in each allocation unit.
2044282 total allocation units on disk.
898520 allocation units available on disk.
Checking file system on D:
The type of the file system is FAT32.
One of your disks needs to be checked for consistency. You
may cancel the disk check, but it is strongly recommended
that you continue.
Windows will now check the disk.
Volume Serial Number is 3E8F-0823
Windows has checked the file system and found no problems.
8177128 KB total disk space.
103116 KB in 770 hidden files.
16064 KB in 3648 folders.
4463872 KB in 44212 files.
3594072 KB are available.
4096 bytes in each allocation unit.
2044282 total allocation units on disk.
898518 allocation units available on disk.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.