Stop Error 0x00000035: NO_MORE_IRP_STACK_LOCATIONS

Archived from groups: microsoft.public.windowsxp.help_and_support (More info?)

I get consistantly get a 0x00000035: NO_MORE_IRP_STACK_LOCATIONS stop error
about 3/4 of the way through the WinXP black screen in the boot.

From http://aumha.org/win5/kbestop.htm it seems to be a driver or RAM issue,
but doesn't give much more about how to diagnose it. The MS knowledge base
and the rest of the web has been less helpful.

I have run MemTest86 for several hours (which in the past has always found
broken RAM) and here the RAM does not appear to be an issue.

How do I continue to diagnose this issue? If it's a driver problem how do I
figure out which one?

Thanks,

John
4 answers Last reply
More about stop error 0x00000035 no_more_irp_stack_locations
  1. Archived from groups: microsoft.public.windowsxp.help_and_support (More info?)

    I also wanted to add that booting in any kind of Safe Mode, of course, works
    fine.

    "John McDowell" wrote:

    > I get consistantly get a 0x00000035: NO_MORE_IRP_STACK_LOCATIONS stop error
    > about 3/4 of the way through the WinXP black screen in the boot.
    >
    > From http://aumha.org/win5/kbestop.htm it seems to be a driver or RAM issue,
    > but doesn't give much more about how to diagnose it. The MS knowledge base
    > and the rest of the web has been less helpful.
    >
    > I have run MemTest86 for several hours (which in the past has always found
    > broken RAM) and here the RAM does not appear to be an issue.
    >
    > How do I continue to diagnose this issue? If it's a driver problem how do I
    > figure out which one?
    >
    > Thanks,
    >
    > John
    >
    >
    >
  2. Archived from groups: microsoft.public.windowsxp.help_and_support (More info?)

    Ok, so I tried enabling boot logging from the boot menu, but because it blue
    screens at the black win xp screen, before the session manager service
    flushes the log to disk, I cannot see which driver causes the issue.
    (Similar to here: http://support.microsoft.com/?kbid=275735)

    Is there a way to have Windows print out status information as it boots?

    John McDowell


    "John McDowell" wrote:

    > I also wanted to add that booting in any kind of Safe Mode, of course, works
    > fine.
    >
    > "John McDowell" wrote:
    >
    > > I get consistantly get a 0x00000035: NO_MORE_IRP_STACK_LOCATIONS stop error
    > > about 3/4 of the way through the WinXP black screen in the boot.
    > >
    > > From http://aumha.org/win5/kbestop.htm it seems to be a driver or RAM issue,
    > > but doesn't give much more about how to diagnose it. The MS knowledge base
    > > and the rest of the web has been less helpful.
    > >
    > > I have run MemTest86 for several hours (which in the past has always found
    > > broken RAM) and here the RAM does not appear to be an issue.
    > >
    > > How do I continue to diagnose this issue? If it's a driver problem how do I
    > > figure out which one?
    > >
    > > Thanks,
    > >
    > > John
    > >
    > >
    > >
  3. Archived from groups: microsoft.public.windowsxp.help_and_support (More info?)

    Here is the dumpchk output for my blue screen, does this help?


    C:\WINDOWS>"c:\Program Files\Support Tools\dumpchk.exe" -v -c MEMORY.DMP
    Loading dump file MEMORY.DMP
    ----- 32 bit Kernel Full Dump Analysis

    DUMP_HEADER32:
    MajorVersion 0000000f
    MinorVersion 00000a28
    DirectoryTableBase 0d65e000
    PfnDataBase 81a51000
    PsLoadedModuleList 8055ab20
    PsActiveProcessHead 80560bd8
    MachineImageType 0000014c
    NumberProcessors 00000001
    BugCheckCode 00000035
    BugCheckParameter1 829ca008
    BugCheckParameter2 00000000
    BugCheckParameter3 00000000
    BugCheckParameter4 00000000
    PaeEnabled 00000000
    KdDebuggerDataBlock 8054c760

    Physical Memory Description:
    Number of runs: 3
    FileOffset Start Address Length
    00001000 00001000 0009e000
    0009f000 00100000 00eff000
    00f9e000 01000000 1ef70000
    Last Page: 1ff0d000 1ff6f000

    KiProcessorBlock at 80559a20
    1 KiProcessorBlock entries:
    ffdff120


    Windows XP Kernel Version 2600 (Service Pack 2) UP Free x86 compatible
    Built by: 2600.xpsp_sp2_rtm.040803-2158
    Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055ab20
    Debug session time: Sat Apr 16 22:00:30 2005
    System Uptime: 0 days 0:00:48
    start end module name
    804d7000 806eb780 nt Checksum: 002160C9 Timestamp: Wed Aug 04
    02:
    19:48 2004 (41108004)

    Unloaded modules:
    f8866000 f8871000 imapi.sys Timestamp: Sat Apr 16 22:00:08 2005
    (4261C328)
    f8856000 f885f000 processr.sys Timestamp: Sat Apr 16 22:00:08 2005
    (4261C32
    8)
    f8be6000 f8bea000 kbdhid.sys Timestamp: Sat Apr 16 22:00:08 2005
    (4261C328)

    f8aee000 f8af3000 Cdaudio.SYS Timestamp: Sat Apr 16 22:00:08 2005
    (4261C328
    )
    f8be2000 f8be5000 Sfloppy.SYS Timestamp: Sat Apr 16 22:00:08 2005
    (4261C328
    )
    f8ae6000 f8aeb000 Flpydisk.SYS Timestamp: Sat Apr 16 22:00:08 2005
    (4261C32
    8)

    Finished dump check
  4. Archived from groups: microsoft.public.windowsxp.help_and_support (More info?)

    In case anyone was following this, I finally gave up on understanding this
    error and did a windows repair on this, which fixed it.

    John


    "John McDowell" wrote:

    > Here is the dumpchk output for my blue screen, does this help?
    >
    >
    > C:\WINDOWS>"c:\Program Files\Support Tools\dumpchk.exe" -v -c MEMORY.DMP
    > Loading dump file MEMORY.DMP
    > ----- 32 bit Kernel Full Dump Analysis
    >
    > DUMP_HEADER32:
    > MajorVersion 0000000f
    > MinorVersion 00000a28
    > DirectoryTableBase 0d65e000
    > PfnDataBase 81a51000
    > PsLoadedModuleList 8055ab20
    > PsActiveProcessHead 80560bd8
    > MachineImageType 0000014c
    > NumberProcessors 00000001
    > BugCheckCode 00000035
    > BugCheckParameter1 829ca008
    > BugCheckParameter2 00000000
    > BugCheckParameter3 00000000
    > BugCheckParameter4 00000000
    > PaeEnabled 00000000
    > KdDebuggerDataBlock 8054c760
    >
    > Physical Memory Description:
    > Number of runs: 3
    > FileOffset Start Address Length
    > 00001000 00001000 0009e000
    > 0009f000 00100000 00eff000
    > 00f9e000 01000000 1ef70000
    > Last Page: 1ff0d000 1ff6f000
    >
    > KiProcessorBlock at 80559a20
    > 1 KiProcessorBlock entries:
    > ffdff120
    >
    >
    > Windows XP Kernel Version 2600 (Service Pack 2) UP Free x86 compatible
    > Built by: 2600.xpsp_sp2_rtm.040803-2158
    > Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055ab20
    > Debug session time: Sat Apr 16 22:00:30 2005
    > System Uptime: 0 days 0:00:48
    > start end module name
    > 804d7000 806eb780 nt Checksum: 002160C9 Timestamp: Wed Aug 04
    > 02:
    > 19:48 2004 (41108004)
    >
    > Unloaded modules:
    > f8866000 f8871000 imapi.sys Timestamp: Sat Apr 16 22:00:08 2005
    > (4261C328)
    > f8856000 f885f000 processr.sys Timestamp: Sat Apr 16 22:00:08 2005
    > (4261C32
    > 8)
    > f8be6000 f8bea000 kbdhid.sys Timestamp: Sat Apr 16 22:00:08 2005
    > (4261C328)
    >
    > f8aee000 f8af3000 Cdaudio.SYS Timestamp: Sat Apr 16 22:00:08 2005
    > (4261C328
    > )
    > f8be2000 f8be5000 Sfloppy.SYS Timestamp: Sat Apr 16 22:00:08 2005
    > (4261C328
    > )
    > f8ae6000 f8aeb000 Flpydisk.SYS Timestamp: Sat Apr 16 22:00:08 2005
    > (4261C32
    > 8)
    >
    > Finished dump check
    >
Ask a new question

Read More

Stop Error RAM Windows XP