BSOD Physical Memory Dump


  1. Posts : 2
    Windows 7 Home Premium x64
       #1

    BSOD Physical Memory Dump


    Hello, I've recently started experiencing BSOD talking about memory dumping. It first happened a few days ago when I clicked on a java application and it crashed. It took forever to start up again, and I was having some problems with my internet disconnecting, so I reformatted hoping that would fix it. It was fine up until now, where it BSOD again.

    I custom built my computer in December of this year. I'm running Win 7 Home Prem x64 bit and my specs are:

    Mobo: GIGABYTE GA-880GA-UD3H
    CPU: AMD Athlon II X4 640 Propus 3.0GHz
    Vid Card: EVGA GeForce GTX 460
    RAM: G.SKILL Ripjaws Series 4GB (2 x 2GB) 240-Pin DDR3 SDRAM DDR3 1600
    (Recently bought 2 more 2GB of the same RAM to reach 8GB)
    Last edited by Torgen; 06 Jun 2011 at 02:04.
      My Computer


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

    Torgen said:
    Hello, I've recently started experiencing BSOD talking about memory dumping. It first happened a few days ago when I clicked on a java application and it crashed. It took forever to start up again, and I was having some problems with my internet disconnecting, so I reformatted hoping that would fix it. It was fine up until now, where it BSOD again.

    I custom built my computer in December of this year. I'm running Win 7 Home Prem x64 bit and my specs are:

    Mobo: GIGABYTE GA-880GA-UD3H
    CPU: AMD Athlon II X4 640 Propus 3.0GHz
    Vid Card: EVGA GeForce GTX 460
    RAM: G.SKILL Ripjaws Series 4GB (2 x 2GB) 240-Pin DDR3 SDRAM DDR3 1600
    (Recently bought 2 more 2GB of the same RAM to reach 8GB)
    No DMP included in upload. Try this method




    To enable us to assist you with your computer's BSOD symptoms, upload the contents of your "\Windows\Minidump" folder.

    The procedure:

    * Copy the contents of \Windows\Minidump to another (temporary) location somewhere on your machine.
    * Zip up the copy.
    * Attach the ZIP archive to your post using the "paperclip" (file attachments) button.



    To ensure minidumps are enabled:

    Go to Start, in the Search Box type: sysdm.cpl, press Enter.
    Under the Advanced tab, click on the Startup and Recovery Settings... button.
    Ensure that Automatically restart is unchecked.
    Under the Write Debugging Information header select Small memory dump (256 kB) in the dropdown box (the 256kb varies).
    Ensure that the Small Dump Directory is listed as %systemroot%\Minidump.
    OK your way out.
    Reboot if changes have been made.
      My Computer


  3. Posts : 2
    Windows 7 Home Premium x64
    Thread Starter
       #3

    zigzag3143 said:
    Torgen said:
    Hello, I've recently started experiencing BSOD talking about memory dumping. It first happened a few days ago when I clicked on a java application and it crashed. It took forever to start up again, and I was having some problems with my internet disconnecting, so I reformatted hoping that would fix it. It was fine up until now, where it BSOD again.

    I custom built my computer in December of this year. I'm running Win 7 Home Prem x64 bit and my specs are:

    Mobo: GIGABYTE GA-880GA-UD3H
    CPU: AMD Athlon II X4 640 Propus 3.0GHz
    Vid Card: EVGA GeForce GTX 460
    RAM: G.SKILL Ripjaws Series 4GB (2 x 2GB) 240-Pin DDR3 SDRAM DDR3 1600
    (Recently bought 2 more 2GB of the same RAM to reach 8GB)
    No DMP included in upload. Try this method




    To enable us to assist you with your computer's BSOD symptoms, upload the contents of your "\Windows\Minidump" folder.

    The procedure:

    * Copy the contents of \Windows\Minidump to another (temporary) location somewhere on your machine.
    * Zip up the copy.
    * Attach the ZIP archive to your post using the "paperclip" (file attachments) button.
    Sorry, I added it now
      My Computer


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

    Blamed on tcpip. That usually is related to firewall or AV app. I would remove avg replace with microsoft security essentials.

    AVG - PC TuneUp 2011 | Registry Cleaner, File Recovery, Internet Accelerator
    or
    AVG Removal Tool


    Virus, Spyware & Malware Protection | Microsoft Security Essentials


    I would also run driver verifier to find the offending driver.

    I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).

    In Windows 7 you can make a Startup Repair disk by going to Start....All Programs...Maintenance...Create a System Repair Disc - with Windows Vista you'll have to use your installation disk or the "Repair your computer" option at the top of the Safe Mode menu .

    Then, here's the procedure:
    - Go to Start and type in "verifier" (without the quotes) and press Enter
    - Select "Create custom settings (for code developers)" and click "Next"
    - Select "Select individual settings from a full list" and click "Next"
    - Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
    - Select "Select driver names from a list" and click "Next"
    Then select all drivers NOT provided by Microsoft and click "Next"
    - Select "Finish" on the next page.

    Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).

    If you can't get into Windows because it crashes too soon, try it in Safe Mode.
    If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.
    Code:
    Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
    Copyright (c) Microsoft Corporation. All rights reserved.
    
    
    Loading Dump File [C:\Users\K\Desktop\060611-41215-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    
    Symbol search path is: SRV*C:\Symbols*http://msdl.microsoft.com/download/symbols;srv*e:\symbols
    *http://msdl.microsoft.com/download/symbols
    Executable search path is: 
    Windows 7 Kernel Version 7600 MP (4 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS Personal
    Built by: 7600.16792.amd64fre.win7_gdr.110408-1633
    Machine Name:
    Kernel base = 0xfffff800`02e0f000 PsLoadedModuleList = 0xfffff800`0304ce50
    Debug session time: Mon Jun  6 01:30:21.017 2011 (GMT-4)
    System Uptime: 0 days 2:58:57.827
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ............................
    Loading User Symbols
    Loading unloaded module list
    ....
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 4E, {7, 22e0f2, 1, 0}
    
    Probably caused by : tcpip.sys ( tcpip!TcpTcbReceive+4f4 )
    
    Followup: MachineOwner
    ---------
    
    2: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    PFN_LIST_CORRUPT (4e)
    Typically caused by drivers passing bad memory descriptor lists (ie: calling
    MmUnlockPages twice with the same list, etc).  If a kernel debugger is
    available get the stack trace.
    Arguments:
    Arg1: 0000000000000007, A driver has unlocked a page more times than it locked it
    Arg2: 000000000022e0f2, page frame number
    Arg3: 0000000000000001, current share count
    Arg4: 0000000000000000, 0
    
    Debugging Details:
    ------------------
    
    
    BUGCHECK_STR:  0x4E_7
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    
    PROCESS_NAME:  System
    
    CURRENT_IRQL:  2
    
    LAST_CONTROL_TRANSFER:  from fffff80002edffe9 to fffff80002e7f700
    
    STACK_TEXT:  
    fffff880`08a227d8 fffff800`02edffe9 : 00000000`0000004e 00000000`00000007 00000000`0022e0f2 00000000`00000001 : nt!KeBugCheckEx
    fffff880`08a227e0 fffff800`02ef3f6e : 00000000`000007ff 00000000`000000f0 00000012`0afb0818 fffffa80`086cde20 : nt! ?? ::FNODOBFM::`string'+0x16d56
    fffff880`08a22820 fffff800`02e81ae8 : fffffa80`12870004 00000000`00000000 00000000`00000002 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x34879
    fffff880`08a228b0 fffff880`01677194 : fffffa80`0b598ce0 fffffa80`079c4f02 00000000`00000000 00000000`00000000 : nt!IopfCompleteRequest+0x168
    fffff880`08a22990 fffff880`0167b86a : fffffa80`079c4f00 fffffa80`06b5d000 fffffa80`07869801 fffffa80`079c5270 : tcpip!TcpTcbReceive+0x4f4
    fffff880`08a22b40 fffff880`0167b4df : fffff880`0487d522 fffffa80`079c5270 fffffa80`079c5270 fffff880`0165e600 : tcpip!TcpMatchReceive+0x1fa
    fffff880`08a22c90 fffff880`0165d6c7 : fffffa80`079c59c0 fffffa80`079c9e30 fffffa80`079c5000 00000000`00000008 : tcpip!TcpPreValidatedReceive+0x29f
    fffff880`08a22d40 fffff880`0165d799 : fffff880`08a22ec0 fffff880`0176b9a0 fffff880`08a22ed0 00000000`00000001 : tcpip!IppDeliverListToProtocol+0x97
    fffff880`08a22e00 fffff880`0165dc90 : fffffa80`079c5000 00000000`00000000 00000000`00000000 fffff880`08a22ec0 : tcpip!IppProcessDeliverList+0x59
    fffff880`08a22e70 fffff880`0165cb21 : 00000000`00000000 fffffa80`079c59c0 fffff880`0176b9a0 00000000`08bae001 : tcpip!IppReceiveHeaderBatch+0x231
    fffff880`08a22f50 fffff880`0165b592 : fffffa80`08d7a8a0 00000000`00000000 fffffa80`08bae001 00000000`00000009 : tcpip!IpFlcReceivePackets+0x651
    fffff880`08a23150 fffff880`01674e5a : fffffa80`08bae010 fffff880`08a23280 fffffa80`08bae010 00000000`00000000 : tcpip!FlpReceiveNonPreValidatedNetBufferListChain+0x2b2
    fffff880`08a23230 fffff800`02e8ee5a : fffffa80`086cde20 fffff880`08a1e000 00000000`00004800 00000000`00000000 : tcpip!FlReceiveNetBufferListChainCalloutRoutine+0xda
    fffff880`08a23280 fffff880`01674882 : fffff880`01674d80 fffff880`08a23390 00000000`02020002 00000000`00100100 : nt!KeExpandKernelStackAndCalloutEx+0xda
    fffff880`08a23360 fffff880`015500eb : fffffa80`08bae8d0 00000000`00000000 fffffa80`081e51a0 00000000`00100100 : tcpip!FlReceiveNetBufferListChain+0xb2
    fffff880`08a233d0 fffff880`01519fc6 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ndis!ndisMIndicateNetBufferListsToOpen+0xdb
    fffff880`08a23440 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ndis!ndisMDispatchReceiveNetBufferLists+0x1d6
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    tcpip!TcpTcbReceive+4f4
    fffff880`01677194 488b4b48        mov     rcx,qword ptr [rbx+48h]
    
    SYMBOL_STACK_INDEX:  4
    
    SYMBOL_NAME:  tcpip!TcpTcbReceive+4f4
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: tcpip
    
    IMAGE_NAME:  tcpip.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4c15a458
    
    FAILURE_BUCKET_ID:  X64_0x4E_7_tcpip!TcpTcbReceive+4f4
    
    BUCKET_ID:  X64_0x4E_7_tcpip!TcpTcbReceive+4f4
    
    Followup: MachineOwner
    ---------
      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 23:59.
Find Us