Birdie wrote:
Win XP Pro on a Lenovo T500 laptop
Session3 error at blue screen on boot.
Has a Samsung Pro 256G SSD. C: and D: partitions.
Tried all Win boot methods on the SSD - no go.
Plugged and unplugged the SSD several times in case of a mechanical
problem. No go there either.
Installed original HDD and it boots and etc OK. So maybe only the SSD
is the problem.
Have a Macrium Rescue Disk made when I installed the SSD !
Put SSD back in.
Booted on CD OK. Win PE is there. All drivers are there.
Tried to do the Macrium FIX (boot record etc) all it could but that did
not work. Will Macrium FIX report problems or just mush on through all
fixes ?
Went to Win PE that Macrium installed in memory and seen as Disk X:
Opened Windows Explorer and see what looks like all SSD partitions are
there with correct sizes etc.
I do have a Macrium restore file on LAN but it is old and not sure if I
should bother,.
Win PE has ChkDisk.
Question 1:
What ChkDisk options should I run on the SSD ?
The Lenovo T500 has a built in BIOS disk check that I started to run and
for the first few parts it passed but I gave up since I am not familiar
with the Lenovo disk check.
Question 2:
If I can see m LAN can I copy SSD files to a NAS there ?
Not sure if that is possible or how that works buy would like to try
since it will diminish the full restore to the HDD.
Question 3:
Can I tell if the SSD does get "fixed" ?, Should I get the data off and
abandon it ?
I have other PCs running older and newer Samsung SSDs and no problems.
I really like the quick boot the SSD gives me.
SSD is only two years old.
As an aside, what kind of problem might the SSD be having ?
Thank you.
This web site is both helpful and un-helpful.
It says SESSION3_INITIALIZATION_FAILED 0x6F stop code,
indicates a missing file. The next image down, mentions
HAL (Hardware Abstraction Layer) is missing. So it's
something to do with HAL. WinXP has Uniprocessor ACPI,
Multiprocessor ACPI, and at least one non-ACPI option
for the HAL, and the HAL has to match the situation
for the install to work its best.
https://www.reviversoft.com/blog/201...zation-failed/
So you really need to trace down the 0x6F thing.
http://aumha.org/a/stop.htm
(Sorry, slim-pickins for 0x6F...
archive.org is broken for me at the moment)
Macrium "boot fix" can't fix that, because it
might be a file that is missing, deleted (or
maybe the signature is damaged). Macrium cannot
create files from thin air - that's what OS
restores are for.
By mounting the Macrium restore MRIMG as a disk partition,
you could compare the core files in the System32 versus
the files in the machine right now. And the difference might
hint which file or files have changed.
The HAL consists of several files, and the HAL is
selected during install. You'd need to dig up a
good article on HAL, to find a description of what
is involved. And, of course, we're relying on that error
number to be accurate, and the problem isn't something
else that causes 0x6F to pop up like that.
You could do a Repair Install of WinXP, but this late
in the game, that would be a hell of a lot of work.
WinXP is the last OS where you can *boot* the installer
media and do a Repair Install. With the usual caveats on
version matching.
I would tinker on comparing System32 files and see
what I could figure out first.
If sfc /scannow were to work, it would probably be
"easy to fix". Maybe someone else knows how to do
that, in your current broken state. I don't think
there are quite the same offline repair options as in later
OSes. And using the installer CD as the "reference"
for SFC, just feels... so wrong. Windows File Protection
has the capability to put files back from things like
a DLL cache, but again, it's got no opportunity to run
when the OS won't boot.
Paul