BSOD Randomly for over a year, recently starting getting dump files


  1. Posts : 3
    Windows 7 64
       #1

    BSOD Randomly for over a year, recently starting getting dump files


    Hello,

    I have just returned home to my desktop (Used my laptop at school) and it is still having blue screen problems.

    I have had this computer for over a year, and ever since I built it, it randomly blue screened.

    I have changed the memory and ran memtest(Like a year ago but i did it), I also purchased a new hard drive so i know its not the ram or the hard drive thats causing my problem.

    I was never able to find out what was wrong with my computer because of the fact that it never gave me minidump files. Recently for some reason, it started to give me actual minidump files.

    I have uploaded my minidump files, so if anyone can take a look that would be great.

    In terms of what im doing when it happens, its completely random. Sometimes it happens 5 minutes after turning on the computer, other times it takes weeks.
      My Computer


  2. Posts : 3
    Windows 7 64
    Thread Starter
       #2

    Here's one of the dumps that i pulled off of windbg.


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


    Loading Dump File [C:\Windows\Minidump\072013-8049-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available

    Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
    Executable search path is:
    Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 7601.17790.amd64fre.win7sp1_gdr.120305-1505
    Machine Name:
    Kernel base = 0xfffff800`03002000 PsLoadedModuleList = 0xfffff800`03246650
    Debug session time: Sat Jul 20 13:40:27.721 2013 (UTC - 5:00)
    System Uptime: 0 days 19:07:54.533
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ..........................
    Loading User Symbols
    Loading unloaded module list
    .....
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck F4, {3, fffffa8008981b30, fffffa8008981e10, fffff80003381660}

    Probably caused by : csrss.exe

    Followup: MachineOwner
    ---------

    6: kd> !analyze -v
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    CRITICAL_OBJECT_TERMINATION (f4)
    A process or thread crucial to system operation has unexpectedly exited or been
    terminated.
    Several processes and threads are necessary for the operation of the
    system; when they are terminated (for any reason), the system can no
    longer function.
    Arguments:
    Arg1: 0000000000000003, Process
    Arg2: fffffa8008981b30, Terminating object
    Arg3: fffffa8008981e10, Process image file name
    Arg4: fffff80003381660, Explanatory message (ascii)

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


    PROCESS_OBJECT: fffffa8008981b30

    IMAGE_NAME: csrss.exe

    DEBUG_FLR_IMAGE_TIMESTAMP: 0

    MODULE_NAME: csrss

    FAULTING_MODULE: 0000000000000000

    PROCESS_NAME: csrss.exe

    EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

    BUGCHECK_STR: 0xF4_C0000005

    CUSTOMER_CRASH_COUNT: 1

    DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

    CURRENT_IRQL: 0

    STACK_TEXT:
    fffff880`040a6e38 fffff800`03408772 : 00000000`000000f4 00000000`00000003 fffffa80`08981b30 fffffa80`08981e10 : nt!KeBugCheckEx
    fffff880`040a6e40 fffff800`033b5f7b : ffffffff`ffffffff fffffa80`0938db60 fffffa80`08981b30 fffffa80`08981b30 : nt!PspCatchCriticalBreak+0x92
    fffff880`040a6e80 fffff800`033350f4 : ffffffff`ffffffff 00000000`00000001 fffffa80`08981b30 00000000`00000008 : nt! ?? ::NNGAKEGL::`string'+0x176d6
    fffff880`040a6ed0 fffff800`0307df13 : fffffa80`08981b30 fffff800`c0000005 fffffa80`0938db60 00000000`01b90900 : nt!NtTerminateProcess+0xf4
    fffff880`040a6f50 fffff800`0307a4d0 : fffff800`030c99df fffff880`040a7a38 fffff880`040a7790 fffff880`040a7ae0 : nt!KiSystemServiceCopyEnd+0x13
    fffff880`040a70e8 fffff800`030c99df : fffff880`040a7a38 fffff880`040a7790 fffff880`040a7ae0 00000000`01b91d50 : nt!KiServiceLinkage
    fffff880`040a70f0 fffff800`0307e302 : fffff880`040a7a38 00000000`0002db26 fffff880`040a7ae0 00000000`01b91828 : nt! ?? ::FNODOBFM::`string'+0x48e24
    fffff880`040a7900 fffff800`0307ce7a : 00000000`00000001 00000000`01b90ff8 00000000`00000001 00000000`0002db26 : nt!KiExceptionDispatch+0xc2
    fffff880`040a7ae0 00000000`77b78e2b : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x23a
    00000000`01b91000 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77b78e2b


    STACK_COMMAND: kb

    FOLLOWUP_NAME: MachineOwner

    FAILURE_BUCKET_ID: X64_0xF4_C0000005_IMAGE_csrss.exe

    BUCKET_ID: X64_0xF4_C0000005_IMAGE_csrss.exe

    Followup: MachineOwner
    ---------

    6: kd> !analyze -v
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    CRITICAL_OBJECT_TERMINATION (f4)
    A process or thread crucial to system operation has unexpectedly exited or been
    terminated.
    Several processes and threads are necessary for the operation of the
    system; when they are terminated (for any reason), the system can no
    longer function.
    Arguments:
    Arg1: 0000000000000003, Process
    Arg2: fffffa8008981b30, Terminating object
    Arg3: fffffa8008981e10, Process image file name
    Arg4: fffff80003381660, Explanatory message (ascii)

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


    PROCESS_OBJECT: fffffa8008981b30

    IMAGE_NAME: csrss.exe

    DEBUG_FLR_IMAGE_TIMESTAMP: 0

    MODULE_NAME: csrss

    FAULTING_MODULE: 0000000000000000

    PROCESS_NAME: csrss.exe

    EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

    BUGCHECK_STR: 0xF4_C0000005

    CUSTOMER_CRASH_COUNT: 1

    DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

    CURRENT_IRQL: 0

    STACK_TEXT:
    fffff880`040a6e38 fffff800`03408772 : 00000000`000000f4 00000000`00000003 fffffa80`08981b30 fffffa80`08981e10 : nt!KeBugCheckEx
    fffff880`040a6e40 fffff800`033b5f7b : ffffffff`ffffffff fffffa80`0938db60 fffffa80`08981b30 fffffa80`08981b30 : nt!PspCatchCriticalBreak+0x92
    fffff880`040a6e80 fffff800`033350f4 : ffffffff`ffffffff 00000000`00000001 fffffa80`08981b30 00000000`00000008 : nt! ?? ::NNGAKEGL::`string'+0x176d6
    fffff880`040a6ed0 fffff800`0307df13 : fffffa80`08981b30 fffff800`c0000005 fffffa80`0938db60 00000000`01b90900 : nt!NtTerminateProcess+0xf4
    fffff880`040a6f50 fffff800`0307a4d0 : fffff800`030c99df fffff880`040a7a38 fffff880`040a7790 fffff880`040a7ae0 : nt!KiSystemServiceCopyEnd+0x13
    fffff880`040a70e8 fffff800`030c99df : fffff880`040a7a38 fffff880`040a7790 fffff880`040a7ae0 00000000`01b91d50 : nt!KiServiceLinkage
    fffff880`040a70f0 fffff800`0307e302 : fffff880`040a7a38 00000000`0002db26 fffff880`040a7ae0 00000000`01b91828 : nt! ?? ::FNODOBFM::`string'+0x48e24
    fffff880`040a7900 fffff800`0307ce7a : 00000000`00000001 00000000`01b90ff8 00000000`00000001 00000000`0002db26 : nt!KiExceptionDispatch+0xc2
    fffff880`040a7ae0 00000000`77b78e2b : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x23a
    00000000`01b91000 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77b78e2b


    STACK_COMMAND: kb

    FOLLOWUP_NAME: MachineOwner

    FAILURE_BUCKET_ID: X64_0xF4_C0000005_IMAGE_csrss.exe

    BUCKET_ID: X64_0xF4_C0000005_IMAGE_csrss.exe

    Followup: MachineOwner
    ---------

    6: kd> !process fffffa8008981b30 3
    GetPointerFromAddress: unable to read from fffff800032b0000
    PROCESS fffffa8008981b30
    SessionId: none Cid: 0264 Peb: 7fffffdb000 ParentCid: 0254
    DirBase: 1cb340000 ObjectTable: fffff8a000c9f9a0 HandleCount: <Data Not Accessible>
    Image: csrss.exe
    VadRoot fffffa8009457170 Vads 141 Clone 0 Private 692. Modified 2489. Locked 0.
    DeviceMap fffff8a000008ca0
    Token fffff8a0017a8b00
    ReadMemory error: Cannot get nt!KeMaximumIncrement value.
    fffff78000000000: Unable to get shared data
    ElapsedTime 00:00:00.000
    UserTime 00:00:00.000
    KernelTime 00:00:00.000
    QuotaPoolUsage[PagedPool] 0
    QuotaPoolUsage[NonPagedPool] 0
    Working Set Sizes (now,min,max) (2475, 50, 345) (9900KB, 200KB, 1380KB)
    PeakWorkingSetSize 4999
    VirtualSize 123 Mb
    PeakVirtualSize 213 Mb
    PageFaultCount 23684
    MemoryPriority BACKGROUND
    BasePriority 13
    CommitCharge 915

    *** Error in reading nt!_ETHREAD @ fffffa800933db60
      My Computer


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

    From your second post:
    Code:
    BugCheck F4, {3, fffffa8008981b30, fffffa8008981e10, fffff80003381660}
    Stop 0xF4 is usually storage related.

    Your Pyro SSD is the H drive here. And H is the system drive fro your case, which is not very usual. Make it sure that the SSD is running with the latest firmware. I am not very sure about the specific source, but it seems that you need to go to their forums: SSD Support

    The SSD is small, and only 12 GB free space is remaining. And it also may cause disc errors. Salvage some free space. Disable Hibernate. It will free up some space.

    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.

    Also make it sure that the SSD is properly seated.

    Let us know the results.
      My Computer


  4. Posts : 3
    Windows 7 64
    Thread Starter
       #4

    I have done all that you have said.

    Hibernation was already disabled, but windows + a few things seems to just take up most of my space on my solid state.

    I took of rapid storage.

    I updated my SSD.

    The thiung is the crashing started happening with an old hard drive, so i piurchased the solid state and the crashing still kept happening, so i dont think its the SSD.

    Im unsure if i changed the sata cable so maybe that could possibly be it?

    Is there anything else you can think of? Because the blue screen happens randomly like i said, sometimes in over a month intervals, so itll be hard to tell if its fixed.

    Thank you though, hopefully your suggstions have helped.
      My Computer


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

    Yes, if the SATA cable is not good and not properly seated it may cause srop 0xF4 BSODs. So check all the connections and make it sure that there is no loose connection.
      My Computer


 

  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 17:16.
Find Us