SESSION3_INITIALIZATION_FAILED

nearownkira · 13th Feb 2008, 12:31 PM

I bought all new computer part and assembled together, when I wanted to install window xp, it will go to this BSOD screen,SESSION3_INITIALIZATION_FAILED.I tried check google, but cant find any solution

spec:
asrock conroe 945GC
e2160
kingston 1gb 667mhz
wd 160gb

Chai · 13th Feb 2008, 03:27 PM

If you get BSOD when you are trying to install new WinXP installation, it usually means hardware problem. Try changing the RAM first.

zicovsky · 14th Feb 2008, 12:37 AM

could be incompatibility with something.

could also be defective hard drive.

peaz · 14th Feb 2008, 12:51 AM

I'd say try checking the RAM too.

belikethat · 14th Feb 2008, 01:32 AM

probably u might want to read this, they fix it.. it's something to do with the driver

session3_initialization_failed - Tech Support Forums - TechIMO.com

64bit · 14th Feb 2008, 08:24 PM

If it is a blue screen on death message, the cause might be that your BIOS is set as running SATA HDD as RAID, try setting the SATA options to IDE or install the RAID SATA driver via floppy disk at the 1st install screen

nearownkira · 15th Feb 2008, 01:00 PM

thanks, I found out what is the problem, the Window XP installation CD has too many scratches.

Ares68 · 28th Mar 2008, 09:04 PM

I got an pretty old Compaq EVO.
Had the same problem after crash of unique harddisk.
Installed a brand new ATA/SATA Hard Drive, 160 Gb.

Problem corrected by changing the Harddisk transfer mode option: was set to UDMA, changed to Ultra DMA 0.

13th Feb 2008, 12:31 PM	#1 (permalink)
nearownkira Just Started Join Date: 18 Jan 2007 Posts: 41 Reputation: 0 Rep Power: 0	SESSION3_INITIALIZATION_FAILED I bought all new computer part and assembled together, when I wanted to install window xp, it will go to this BSOD screen,SESSION3_INITIALIZATION_FAILED.I tried check google, but cant find any solution spec: asrock conroe 945GC e2160 kingston 1gb 667mhz wd 160gb

13th Feb 2008, 03:27 PM	#2 (permalink)
Chai Administrator Join Date: 6 Oct 2002 Location: Maranello Posts: 26,260 Reputation: 3845 Rep Power: 71	If you get BSOD when you are trying to install new WinXP installation, it usually means hardware problem. Try changing the RAM first. __________________ Chai (Contributor & Forum Admin) http://www.techarp.com/

14th Feb 2008, 12:37 AM	#3 (permalink)
zicovsky I'm a regular Join Date: 11 Feb 2005 Posts: 300 Reputation: 132 Rep Power: 5	could be incompatibility with something. could also be defective hard drive. __________________ life is what happens to you while you're busy making other plans.. Please SUPPORT RojakPot!

14th Feb 2008, 12:51 AM	#4 (permalink)
peaz ARP Webmaster Join Date: 13 Oct 2002 Location: http://atpeaz.placidthoughts.com/ Posts: 8,499 Reputation: 1633 Rep Power: 30	I'd say try checking the RAM too. __________________ Ken Ng Tech ARP Visit my web gallery - Ken's Digital Canvas Shoot and Earn Money from Stock Photography Sterling@PJ Community Forums

14th Feb 2008, 01:32 AM	#5 (permalink)
belikethat I'm a regular Join Date: 25 Apr 2006 Posts: 496 Reputation: 58 Rep Power: 3	probably u might want to read this, they fix it.. it's something to do with the driver session3_initialization_failed - Tech Support Forums - TechIMO.com __________________ Control Panel Settings & Options Edit Signature

14th Feb 2008, 08:24 PM	#6 (permalink)
64bit Just Started Join Date: 29 Jun 2006 Posts: 30 Reputation: 0 Rep Power: 0	If it is a blue screen on death message, the cause might be that your BIOS is set as running SATA HDD as RAID, try setting the SATA options to IDE or install the RAID SATA driver via floppy disk at the 1st install screen

15th Feb 2008, 01:00 PM	#7 (permalink)
nearownkira Just Started Join Date: 18 Jan 2007 Posts: 41 Reputation: 0 Rep Power: 0	thanks, I found out what is the problem, the Window XP installation CD has too many scratches.

28th Mar 2008, 09:04 PM	#8 (permalink)
Ares68 Newbie Join Date: 28 Mar 2008 Posts: 1 Reputation: 0 Rep Power: 0	SESSION3_INITIALIZATION_FAILED I got an pretty old Compaq EVO. Had the same problem after crash of unique harddisk. Installed a brand new ATA/SATA Hard Drive, 160 Gb. Problem corrected by changing the Harddisk transfer mode option: was set to UDMA, changed to Ultra DMA 0.