BSOD occuring when logging in, error 0x0000007a

Page 2 of 2 FirstFirst 12

  1. Posts : 28,845
    Win 8 Release candidate 8400
       #11

    barryc182 said:
    When logging back on from hibernation the BSOD happens again, what could be causing this?
    We still need the DMPS
      My Computer


  2. Posts : 8
    Windows 7 Ultimate 32bit
    Thread Starter
       #12

    New dumps for same problem


    these are the new dumps after everything that has been done...

    thanks
      My Computer


  3. Posts : 28,845
    Win 8 Release candidate 8400
       #13

    barryc182 said:
    these are the new dumps after everything that has been done...

    thanks
    Again it points to HD issues.


    KERNEL_DATA_INPAGE_ERROR (7a)
    The requested page of kernel data could not be read in. Typically caused by
    a bad block in the paging file or disk controller error. Also see
    KERNEL_STACK_INPAGE_ERROR.
    If the error status is 0xC000000E, 0xC000009C, 0xC000009D or 0xC0000185,
    it means the disk subsystem has experienced a failure.
    If the error status is 0xC000009A, then it means the request failed because
    a filesystem failed to make forward progress.
    Arguments:
    Arg1: c057bfb8, lock type that was held (value 1,2,3, or PTE address)
    Arg2: c000000e, error status (normally i/o status code)
    Arg3: 1218b8c0, current process (virtual address for lock type 3, or PTE)
    Arg4: af7f74da, virtual address that could not be in-paged (or PTE contents if arg1 is a PTE address)

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


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

    DISK_HARDWARE_ERROR: There was error with disk hardware
      My Computer


  4. Posts : 8
    Windows 7 Ultimate 32bit
    Thread Starter
       #14

    zigzag3143 said:
    barryc182 said:
    these are the new dumps after everything that has been done...

    thanks
    Again it points to HD issues.


    KERNEL_DATA_INPAGE_ERROR (7a)
    The requested page of kernel data could not be read in. Typically caused by
    a bad block in the paging file or disk controller error. Also see
    KERNEL_STACK_INPAGE_ERROR.
    If the error status is 0xC000000E, 0xC000009C, 0xC000009D or 0xC0000185,
    it means the disk subsystem has experienced a failure.
    If the error status is 0xC000009A, then it means the request failed because
    a filesystem failed to make forward progress.
    Arguments:
    Arg1: c057bfb8, lock type that was held (value 1,2,3, or PTE address)
    Arg2: c000000e, error status (normally i/o status code)
    Arg3: 1218b8c0, current process (virtual address for lock type 3, or PTE)
    Arg4: af7f74da, virtual address that could not be in-paged (or PTE contents if arg1 is a PTE address)

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


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

    DISK_HARDWARE_ERROR: There was error with disk hardware
    The solution in other words is to replace the hard drive to fix the errors?

    what usually causes these errors just so i avoid it in the future?

    THANKS
      My Computer


 
Page 2 of 2 FirstFirst 12

  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 18:58.
Find Us