1. TechSpot is dedicated to computer enthusiasts and power users. Ask a question and give support. Join the community here.
    TechSpot is dedicated to computer enthusiasts and power users.
    Ask a question and give support.
    Join the community here, it only takes a minute.
    Dismiss Notice

occasional BSODs after wakeup

By bsodcollector
Feb 19, 2006
  1. Hi all,
    I have a WinXP Home SP2 running on a Gigabyte GA8IHXP with 512 MB ram,
    a Nvidia Ti4200 video card, a DVB-S and a Benq DW1640 DVD burner.

    The system is basically used to sleep :), wakeup to record some DVB-S stuff
    and fall back to sleep again. At times I cut and burn the recordings onto DVD.

    The problem: ocassionally the system wakes up when it actually shouldn't and
    hangs. Also sometimes it should wake up and when doing so, it hangs.

    I downloaded windbg, the symbols and Horard's debugwiz and here's the beginning of debuglog.txt (the complete debuglog.zip is attached). Now what
    does this tell you? How can I fix this system?

    Thanks in advance,
    BSOD Collector

    Opened log file 'c:\debuglog.txt'

    BugCheck 1000008E, {c0000005, 804db69c, f89a8e8c, 0}

    Probably caused by : ACPI.sys ( ACPI!ACPIDeviceIrpCompleteRequest+27 )

    Followup: MachineOwner

    1: kd> !analyze -v;r;kv;lmtn;.logclose;q

    Arg1: c0000005, The exception code that was not handled
    Arg2: 804db69c, The address that the exception occurred at
    Arg3: f89a8e8c, Trap Frame
    Arg4: 00000000

    Debugging Details:

    EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - Die Anweisung in "0x%08lx" verweist auf Speicher in "0x%08lx". Der Vorgang "%s" konnte nicht auf dem Speicher durchgef hrt werden.

    804db69c f00fba2b00 lock bts dword ptr [ebx],0x0

    TRAP_FRAME: f89a8e8c -- (.trap fffffffff89a8e8c)
    .trap fffffffff89a8e8c
    Unable to read trap frame at f89a8e8c




    LAST_CONTROL_TRANSFER: from 804e18ff to 804db69c

    f89a8f24 804e18ff 82b7c948 829d1c60 00000000 nt!KeSynchronizeExecution+0x12
    f89a8f54 f8529a2d 81b65948 f89a8f80 f852ab8f nt!IopfCompleteRequest+0xa2
    f89a8f60 f852ab8f 82bbc9c8 829d1c60 00000000 ACPI!ACPIDeviceIrpCompleteRequest+0x27
    f89a8f80 f852ac7a 81b65948 f8543238 f8543230 ACPI!ACPIDeviceCompleteRequest+0xb1
    f89a8fa4 f852b0bf f8543218 f85416b0 00000001 ACPI!ACPIDevicePowerProcessGenericPhase+0x72
    f89a8fcc 804dcd22 f85431e0 00000000 00000000 ACPI!ACPIDevicePowerDpc+0x18f
    f89a8ff4 804dc88d f8a00c4c 00000000 00000000 nt!KiRetireDpcList+0x61
    f89a8ff8 f8a00c4c 00000000 00000000 00000000 nt!KiDispatchInterrupt+0x2b
    WARNING: Frame IP not in any known module. Following frames may be wrong.
    f89a8ffc 00000000 00000000 00000000 00000000 0xf8a00c4c
  2. cpc2004

    cpc2004 TS Evangelist Posts: 1,994

    ?? Faulty RAM


    Crashes at module APCI is usually related to faulty ram. Run memtest to stress test the ram. Usually one minidump is insufficient to confirm the culprit. Perform dump analysis for 5 to 6 minidumps. If the culprit is faulty ram, your windows crashes with various bugcheck codes.
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...