AIW 8500DV crashes with IRQL_NOT_LESS_OR_EQUAL

  • Thread starter Thread starter Thomas Boettcher
  • Start date Start date
T

Thomas Boettcher

I have had an AIW 8500DV since last April. I love the TV features when it
is working properly but I have had continuous problems with system crashes
and lock-ups. These crashes and lock-up seem to occur after about 30
minutes of opearation and most often while I am viewing TV in a small window
and then I launch IE or Quicken. From suggestions to others on this board I
have monitored temperature and 3.3V voltage and neither seems unusual.

In the past the crashes have gone to a blue screen for an unreadable split
seconds and then reboot. This morning the blue screen froze and I was able
to get the following information.

IRQL_NOT_LESS_OR_EQUAL
STOP: 0X0000000A (0X00CFF32E,0X000000FF,0X00000001,0X8052DDCE)

Any suggestion?
Thanks.
 
Hi Thomas,

I think I experienced a very similar problem like you have. On my system the
computer went into a blue screen - just for a split second - and rebooted.
The problem still persists, unfortunately, even though I tried many things.
The only solution I have never tried is to deactivate the firewire on the
graphics card, which one person suggested to me.

However, now I'm using showshifter for TV viewing. As long as I don't use
the ati software, my system is stable. By the way, I'm running Win2000
Server.

May be somebody else can suggest a solution.

Lars
 
Last time I had IRQL_NOT_LESS_OR_EQUAL and blue screen error, it turns out
that a DRAM stick went bad. After replacing it, my system is back to normal.
 
Last time I had IRQL_NOT_LESS_OR_EQUAL and blue screen error, it turns out
that a DRAM stick went bad. After replacing it, my system is back to normal.
Click to expand...


That being the case...


If you have more than two sticks, start playing musical RAM by pulling
them all out and swapping them into slot one, one at a time until you
find the culprit.
 
This seemed like a reasonable suggestion so I tried loading each of my two
256 MB sticks one at a time. The problem continued to occur with each stick
installed alone.
Nice try.
Thanks.
 
I decided to pursue this RAM thing one step further. I ran Memtest86 once
with just one of my two 256MB memory sticks installed and again with just
the second 256MB stick installed. Both tests showed the same failed memory
addresses for test #8 (block move, 512 moves, cached).
Failed memory addresses:
000000044d0 - .2MB
000000539b8 - .1MB

I'm a little stumped how two different RAM sticks would show identical
failed memory addresses. I know very little about RAM addressing but that
seems highly unlikely.

Here's a little system info:
Asus A7M266 Bios 1007 motherboard
S2K slew rate: 1
Athlon XP 2100+
Windows XP Pro (fully updated)
ATI Radeon Catalyst 3.6 video drivers
 
I'm a little stumped how two different RAM sticks would show identical
failed memory addresses. I know very little about RAM addressing but that
seems highly unlikely.
Click to expand...


Nor do I. However, it couldn't hurt to borrow a stick of known good
RAM from a friend and try the test again. Is it "budget' RAM? Or the
good stuff? Some motherboards don't do well with the bargain basement
stuff. Barring a RAM issue, it could be your motherboard.

Something else to try might be to clear the CMOS...it might be partially
corrupt, and clearing would set the board back to default settings.
You can find out about this in your MB manual. I've solved many a
problem with this simple procedure.
 
One stick is Corsair and the other is Kingston Valueram.
I'll try the CMOS thing tonight.
Click to expand...

Come to think of it, I had an issue several months ago where I would
receive memory errors upon closing many different applications.
A format and Windows reinstall did not rectify the problem.
The CMOS clearing thing resolved the issue.
 
Did the CMOS clear thing. Same Memtest86 test results - errors at the same
address
locations on two different sticks in either slot.

I will try to get some fresh memory and I will hope that it tests good so
that I don't have to dig into my processor or my motherboard which is where
the coincidental error address thing seems to be pointing to.

Thanks.
 
are you running a VIA chipped board and you have done all the 4in1 updates?
Have you PNP OS installed set to 'NO' and reset configuration data to
'enable' in the CMOS? You do not have anything in the #1 PCI slot?
 
As an update of my situation - I seem to be running stable again. I got
there by reducing my FSB speed from 133 to 132. The memory still shows
errors using Memtest86 test #8 but it runs XP and applications ok again. Go
figure.
Thanks for the suggestions.
 
I am not sure what my settings are. I have never gone to that CMOS screen.
I have my Asus A7M266 "SDRAM Configuration" set to "BY SPD" where it takes
care of the configuration details automatically.
Is there anything in particular I should be looking out for?
Thanks.
 
I am not sure what my settings are. I have never gone to that CMOS screen.
I have my Asus A7M266 "SDRAM Configuration" set to "BY SPD" where it takes
care of the configuration details automatically.
Is there anything in particular I should be looking out for?
Thanks.
Click to expand...


I wouldn't sweat it, if slowing your FSB down fixed the problem. Were
you overclocked to begin with?
 
No, it was not overclocked. It is PC2100 running at 133 so I'm not sure why
taking it down to 132 made the difference it did. I also discovered the RAM
had been set at 3.45V instead of 3.3V for the past two years. I corrected
the voltage thing while it was still a 133 but my system still crashed or
locked after just a few minutes of operation. The improvement came when I
went to 132 on the FSB with the voltage at 3.3V.
 
Oops ... sorry. The RAM voltage had been at 2.8V for the past two years. I
corrected it down to 2.7V (the lowest jumper setting).
 
Back
Top