Windows XP SP2 BSOD - Repetative Errors!

By MobiTec
Nov 8, 2005
Topic Status:
Not open for further replies.
  1. Hello Ladies/Gents

    I firstly appologise for jumping upon this bandwagon of BSOD errors, i have tried
    many ways to find out the culprit of the errors i am recieving, which are becoming ever so repetative...

    i have changed my RAM, tested both sticks using "MemTest86 v1.65" no errors occured running 8 passes each stick,
    updated all my drivers using a very usefull program called "Driver Genius Professional Edition 2005"

    and still no joy, and i still keep getting the BSOD!! *doh*

    Sys Specs =
    OS Name - Microsoft Windows XP Home Edition Version 5.1.2600 Service Pack 2 Build 2600
    System Manufacturer - Packard Bell : IMedia 5009
    System Type - X86-based PC
    Processor - x86 Family 15 Model 2 Stepping 7 GenuineIntel ~3066 Mhz
    RAM - 1024MB (2x 512MB Infineon DDR 333Mhz SDRAM PC2700)
    BIOS Version/Date - American Megatrends Inc. 1.0N, 15/09/2003
    SMBIOS Version - 2.3
    Windows Directory - C:\WINDOWS
    System Directory - C:\WINDOWS\system32
    Boot Device - \Device\HarddiskVolume2
    Hardware Abstraction Layer Version - "5.1.2600.2180 (xpsp_sp2_rtm.040803-2158)"
    Total Physical Memory - 768.00 MB
    Available Physical Memory - 159.96 MB
    Total Virtual Memory - 2.00 GB
    Available Virtual Memory - 1.96 GB
    Page File Space - 1.22 GB
    Page File - C:\pagefile.sys

    here are some of my MiniDump files if someone would be so kind to have alook and see if they can solve my ongoing mystery,
    there are 7-8 minidumps in total from the last week or so..


    Hopefully someone can smack me in the face and show me what is wrong.. haha.

    Thanks for reading (and helping)

    MobiTec ;)
  2. Rick

    Rick TechSpot Staff Posts: 6,304   +52 Staff Member

    If you don't have 256MB of integrated graphics memory and you are seeing things like this, then your memory is definitely questionable. :p

    Memtest won't turn up all problems, so don't rely on it as the end-all test... But it is good reassurance that your memory is working OK.

    Other things that can cause blue screens? Well, tons of things. But most the most common items might be a failing drive, memory, cpu or board. Overheating is a common cause too. Software wise, just about anything goes, but most likely if software is the culprit, you have yourself a driver or virus problem.

    Is it the same BSOD each time? Same message maybe? That might help narrow it down. What's the frequency? Does it happen at certain times, or does it happen randomly without cause?

    I'd recommend running a disk diagnostic to verify your hard drive is in proper working order. Much like memtest, these diagnostics aren't 100%, but pretty darn close. http://www.techspot.com/vb/topic7602.html
  3. cpc2004

    cpc2004 Newcomer, in training Posts: 2,044

    Hi MobiTec,

    The culprit is faulty ram.

    The culprit is faulty memory. You can run memtest to stress the ram. If memtest reports the ram is faulty, ram is bad. However Memtest is not a perfect tool to test the memory as some faulty ram can pass memtest.

    Suggestion
    1. Check the temperature of the CPU and make sure that it is not overheat (ie temperature < 60C)
    Make sure that the CPU fan works properly
    2. Reseat the memory stick to another memory slot
    3. Downclock the ram
    4. Clean the dust inside the computer case
    5. Make sure that the ram is compatible to the motherboard
    6. Check the bios setting about memory timing and make sure that it is on
    If it still crashes, diagnostic which memory stick is faulty
    1. Take out one memory stick. If windows does not crash, the removed memory stick is faulty.
    2. If you have only one memory stick, replace the ram



    PAGE_FAULT_IN_NONPAGED_AREA (50)
    Invalid system memory was referenced. This cannot be protected by try-except,
    it must be protected by a Probe. Typically the address is just plain bad or it
    is pointing at freed memory.
    Arguments:
    Arg1: 9a86324f, memory referenced.
    Arg2: 00000000, value 0 = read operation, 1 = write operation.
    Arg3: 804ed81d, If non-zero, the instruction address which referenced the bad memory
    address.
    Arg4: 00000000, (reserved)

    Debugging Details:
    ------------------
    Could not read faulting driver name
    READ_ADDRESS: 9a86324f

    FAULTING_IP:
    nt!MmAccessFault+8d5
    804ed81d 8b0489 mov eax,[ecx+ecx*4]

    MM_INTERNAL_CODE: 0
    CUSTOMER_CRASH_COUNT: 1
    DEFAULT_BUCKET_ID: CODE_CORRUPTION
    BUGCHECK_STR: 0x50
    LAST_CONTROL_TRANSFER: from 00265867 to 804ed81d
    SYMBOL_ON_RAW_STACK: 1

    STACK_TEXT:
    c030000c 00265867 003cc867 00366867 003df867 nt!MmAccessFault+0x8d5
    WARNING: Frame IP not in any known module. Following frames may be wrong.
    c0300020 09f65867 00000000 00000000 00000000 0x265867
    c0300024 00000000 00000000 00000000 00000000 0x9f65867

    STACK_COMMAND: dds @$csp ; kb

    CHKIMG_EXTENSION: !chkimg -lo 50 -db !nt
    !chkimg -lo 50 -db !nt
    63 errors : !nt (804ed786-804ed87f)
    804ed780 91 03 00 3d 00 01 *5b *74 0f 84 eb b2 ff ff *ff *80 ...=..[t........

    804ed790 50 ff 75 10 8b 45 *00 *00 e0 01 50 56 e8 8a *6a *00 P.u..E....PV..j.

    804ed7a0 ff 8b f8 85 ff 0f *08 *83 b2 ff ff 8b 4d e0 *fe *ff ............M...

    804ed7b0 1c 81 4d 80 83 7d *84 *ce 0f 84 8b b8 03 00 *ff *15 ..M..}..........

    804ed7c0 01 00 00 80 0f 85 *c7 *ff 02 00 8b 4d 0c e8 *a0 *e9 ...........M....

    804ed7d0 00 00 e9 b6 b3 ff *99 *21 eb 02 81 e3 f8 00 *b5 *ed .......!........

    804ed7e0 83 65 fc 00 e9 d1 *1a *72 ff 8b 4d 0c c1 e8 *8b *5d .e.....r..M....]

    804ed7f0 e0 1f 89 01 e9 20 *fd ff ff 66 25 a0 00 3c *18 *83 ..... ...f%..<..

    804ed800 d7 fe ff ff 8b c1 *00 *00 05 83 e0 1f f6 c5 *ff *c1 ................

    804ed810 45 f8 0f 84 6b ff *c1 *e8 ba 00 f0 ff ff 8b *04 *89 E...k...........

    804ed820 c2 3b c2 0f 85 04 *ff *ff 00 8d 45 ec 50 ff *c1 *23 .;........E.P..#

    804ed830 e8 78 c6 ff ff 85 *36 *00 45 e8 0f 84 fc b6 *75 *0c .x....6.E.....u.

    804ed840 8b 45 f8 e9 3b ff *f4 *01 ff ff ff ff cb cf *81 *ff .E..;...........

    804ed850 de cf 5f 80 f6 c4 *ff *ff 85 80 fd ff ff 83 *5f *80 .._..........._.

    804ed860 01 8b 4e 0c 83 c8 *02 *0f 46 11 04 89 45 08 *4e *0c ..N.....F...E.N.

    804ed870 69 fd ff ff f6 c1 *42 *f6 85 60 fd ff ff ff *0f *85 i.....B..`......


    MODULE_NAME: memory_corruption
    IMAGE_NAME: memory_corruption
    FOLLOWUP_NAME: memory_corruption
    DEBUG_FLR_IMAGE_TIMESTAMP: 0
    MEMORY_CORRUPTOR: STRIDE
    FAILURE_BUCKET_ID: MEMORY_CORRUPTION_STRIDE
    BUCKET_ID: MEMORY_CORRUPTION_STRIDE
    Followup: memory_corruption
    ---------
    1: kd> r
    eax=00002000 ebx=82600da0 ecx=b8813d43 edx=fffff000 esi=00e90548 edi=828b29d8
    eip=804ed81d esp=b8813d04 ebp=c030000c iopl=0 nv up ei pl nz na po nc
    cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010206
    nt!MmAccessFault+0x8d5:
    804ed81d 8b0489 mov eax,[ecx+ecx*4] ds:0023:9a86324f=????????
Topic Status:
Not open for further replies.


Add New Comment

TechSpot Members
Login or sign up for free,
it takes about 30 seconds.
You may also...


Get complete access to the TechSpot community. Join thousands of technology enthusiasts that contribute and share knowledge in our forum. Get a private inbox, upload your own photo gallery and more.