BSOD while waking from hibernation

Discussion in 'Windows Vista Hardware' started by 4fingers, Jun 2, 2007.

  1. 4fingers

    4fingers Guest

    I have recently been having problems when trying to waken from hibernation
    mode. I seem to be able to do it fine the first time but when I the computer
    wakes from it the second time it simple gives a BSOD giving this technical

    STOP 0x00000077 (0000000E 0x0000000E 0x00000000 0x19E81000)

    I tried Microsoft support
    But that didn't help much

    It made a crash dump file so I used WinDb to try and analyse it and this is
    what I got

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

    Loading Dump File [C:\Users\Graeme\Desktop\MEMORY.DMP]
    Kernel Complete Dump File: Full address space is available

    Symbol search path is:
    Executable search path is:
    Windows Vista Kernel Version 6000 UP Free x86 compatible
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 6000.16386.x86fre.vista_rtm.061101-2205
    Kernel base = 0x81c00000 PsLoadedModuleList = 0x81d11db0
    Debug session time: Sat Jun 2 14:03:49.781 2007 (GMT+1)
    System Uptime: 0 days 11:57:32.732
    Loading Kernel Symbol
    Loading User Symbols

    Loading unloaded module list
    * Bugcheck Analysis


    Use !analyze -v to get detailed debugging information.

    BugCheck 77, {c000000e, c000000e, 0, 19e81000}

    Probably caused by : memory_corruption ( nt!MiMakeOutswappedPageResident+471 )

    Followup: MachineOwner

    kd> !analyze -
    * Bugcheck Analysis


    The requested page of kernel data could not be read in. Caused by
    bad block in paging file or disk controller error.
    In the case when the first arguments is 0 or 1, the stack signature
    in the kernel stack was not found. Again, bad hardware.
    An I/O status of c000009c (STATUS_DEVICE_DATA_ERROR) or
    C000016AL (STATUS_DISK_OPERATION_FAILED) normally indicates
    the data could not be read from the disk due to a bad
    block. Upon reboot autocheck will run and attempt to map out the bad
    sector. If the status is C0000185 (STATUS_IO_DEVICE_ERROR) and the paging
    file is on a SCSI disk device, then the cabling and termination should be
    checked. See the knowledge base article on SCSI termination.
    Arg1: c000000e, status code
    Arg2: c000000e, i/o status code
    Arg3: 00000000, page file number
    Arg4: 19e81000, offset into page file

    Debugging Details:

    ERROR_CODE: (NTSTATUS) 0xc000000e - A device which does not exist was

    DISK_HARDWARE_ERROR: There was error with disk hardware

    BUGCHECK_STR: 0x77_c000000e


    PROCESS_NAME: System


    LAST_CONTROL_TRANSFER: from 81ccc677 to 81cd85c9

    835cbc2c 81ccc677 00000077 c000000e c000000e nt!KeBugCheckEx+0x1e
    835cbcb0 81cccacc c041aeb8 0000bd6d 00000001
    835cbd38 81cccba2 84181438 835cbd58 00000000
    835cbd6c 81cb3957 841814a8 00000000 835cbdc0 nt!KiInSwapKernelStacks+0x43
    835cbd7c 81e254a8 00000000 835c0680 00000000 nt!KeSwapProcessOrStack+0x83
    835cbdc0 81c9145e 81cb38d4 00000000 00000000 nt!PspSystemThreadStartup+0x9d
    00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16


    81ccc677 cc int 3


    FOLLOWUP_NAME: MachineOwner



    SYMBOL_NAME: nt!MiMakeOutswappedPageResident+471

    IMAGE_NAME: memory_corruption

    FAILURE_BUCKET_ID: 0x77_c000000e_nt!MiMakeOutswappedPageResident+471

    BUCKET_ID: 0x77_c000000e_nt!MiMakeOutswappedPageResident+471

    Followup: MachineOwner

    I am running on windows Vista Business 32 Bit edition. If you need more
    information just ask otherwise does anyone have any idea what could be
    causing it to do this.

    Thanks in Advance
    4fingers, Jun 2, 2007
    1. Advertisements

  2. 4fingers

    freddy Guest


    My reading makes me believe you have a bad hard drive, or at least bad
    portions on the hard drive.

    freddy, Jun 2, 2007
    1. Advertisements

  3. 4fingers

    4fingers Guest

    Hi freddy
    Well I did a Disk check and no errors were found and I see no other reason
    to suspect my hard drive is bad.
    Also if that were the case why would it work fine the first time and not the
    4fingers, Jun 3, 2007
  4. 4fingers

    freddy Guest


    The problem with the error interpretation is that there are too many, to wit:

    1. Memory corruption
    2. Bad block in paging file
    3. Bad hardware (SCSI device)
    4. Device specified not found

    That's only after a quick reading. There may be others lurking within all
    that verbiage. This multitude of possibilities is difficult to deal with,
    and I can see why your asking. To get to the bottom of this takes someone
    with more technical knowledge than that which I possess.

    Suggestions: You ideas are just as good as mine. Take more reads of all
    those error statements, one at a time, and try using google to search for
    ideas. This approach likely could be time consuming, but there is likely no
    magic pixie dust available to solve this situation. Just some thoughts.
    It's unlikely any one else can determine the exact problem here, but--anyone?
    freddy, Jun 3, 2007
  5. 4fingers

    freddy Guest


    One other possible approach that I didn't mention is to google on the words
    you used in your subject line, that is:

    troubleshooting BSOD while waking from hibernation

    Or words to that effect. You can sometimes get different results by
    changing the search terms even slightly.

    I've learned that something over here can cause something over there to
    crash. The system will then report that something over there crashed, giving
    you error codes that makes one think that the problem is that thing over
    there. But the problem is actually the thing over here. Now you're chasing
    your tail.

    I've seen video card functions crash because of a bad (incompatible) driver
    in something like the NIC card. The NIC driver causes the video card
    function to crash giving you an error code that says, if effect, "hey, your
    video card crashed." Now people start chasing after updated video card
    drivers, swapping out the video card, replacing the PSU, etc., etc., all of
    which don't work. You get the idea.

    Just some more things to consider. That's why searching on the above
    suggested search term might lead you in a different and more productive
    freddy, Jun 3, 2007
    1. Advertisements

Ask a Question

Want to reply to this thread or ask your own question?
