BSOD after computer sits idle

Page 1 of 2 12 LastLast

  1. Posts : 6
    Windows 7 Ultimate x64
       #1

    BSOD after computer sits idle


    About 5 days ago I noticed my computer would restart itself at some point during the day. I caught it in the act once, and it was a BSOD. I didn't have a chance to catch the type of error. My best guess on the timing is about 2 hours of idling.

    I haven't made any hardware changes recently. I've also noticed during this time span that my computer's boot time has gotten a bit longer. It'll sit for a while on a black screen with my cursor on it, after the Starting Windows 7 screen and before my login screen pops up. Don't know if related.

    Microsoft Security Essentials and MalwareBytes haven't picked up anything in my multiple scans. I've tried multiple error tests and have come up with nothing. Attached is the .zip file.
      My Computer


  2. Posts : 3,904
    Windows 7 Ultimate 64-bit
       #2

    I have had a look at the Dumps, and i believe its caused by "Fastfat.sys"

    This issue may occur if either of the following conditions exist:
    The Fastfat.sys file is damaged or missing.
    The RAM in your computer is damaged or is not installed correctly.
      My Computer


  3. Posts : 81
    Windows 7 Ultimate X64
       #3

    Hello and welcome to SevenForums!

    KERNEL_DATA_INPAGE_ERROR (7a_c0000185) seems to be the error here:

    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    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: fffff6fc40008730, lock type that was held (value 1,2,3, or PTE address)
    Arg2: ffffffffc0000185, error status (normally i/o status code)
    Arg3: 00000000866ea860, current process (virtual address for lock type 3, or PTE)
    Arg4: fffff880010e6b9c, virtual address that could not be in-paged (or PTE contents if arg1 is a PTE address)
    
    Debugging Details:
    ------------------
    
    TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2
    
    ERROR_CODE: (NTSTATUS) 0xc0000185 - The I/O device reported an I/O error.
    
    DISK_HARDWARE_ERROR: There was error with disk hardware
    
    BUGCHECK_STR:  0x7a_c0000185
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  CODE_CORRUPTION
    
    PROCESS_NAME:  System
    
    CURRENT_IRQL:  0
    
    TRAP_FRAME:  fffff88002fe7a20 -- (.trap 0xfffff88002fe7a20)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=fffff880010e42a0 rbx=0000000000000000 rcx=fffffa8004a9d060
    rdx=fffffa800883c620 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff880010e6b9c rsp=fffff88002fe7bb8 rbp=fffff8a013735790
     r8=0000000000000007  r9=fffffa8004a9d1b0 r10=0000000000000000
    r11=fffffa800883c6f0 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up ei ng nz ac po cy
    PCIIDEX!GenPnpPdoQueryDeviceRelations:
    fffff880`010e6b9c 0000            add     byte ptr [rax],al ds:fffff880`010e42a0=??
    Resetting default scope
    
    LAST_CONTROL_TRANSFER:  from fffff80003145752 to fffff800030d2bc0
    
    STACK_TEXT:  
    fffff880`02fe7708 fffff800`03145752 : 00000000`0000007a fffff6fc`40008730 ffffffff`c0000185 00000000`866ea860 : nt!KeBugCheckEx
    fffff880`02fe7710 fffff800`030f991f : fffffa80`04708010 fffff880`02fe7880 fffff800`0330d540 fffffa80`04708010 : nt! ?? ::FNODOBFM::`string'+0x36c1a
    fffff880`02fe77f0 fffff800`030e01b9 : 00000000`00000000 00000000`00000008 ffffffff`ffffffff fffff880`010cc100 : nt!MiIssueHardFault+0x28b
    fffff880`02fe78c0 fffff800`030d0cee : 00000000`00000008 fffff880`010e6b9c 00000000`50656400 fffffa80`0883c6f0 : nt!MmAccessFault+0x1399
    fffff880`02fe7a20 fffff880`010e6b9c : fffff880`010e7ada fffffa80`04ae61b0 00000000`000007ff 00000000`00000001 : nt!KiPageFault+0x16e
    fffff880`02fe7bb8 fffff880`010e7ada : fffffa80`04ae61b0 00000000`000007ff 00000000`00000001 fffffa80`04a9f050 : PCIIDEX!GenPnpPdoQueryDeviceRelations
    fffff880`02fe7bc0 fffff880`010c8efe : 00000000`00000001 00000000`00000004 fffff800`03278200 fffffa80`04a9f1a0 : PCIIDEX!PciIdeDispatchPnp+0x22
    fffff880`02fe7bf0 fffff800`033c9c93 : 00000000`00000001 00000000`00000004 00000000`00000000 fffff880`02fe7c50 : ataport!ChannelQueryBusRelation+0xfa
    fffff880`02fe7c40 fffff800`030dc261 : fffff800`034eaa00 fffff800`03278201 fffffa80`03ce5b00 fffffa80`03ce5b50 : nt!IopProcessWorkItem+0x23
    fffff880`02fe7c70 fffff800`0336e73a : eefff4ff`f7bbff1f fffffa80`03ce5b50 00000000`00000080 fffffa80`03c709e0 : nt!ExpWorkerThread+0x111
    fffff880`02fe7d00 fffff800`030c38e6 : fffff880`009eb180 fffffa80`03ce5b50 fffff880`009f5f40 3ffffff7`2ffdf5bf : nt!PspSystemThreadStartup+0x5a
    fffff880`02fe7d40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16
    
    
    STACK_COMMAND:  kb
    
    MODULE_NAME: memory_corruption
    
    IMAGE_NAME:  memory_corruption
    
    FOLLOWUP_NAME:  memory_corruption
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  0
    
    MEMORY_CORRUPTOR:  LARGE
    
    FAILURE_BUCKET_ID:  X64_MEMORY_CORRUPTION_LARGE
    
    BUCKET_ID:  X64_MEMORY_CORRUPTION_LARGE
    
    Followup: memory_corruption
    ---------
    Run an SFC /SCANNOW command and inform us with the results.

    The error subset "c000185" could also mean there's an issue with your hard drive cabling. Check to see if all the ports to your hard drive are installed correctly, pushed in all the way, and free of any dust.

    Best of luck,

    PeregrineX

    EDIT: Dangit, HLPTech ninja'd me. He seems to be more experienced than I am, but I believe either one of the two of us could be right. I'll look into this some more, and check back on you.
      My Computer


  4. Posts : 6
    Windows 7 Ultimate x64
    Thread Starter
       #4

    I ran the sfc /scannow command- "Windows Resource Protection did not find any integrity violations."

    I opened up the bottom of my computer just to take a quick look to see if anything looked loose. Everything seemed in place to me, but then again I'm not sure what and where I should be looking. I'm running on an HP dv7, for the record.
      My Computer


  5. Posts : 6
    Windows 7 Ultimate x64
    Thread Starter
       #5

    Just now I was running a MSE scan in the background while attempting to open up a Word document off of my flash drive. Word was unresponsive, and then I got the BSOD. I've attached a picture.
      My Computer


  6. Posts : 81
    Windows 7 Ultimate X64
       #6

    clydefrawg said:
    Just now I was running a MSE scan in the background while attempting to open up a Word document off of my flash drive. Word was unresponsive, and then I got the BSOD. I've attached a picture.
    OK, this BSOD gives us more information.

    The 0x7a error KERNEL_DATA_INPAGE_ERROR with parameter 2 being 0xc00000185 means that there is defective cabling of your SCSI (or, your SATA HDD) device, or two devices are using the same interrupt request (IRQ) at the same time.

    Other common causes are faulty hardware, failing RAM, or a virus infection, however these are less common than the causes above.

    Let's start simple: run a Memtest86+ test by downloading the software off of this website: www.memtest.org. This will test your RAM for any errors or corruption.

    Please inform us of the results.

    Best of luck,

    PeregrineX
      My Computer


  7. Posts : 6
    Windows 7 Ultimate x64
    Thread Starter
       #7

    Ran the Memtest86+ for one pass, here's a photo from that.
      My Computer


  8. Posts : 81
    Windows 7 Ultimate X64
       #8

    clydefrawg said:
    Ran the Memtest86+ for one pass, here's a photo from that.
    Good, there are no errors. Your RAM is fine.

    It is nighttime in my part of the world, so I best be off to bed. I will return to look at this issue tomorrow.

    Good luck!
      My Computer


  9. Posts : 6,741
    W7 Pro x64 SP1 | W10 Pro IP x64 | W8.1 Pro x64 VM | Linux Mint VM
       #9

    MemTest needs to run for at least 8 passes for conclusive results. 1 pass is nowhere near enough to determine if RAM is faulty or not. Run it again for at least 8 passes.

    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    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: fffff6fc40008730, lock type that was held (value 1,2,3, or PTE address)
    Arg2: ffffffffc0000185, error status (normally i/o status code)
    Arg3: 00000000866ea860, current process (virtual address for lock type 3, or PTE)
    Arg4: fffff880010e6b9c, virtual address that could not be in-paged (or PTE contents if arg1 is a PTE address)
    
    Debugging Details:
    ------------------
    
    
    ERROR_CODE: (NTSTATUS) 0xc0000185 - The I/O device reported an I/O error.
    
    DISK_HARDWARE_ERROR: There was error with disk hardware
    
    BUGCHECK_STR:  0x7a_c0000185
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  CODE_CORRUPTION
    Run MemTest86+ to analyse your RAM. RAM - Test with Memtest86+

       Note
    MemTest86+ needs to be run for at least 8 passes for conclusive results. Set it running before you go to bed and leave it overnight. We're looking for zero errors here. Even a single error will indicate RAM failure.


    Run SeaTools to check the integrity of your HDD. SeaTools for DOS and Windows - How to Use

    Run chkdsk. Disk Check

    Report back with the results.
      My Computer


  10. Posts : 6
    Windows 7 Ultimate x64
    Thread Starter
       #10

    Ran 8 sweeps with Memtest last night, no errors. I attached a picture.

    Ran chkdsk C: /r and found bad clusters. Filename it gave me was for a sound effect for one of my Steam games.

    Ran Seatools under Windows. Short Generic Test: FAIL. Perhaps a dumb question, but does it stop scanning once it fails? Progress bar hasn't moved for a while and no further information given.

    Does this mean my HD is nearing the end of its life?
      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 23:54.
Find Us