Try a different xp cd, like jedblack suggested.
Main Topics
Browse All TopicsHP Pavilion xt921
XPHome 128Mb RAM
30GB HD
Lost Inet connection, NIC not working, replaced it with another NIC, works ok...decided to put another NIC of same brand as original, NIC didn't work...hmmm, strange...ALso...it seems like the computer is getting slower and slower ....
Now I can't open My Computer, Properties...ditto for Control Panel, I have all the applets, but can't open any of them...
OK...time to re-image...
Ghosted the HD no problems...
Wiped the HD, no problems...no there is NOTHING on the HD...
Popped in XP CD for fresh install and things start going to %ell...
XP starts the normal install process, loading up the various files etc...but when it gets to the part where it is starting Windows, it blue screens with stop error 0x0000006f...
REsearch shows this...0x0000006F: SESSION3_INITIALIZATION_FA
(Click to consult the online MSDN article.)
The process creation failure indicated by this error message can only happen during the fairly brief time that the Windows Executive is being initialized, which is during phase 4 of Windows startup. Typically there is a problem with a device driver or with a missing or corrupt system file used during Windows startup.
I have NO device dirvers on this HD...the HD was wiped CLEAN...
So, swapped out the memory and the HD and still same stop error...
Possible motherboard???
Any thoughts???
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.

Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
I'd suspect your RAM here. Test it using memtest86+.
http://www.memtest.org/
Try your memory in different slots and also reseating it, and get more of it. 128 MB is very little for XP and this will be the cause of your slowdowns... 256 MB is the minimum for a smoothly running windows XP, If you want to actually work with it, 512 MB is more like what is needed.
Thanx guys...
1. How can I flash the BIOS without haveing any OS installed???
2. The XP cd is a brand new copy of the original...I will try the original...
3. I can load XP with 128 RAM...and I have gone thru 4 RAM chips so far...each one re-seated etc...but, yes, it should have more...but it originally had only 128 and was running XP slowly, but running ok...
4. Have NOT tried a different CD drive...
Thanx
Read this about bios, you need a bootdisk so you can flash from DOS.
http://www.wimsbios.com/HT
Business Accounts
Answer for Membership
by: jedblackPosted on 2005-10-23 at 21:17:48ID: 15144121
Reflash and or upgrade the system bios....
Have you tried to switch the XP cds? if its orginal without burrs, scratch, waves and not a copy then skip this....sometimes the dye in the cheap cd's start to break down. So what you get is files that copy over and pass the stream checksum. However in reality they are corrupt. Hence your session init failure.
second senario would be the cd drive itself, in older cd drives you will see the mouting points for the laser head start to wear and you get "beam velocity vibration" which cause data stream corruption
last but not least...if you were getting frozen windows session..that poing to the CPU. Motherboard will not stop the kernel from executing thread. You will however, see tons of errors in the event log and/or eventually blue screen. But if its completly frozen or parts of the os are frozen (i.e. mouse moves but cant type or do anthing else) that is your CPU(s) that have tanked
hope some of this helps....issue like this are tough...can be so many different things or a combo of things...