BSOD minidump comments

Discussion in 'Windows Vista Help and Support' started by hgy, Nov 20, 2011.

  1. hgy

    hgy New Member

    Joined:
    Nov 20, 2011
    Messages:
    6
    Likes Received:
    0
    Hello have a computer 4 cpu Q6600 core
    GA p35 s3g mainboard
    4GB RAM
    ATI4850 series advanced graphic card 512MB
    OP system is: Windows Business 64bit with service pack 2

    I am having very frequent BSOD while playing games and alsor ecently watching movies!!
    i pasted one of the recent minidump file here below.

    Can someone tell me how can i realise the reason of that BSOD from this minidump?
    what are your suggestions?
    i was watching movie while downloading files in the instance of BSOD.... is the virtual and physical memory went too low because of downloads? or what happened?

    thanks in advance




    * Bugcheck Analysis *
    * *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck D1, {0, 2, 1, fffffa6000c09318}

    Unable to load image \SystemRoot\system32\DRIVERS\Rtlh64.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for Rtlh64.sys
    Probably caused by : pacer.sys ( pacer!PcFilterSendNetBufferListsComplete+f4 )

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

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

    DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
    An attempt was made to access a pageable (or completely invalid) address at an
    interrupt request level (IRQL) that is too high. This is usually
    caused by drivers using improper addresses.
    If kernel debugger is available get stack backtrace.
    Arguments:
    Arg1: 0000000000000000, memory referenced
    Arg2: 0000000000000002, IRQL
    Arg3: 0000000000000001, value 0 = read operation, 1 = write operation
    Arg4: fffffa6000c09318, address which referenced memory

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


    WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80001e27080
    0000000000000000

    CURRENT_IRQL: 2

    FAULTING_IP:
    ndis!NdisFSendNetBufferListsComplete+148
    fffffa60`00c09318 498917 mov qword ptr [r15],rdx

    CUSTOMER_CRASH_COUNT: 3

    DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

    BUGCHECK_STR: 0xD1

    PROCESS_NAME: System

    TRAP_FRAME: fffffa600171acd0 -- (.trap 0xfffffa600171acd0)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=0000000000000000 rbx=0000000000000000 rcx=fffffa6000d680e0
    rdx=fffffa8004ae5030 rsi=0000000000000000 rdi=0000000000000000
    rip=fffffa6000c09318 rsp=fffffa600171ae60 rbp=0000000000000000
    r8=0000000000000001 r9=fffffa80045ff780 r10=0000000000000272
    r11=fffffa600171aec8 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0 nv up ei pl zr na po nc
    ndis!NdisFSendNetBufferListsComplete+0x148:
    fffffa60`00c09318 498917 mov qword ptr [r15],rdx ds:1200:00000000`00000000=????????????????
    Resetting default scope

    LAST_CONTROL_TRANSFER: from fffff80001c5a1ee to fffff80001c5a450

    STACK_TEXT:
    fffffa60`0171ab88 fffff800`01c5a1ee : 00000000`0000000a 00000000`00000000 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
    fffffa60`0171ab90 fffff800`01c590cb : 00000000`00000001 fffffa80`04601200 fffffa80`04a9fe70 fffffa80`069e4300 : nt!KiBugCheckDispatch+0x6e
    fffffa60`0171acd0 fffffa60`00c09318 : fffffa80`04a9feb0 fffff800`0211c5df fffffa80`06539940 00000000`00000074 : nt!KiPageFault+0x20b
    fffffa60`0171ae60 fffffa60`05b968f0 : 00000000`00000000 fffffa80`063d31a0 fffffa80`069c2400 fffffa80`04a9feb0 : ndis!NdisFSendNetBufferListsComplete+0x148
    fffffa60`0171aed0 fffffa60`00dab24c : fffffa80`063d31a0 fffffa60`00c5f110 00000000`00000001 fffffa80`06468320 : pacer!PcFilterSendNetBufferListsComplete+0xf4
    fffffa60`0171af40 fffffa60`024b89d7 : 00000000`00000000 fffffa80`045ff780 00000000`00000000 fffffa80`045ff780 : ndis!NdisMSendNetBufferListsComplete+0x7c
    fffffa60`0171af80 fffffa60`024b4618 : 00000007`00000000 00000010`00000000 fffffa80`00000000 00000000`00000014 : Rtlh64!MiniportSendNetBufferList+0x247
    fffffa60`0171b000 fffffa60`024b4425 : 00000000`00000000 00000000`00000006 fffffa80`00000014 fffffa80`00000000 : Rtlh64!MPSendNetBufferListsNPQ+0x1e8
    fffffa60`0171b070 fffffa60`00c09122 : 00000000`000009d7 fffffa80`00000001 00000000`00000001 fffffa80`00000000 : Rtlh64!MPSendNetBufferLists+0x25
    fffffa60`0171b0a0 fffffa60`05b96ea7 : 00000000`00000000 00000000`00000000 fffffa60`00c5f110 fffffa80`063d31a0 : ndis!NdisFSendNetBufferLists+0xe2
    fffffa60`0171b0f0 fffffa60`00c091ae : 00000000`00000000 fffffa80`04a9fca0 00000000`00000000 00000000`00000000 : pacer!PcFilterSendNetBufferLists+0x3b3
    fffffa60`0171b1f0 fffffa60`00dab189 : ffff0000`0185bf09 fffffa80`063d31a0 00000000`00000000 00000000`00000000 : ndis!ndisSendNBLToFilter+0x3e
    fffffa60`0171b230 fffffa60`00e7a7c4 : fffffa80`069cf4e0 00000000`0000000e fffffa60`0171b300 fffffa80`065a58f0 : ndis!NdisSendNetBufferLists+0x69
    fffffa60`0171b280 fffffa60`00e7def8 : 00000000`00000000 00000000`00000800 00000000`00000001 fffffa60`00e70d25 : tcpip!IppDispatchSendPacketHelper+0x414
    fffffa60`0171b380 fffffa60`00e7d35a : fffffa60`00000000 fffffa60`00000006 fffffa80`00000014 fffffa80`00000000 : tcpip!IppPacketizeDatagrams+0x2e8
    fffffa60`0171b4b0 fffffa60`00e64e8e : fffffa80`070e6170 00000000`75078206 00000000`00000001 fffffa80`044113b0 : tcpip!IppSendDatagramsCommon+0x77b
    fffffa60`0171b8d0 fffffa60`00e75090 : fffffa80`047f0000 fffff800`01c49eed fffffa80`04ac21f0 fffffa60`00c08a12 : tcpip!IpNlpSendDatagrams+0x3e
    fffffa60`0171b910 fffffa60`00e85bdc : fffffa80`0460121c 00000000`00000002 00000000`00000002 00000000`00000000 : tcpip!TcpTcbSend+0x5c0
    fffffa60`0171bad0 fffffa60`00e84e8a : fffffa80`04850100 00000000`0000000d 00000000`00000440 fffffa60`026fa9a5 : tcpip!TcpFlushDelay+0x2ac
    fffffa60`0171bb90 fffff800`01c5e667 : 00000000`01cca77f 00000000`00000001 fffffa80`047f3880 00000000`00000000 : tcpip!TcpPeriodicTimeoutHandler+0x6ca
    fffffa60`0171bd10 fffff800`01c5e8e2 : fffffa60`00e847c0 fffffa60`005ec180 00000000`00000000 fffffa60`005f5d40 : nt!KiRetireDpcList+0x117
    fffffa60`0171bd80 fffff800`01e2b860 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x62
    fffffa60`0171bdb0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!zzz_AsmCodeRange_End+0x4


    STACK_COMMAND: kb

    FOLLOWUP_IP:
    pacer!PcFilterSendNetBufferListsComplete+f4
    fffffa60`05b968f0 4c8d5c2450 lea r11,[rsp+50h]

    SYMBOL_STACK_INDEX: 4

    SYMBOL_NAME: pacer!PcFilterSendNetBufferListsComplete+f4

    FOLLOWUP_NAME: MachineOwner

    MODULE_NAME: pacer

    IMAGE_NAME: pacer.sys

    DEBUG_FLR_IMAGE_TIMESTAMP: 49e02de0

    FAILURE_BUCKET_ID: X64_0xD1_pacer!PcFilterSendNetBufferListsComplete+f4

    BUCKET_ID: X64_0xD1_pacer!PcFilterSendNetBufferListsComplete+f4

    Followup: MachineOwner
    ---------
     
    #1 hgy, Nov 20, 2011
    Last edited: Nov 20, 2011
  2. Trouble

    Trouble Noob Whisperer

    Joined:
    Nov 30, 2009
    Messages:
    13,845
    Likes Received:
    833
    Hello and welcome to the forums.
    Please read the first post in this sticky thread here How to ask for help with a BSOD problem
    Do your best to accumulate the data required.
    Run the SF Diagnostic tool (download and right click the executable and choose run as administrator)
    Download and run CPUz. Use the Windows snipping tool to gather images from all tabs including all slots populated with memory under the SPD tab.
    Likewise RAMMon. Export the html report, put everything into a desktop folder that you've created for this purpose, zip it up and attach it to your next post (right click it and choose send to, compressed (zipped) folder.
    It looks like from what you've posted thus far that you have a problem with a Realtek Network Adapater driver (rtlh64.sys) if you can determine that actual Model Name / Number of the card installed you may want to try using this link Realtek to see if there is a driver update available for you adapter.
    Good luck
    Randy
     
    1 person likes this.
  3. hgy

    hgy New Member

    Joined:
    Nov 20, 2011
    Messages:
    6
    Likes Received:
    0
    Hello,
    I am using the latest drivers of realtek.... my computer was not able recognize microphone from the front jack of computer so that is why i needed to install realtek drivers extra...normally i was using standart installed drivers from vista installation. I am not sure where exactely began BSODs but clearly after that sound driver updates.

    I made screenshots and all necessary files as you requested and i am attaching them to the thread.
    I added all minidumps files i got since 4-5 days. Many of them appeared while playing a game, i changed(lowered) graphic options everyday but it still did that BSOD, once it happened while watching a movie and downloading, once it did while using firefox.
    a last detail i remembered: I somewhat cleaned the dust in the computer lately, removed RAMS, graphic card cleaned them and reinstalled....i also blowed aid in the case and also in the powersupply and took the dust comes out with a vacuum cleaner, this was not the 1st time i did this....i used plastic gloves to prevent electrical damages to RAMs and others, i also removed and turned the main electrical shalter of the case off before i did these.

    i hope this help understanding the problems. Since 2008 i am using this computer with this same vista installation(of course i did some updates) and it never made any problems so far.
     

    Attached Files:

    #3 hgy, Nov 23, 2011
    Last edited: Nov 23, 2011
  4. Trouble

    Trouble Noob Whisperer

    Joined:
    Nov 30, 2009
    Messages:
    13,845
    Likes Received:
    833
    Yes it did help some and nice job on the CPUz image, your memory seems to be set properly so we can at least eliminate that for now..
    Unfortunately we're still looking at
    Rtlh64.sys 9/26/2006
    That is a realtek network adapter driver file and is not even close to the latest. Try this link here to update it Realtek
    If you don't have or no longer use that adapter then it is possible to clean / remove or rename that driver to prevent it from loading and then we can explicitly remove it from any further diagnostic steps. Just do a search for it (probably in C:\Windows\System32\Drivers folder) and rename the extension (Rtlh64.sys to Rtlh64.OLD) easily reversed if problems arise.
     
  5. hgy

    hgy New Member

    Joined:
    Nov 20, 2011
    Messages:
    6
    Likes Received:
    0
    Hello,
    thanks for directions..i am updating the driver of network adapter, i will use the computer a few more days with this new drivers and i will tell you about the results.

    thanks again, lets look what will happen ;)
     
  6. Trouble

    Trouble Noob Whisperer

    Joined:
    Nov 30, 2009
    Messages:
    13,845
    Likes Received:
    833
    Thanks and keep us posted. Any new BSODs please put them in a folder and zip it up and attach it to your next post.
    Regards
    Randy
     

Share This Page

Loading...