9 Legend

 • 

87.5K Posts

March 29th, 2005 22:00

Boot to the Dell diagnostics (F12 or the CD if the system came with one) and run a full RAM and hard drive test, including a surface scan of the latter.

One strong possibility: the hard drive is a Maxtor, and it has failed.

136 Posts

March 29th, 2005 23:00

Possible RAM, DVD, or USB driver problems, or device issues in that group of things.

See if you can replicate it, this time write down the file name.

This seems to happen more with upgrades than totally clean installs, so is this a clean install or an upgrade to XP?

Other than RAM it could be caused by:

Keyboard drivers, for USB keyboards
mouse drivers, for USB mice
DVD drivers and underlying windows stuff when upgrading

RAM failures are the most common thing, any chance a RAM stick worked loose?

BAD RAM can cause all kinds of wierd stop errors, run a memroy test, let it run overnight. No errors by morning, it is not RAM and could be even a bad hub for USB, bad cable to DVD drive, USB device with bad cable, that kind of thing.

Having the file name helps alot with 7E stops, too many possibilities without it.

563 Posts

March 30th, 2005 00:00

I didn't even think to write it down.  If it comes up again I'll write it down.  Once it came up I turned the system off then back on and it dodn't come up again.  I'll run a few tests on the system.

563 Posts

March 30th, 2005 16:00

I ran the diagnostic test on the hard drive and it passed so I guess that isn't the problem.  When I turned on the comp after I got back from class it got to windows and then said it had a serious error.  I swear I've had so many problems with only my 8300 and this is the second one I'm on after Dell replaced the first one.  Good thing I have a warranty 'til June '07.

1 Message

April 1st, 2005 01:00

I am having the same problem with this. I have a blue screen pop up during the loading sequence, I have dimension 2350 with XP. It did this after it froze and i was forced to cut the power.I ran complete diagnoxtics and nothing is wrong, according to it.......
I cant run any mode, not even DOS, the code that pops up is exactly 0x00000051(0x00000003,0x00000003,0x00000000,0xE1585000) Ive had this problem for nearly 2 days, and i cant run anything on it. It also says if i hold F8 during startup " keyboard error or no keyboard" but i got a friends keyboard, exactly like mine, and it did the same thing. Could it be the computers USB connecter, or could there be a faulty wire? please any help would be appreciated, even if it doesnt solve the problem.

26 Posts

April 1st, 2005 21:00

I have been having this problem intermittantly over the last few weeks. Usually after the second or third restart I would manage to boot to windows and everthing would be fine. Would happen every second day or so for a while then stop for a few weeks, then back again. Got really bad about 5 days ago when it took about 10 or 15 restarts to finally boot. The last time it happened I noticed ide mentioned in the message somewhere and when I finally managed to boot I decided to investigate my HDD setinngs etc. Straight away I noticed I had 2 gigs set aside for System restore and 2 gigs for my pagefile. Thing was though, that I only had 200mb free space left. Deleted 9 gigs worth of rubbish, defragged and haven't had a stop code in 5 days. Then I remebered that the last time I had the stop codes bad, around the same time I had very little HDD space left and that it seemed to resolve when I deleted about 3 gigs back then. Of course this could all be coincidence but I wonder were the lack of HDD space and the conflicting demands of System Restore and pagefile causeing me my stopcode start-up problems?
No Events found!

Top