If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
Thread Tools | Display Modes |
#1
|
|||
|
|||
DD Recovery Help Needed
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. |
Ads |
#2
|
|||
|
|||
DD Recovery Help Needed
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 |
#3
|
|||
|
|||
DD Recovery Help Needed
Macrium Reflect installs Win PE3 in memory as drive X:. X: has SFC application. However I cannot find the right combination of parameters to get SFC to do any scan. The is even an offboot param to specify a different drive as the boot drive but no go for that. X: seems to have windows files but I do not know how to do a compare between X: and C: to see if it can identify any anomalies. I plugged in a USB drive while in Win PE and am able to copy files from C: and D: to the USB drive. That helps some. About ready to give up on fixing the SSD. Any additional suggestions please. Paul wrote: 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 |
#4
|
|||
|
|||
DD Recovery Help Needed
Birdie wrote:
Macrium Reflect installs Win PE3 in memory as drive X:. X: has SFC application. However I cannot find the right combination of parameters to get SFC to do any scan. The is even an offboot param to specify a different drive as the boot drive but no go for that. X: seems to have windows files but I do not know how to do a compare between X: and C: to see if it can identify any anomalies. I plugged in a USB drive while in Win PE and am able to copy files from C: and D: to the USB drive. That helps some. About ready to give up on fixing the SSD. Any additional suggestions please. What you could do is, while you're in the recovery system, make an image of the C: and D: partitions (and any other partitions) to an external drive, i.e. for example the USB drive. I.e. you not restore your old image(s), but make new ones. That way, if you restore/re-install the system in some way, but later find out that there was something on the SSD which you want/need, you can - try to - restore it - file-by-file - from the newly made images. It's basically a technique anyone should use in any kind of recovery operation: If the 'sick' disk still can be accessed, *first* make a backup of it, *before* doing anything which might change its content. That way, you can always go back, in case your recovery attempts fail or make things worse instead of better. [...] |
#5
|
|||
|
|||
DD Recovery Help Needed
Birdie wrote:
Macrium Reflect installs Win PE3 in memory as drive X:. X: has SFC application. However I cannot find the right combination of parameters to get SFC to do any scan. The is even an offboot param to specify a different drive as the boot drive but no go for that. X: seems to have windows files but I do not know how to do a compare between X: and C: to see if it can identify any anomalies. I plugged in a USB drive while in Win PE and am able to copy files from C: and D: to the USB drive. That helps some. About ready to give up on fixing the SSD. Any additional suggestions please. Here's a picture of the HAL elements on my dual core processor. If one of the three files was damaged, that would probably do it. https://i.postimg.cc/6pg24fB4/Win-XP...ce-Manager.gif ACPI Multiprocessor PC (a P4 with hyperthreading, a Core2Duo) hal.dll ntkmlpa.exe ntoskml.exe And it's not just the files that are important. More info here. https://neosmart.net/wiki/hal-dll-missing-corrupt/ Paul |
Thread Tools | |
Display Modes | |
|
|