Forum Home
Press F1
Thread ID: 91273	2008-07-01 22:49:00	Blue screen when installing XP ? ... but linux works!?	mOOseCaNNoN (13319)	Press F1

Post ID	Timestamp	Content	User
684438	2008-07-01 22:49:00	Hi all, My friend bought a new computer a while ago which came with Vista, over time it got infected with all sorts of spyware and viruses and he asks me if i could re-format his computer and install XP, i said sure because it would make his computer run faster (it's a 1.8 with 1GB of RAM). I'm using a corporate XP disc with SP2 slip streamed into it (legit key btw) All is well when it boots from the CD and says inspecting hardware, it continues to bring up the blue loading screen and installs the different components (grey bar down the bottom), but when it says windows is starting up it blue screens every time. I tried taking his hdd out, plugging it into my computer and loading the setup beyond the point where it blue screns on his machine, but then I put it back in his machine and it blue screens in a different place. I thought screw it and just loaded ubuntu on it which works fine, but he's a gamer and wants to be able to play CS etc which is a hassle to get working on linux. has anyone had this problem before? I thought it may be faulty RAM but linux seems to work fine without crashing ? is it because linux is so l33t that it can run on faulty RAM? lol your thoughts ? :) MC :badpc:	mOOseCaNNoN (13319)
684439	2008-07-01 22:57:00	CD drive or HD dying??	jwil1 (65)
684440	2008-07-01 23:00:00	ummm. sorry i forgot to mention that i plugged a different hard drive into his machine and tried it, did the same blue screen in the same place. So a faulty CD drive could be a possibility?	mOOseCaNNoN (13319)
684441	2008-07-01 23:12:00	Had a similar issue with a PC a few months back - in my case it was the onboard sound card (Realtek AC'97) that was causing the BSOD . Disabled it in the BIOS, re-installed XP, re-enabled it in BIOS, downloaded drivers, and hey presto . Maybe be a long shot, but give it a try . . . :thumbs:	nofam (9009)
684442	2008-07-01 23:13:00	What does the BSOD say (ie what is the filename that it gives?)	jwil1 (65)
684443	2008-07-01 23:21:00	from memory the BSOD didnt give us a file name, just a bunch of code. I'll try your suggestion nofam, sounds like a long shot but worth a try. It's an HP machine if that helps at all. Oh I also forgot to mention that I took his hdd, plugged it into my pc, did a full install of windows (minus any drivers because of different hardware), used windows deployment tooks to reseal it, took the hdd out of my computer, pluggd it back into his, booted it up, starts loading the mini-setup and BSOD again...	mOOseCaNNoN (13319)
684444	2008-07-01 23:31:00	Might pay to run memtest through it to eliminate memory issues.	stormdragon (6013)
684445	2008-07-01 23:31:00	Could be dodgy graphics card?? BTW If you install XP on a machine you can't transfer the HD containing XP to another unless it's exactly the same as the one you installed it on and expect it to work properly :) This worked with MSDOS/Win 3.x/9x though.	jwil1 (65)
684446	2008-07-01 23:35:00	Could be dodgy graphics card?? BTW If you install XP on a machine you can't transfer the HD containing XP to another unless it's exactly the same as the one you installed it on and expect it to work properly :) This worked with MSDOS/Win 3.x/9x though. I thought you could if you resealed it using deployment tools? I know for a fact that the graphics card is fine :thumbs:	mOOseCaNNoN (13319)
684447	2008-07-01 23:35:00	Is it because Linux is so l33t that it can run on faulty RAM? lol :p Something like that. See if you can tell which driver it's failing on - that may give some clue, you can often temporarily disable hardware in the BIOS like nofam suggested. I'd grab the Ultimate Boot CD (www.ultimatebootcd.com/) (burn ISO to a cd using ImgBurn (http:)) and do a memory test. Wouldn't hurt to do a HDD diag either. And pull out all PCI cards that aren't necessary.	wratterus (105)
1 2