Session3_inititalization_failed

[Tripredacus]

I was imaging up a bunch of notebooks when I came across one that wouldn't boot up. It was in the middle of the image load, meaning there were machines before it and after it that imaged fine. This one machine wouldn't seem to boot into Windows. I restarted and selected the "disable automatic restart on system failure" option from the XP boot menu. On the restart I encountered the following error:

SESSION3_INITIALIZATION_FAILED

STOP: 0x0000006F (0x6f)

I looked online for this error but it all seemed to be related to the install media, with a few references to HDDs.

I booted into NTFSDOS and confirmed that the drive was imaged properly.

OH my image was applied with WDS not from a CD, on 8 identical build notebooks. 7 work, 1 get this error.

Am I to presume that this is a problem with the HDD inside the unit?

[cluberti]

The error would have nothing to do with the imaging, per se - the windows kernel itself throws the bugcheck when it determines that the OS has failed to initialize properly (in this case it was Session3, there are Sessions 1-5, bug checks 0x6D to 0x71). The only thing relevant in the bugcheck is the first parameter (please post), as this tells us the status code that caused the kernel to conclude that the initialization of Windows has failed.

[Tripredacus]

The error would have nothing to do with the imaging, per se - the windows kernel itself throws the bugcheck when it determines that the OS has failed to initialize properly (in this case it was Session3, there are Sessions 1-5, bug checks 0x6D to 0x71). The only thing relevant in the bugcheck is the first parameter (please post), as this tells us the status code that caused the kernel to conclude that the initialization of Windows has failed.

I will try to remember this in the future. We ended up replacing the drive and reimaging it and it worked that way.

[scam]

The only thing relevant in the bugcheck is the first parameter (please post), as this tells us the status code that caused the kernel to conclude that the initialization of Windows has failed.

I have the same problem. The first error parameter is: 0xC0000034

I'm trying to install nLite from USB on EEE PC according to this instructions:

http://www.i64x.com/eeexp.php

[cluberti]

I have the same problem. The first error parameter is: 0xC0000034

I'm trying to install nLite from USB on EEE PC according to this instructions:

http://www.i64x.com/eeexp.php

According to that error, the error you got was "OBJECT_NAME_NOT_FOUND". What this means is that there is really two possible reasons for this - either a file on disk is missing or corrupted, or you have a bad device driver. Since this is Session3, it's probably smss.exe or one of the files it calls if we have corruption, and if it's a driver, that's nigh impossible to troubleshoot if you can't boot. It can also be caused if Windows is trying to load a driver during setup for your hardware, but the hardware isn't working properly - this is really rare, but it can be that too.

When during the install do you see this error?

[J3lly]

Hi i have the exact same problem. Thanks for saying what it means but do you have any idea on how to fix it ?

[fetgris]

Solution:

DONT REMOVE "Manual Install and Upgrade" with nlite. That one is needed for bootable usb install.

http://forum.eeeuser.com/viewtopic.php?id=34599&p=1

[Tripredacus]

Solution:

DONT REMOVE "Manual Install and Upgrade" with nlite. That one is needed for bootable usb install.

http://forum.eeeuser.com/viewtopic.php?id=34599&p=1

FYI: This may be a fix if using nLite (on EEEs), but I don't use nLite and didn't get this error on an EEE PC.