Login | Register
SearchMy Stuff
My ProfileMy PreferencesMy Mates RSS Feed
Reply to Topic
Author Discussion

audi321

Original Poster:

2,308 posts

82 months

[news] 
Friday 6th July 2012 quote quote all
Hi all, I've got an old netbook (Dell Latitude 2100) running XP. Great little machine, but recently after about 3 minutes of booting up, I get the following BSOD



Anyone have an idea where to start?

Thanks in advance!

oldcynic

1,545 posts

30 months

[news] 
Friday 6th July 2012 quote quote all
Do you have any disk space left? Try booting to safe mode - press F8 about once a second whilst booting until the boot menu appears, then choose safe mode. If the disk is full then delete some files (note full means less than about 200-500MB free, as the paging file will want some space.

Don't follow my step-son's lead and delete system files to make space for more downloads - this rarely ends well!

davepoth

19,925 posts

68 months

[news] 
Friday 6th July 2012 quote quote all
Googling the error code (0x0000008E) reveals that it can be all kinds of problems, but the two most likely things are out of hard disk space or bad RAM. Boot into safe mode as suggested and make sure there's some space free, and perhaps roll Windows back to the last system restore point to see if that helps.

LordGrover

18,645 posts

81 months

[news] 
Friday 6th July 2012 quote quote all
I don't know how accessible the RAM is on that machine, but it's usually fairly simple to just remove and reseat the memory. It may make a difference. If there are two or more modules try them one at a time.

audi321

Original Poster:

2,308 posts

82 months

[news] 
Friday 6th July 2012 quote quote all
Cheers guys. I've booted into Safe Mode and there's loads of HDD space left (over 100gb). Whilst there I also did chkdsk and defrag, but still BSODs when not in Safe Mode.

I took the back off, and surprisingly, there's no RAM in the thing! Which will be something I will be sorting out providing I can sort the BSOD error out.

I have a spare HDD if you think it could be this? I would need to clone the original one first though, is there any free software that can do this (would need to be in Safe Mode).

Other than that, what else is could it be? Is it gonna be a gonner?
Advertisement

RobCrezz

7,554 posts

77 months

[news] 
Friday 6th July 2012 quote quote all
audi321 said:
Cheers guys. I've booted into Safe Mode and there's loads of HDD space left (over 100gb). Whilst there I also did chkdsk and defrag, but still BSODs when not in Safe Mode.

I took the back off, and surprisingly, there's no RAM in the thing! Which will be something I will be sorting out providing I can sort the BSOD error out.

I have a spare HDD if you think it could be this? I would need to clone the original one first though, is there any free software that can do this (would need to be in Safe Mode).

Other than that, what else is could it be? Is it gonna be a gonner?
Try a chkdsk /r


davepoth

19,925 posts

68 months

[news] 
Friday 6th July 2012 quote quote all
Unlikely to be the HDD IMO. I would now take a look at device drivers and memory resident programs, to see if any of them are being naughty. Are you running antivirus of any kind?

audi321

Original Poster:

2,308 posts

82 months

[news] 
Friday 6th July 2012 quote quote all
Update - I uninstalled a good few programs whilst in Safe Mode, and I also uninstalled the graphics card driver.

Booted back into normal mode and it reinstalled the graphics driver and all looks to be stable (so far fingers crossed!).

Just backing everything up, then I'm off to crucial to get a load of RAM for it!

Thanks everyone!

oldcynic

1,545 posts

30 months

[news] 
Friday 6th July 2012 quote quote all
The system wouldn't start up if it had no memory. Try running msinfo32 (windows-r, then type in msinfo32) or for older operating systems winmsd. That will tell you how much memory it's got.

I suspect you're looking in the wrong place for the RAM. (And despite the earlier advice RAM is generally best left undisturbed. If you must touch it hold it by the edges and especially don't touch the contacts - you can create problems which aren't immediately obvious)

By the sound of it you had some kind of driver / software issue.
Reply to Topic