TechSpot

BSod 0xA 0x4E Help

By ShadowGun
Sep 9, 2008
  1. Well i have been trying to figure this out for months can someone help me?
    Memtest passed 10 times

    Specs:
    Processor: Intel Core 2 Duo E6420
    Mobo: Asus P5NSLI
    RAM: Kenston Value RAM 2x1 GB sticks 667
    HD: Western Digital 250 GB
    Graphic Card: MSI Geforce 8600GT OC Edition
    PSU: 550 Watt

    Mini Dumps:

    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    IRQL_NOT_LESS_OR_EQUAL (a)
    An attempt was made to access a pageable (or completely invalid) address at an
    interrupt request level (IRQL) that is too high. This is usually
    caused by drivers using improper addresses.
    If a kernel debugger is available get the stack backtrace.
    Arguments:
    Arg1: 00000000, memory referenced
    Arg2: 00000002, IRQL
    Arg3: 00000001, bitfield :
    bit 0 : value 0 = read operation, 1 = write operation
    bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
    Arg4: 805226e8, address which referenced memory

    Debugging Details:
    ------------------


    WRITE_ADDRESS: 00000000

    CURRENT_IRQL: 2

    FAULTING_IP:
    nt!MiRemovePageByColor+66
    805226e8 ff08 dec dword ptr [eax]

    CUSTOMER_CRASH_COUNT: 1

    DEFAULT_BUCKET_ID: DRIVER_FAULT

    BUGCHECK_STR: 0xA

    PROCESS_NAME: explorer.exe

    TRAP_FRAME: baa17388 -- (.trap 0xffffffffbaa17388)
    ErrCode = 00000002
    eax=0c910200 ebx=89e66028 ecx=00000000 edx=89e6b008 esi=e74eb000 edi=000001ff
    eip=8054c1cb esp=baa173fc ebp=baa17450 iopl=0 nv up ei pl zr na pe nc
    cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246
    nt!ExAllocatePoolWithTag+0x863:
    8054c1cb 8906 mov dword ptr [esi],eax ds:0023:e74eb000=????????
    Resetting default scope

    LAST_CONTROL_TRANSFER: from 80522c12 to 805226e8

    STACK_TEXT:
    baa1725c 80522c12 00000001 0000003e c073a758 nt!MiRemovePageByColor+0x66
    baa17274 80514b64 c073a758 00000000 00000000 nt!MiRemoveAnyPage+0xbc
    baa1728c 80516563 e74eb000 c073a758 00000000 nt!MiResolveDemandZeroFault+0x12a
    baa17304 80520239 00000000 e74eb000 c073a758 nt!MiDispatchFault+0x145
    baa17370 80544578 00000001 e74eb000 00000000 nt!MmAccessFault+0x877
    baa17370 8054c1cb 00000001 e74eb000 00000000 nt!KiTrap0E+0xd0
    baa17450 bf802b1c 00000001 00000000 35306847 nt!ExAllocatePoolWithTag+0x863
    baa17470 bf8139ca 0000047c 35306847 00000000 win32k!HeavyAllocPool+0x74
    baa17484 bf80598e 0000047c 35306847 baa1751c win32k!PALLOCMEM+0x18
    baa174a0 bf8094de 0000047c 00000005 00000001 win32k!AllocateObject+0x9a
    baa174e8 bf82d503 00000040 00000000 00000000 win32k!SURFMEM::bCreateDIB+0x1d4
    baa17564 bf838807 03010397 00000002 00000000 win32k!GreCreateDIBitmapReal+0x2fb
    baa175d0 8054161c 03010397 00000010 00000010 win32k!NtGdiCreateDIBitmapInternal+0xe2
    baa175d0 7c90e4f4 03010397 00000010 00000010 nt!KiFastCallEntry+0xfc
    WARNING: Frame IP not in any known module. Following frames may be wrong.
    00fdf630 00000000 00000000 00000000 00000000 0x7c90e4f4


    STACK_COMMAND: kb

    FOLLOWUP_IP:
    win32k!HeavyAllocPool+74
    bf802b1c 8bd0 mov edx,eax

    SYMBOL_STACK_INDEX: 7

    SYMBOL_NAME: win32k!HeavyAllocPool+74

    FOLLOWUP_NAME: MachineOwner

    MODULE_NAME: win32k

    IMAGE_NAME: win32k.sys

    DEBUG_FLR_IMAGE_TIMESTAMP: 48025f2a

    FAILURE_BUCKET_ID: 0xA_W_win32k!HeavyAllocPool+74

    BUCKET_ID: 0xA_W_win32k!HeavyAllocPool+74

    Followup: MachineOwner
    ---------




    PFN_LIST_CORRUPT (4e)
    Typically caused by drivers passing bad memory descriptor lists (ie: calling
    MmUnlockPages twice with the same list, etc). If a kernel debugger is
    available get the stack trace.
    Arguments:
    Arg1: 0000008f, The free or zeroed page listhead is corrupt
    Arg2: ffffff7f, new page
    Arg3: 000728fe, old page
    Arg4: 00000000, 0

    Debugging Details:
    ------------------


    BUGCHECK_STR: 0x4E_8f

    CUSTOMER_CRASH_COUNT: 3

    DEFAULT_BUCKET_ID: DRIVER_FAULT

    PROCESS_NAME: System

    LAST_CONTROL_TRANSFER: from 8051cbb4 to 804f9f33

    STACK_TEXT:
    bacc37f8 8051cbb4 0000004e 0000008f ffffff7f nt!KeBugCheckEx+0x1b
    bacc3840 80698b94 89e3f5e0 00000000 00000044 nt!MmZeroPageThread+0x250
    bacc3dac 805cff64 80087000 00000000 00000000 nt!Phase1Initialization+0x1288
    bacc3ddc 805460de 8069790c 80087000 00000000 nt!PspSystemThreadStartup+0x34
    00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16


    STACK_COMMAND: kb

    FOLLOWUP_IP:
    nt!MmZeroPageThread+250
    8051cbb4 cc int 3

    SYMBOL_STACK_INDEX: 1

    SYMBOL_NAME: nt!MmZeroPageThread+250

    FOLLOWUP_NAME: MachineOwner

    MODULE_NAME: nt

    DEBUG_FLR_IMAGE_TIMESTAMP: 4802516a

    IMAGE_NAME: memory_corruption

    FAILURE_BUCKET_ID: 0x4E_8f_nt!MmZeroPageThread+250

    BUCKET_ID: 0x4E_8f_nt!MmZeroPageThread+250

    Followup: MachineOwner
    ---------
     
  2. Route44

    Route44 TechSpot Ambassador Posts: 11,966   +70

    Both of these errors are strong indications of hardware issues. The 0x4E is especially an indication of corupt memory and if you read what you posted that is exactly what it cites as the cause.

    Therefore run MemTest for a minimum of 7 passes. If you have errors you have to replace your memory. If you have errors run this test on each stick to determine if one or all are defective.

    www.memtest.org
     
  3. ShadowGun

    ShadowGun TS Rookie Topic Starter

    It passes 10 times did it yesterday
     
  4. Route44

    Route44 TechSpot Ambassador Posts: 11,966   +70

    As good as memtest is bad memory has been known to pass it. Are you doing any overclocking?
     
  5. ShadowGun

    ShadowGun TS Rookie Topic Starter

    No but i had the GPU oced a few months back then took it off because i re-formated and decided not to OC it.
     
  6. Route44

    Route44 TechSpot Ambassador Posts: 11,966   +70

    Asus motherboards are notorious for being picky about RAM which leads me to two more questions:

    1. Is your RAM compatible with your motherboard as per Asus?

    2. Is your motherboard setting your RAM at correct voltage?
     
  7. ShadowGun

    ShadowGun TS Rookie Topic Starter

    RAM setting is all on auto and i checked ram is compatible i have this computer for a year now
     
Topic Status:
Not open for further replies.

Similar Topics

Add New Comment

You need to be a member to leave a comment. Join thousands of tech enthusiasts and participate.
TechSpot Account You may also...