BSOD going to hibernating, etc.

Page 1 of 2 12 LastLast

  1. Posts : 37
    Windows 7 Home Premium 64bit
       #1

    BSOD going to hibernating, etc.


    Laptop started having BSOD when I try and go into hibernation mode, etc. I think it read something along the lines of "Internal_power_error".

    Not sure if i got any dump files complete, as most of the time it would reach 80%+ then turn off on it's own. If you point me in the right direction, I'll try and get a dump file, if someone can help me out. Maybe drivers went out of date, haven't had a problem for years, till now on this laptop. Thanks!
      My Computer


  2. Posts : 37
    Windows 7 Home Premium 64bit
    Thread Starter
       #2

    Found some dump files that were created when BSOD happened I guess.
      My Computer


  3. Arc
    Posts : 35,373
    Microsoft Windows 10 Pro Insider Preview 64-bit
       #3

    Code:
    INTERNAL_POWER_ERROR (a0)
    The power policy manager experienced a fatal error.
    Arguments:
    Arg1: 0000000000000009, A fatal error occured while preparing the hibernate file.
    Arg2: ffffffffc000009c, Status code
    Arg3: 0000000000000001, Mirroring phase
    Arg4: 0000000000000000
    Code:
    Error code: (NTSTATUS) 0xc000009c (3221225628) - STATUS_DEVICE_DATA_ERROR
    Some device is causing a fatal error during hibernation, but the supplied information is not sufficient to infer what that device may be. Please follow the Blue Screen of Death (BSOD) Posting Instructions and post the resulting zip file in your reply post.
      My Computer


  4. Posts : 37
    Windows 7 Home Premium 64bit
    Thread Starter
       #4

    Arc said:
    Code:
    INTERNAL_POWER_ERROR (a0)
    The power policy manager experienced a fatal error.
    Arguments:
    Arg1: 0000000000000009, A fatal error occured while preparing the hibernate file.
    Arg2: ffffffffc000009c, Status code
    Arg3: 0000000000000001, Mirroring phase
    Arg4: 0000000000000000
    Code:
    Error code: (NTSTATUS) 0xc000009c (3221225628) - STATUS_DEVICE_DATA_ERROR
    Some device is causing a fatal error during hibernation, but the supplied information is not sufficient to infer what that device may be. Please follow the Blue Screen of Death (BSOD) Posting Instructions and post the resulting zip file in your reply post.
    My bad, haven't been here in a while, I knew i missed something, my bad. Here it is :)
      My Computer


  5. Arc
    Posts : 35,373
    Microsoft Windows 10 Pro Insider Preview 64-bit
       #5

    Get rid of intel rapid storage. First uninstall it from Control Panel > Programs and Features. Then Uninstall the driver from device manager.

    1. Right click on "my computer" icon and click "manage" on the context menu.
    2. It will open the "computer management" window.
    3. Select "Device Manager" in the left pane, It will list all the existing devices up.
    4. Expand "IDE ATA/ATAPI controllers" by clicking on the triangle in front of it.
    5. Select one Intel device item under it, right click, uninstall.
    6. Continue the process for all Intel items under "IDE ATA/ATAPI controllers"
    7. Now restart the computer. At restart, windows will auto configure the appropriate native system driver.

    Free up the startup. Windows does not need any other program to auto start with it, but the auto start programs often conflicts and causes various problems including BSODs.

    1. Click on the Start button
    2. Type “msconfig (without quotes), click the resulting link. It will open the System Configuration window.
    3. Select the “Startup” tab.
    4. Deselect all items other than the antivirus.
    5. Apply > OK
    6. Accept then restart.

    And, if there is any issue (it seems that there is, but cannot be said with certainty in a remote assistance) with MBAM, resolve it. As the user, you know how to resolve it.
      My Computer


  6. Posts : 37
    Windows 7 Home Premium 64bit
    Thread Starter
       #6

    Arc said:
    Get rid of intel rapid storage. First uninstall it from Control Panel > Programs and Features. Then Uninstall the driver from device manager.

    1. Right click on "my computer" icon and click "manage" on the context menu.
    2. It will open the "computer management" window.
    3. Select "Device Manager" in the left pane, It will list all the existing devices up.
    4. Expand "IDE ATA/ATAPI controllers" by clicking on the triangle in front of it.
    5. Select one Intel device item under it, right click, uninstall.
    6. Continue the process for all Intel items under "IDE ATA/ATAPI controllers"
    7. Now restart the computer. At restart, windows will auto configure the appropriate native system driver.

    Free up the startup. Windows does not need any other program to auto start with it, but the auto start programs often conflicts and causes various problems including BSODs.

    1. Click on the Start button
    2. Type “msconfig (without quotes), click the resulting link. It will open the System Configuration window.
    3. Select the “Startup” tab.
    4. Deselect all items other than the antivirus.
    5. Apply > OK
    6. Accept then restart.

    And, if there is any issue (it seems that there is, but cannot be said with certainty in a remote assistance) with MBAM, resolve it. As the user, you know how to resolve it.
    You think Intel rapid storage driver might be causing BSOD? Haven't had problems with anything up to now. Maybe i need certain drivers to be updated? Also, would uninstalling intel rapid storage affect my pc running correctly?
      My Computer


  7. Arc
    Posts : 35,373
    Microsoft Windows 10 Pro Insider Preview 64-bit
       #7

    denden said:
    You think Intel rapid storage driver might be causing BSOD?
    The only device driver that failed to load in the dumps is the IRST driver. So there is a fair chance.

    denden said:
    Haven't had problems with anything up to now.
    Problems start to cause from a particular point of time.

    denden said:
    Maybe i need certain drivers to be updated? Also, would uninstalling intel rapid storage affect my pc running correctly?
    In AHCI mode, system native driver is more stabler than IRST. Some people say that there might be some performance drop; but I tried it myself and never have seen any visible or noticeable performance drop.
      My Computer


  8. Posts : 37
    Windows 7 Home Premium 64bit
    Thread Starter
       #8

    Looks like intel rapid storage was removed form contorl panel, and device manager, and cleared up start up. Will let you know if BSOD still happens. Heard from my bro that it crashed again yesterday, but no minidump of it. Not sure what he did, but looks like the laptop went into hibernation or w.e cuz the laptop looked like it was off, no buttons(power, etc) was on, the fan was on full blast spinning like crazy, then had to turn it off push and hold power button.
      My Computer


  9. Posts : 37
    Windows 7 Home Premium 64bit
    Thread Starter
       #9

    Got another BSOD today again. New Dump file is attached. Looking for more solutions.
      My Computer


  10. Posts : 2,528
    Windows 10 Pro x64
       #10

    This one is a directx race condition bug with Intel video chipsets (and your Acer Aspire 4830T is indeed running an Intel video chip), it appears, fixed by KB2870102:
    Code:
    // Stop 0xA - IRQL_NOT_LESS_OR_EQUAL
    // Something tried to access an invalid memory address at IRQL 2 or higher (insta-bugcheck):
    0: kd> .bugcheck
    Bugcheck code 0000000A
    Arguments 00000000`00000000 00000000`00000002 00000000`00000000 fffff800`03091822
    
    // Trap frame showing the site of the bugcheck in the stack:
    0: kd> .trap 0xfffff880073968c0
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=0000000000000002 rbx=0000000000000000 rcx=fffff80003209e80
    rdx=fffffa8005cd0d80 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff80003091822 rsp=fffff88007396a50 rbp=0000000000000000
     r8=0000000000000000  r9=fffffa80082c8c40 r10=fffffa80082c8c40
    r11=fffff88007396ae0 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up ei pl nz ac po cy
    nt!KiSignalSynchronizationObject+0x42:
    fffff800`03091822 488b3f          mov     rdi,qword ptr [rdi] ds:00000000`00000000=????????????????
    
    // Here's where the pagefault occurred (again, page fault in kernel at IRQL2 or higher is insta-bugcheck):
    0: kd> k
      *** Stack trace for last set context - .thread/.cxr resets it
     # Child-SP          RetAddr           Call Site
    00 fffff880`07396a50 fffff800`0308fbd6 nt!KiSignalSynchronizationObject+0x42
    01 fffff880`07396aa0 fffff880`0436347f nt!KeSetEvent+0x106
    02 fffff880`07396b10 fffff880`043812e9 dxgmms1!VidMmiProcessTerminationCommand+0x5f
    03 fffff880`07396b60 fffff880`04380574 dxgmms1!VidSchiSubmitDeviceCommand+0x39
    04 fffff880`07396b90 fffff880`04380012 dxgmms1!VidSchiSubmitQueueCommand+0xb0
    05 fffff880`07396bc0 fffff800`03324456 dxgmms1!VidSchiWorkerThread+0xd6
    06 fffff880`07396c00 fffff800`0307c2c6 nt!PspSystemThreadStartup+0x5a
    07 fffff880`07396c40 00000000`00000000 nt!KxStartSystemThread+0x16
    
    // Running old DirectX binaries for Windows 7 (non-hotfixed):
    0: kd> lmvm Dxgkrnl
    start             end                 module name
    fffff880`04253000 fffff880`04348000   dxgkrnl    (deferred)             
        Mapped memory image file: C:\ProgramData\dbg\sym\dxgkrnl.sys\539E411Cf5000\dxgkrnl.sys
        Image path: \SystemRoot\System32\drivers\dxgkrnl.sys
        Image name: dxgkrnl.sys
        Timestamp:        Sun Jun 15 17:58:04 2014 (539E411C)
        CheckSum:         000FF01E
        ImageSize:        000F5000
        File version:     6.1.7601.18510
        Product version:  6.1.7601.18510
        File flags:       0 (Mask 3F)
        File OS:          40004 NT Win32
        File type:        3.7 Driver
        File date:        00000000.00000000
        Translations:     0409.04b0
        CompanyName:      Microsoft Corporation
        ProductName:      Microsoft® Windows® Operating System
        InternalName:     dxgkrnl.sys
        OriginalFilename: dxgkrnl.sys
        ProductVersion:   6.1.7601.18510
        FileVersion:      6.1.7601.18510 (win7sp1_gdr.140615-1511)
        FileDescription:  DirectX Graphics Kernel
        LegalCopyright:   © Microsoft Corporation. All rights reserved.
    Get the hotfix on the box and at least this issue will go away. Can't say much for the other issue you started this thread for, as this seems unrelated.
      My Computer


 
Page 1 of 2 12 LastLast

  Related Discussions
Our Sites
Site Links
About Us
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 06:28.
Find Us