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
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