Repeated STOP 0x00000050 at startup in both normal and safe modes

  • Thread starter Thread starter vof
  • Start date Start date
V

vof

I have been asked by a client to sort out this problem which appeared
spontaneously about two weeks ago on a Dell Inspiron 1100 laptop. The PC
always blue screens during startup with exactly the same data whether it is
starting in normal or safe mode. The BSoD appears a few seconds after the
splash screen disappears in normal mode.

The data is:
STOP 0x00000050 (0x80087000, 0x00000000, 0x82D259DC, 0x00000000)

Suspecting faulty RAM, I have run memtest for many cycles without it
reporting any errors.

There seems to have been a rash of this problem since about 24 June. Search
for:
STOP 0x00000050 0x80087000
to see what I mean.

In these reports, the third parameter – an address – has a variable segment
number but the displacement always ends 9DC which suggests that the failing
memory access is always at the same code position.

Can anyone suggest a cause for this, in particular anything pushed out
recently through AU which might have this as a side-effect?

Since the graphics driver must be a likely source of the problem, note that
this laptop seems to use the Intel 82845G graphics chipset.

TIA

vof
 
Hello,

Past archives may help, although it is going to be a tedious task
http://groups.google.com/groups/search?q=0x00000050&sitesearch=groups.google.com&scoring=d

See if you can reproduce the problem with a fresh installation on another
partition. You can then rule out a hardware problem if XP manages to start
up. Then install the drivers/updates until you can nail the one causing the
problem.
__
http://www.bootstrike.com/ComputerService/
Singapore Computer Home Remote On-Site Repair Service
 
--
.......?........?


vof said:
I have been asked by a client to sort out this problem which appeared
spontaneously about two weeks ago on a Dell Inspiron 1100 laptop. The PC
always blue screens during startup with exactly the same data whether it is
starting in normal or safe mode. The BSoD appears a few seconds after the
splash screen disappears in normal mode.

The data is:
STOP 0x00000050 (0x80087000, 0x00000000, 0x82D259DC, 0x00000000)

Suspecting faulty RAM, I have run memtest for many cycles without it
reporting any errors.

There seems to have been a rash of this problem since about 24 June. Search
for:
STOP 0x00000050 0x80087000
to see what I mean.

In these reports, the third parameter – an address – has a variable segment
number but the displacement always ends 9DC which suggests that the failing
memory access is always at the same code position.

Can anyone suggest a cause for this, in particular anything pushed out
recently through AU which might have this as a side-effect?

Since the graphics driver must be a likely source of the problem, note that
this laptop seems to use the Intel 82845G graphics chipset.

TIA

vof
Click to expand...





i too have same problem but i can start in safe mode i at the momnet am
typing this from said safe mode
 
Thanks for this suggestion and for those from others who have posted responses.

To keep my original post short, I did not list everything I had already tried:

- I have run chkdsk /r from recovery console - it fixes the unclean shutdown
inconsistencies but does not help with the BSoD

- I know about the aumha.org site and had checked it again to no avail

It is beginning to look as if a reinstall will be necessary...

Thanks, vof
 
What is the value of the third parameter in your STOP message? Did it end
0x.....9DC? Did your problem recur after the safe mode shutdown?

vof
 
Back
Top