BSOD upon resuming from sleep or hibernation on windows 7 64 bit

Page 1 of 3 123 LastLast

  1. Posts : 11
    Window 7 64 bit home premium
       #1

    BSOD upon resuming from sleep or hibernation on windows 7 64 bit


    I recently upsized my SSD drive and changed from a samsung 830 to a larger crucial drive.

    This is a custom built computer that is on it's second MB and cpu combo and had been stable for years until just recently with the new drive addition, so I do not feel it is a driver or something along these lines. I am unsure if it may be RAM or just a bad SSD.

    I used windows home server to re-image the c drive from the samsung to to the crucial drive. It ran with no problems for several weeks and then the Blue screens started on resuming from sleep and hibernation.

    I have included the zip file from the debugging bat file as instructed from these forums. I have tried to add the dump file but the uploader is telling me it is an invalid file and not accepting it.

    The blue screen does indicate that it is a kernal_data_inpage_error.

    It list off half a dozen error codes as well, that I can add if needed.

    Thanks for any help you can give.
    Last edited by randombetrayal; 03 Mar 2014 at 18:42.
      My Computer


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

    The uploaded zip is empty. Post it following the Blue Screen of Death (BSOD) Posting Instructions.
      My Computer


  3. Posts : 11
    Window 7 64 bit home premium
    Thread Starter
       #3

    Ok, I am having trouble getting the diagnostic tool to work. I run the program and it seems as if it is creating files but once it finishes there is no folder on my desktop to zip. I have run it twice and it asked if I wanted to copy or replace the files it had already created, but I can't find anything once it is done.

    I ran a different program and it gave the following output on the minidump file:

    I have read some forum posts on the ntoskrnl.exe and it seems that they are all over the place on what is the cause. There was some mention about Avast antivirus, and I did change antivirus to Avast a few weeks ago.

    On Tue 3/4/2014 7:59:34 PM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\030414-15132-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
    Bugcheck code: 0x7A (0xFFFFF6FB41FFBEF8, 0xFFFFFFFFC000000E, 0x7FE6E884, 0xFFFFF683FF7DF090)
    Error: KERNEL_DATA_INPAGE_ERROR
    file path: C:\Windows\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    Bug check description: This bug check indicates that the requested page of kernel data from the paging file could not be read into memory.
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



    On Mon 3/3/2014 1:58:39 AM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\030314-14726-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
    Bugcheck code: 0x7A (0xFFFFF6FC4001DFF8, 0xFFFFFFFFC000000E, 0x1BFD62BE0, 0xFFFFF88003BFF000)
    Error: KERNEL_DATA_INPAGE_ERROR
    file path: C:\Windows\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    Bug check description: This bug check indicates that the requested page of kernel data from the paging file could not be read into memory.
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



    On Sat 3/1/2014 11:37:01 PM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\030214-14632-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
    Bugcheck code: 0x7A (0xFFFFF6FB41FFBEE8, 0xFFFFFFFFC000000E, 0x17B5BF884, 0xFFFFF683FF7DD548)
    Error: KERNEL_DATA_INPAGE_ERROR
    file path: C:\Windows\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    Bug check description: This bug check indicates that the requested page of kernel data from the paging file could not be read into memory.
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
      My Computer


  4. Posts : 11
    Window 7 64 bit home premium
    Thread Starter
       #4

    Ok, I ran the diagnostic tool for a 3rd time and it finally outputted a folder for me to zip that I have attached.
      My Computer


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

    Make it sure that your Crucial M500 240GB 2.5-inch Internal SSD is running with the latest Firmware Update MU03, dated 09/24/2013.
    SSD Support

    Post a screenshot of all your HDDs and SSDs using CrystalDiskInfo - Software - Crystal Dew World

    Re-seat the sata and power.


    If the cables are any bad to look at, change them.

    Let us know the results.
    ___________________________________________
    Code:
    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: fffff6fb41ffbef8, lock type that was held (value 1,2,3, or PTE address)
    Arg2: ffffffffc000000e, error status (normally i/o status code)
    Arg3: 000000007fe6e884, current process (virtual address for lock type 3, or PTE)
    Arg4: fffff683ff7df090, 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
    
    BUGCHECK_STR:  0x7a_c000000e
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
    
    PROCESS_NAME:  cfp.exe
    
    CURRENT_IRQL:  0
    
    ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre
    
    LAST_CONTROL_TRANSFER:  from fffff8000434a752 to fffff800042d7bc0
      My Computer


  6. Posts : 11
    Window 7 64 bit home premium
    Thread Starter
       #6

    Ok, ran the firmware update and it came back as I have the most current firmware.

    I reseated the sata and power cables to the c: drive, did not notice any change in how they sat.

    I have attached the screenshots of the C drive and all the other data drives on the computer.
      My Computer


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

    Status of your Storage device is not fair at all!

    • Crucial M500: Health Status = Unknown. Contract Crucial about it. It does not sound good. You may need/want to replace it.
    • Western Digital Raptor: Health Status = Caution.
    • Seagate Barracuda 7200: Health Status = Caution
    • SAMSUNG Spinpoint F3: Health Status = Caution

    Let us know the results.
      My Computer


  8. Posts : 11
    Window 7 64 bit home premium
    Thread Starter
       #8

    Ok so i contacted crucial and they requested i unplug the sata cable to the SSD but leave the power on to the computer for 6-8 hours to allow the disks garbage collection work and hopefully clean out the bad sectors and fix the problem. I will do this tonight.

    I ran the seagate tools program on the seagate data disks that I can run the fix all, and both disks came back as passing.

    The other disks I ran the smart test, disk short test, generic short test and all came back passing.

    It did notify me that I have a firmware update for one of the seagate drives that was labeled as important so I will install that, otherwise all disks are good to go.
      My Computer


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

    OK, let us know about the advancement.
      My Computer


  10. Posts : 11
    Window 7 64 bit home premium
    Thread Starter
       #10

    Ok, so I left the computer on last night and allowed the drive to do it's garbage collection and I tested it by puting and then waking it from sleep and no blue screen so at least one attempt in so far so good.

    Strange thing though is upon booting up i got an error when it tried to load windows that the bootmgr is missing. I put the install disk in and did a startup repair but it did not fix it, so I was confused as it restarted itself with the install disk still and I left it alone in that I did not select for it to boot from disk and as the disk drive spun up the computer booted into windows normally. So I assume the disk is providing the bootmgr to allow me to load windows normally??

    If I can get the sleep/hibernate to work it is not a big deal to me as I rarely reboot and it is not much of an issue if just having the install disk in is all it takes to load into windows.

    Any thoughts??
      My Computer


 
Page 1 of 3 123 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 09:53.
Find Us