Laptop Over. Problem = very yes.

[Dark Jaguar]

Well, I've run out of ideas. A basic description follows.

My laptop, up until yesterday, was working flawlessly. However, at some point when I had left it on, it simply crashed. Upon trying to restart it, Windows reported some manner of flagrant error. I couldn't enter safe mode either.

So, I just decided to reinstall it, only I can't, no matter what I do. First, I did a normal repair, but that failed because certain files couldn't be found. I then attempted to delete the old Windows directory (XP by the way, professional) and reinstall from there, but it seems to crash when I do that. I thought there might be an issue with the hard disk, so I bought a new one. I tried a clean install, but now every time I get around the 50% mark, files (random ones it seems) can't be found. Never the same files twice. So, I thought it might be an issue with the install disk. Fortunatly, I have like 5 XP install disks (home, professional), and I tried ALL of them. Same error, and every now and then a complete system lockup during install. So, I tried using other CD drives, which I hooked up using an enclosure kit via USB. Again, same issue. So, I attempted to reinstall using another laptop entirely, with my new drive. Unfortunatly, this laptop is too new, so the old hard disk wouldn't work. I tried hooking that hard disk up via USB and a different enclosure kit instead, and it seemed to work, only windows crashes every time I try to load it. I suppose maybe it doesn't like being loaded in USB?

Anyway, at this point I'm completely out of ideas.

 

[Zep]

Memory (RAM) error springs to my mind for these kinds of symptoms.

How easy/hard is it to get at the memory? Is it in two or more pieces? If so, can you remove one and still fire the laptop up OK? Or if one piece, can you borrow a suitable replacement?

If all is so, do some swapping of memory modules to see if the crashing follows one of them in particular (i.e. basic investigation).

Good luck!

 

[Dark Jaguar]

*slaps head* Now that's an obvious venue of attack I should have considered before plunking down some cash! I'll get right back to you on that. In fact I have two sticks of memory in the machine. I'll attempt to switch between both and see what happens.

 

[Dark Jaguar]

Well nuts... I fixed the problem, but it HAD to be the 1 gig memory stick didn't it. Couldn't be the 256 MB stick that came with the system...

Still, the error sure was annoying to deal with. Thanks! To be honest I'm surprised I didn't think of that myself, but that's what extra brains are for. That is, extra brains are to be manipulated to my own ends.

 

[Zep]

You MANIPULATED me? How...COULD you! I feel strangely violated...



Yep, I've chased that sort of stuff for days before the light came on. *sigh*

 

[Wowbagger]

Sometimes, all it takes is a fresh pair of eyes, to resolve a problem.

 

[Zep]

When this sort of thing gets to me, I usually like to leave the problem overnight and come back to it the next day. I then take one look at it and go D'OH! IT'S OBVIOUS!

 

[Blue Bubble]

Ah, memory problems ...

You have to realise that many PeeCees (and lap-tops) are built to reduce costs. Things like memory with not even parity, never mind ECC.

In my real job, I often analyse system crash dumps (VMS and Tru64) where the cause has been a double-bit memory error that not even ECC could correct. If this error rate from super reliable systems is projected onto cheapo-cheapo PeeCees, then you'll understand why you should not only not be surprised but actually expect such problems on PeeCees.

And the scary thing is, people trust computers!