TechSpot

Irql_not_less Than Bsod

By jb444
Oct 20, 2006
  1. Hi, I dont know much about using minidumps so I was hoping someone could explain the basics of reading them. Basically I got a BSOD IRQL_NOT_LESS_THAN_EQUAL_TO
    0x0000000A (0x00080020, 0x00000002, 0x00000001, 0x8053F970)
    The minidump says:

    ****************************************************************************
    Executable search path is:
    *********************************************************************
    * Symbols can not be loaded because symbol path is not initialized. *
    * *
    * The Symbol Path can be set by: *
    * using the _NT_SYMBOL_PATH environment variable. *
    * using the -y <symbol_path> argument when starting the debugger. *
    * using .sympath and .sympath+ *
    *********************************************************************
    Unable to load image \WINDOWS\system32\ntkrnlpa.exe, Win32 error 2
    *** WARNING: Unable to verify timestamp for ntkrnlpa.exe
    *** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
    Windows XP Kernel Version 2600 (Service Pack 2) MP (2 procs) Free x86 compatible
    Product: WinNt
    Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055c700
    Debug session time: Wed Oct 18 21:49:06.015 2006 (GMT+1)
    System Uptime: 0 days 0:36:44.696
    *********************************************************************
    * Symbols can not be loaded because symbol path is not initialized. *
    * *
    * The Symbol Path can be set by: *
    * using the _NT_SYMBOL_PATH environment variable. *
    * using the -y <symbol_path> argument when starting the debugger. *
    * using .sympath and .sympath+ *
    *********************************************************************
    Unable to load image \WINDOWS\system32\ntkrnlpa.exe, Win32 error 2
    *** WARNING: Unable to verify timestamp for ntkrnlpa.exe
    *** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
    Loading Kernel Symbols
    ........................................................................................................................
    Loading User Symbols
    Loading unloaded module list
    ..........
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck A, {80020, 2, 1, 8053f970}

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

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

    *** WARNING: Unable to verify timestamp for mssmbios.sys
    *** ERROR: Module load completed but symbols could not be loaded for mssmbios.sys
    Probably caused by : ntkrnlpa.exe ( nt+68970 )

    Followup: MachineOwner
    --------

    Could anyone just tell me how I read from that what the error was and how I could solve it?
    Thanks,
    Chris
     
  2. smore9648

    smore9648 TS Rookie Posts: 697

    More then likely a RAM problem.

    Search for MEMTest and make several passes
     
  3. jb444

    jb444 TS Rookie Topic Starter Posts: 100

    I cant seem to set the symbol path for windbg, so ive zipped the three minidumps and would be grateful for any advice people can give me.
    The computer has restarted once and frozen once (suggests dodgy power supply?). Also I while I was getting CRITICAL_OBJECT_TERMINATION 0x000000F4 (0x00000003, 0x863A0900, 0x863A0A74 0x805D1142) but I reinstalled windows and all drivers afresh and it seemed to stop.
    Have run memtest with no errors over two passes but floppy drive stopped working so I cant test RAM any further for the moment.
     
  4. cpc2004

    cpc2004 TS Evangelist Posts: 1,994

    Faulty Ram

    Hi,

    One minidump is crashed at tcpip and mouclass.sys. Both modules are stable module and I believe that the crashes are caused by faulty ram.

    Your debug report
    Mini102006-01.dmp BugCheck A, {80020, 2, 1, 8053f970}
    Mini102006-01.dmp Probably caused by : tcpip.sys ( tcpip!CloseRCE+37 )

    Mini103006-01.dmp BugCheck D1, {8, 2, 0, f7338c00}
    Mini103006-01.dmp Probably caused by : wg111v2.sys ( wg111v2+5c97 )

    Mini103106-01.dmp BugCheck A, {3f98df9d, 2, 1, 806e4a2a}
    Mini103106-01.dmp Probably caused by : mouclass.sys ( mouclass!MouseClassServiceCallback+189 )
     
  5. bushwhacker

    bushwhacker TechSpot Chancellor Posts: 783

    Did you add any RAM to your computer recently?
     
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...