TechSpot

BSOD XP Help

By bigtotoro
Sep 22, 2007
  1. It's listing a hardware error but I have no new hardware installed. MemTest was completely clean. Disnks are defragged on a daily basis. No disk errors. Any ideas?


    Microsoft (R) Windows Debugger Version 6.7.0005.1
    Copyright (c) Microsoft Corporation. All rights reserved.


    Loading Dump File [C:\WINDOWS\Minidump\Mini092207-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available

    Symbol search path is: C:\WINDOWS\Symbols
    Executable search path is:
    Unable to load image ntoskrnl.exe, Win32 error 0n2
    *** WARNING: Unable to verify timestamp 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: Fri Sep 21 20:32:33.390 2007 (GMT-5)
    System Uptime: 2 days 1:14:43.947
    Unable to load image ntoskrnl.exe, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for ntoskrnl.exe
    Loading Kernel Symbols
    .....................................................................................................................................
    Loading User Symbols
    Loading unloaded module list
    ............................
    ERROR: FindPlugIns 8007007b
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck C2, {7, cd4, 2130001, 885c3b00}

    Probably caused by : hardware ( nt!KeForceResumeThread+1 )

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

    1: kd> !analyze -v
    ERROR: FindPlugIns 8007007b
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    BAD_POOL_CALLER (c2)
    The current thread is making a bad pool request. Typically this is at a bad IRQL level or double freeing the same allocation, etc.
    Arguments:
    Arg1: 00000007, Attempt to free pool which was already freed
    Arg2: 00000cd4, (reserved)
    Arg3: 02130001, Memory contents of the pool block
    Arg4: 885c3b00, Address of the block of pool being deallocated

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


    POOL_ADDRESS: 885c3b00

    FREED_POOL_TAG: File

    BUGCHECK_STR: 0xc2_7_File

    CUSTOMER_CRASH_COUNT: 1

    DEFAULT_BUCKET_ID: DRIVER_FAULT

    PROCESS_NAME: System

    LOCK_ADDRESS: 80558b60 -- (!locks 80558b60)

    Resource @ nt!PiEngineLock (0x80558b60) Available

    WARNING: SystemResourcesList->Flink chain invalid. Resource may be corrupted, or already deleted.


    WARNING: SystemResourcesList->Blink chain invalid. Resource may be corrupted, or already deleted.

    1 total locks

    PNP_TRIAGE:
    Lock address : 0x80558b60
    Thread Count : 0
    Thread address: 0x00000000
    Thread wait : 0x0

    MISALIGNED_IP:
    nt!KeForceResumeThread+1
    804f9deb 5d pop ebp

    LAST_CONTROL_TRANSFER: from 8054a583 to 804f9deb

    STACK_TEXT:
    bacd7cd4 8054a583 000000c2 00000007 00000cd4 nt!KeForceResumeThread+0x1
    bacd7d24 805bf940 885c3b00 00000000 87a6b600 nt!MiFreePoolPages+0x2a1
    bacd7d4c 805b9ee5 00000000 87a6b618 00000001 nt!PipForAllDeviceNodesCallback+0x29
    bacd7d64 805ba330 87a6b618 00000001 80561e80 nt!VdmSwapContexts+0x199
    bacd7dac 805ce84c 00000000 00000000 00000000 nt!CcPfParametersRead+0x21
    bacd7ddc 8054532e 805378ce 00000000 00000000 nt!`string'+0x14
    bacd7e64 00000000 00000000 00000000 00000000 nt!WmiTraceMessageVa+0x290


    STACK_COMMAND: kb

    FOLLOWUP_IP:
    nt!KeForceResumeThread+1
    804f9deb 5d pop ebp

    SYMBOL_STACK_INDEX: 0

    FOLLOWUP_NAME: MachineOwner

    IMAGE_NAME: hardware

    DEBUG_FLR_IMAGE_TIMESTAMP: 0

    SYMBOL_NAME: nt!KeForceResumeThread+1

    MODULE_NAME: hardware

    FAILURE_BUCKET_ID: IP_MISALIGNED

    BUCKET_ID: IP_MISALIGNED

    Followup: MachineOwner
    ---------
     
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...