Re: "Buffer Overrun? Microsoft Visual C++ Runtime Library"?!? JD
- From: Paul <nospam@xxxxxxxxxx>
- Date: Thu, 11 Jun 2009 21:04:02 -0400
BNILSSON@xxxxxxxxx wrote:
Hi Paul,- good to hear from you!
Yes, it's a new ball game now, with the WinXP installation, with the
2ea. 1GB RAM sticks installed.
And all new problems for me!
I should had purchased a NEW PC instead of trying to do something that
I'm not familiar with, but- maybe next year.
I also had a problem with the larger 160GB HDD I purchased with the ram
sticks from NewEgg, it would not even boot to load all the BIOS or
anything from the installation CD, so I had to RMA
that back for a replacement.
I have now loading the winXP on to my spare 40GB HDD and that is were my
new problem come in.
I have Memtest 86 V3.4 on a floppy and it's running right now- for about
1 hour.
I noticed that there are so many different Versions of it, so I don't
know if the one I have is any good or not?- what do you think, Paul?
I don't really know what I'm looking at on the screen, but, so far
there are no errors indicated.
I don't really know about all the "Descriptive/Info.- like;
L1 Cache 128K- 8582MB/s,
L2 Cache 64K - 3596MB/s,
Memory- 2016M 563MB/s
If that has any value or not? but as long as there is no indication of
errors I think that the ram sticks are OK?
Thanks again for all your help.
BN
I guess I was hoping for an easy answer :-)
I don't really want to "run you through the wringer" on this. Some
of the things I could suggest, might take you some amount of time
to set up, and there is no guarantee the results would be any better.
I see two possibilities.
1) Prove the individual components in your new setup, are all working
correctly. You might, for example, dig up a diagnostic program for
that brand of hard drive you're using. I have a Seagate
test floppy, I downloaded from their site. The "long test" would tell
you how good the drive was. Each brand may provide their own test.
Another thing to test, would be the ability to read the CD, in case
some of the files are coming off it corrupted. You haven't indicated
what your release of Windows is - it could be WinXP SP3, but there is
probably more than one CD of that in existence. I could run MD5SUM
on my CD, and give you the 5000 checksums of the files in the i386 folder.
That doesn't sound like much fun.
2) Go back to known good components. For example, your old RAM works,
and you didn't have any crashes or problems before, then perhaps
you could temporarily use that RAM again for some tests. WinXP can
easily run with 512MB, as I built a computer for a family member
with that much RAM in it a couple years ago. Try a reinstall,
using the old RAM.
I was hoping the WinXP CD has a build-in check, but I'm not seeing
anything to suggest they have that capability. My Linux CD for example,
has a media test option, so you can verify the files on the CD
are OK. Linux compares the computed checksums, against a checksum file,
as a way to verify the CD is OK and readable by the drive.
*******
If I run your error symptoms...
Buffer Overrun Microsoft Visual C++ Runtime Library winlogon
the post at the bottom of this thread, mentions the master/slave
nature of the hard drive setup. How have you jumpered the IDE
drive ? Are there two drives on the cable, one master, one slave ?
Is there one drive, mounted on the end connector, and set up
as master (or master only, for WD brand drives) ? The suggestion
here, is to check your setup and verify how you've jumpered it.
You can also use cable select on each drive, if you have an
80 wire cable hooked to it.
http://www.dslreports.com/forum/r21987602-XPHome-Buffer-overrun-detectedcorrupted-program-internal-st
It could also be related to SuperAntiSpyware...
http://forums.superantispyware.com/viewtopic.php?f=3&p=14680
It could also be a malware problem, but so far, I don't see how
that would have happened.
This is what Visual C++ is checking for.
http://en.wikipedia.org/wiki/Buffer_overrun
This can happen when poorly written code accepts
too large a data item. It is a technique used to "tip over" machines
via the Internet. As more Service Packs and security updates have
been added to WinXP, it has more protections for things like this,
but there are always people searching for new exploits. In Googling
the above terms, the buffer overrun is also associated with iexplore.exe.
I'm hoping this is just something silly, rather than malware. As
with malware, I'd want to understand how you go infected so quickly,
if that is what happened.
Paul
.
- Follow-Ups:
- References:
- Prev by Date: Re: P3B-F BIOS Hardware Monitor Error
- Next by Date: Re: boot for USB drive
- Previous by thread: Re: "Buffer Overrun? Microsoft Visual C++ Runtime Library"?!? JD
- Next by thread: Re: "Buffer Overrun? Microsoft Visual C++ Runtime Library"?!?
- Index(es):
Relevant Pages
|
