Whitesupraboy2 Posted July 6, 2008 Share Posted July 6, 2008 Right, Bought all the bits built a PC, Put XP on. Moved it from my room too the room it was going in and lsass.exe goes corrupt and causes the registry to go bang...and ends up with the PC in a never ending boot loop. Used a disc off the net to resolve it by going back to a previous checkpoint of the registry but this only fixes it for a while as it happened again. I installed XP 3 times and got the same!! so thought right it must be the XP disc. So took my vista disk installed it no problems, moved it to her room and same problem it now wont boot saying corrupt files on C: drive. So does the whole fix thing and it didnt fix it, I didnt repartition between the installs but did quick format. Anyone seen this before? before i install for the 5th time!! Its weird I can reboot over and over but as soon as its moved...i.e power totally unplugged I get a problem next time where it wont boot properly Tried safe mode, tried UBC4win Disc. Im wondering if its something to do with the hard drive. Im thinking of installing windows on an E: partition to rule out bad sectors that are causing these corrupt system files. 500Gb hard disc C: - 100Gb d: 200Gb E: 176Gb Im pulling my hair out here Link to comment Share on other sites More sharing options...
MaveriK Posted July 6, 2008 Share Posted July 6, 2008 The XP rebooting so sounds like a sasser problem. I guess i would disconnect the machine from the network and switch it off cold. Then install windows again (booting from the cd of course) after full formatting the entire hard drive. Once installed reboot it a few times and see if the system is stable. Do not connect it to the internet until you are happy it is stable and that you have virus/firewall/spyware protection on it. Then update the holy hell out of it. Link to comment Share on other sites More sharing options...
Branners Posted July 6, 2008 Share Posted July 6, 2008 poorly matched memory could cause the problem. Its not writing the registry back properly. Quite why it does it when you move it I dont know. I would remove all but a single stick of memory and try again. Link to comment Share on other sites More sharing options...
Whitesupraboy2 Posted July 6, 2008 Author Share Posted July 6, 2008 The XP rebooting so sounds like a sasser problem. I guess i would disconnect the machine from the network and switch it off cold. Then install windows again (booting from the cd of course) after full formatting the entire hard drive. Once installed reboot it a few times and see if the system is stable. Do not connect it to the internet until you are happy it is stable and that you have virus/firewall/spyware protection on it. Then update the holy hell out of it. exactly what i read up it could be. I had full antivirus etc... and tried various things. but the XP machine was rebooted close to 10 times before being moved (i.e fully powered off I guess) and was used for close to 5 hours where it was prior to moving. poorly matched memory could cause the problem. Its not writing the registry back properly. Quite why it does it when you move it I dont know. I would remove all but a single stick of memory and try again. Im going to give this a go, it could easily be this, it being a new machine and all! Link to comment Share on other sites More sharing options...
DamanC Posted July 6, 2008 Share Posted July 6, 2008 Naff memory or failing Hard drive is normally the cause here. Link to comment Share on other sites More sharing options...
jonshaw_uk Posted July 6, 2008 Share Posted July 6, 2008 id go with the memory - we have probs similar to this all the time Link to comment Share on other sites More sharing options...
b_have Posted July 6, 2008 Share Posted July 6, 2008 Shall I pop around to take a look James? Link to comment Share on other sites More sharing options...
Branners Posted July 6, 2008 Share Posted July 6, 2008 Shall I pop around to take a look James? bring a big stick and just beat it to death, its kinder in the long run. Link to comment Share on other sites More sharing options...
Whitesupraboy2 Posted July 6, 2008 Author Share Posted July 6, 2008 Shall I pop around to take a look James? lol well rebuilt again and done it again GGRRRRRR this time installed on to partition E: and with one memory stick and it occured again. I will try with another hard drive I reckon ive got one hanging around somewhere. Any chance it could be the Sata cable? Link to comment Share on other sites More sharing options...
DamanC Posted July 6, 2008 Share Posted July 6, 2008 Can be, unlikely thou. Link to comment Share on other sites More sharing options...
Scott Posted July 6, 2008 Share Posted July 6, 2008 lol well rebuilt again and done it again GGRRRRRR this time installed on to partition E: and with one memory stick and it occured again. I will try with another hard drive I reckon ive got one hanging around somewhere. Any chance it could be the Sata cable? Have you tried it disconnected from the net yet? Link to comment Share on other sites More sharing options...
Whitesupraboy2 Posted July 6, 2008 Author Share Posted July 6, 2008 Have you tried it disconnected from the net yet? yea that happened the time before last, hadnt even installed the wireless card Current build; without 1 of the 1gb sticks. So far ok, but the builds have lasted longer then this. If it lasts a few days then I will switch the sticks over and hopefully it will error with the other stick. Bad bit bought from Ebuyer in a 2x 1Gb back so both will have to go back. Link to comment Share on other sites More sharing options...
Whitesupraboy2 Posted July 6, 2008 Author Share Posted July 6, 2008 Jut updting n case anyone searches relly. Currently doing memory checks using http://oca.microsoft.com/en/windiag.asp and http://www.memtest.org/#downiso This tests memory without the operating system. Im doing 1 stick at a time. Im hoping for a fail! Link to comment Share on other sites More sharing options...
RedM Posted July 6, 2008 Share Posted July 6, 2008 Why partition E: in particular? Is XP not the primary OS? Link to comment Share on other sites More sharing options...
Whitesupraboy2 Posted July 6, 2008 Author Share Posted July 6, 2008 Why partition E: in particular? Is XP not the primary OS? I tried it on C: I was beginning to think bad hard drive, so I wondered if it was bad sectors or something. Hence I gave drive e: a go but made no difference. Ive been working on this PC for nearly the whole weekend....ill take any fix Memory checks still going.... Link to comment Share on other sites More sharing options...
MaveriK Posted July 6, 2008 Share Posted July 6, 2008 Fingers crossed buddy Link to comment Share on other sites More sharing options...
RobCowley Posted July 6, 2008 Share Posted July 6, 2008 Had a very similiar problem this weekend...turned out to be the SATA cable. It all works fine now i've changed it! Are there such things as SATA 1 and 2 cables or are they both the same? Just i seem to remember buying the cable that works branded as "SATA II" Also the cable i used that didn't work with the SATA2 drive is working perfectly with an SATA drive! Link to comment Share on other sites More sharing options...
Whitesupraboy2 Posted July 6, 2008 Author Share Posted July 6, 2008 Had a very similiar problem this weekend...turned out to be the SATA cable. It all works fine now i've changed it! Are there such things as SATA 1 and 2 cables or are they both the same? If its the cable I wont be impressed!!! However I'll take the fix, if memory comes back clean. I'll switch the DVD rom cable with hard drive cable. Link to comment Share on other sites More sharing options...
RedM Posted July 6, 2008 Share Posted July 6, 2008 Failing any resolution I can totally recommend Ubuntu Linux. Link to comment Share on other sites More sharing options...
Supra Size Me Posted July 6, 2008 Share Posted July 6, 2008 just a quick idea, have you checked all of your voltages in bios etc as a slightly low voltage can cause that kinda crap esp if its memory or mobo. Along the same lines is your PSU up for the job for the build you've put together ? or not firing on all cylinders so to speak ? just the areas i'd be concentrating on first by sound of it all Link to comment Share on other sites More sharing options...
Whitesupraboy2 Posted July 6, 2008 Author Share Posted July 6, 2008 I have to admit the PSU is on the bottom (400watt) range of what id like it to be. Memory checks have all come back clear. I'll check the voltage in the bios but I believe they are all set to auto and I think they looked ok. I know the graphics card is quite heavy on the PSU when being used to the full (ATI Radeon 3850) Link to comment Share on other sites More sharing options...
Supra Size Me Posted July 7, 2008 Share Posted July 7, 2008 aha ! throw away that 400 watt tbh It's likely to be your prob depending on what other bits you've put in there but min I'd recommend is 550-600 Watt for an average modern setup depending on what you're putting in the case, see if the company you bought the PSU from will do an exchange for you for something a bit beefier. Shouldn't cost too much extra and if you've bought a setup that is crossfire capable you won't need to upgrade PSU in the future if you want to crank out a few more FPS on games when you stick a second card in hope this helps (it's not guaranteed to be the problem as I don't know what else you have in the build but is a good place to start) Hope this helps Link to comment Share on other sites More sharing options...
Whitesupraboy2 Posted July 7, 2008 Author Share Posted July 7, 2008 Ive gone for 550watt PSU. The gold one, forget the make but ive used them before and I know they are quiet. It cost £450 and I got; AMB athlon 4800+ 2.5Ghz dual core 2gb Ram DDR II PC8500 500gb 16mb cache SATA hard disc DVD rewriter ASUS motherboard Digital TV card with remote control (really impressed by this) ATI Radeon 3850 Overclocked version 22" widescreen Monitor case for £450 Im really happy with the system....will be much happier once I work out the fault. I put call of duty 4 on and ran full graphics without a stutter Link to comment Share on other sites More sharing options...
JustGav Posted July 7, 2008 Share Posted July 7, 2008 Hold on... Why do you need to get a 10023957234W power supply. IF you have a decent power supply from a line conditioning point of view, then you only require a PSU that is of sufficient size to drive all the kit. Just because a power supply is 1000W doesn't suddenly mean it is good. Link to comment Share on other sites More sharing options...
Scott Posted July 7, 2008 Share Posted July 7, 2008 Hold on... Why do you need to get a 10023957234W power supply. IF you have a decent power supply from a line conditioning point of view, then you only require a PSU that is of sufficient size to drive all the kit. Just because a power supply is 1000W doesn't suddenly mean it is good. Because Link to comment Share on other sites More sharing options...
Recommended Posts
Please sign in to comment
You will be able to leave a comment after signing in
Sign In Now