Ever seen this problem before in XP open a drive or folder it crashes and goes back again.

  • Thread starter Thread starter Ridge Walker
  • Start date Start date
R

Ridge Walker

Application popup : Explorer.exe - Application Error: The Instruction
at 0x02900bd8 reference memory at 0x000000. The Memory couold not be
written and it is exasperating as I try to move some word docs, excel
spreadsheets would just close again. Dr Watson was also in error as
well

Scenario: Open the folder it crashes but do not freeze it sends the
error to Microsoft and then when I try to open the drive --> then the
folder it happens again. Strangely, other folders in the same drive
just does not happen that way. Only the folder. What can I do?? Using
XP SP2, every single component is new. Tried everything. XP was
installed just about 2 weeks ago and had all the updates installed as
well and patches from MS site. Was working fine until just recently.
 
I get the same thing and can't remove. It is as follows 0x7c9105f8 reference
memory at 0x019d0010. Tried file search, but nothing shows.
 
Ridge said:
Application popup : Explorer.exe - Application Error: The Instruction
at 0x02900bd8 reference memory at 0x000000. The Memory couold not be

Got generic ram?
 
Yep. I have had generic ram for a long time, but never this problem before
and what is: ixplore.exe-Application Error?? TIA...
 
I am not sure myself as I got Cosair Memory and in other PCs I had for
donkey years.. never a problem. It is also explorer error but somehow
it does not like totally freeze the PC and have to restart or so but
just frustrating only. Anyone ?
 
=?Utf-8?B?YWxhY3Jhbg==?= said:
Yep. I have had generic ram for a long time, but never this problem before
and what is: ixplore.exe-Application Error?? TIA...

Good guess on my part eh?
 
alacran thought carefully and wrote on 12/30/2005 4:11 PM:
Yep. I have had generic ram for a long time, but never this problem before
and what is: ixplore.exe-Application Error?? TIA...

ixplore.exe may indicate a virus infection. Maybe it's time for some
antivirus scans.

Lance
*****
 
=?Utf-8?B?YWxhY3Jhbg==?= wrote:
Good guess on my part eh?

Except you mis-spelled "defective" as "generic".

Nothing wrong with generic RAM if there's nothing wrong with it. Any
RAM can be defective, not matter how glossily-branded it is, and it is
defective RAM that suuucks.


---------- ----- ---- --- -- - - - -
Don't pay malware vendors - boycott Sony
 
This makes the fifth post I've read today on this issue. I have the same
issue and do not have generic ram.

Five posts and no resolution.
 
On Sun, 8 Jan 2006 07:51:02 -0800, Bobbee
This makes the fifth post I've read today on this issue. I have the same
issue and do not have generic ram.

Any RAM can be defective, no matter who makes it. That's why "good"
brands say "we offer a longer warranty period" rather than "who needs
a steenkin warranty; our stuff is never defective!" :-)
Five posts and no resolution.

Five posts in what thread, in what ngs?
Specifically, what is the "issue" you refer to?
If RAM = bad, resolution = replace RAM and re-test to verify.


---------- ----- ---- --- -- - - - -
Don't pay malware vendors - boycott Sony
 
=?Utf-8?B?Qm9iYmVl?= said:
This makes the fifth post I've read today on this issue. I have the same
issue and do not have generic ram.

Five posts and no resolution.

If I were you, I'd demand a refund.
 
Back
Top