Random Restarts 4 Dump Files Posted

Page 1 of 2 12 LastLast

  1. Posts : 12
    Windows 7 Ultimate x64
       #1

    Random Restarts -Attachment Fixed-


    I've been having this problem for months, but I've never been able to figure it out. I originally thought it was a problem with my C drive running out of space due to an oversized pagefile.sys and hibernate.sys, but I fixed those issues recently and it's still occurring. If anyone can give me some feedback on what could be causing this I'd appreciate it. If you need additional information please leave a post and I'll respond to it as fast as I can.

    Thank you for the help in advance,

    Malk



    Edit: Sorry for some reason they weren't showing up...
    Last edited by Malkirion; 17 Jul 2013 at 15:23. Reason: Replaced DMP files with a full SF folder.
      My Computer


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


  3. Posts : 12
    Windows 7 Ultimate x64
    Thread Starter
       #3

    Sorry, for some reason it wasn't showing up when I added it to attachments, I redid it with advance settings and it's posted now.

    Thank you,
    Malkirion
      My Computer

  4.    #4

    Code:
    BugCheck F4, {3, fffffa8008d219a0, fffffa8008d21c80, fffff800039cc350}
    
    ----- ETW minidump data unavailable-----
    Probably caused by : csrss.exe
    From the call stack, the process referenced a memory address, which caused the thread to have a page fault, although, the page fault couldn't handed and processed by the thread as a result of some kind of I/O error.

    Code:
    6: kd> !process fffffa8008d219a0 3
    GetPointerFromAddress: unable to read from fffff800038fd000
    PROCESS fffffa8008d219a0
        SessionId: none  Cid: 02c8    Peb: 7fffffd3000  ParentCid: 02b8
        DirBase: 1d5596000  ObjectTable: fffff8a00ed363d0  HandleCount: <Data Not Accessible>
        Image: csrss.exe
        VadRoot fffffa800a9a4f80 Vads 319 Clone 0 Private 2743. Modified 25193. Locked 0.
        DeviceMap fffff8a000008b30
        Token                             fffff8a00ed2e060
        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]         465848
        QuotaPoolUsage[NonPagedPool]      52400
        Working Set Sizes (now,min,max)  (4468, 50, 345) (17872KB, 200KB, 1380KB)
        PeakWorkingSetSize                9750
        VirtualSize                       176 Mb
        PeakVirtualSize                   335 Mb
        PageFaultCount                    197972983
        MemoryPriority                    BACKGROUND
        BasePriority                      13
        CommitCharge                      3024
    
            *** Error in reading nt!_ETHREAD @ fffffa8008d72b50
    Code:
    STACK_TEXT:  
    fffff880`095dee38 fffff800`03a53d22 : 00000000`000000f4 00000000`00000003 fffffa80`08d219a0 fffffa80`08d21c80 : nt!KeBugCheckEx
    fffff880`095dee40 fffff800`03a0008b : ffffffff`ffffffff fffffa80`09420060 fffffa80`08d219a0 fffffa80`08d219a0 : nt!PspCatchCriticalBreak+0x92
    fffff880`095dee80 fffff800`03980144 : ffffffff`ffffffff 00000000`00000001 fffffa80`08d219a0 00000000`00000008 : nt! ?? ::NNGAKEGL::`string'+0x17486
    fffff880`095deed0 fffff800`036c4e93 : fffffa80`08d219a0 fffff800`c0000006 fffffa80`09420060 00000000`02940c00 : nt!NtTerminateProcess+0xf4
    fffff880`095def50 fffff800`036c1450 : fffff800`0371081f fffff880`095dfa38 fffff880`095df790 fffff880`095dfae0 : nt!KiSystemServiceCopyEnd+0x13
    fffff880`095df0e8 fffff800`0371081f : fffff880`095dfa38 fffff880`095df790 fffff880`095dfae0 00000000`02941910 : nt!KiServiceLinkage
    fffff880`095df0f0 fffff800`036c5282 : fffff880`095dfa38 00000000`00013600 fffff880`095dfae0 00000000`029413e8 : nt! ?? ::FNODOBFM::`string'+0x488e4
    fffff880`095df900 fffff800`036c3dfa : 00000000`00000000 000007fe`fd56d8c0 00000000`77888d01 00000000`00013600 : nt!KiExceptionDispatch+0xc2
    fffff880`095dfae0 00000000`77789c12 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x23a
    00000000`02941330 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77789c12
    Code:
    6: kd> !error fffff800`c0000006
    Error code: (NTSTATUS) 0xc0000006 (3221225478) - The instruction at 0x%p referenced memory at 0x%p. The required data was not placed into memory because of an I/O error status of 0x%x.

    Run Memtest86+ for least 7-8 passes, and preferably overnight as it can take a while to fully complete.

    Test each RAM stick individually, if an error is found then move the same RAM stick into the next DIMM slot and test again, if errors are found for the same RAM stick in every available slot then you have a faulty RAM module. On the other hand, if no errors are found in the next slot or the other slots for the same RAM module, then you have a faulty DIMM slot.

    Test each RAM stick and every motherboard DIMM slot available.

    Arc said:
    No code has to be inserted here. It is a RAM, a bad RAM.

    But if you have got a result like that:
    No code has to be inserted here. It is a motherboard issue. The particular slot is bad.
      My Computer

  5.    #5

    Could you also post a screenshot of Task Manager Performance tab?

    Screenshots and Files - Upload and Post in Seven Forums
      My Computer


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

    Well I was running a lot of programs and I left the computer to run them overnight, but the cpu usage wasn't showing but 3-17% cpu usage with all the programs running.
      My Computer

  7.    #7

    The process has already gone beyond it's maximum working set, which it is technically allowed to do, if there is enough free memory available to use. From your system, there is only seems to be around 35MB of physical memory, therefore the page fault may not have been able to occur because of this. Although, the Working Set Manager should have begun some working set trimming to free some memory.

    This is just a assumption I've got, I could be wrong, does this bugcheck occur in certain memory consuming situations?

    Make sure to run the MemTest86+.
      My Computer


  8. Posts : 12
    Windows 7 Ultimate x64
    Thread Starter
       #8

    I ran the full memtest off a burnt CD, it got to pass 7 with no errors. Any ideas?

    Malkirion

    Edit: It does seem to be during memory consuming times. It doesn't usually do it though until I've gone to sleep. The crashes usually happen during the night when I wake up to a black error page (the computer won't automatically boot back up, I usually have to turn it off when it comes to that error page and then turn off and turn back on the computer). I've started to have programs that I needed to run 24/7, so I've been letting the comp run overnight with them. This crash issue has been going on before I started doing that. Though, this could possibly be an unrelated crash to the ones I was having before... What would you recommend to prevent it from crashing in high memory consuming situations? More RAM? Or are there settings I can adjust to prevent it from crashing?
      My Computer

  9.    #9

    What does it say on the black error page? Programs running constantly can lead to memory leaks.

    Run Driver Verifier to scan for any corrupted drivers which may be causing problems, this program works by running various stress tests on drivers, in order to produce a BSOD which will locate the driver; run for least 24 hours:

       Information
      My Computer


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

    I encountered two crashes with the verifier. The first was caused by my peerblock program so I disabled it at startup to see if there were any other problems and I got "HIDCLASS.sys FFFF8800448710 base at FFFFF88004446000, Date Stamp 4ce7a665." I included a new SF rar with the new crash dumps in it. Hopefully this helps out, if not, I can try the verifier again to see if anything else comes up.


    Thank you,
    Malkirion
      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 00:03.
Find Us