TechSpot

Problem with Gateway MX3701 Laptop Helppppppppp

By rwbrierley
Dec 6, 2007
Topic Status:
Not open for further replies.
  1. All-

    Started receiving BSOD of death during initial bootup so I decided to reinstall OS and drivers. BSOD started again AFTER I installed the OS.

    I perfomed a MEMTEST which was successful on all three passes. I also perfomed a harddrive extended scan which was successuf. The BSOD error messages are now changing as can be seen below:


    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: e5726854, memory referenced
    Arg2: 0000001c, IRQL
    Arg3: 00000000, 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: 805021af, address which referenced memory



    MODULE_NAME: nt

    FAULTING_MODULE: 804d7000 nt

    DEBUG_FLR_IMAGE_TIMESTAMP: 45e53f9d

    READ_ADDRESS: unable to get nt!MmSpecialPoolStart
    unable to get nt!MmSpecialPoolEnd
    unable to get nt!MmPoolCodeStart
    unable to get nt!MmPoolCodeEnd
    e5726854

    CURRENT_IRQL: 1c

    FAULTING_IP:
    nt+2b1af
    805021af 8b10 mov edx,dword ptr [eax]

    CUSTOMER_CRASH_COUNT: 1

    DEFAULT_BUCKET_ID: WRONG_SYMBOLS

    BUGCHECK_STR: 0xA

    LAST_CONTROL_TRANSFER: from 8050240d to 805021af

    STACK_TEXT:
    WARNING: Stack unwind information not available. Following frames may be wrong.
    805502c4 8050240d 00000000 805502e0 00000000 nt+0x2b1af
    805502f0 80501626 1cdc9869 0000001b 80550418 nt+0x2b40d
    805503fc 80501813 8055b0a0 ffdff9c0 ffdff000 nt+0x2a626
    80550428 805450bf 8055b4a0 00000000 00000c1b nt+0x2a813
    8055042c 8055b4a0 00000000 00000c1b 00000000 nt+0x6e0bf
    80550430 00000000 00000c1b 00000000 8055b0a0 nt+0x844a0


    STACK_COMMAND: kb

    FOLLOWUP_IP:
    nt+2b1af
    805021af 8b10 mov edx,dword ptr [eax]

    SYMBOL_STACK_INDEX: 0

    SYMBOL_NAME: nt+2b1af

    FOLLOWUP_NAME: MachineOwner

    IMAGE_NAME: ntoskrnl.exe

    BUCKET_ID: WRONG_SYMBOLS

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



    Second Dump


    *********************************************************************
    Unable to load image ntoskrnl.exe, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for ntoskrnl.exe
    *** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
    Windows XP Kernel Version 2600 (Service Pack 2) MP (2 procs) Free x86 compatible
    Product: WinNt, suite: TerminalServer SingleUserTS Personal
    Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055c700
    Debug session time: Tue Dec 4 18:41:53.906 2007 (GMT-5)
    System Uptime: 0 days 0:00:38.616
    *
    DRIVER_CORRUPTED_EXPOOL (c5)
    An attempt was made to access a pageable (or completely invalid) address at an
    interrupt request level (IRQL) that is too high. This is
    caused by drivers that have corrupted the system pool. Run the driver
    verifier against any new (or suspect) drivers, and if that doesn't turn up
    the culprit, then use gflags to enable special pool.
    Arguments:
    Arg1: 019e0108, memory referenced
    Arg2: 00000002, IRQL
    Arg3: 00000000, value 0 = read operation, 1 = write operation
    Arg4: 8054afcb, address which referenced memory

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

    ***** Kernel symbols are WRONG. Please fix symbols to do analysis.

    *************************************************************************
    *** ***
    *** ***
    *** Your debugger is not using the correct symbols ***
    *** ***
    *** In order for this command to work properly, your symbol path ***
    *** must point to .pdb files that have full type information. ***
    *** ***
    *** Certain .pdb files (such as the public OS symbols) do not ***
    *** contain the required information. Contact the group that ***
    *** provided you with these symbols if you need this command to ***
    *** work. ***
    *** ***
    *** Type referenced: nt!_KPRCB ***
    *** ***
    *************************************************************************
    *************************************************************************
    *** ***
    *** ***
    *** Your debugger is not using the correct symbols ***
    *** ***
    *** In order for this command to work properly, your symbol path ***
    *** must point to .pdb files that have full type information. ***
    *** ***
    *** Certain .pdb files (such as the public OS symbols) do not ***
    *** contain the required information. Contact the group that ***
    *** provided you with these symbols if you need this command to ***
    *** work. ***
    *** ***
    *** Type referenced: nt!KPRCB ***
    *** ***
    *************************************************************************
    *************************************************************************
    *** ***
    *** ***
    *** Your debugger is not using the correct symbols ***
    *** ***
    *** In order for this command to work properly, your symbol path ***
    *** must point to .pdb files that have full type information. ***
    *** ***
    *** Certain .pdb files (such as the public OS symbols) do not ***
    *** contain the required information. Contact the group that ***
    *** provided you with these symbols if you need this command to ***
    *** work. ***
    *** ***
    *** Type referenced: nt!_KPRCB ***
    *** ***
    *************************************************************************
    *************************************************************************
    *** ***
    *** ***
    *** Your debugger is not using the correct symbols ***
    *** ***
    *** In order for this command to work properly, your symbol path ***
    *** must point to .pdb files that have full type information. ***
    *** ***
    *** Certain .pdb files (such as the public OS symbols) do not ***
    *** contain the required information. Contact the group that ***
    *** provided you with these symbols if you need this command to ***
    *** work. ***
    ***
    MODULE_NAME: nt

    FAULTING_MODULE: 804d7000 nt

    DEBUG_FLR_IMAGE_TIMESTAMP: 45e53f9d

    BUGCHECK_STR: 0xC5_2

    CURRENT_IRQL: 2

    FAULTING_IP:
    nt+73fcb
    8054afcb 8b06 mov eax,dword ptr [esi]

    CUSTOMER_CRASH_COUNT: 1

    DEFAULT_BUCKET_ID: WRONG_SYMBOLS

    LAST_CONTROL_TRANSFER: from 804f0da7 to 8054afcb

    STACK_TEXT:
    WARNING: Stack unwind information not available. Following frames may be wrong.
    efdd0bfc 804f0da7 00000000 00000001 20707249 nt+0x73fcb
    efdd0c48 804f40f5 0000000a 00000000 858097e8 nt+0x19da7
    efdd0c70 8058265c 0000000a 858097d0 859e7ca0 nt+0x1d0f5
    efdd0ca4 805bb459 857aaaf0 84cf89d8 00120089 nt+0xab65c
    efdd0cd4 805badab 857aaaf0 018097d0 859e7ca0 nt+0xe4459
    efdd0cfc 805bae49 e10adb38 858097e8 000004e0 nt+0xe3dab
    efdd0d44 805baf81 000004e0 00000001 00000000 nt+0xe3e49
    efdd0d58 8054086c 000004e0 0012e14c 7c90eb94 nt+0xe3f81
    efdd0d64 7c90eb94 badb0d00 0012e148 fffffff9 nt+0x6986c
    efdd0d68 badb0d00 0012e148 fffffff9 fffffff9 0x7c90eb94
    efdd0d6c 0012e148 fffffff9 fffffff9 00000000 0xbadb0d00
    efdd0d70 fffffff9 fffffff9 00000000 00000000 0x12e148
    efdd0d74 fffffff9 00000000 00000000 00000000 0xfffffff9
    efdd0d78 00000000 00000000 00000000 00000000 0xfffffff9


    STACK_COMMAND: kb

    FOLLOWUP_IP:
    nt+73fcb
    8054afcb 8b06 mov eax,dword ptr [esi]

    SYMBOL_STACK_INDEX: 0

    SYMBOL_NAME: nt+73fcb

    FOLLOWUP_NAME: MachineOwner

    IMAGE_NAME: ntoskrnl.exe

    BUCKET_ID: WRONG_SYMBOLS

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

    Now I am getting a different BSOD error AFTER the machine is up and running

    Does anyone have any ideas??? Faulty RAM????

    Thanks in advance,
  2. samjohnson

    samjohnson Newcomer, in training Posts: 320

    I have read on here several times that you need to let the memtest run for at least seven passes. Sorry I can't help further. But try the memtest again and let it go for the seven passes and see what it says.
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.