Memory Corruption?? Not so simple.....

Discussion in 'Hardware' started by FrEaK_on_FeEt, Oct 1, 2008.

  1. FrEaK_on_FeEt

    FrEaK_on_FeEt Private E-2

    :wave. I am new so pleeease be gentle with me. Yes I'm a geek chick and I fiddle waaay too much! But I am innocent in this case. I bought a compaq presario a few years back (SR1499AN). It went well for 12 months then one day I got the dreaded BLUE SCREEN...and that was the end of it. It started crashing constantly to the point it wouldnt start at all. I sent it to be repaired and they replaced the hard drive. 3 months later...same thing...and same action from technician (new hard drive). Anyhoo...long story short...

    Still doing it, formatted hard drive, refreshed windows XP Home edition, all drivers up to date and I ran the debug software on the last 10 crashes and got the same response. I am really green when it comes to corrupt memory but am guessing I should be testing the modules yes? :confused

    I have attached the minidump info and would really appreciate your imput.....please help a damsel in distress :cry lol!!
     

    Attached Files:

  2. plodr

    plodr MajorGeek Super Extraordinaire Moderator Staff Member

    Yes test your RAm.
    I went searching to see what I could find on this MiDecrementShareCount which is mentioned and it points to RAM.

    If you have two sticks and the computer can run on one, of course slower, remove one stik and see if it crashes. Then do the same with the other stick.
    Another option is to run MemTest
    http://www.majorgeeks.com/Memtest86_d4226.html download, burn the ISO and boot the computer with the CD in the drive as the first boot device.
    If you have a floppy drive, it does come in a floppy drive version that you also boot from. If any errors come up, get new memory.
     
  3. FrEaK_on_FeEt

    FrEaK_on_FeEt Private E-2

    Thnks Plodr. I ran MemTest and no errors were reported. When rebooting it crashed again. It happens alot when shutting down. I ran the debugger again and got a new minidump which is showing something about the dll32 file. I'm afraid I'm not too good at reading these test results. I am at the moment running the driver verifier on my non-microsoft drivers but the stressing hasn't yet caused the BSOD. I am at a loss here. I have not modified any of the memory as it has 1024MB and that has been ample for XP. But I will remove one if you think it may be an issue.

    Hope to get more feedback re this issue!
     

    Attached Files:

  4. plodr

    plodr MajorGeek Super Extraordinaire Moderator Staff Member

    Well, if you got no memory errors than you can rule that out.
    This said something about a driver attempting to use a too high memory address and IRQ.
    Hopefully someone who knows about this will post some thoughts.
     

MajorGeeks.Com Menu

Downloads All In One Tweaks \ Android \ Anti-Malware \ Anti-Virus \ Appearance \ Backup \ Browsers \ CD\DVD\Blu-Ray \ Covert Ops \ Drive Utilities \ Drivers \ Graphics \ Internet Tools \ Multimedia \ Networking \ Office Tools \ PC Games \ System Tools \ Mac/Apple/Ipad Downloads

Other News: Top Downloads \ News (Tech) \ Off Base (Other Websites News) \ Way Off Base (Offbeat Stories and Pics)

Social: Facebook \ YouTube \ Twitter \ Tumblr \ Pintrest \ RSS Feeds