STOP: 0x8E - WINXP Pro

  • Thread starter Thread starter Christo
  • Start date Start date
C

Christo

i have been getting a few STOP errors recently in XP

mostly 0xA - IRQL_NOT_LESS_OR_EQUAL

i was told it was a hardware problem i replaced my PSU from a cheap £5 350W
no make piece of scrap to a thermaltake 480W silent purepower that was £50

anyway today i received the STOP 0x8E error

could this be down the incompatable memory?

i have 2 pc2100 ddr266 cl2.5 modules on one channel and one 512 ddr333
pc2700 cl3

i have been told different cas latencys cause problems with memory

is it this as i cant think of anything else that could be causing it?

any help greatly appreciated
 
i have been getting a few STOP errors recently in XP

mostly 0xA - IRQL_NOT_LESS_OR_EQUAL

i was told it was a hardware problem i replaced my PSU from a cheap £5 350W
no make piece of scrap to a thermaltake 480W silent purepower that was £50

anyway today i received the STOP 0x8E error

could this be down the incompatable memory?

i have 2 pc2100 ddr266 cl2.5 modules on one channel and one 512 ddr333
pc2700 cl3

i have been told different cas latencys cause problems with memory

is it this as i cant think of anything else that could be causing it?

any help greatly appreciated

http://search.microsoft.com/search/results.aspx?st=b&na=88&View=en-us&qu=0x8E

If you want to check the mixing-memory issue, remove one or
two memory modules. Mixed memory should work providing the
bios properly sets the timings OR you manually set them,
unless the board simply isn't stable with 3 memory modules
in it, which isn't all that uncommon a problem, many boards
need their memory bus speed reduced for use of 3 or more
modules.

Another test of memory is running http://www.memtest86.com
for several hours. If that doesn't show a problem you might
try manually rasing the memory bus speed by a few (perhaps
5) MHz and rerun Memtest86... I always want a system to have
an absolute minimum of 5MHz (actually more but 5 is a good
start for a test) margin, if the memory won't run even 5MHz
over it's everyday speed then it's questionable whether
there would be errors simply not showing up in testing due
to type of tests or length of time tested. For example if
one tests with memtest for 12 hours, that is no assurance
the system won't have memory error once every 30 hours.

Often though these stop errors are driver related.
 
Back
Top