BSOD help

Page 2 of 3 FirstFirst 123 LastLast

  1. Posts : 1,360
    win7 ultimate / virtual box
       #11

    It does look like hardware, but I believe it could still be software *humour me

    debugger shows
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck 1000007E, {ffffffffc0000005, fffff880010787d9, fffff880035856d8, fffff88003584f40}

    Probably caused by : hardware ( tdx!IN6_IS_ADDR_LINKLOCAL+29 )

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

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

    SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
    This is a very common bugcheck. Usually the exception address pinpoints
    the driver/function that caused the problem. Always note this address
    as well as the link date of the driver/image that contains this address.
    Some common problems are exception code 0x80000003.
    This means a hard
    coded breakpoint or assertion was hit, but this system was booted
    /NODEBUG. This is not supposed to happen as developers should never have
    hardcoded breakpoints in retail code, but ...
    If this happens, make sure a debugger gets connected, and the
    system is booted /DEBUG. This will let us see why this breakpoint is
    happening.
    Arguments:
    Arg1: ffffffffc0000005, The exception code that was not handled
    Arg2: fffff880010787d9, The address that the exception occurred at
    Arg3: fffff880035856d8, Exception Record Address
    Arg4: fffff88003584f40, Context Record Address

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


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

    FAULTING_IP:
    tdx!IN6_IS_ADDR_LINKLOCAL+29
    fffff880`010787d9 105748 adc byte ptr [rdi+48h],dl

    EXCEPTION_RECORD: fffff880035856d8 -- (.exr 0xfffff880035856d8)
    ExceptionAddress: fffff880010787d9 (tdx!IN6_IS_ADDR_LINKLOCAL+0x0000000000000029)
    ExceptionCode: c0000005 (Access violation)
    ExceptionFlags: 00000000
    NumberParameters: 2
    Parameter[0]: 0000000000000001
    Parameter[1]: 00000000000000c4
    Attempt to write to address 00000000000000c4

    CONTEXT: fffff88003584f40 -- (.cxr 0xfffff88003584f40)
    rax=fffff88003585978 rbx=0000000000000096 rcx=fffffa80081c57e4
    rdx=0000000000000038 rsi=00000000000040a9 rdi=000000000000007c
    rip=fffff880010787d9 rsp=fffff88003585918 rbp=0000000000008d0f
    r8=0000000000000000 r9=fffff8800108a590 r10=000000000000008f
    r11=00000000000000b3 r12=fffffa80081c5790 r13=fffff88003585c38
    r14=fffffa80081c57c8 r15=0000000000000000
    iopl=0 nv up ei ng nz na po nc
    cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010286
    tdx!IN6_IS_ADDR_LINKLOCAL+0x29:
    fffff880`010787d9 105748 adc byte ptr [rdi+48h],dl ds:002b:00000000`000000c4=??
    Resetting default scope

    CUSTOMER_CRASH_COUNT: 1

    PROCESS_NAME: System

    CURRENT_IRQL: 0

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

    EXCEPTION_PARAMETER1: 0000000000000001

    EXCEPTION_PARAMETER2: 00000000000000c4

    WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff800034b70e0
    00000000000000c4

    FOLLOWUP_IP:
    tdx!IN6_IS_ADDR_LINKLOCAL+29
    fffff880`010787d9 105748 adc byte ptr [rdi+48h],dl

    BUGCHECK_STR: 0x7E

    DEFAULT_BUCKET_ID: NULL_CLASS_PTR_DEREFERENCE

    MISALIGNED_IP:
    tdx!IN6_IS_ADDR_LINKLOCAL+29
    fffff880`010787d9 105748 adc byte ptr [rdi+48h],dl

    LAST_CONTROL_TRANSFER: from fffff8800107a785 to fffff880010787d9

    STACK_TEXT:
    fffff880`03585918 fffff880`0107a785 : 00000000`00000008 fffff880`03585c38 00000000`00000000 00000000`00000138 : tdx!IN6_IS_ADDR_LINKLOCAL+0x29
    fffff880`03585920 fffff880`0107cfac : 00000000`000007d9 00000000`00000003 fffff880`0108a590 00000000`2baed106 : tdx!StringCbPrintfW+0x35
    fffff880`03585960 fffff880`01080511 : fffffa80`07dcf170 00060000`06000000 00000000`00000000 00000000`00000000 : tdx!TdxCreateAndRegisterDeviceObject+0x31c
    fffff880`03585b50 fffff880`01077965 : fffffa80`077cdcd0 00060000`06000000 00000000`00000000 fffff880`0108c578 : tdx!TdxProcessInterfaceChangeRoutine+0x401
    fffff880`03585c30 fffff800`0357c841 : fffffa80`074f7b80 fffffa80`07137840 fffffa80`07137840 fffffa80`05529680 : tdx!NetiopIoWorkItemRoutine+0x35
    fffff880`03585c80 fffff800`0328c861 : fffff800`03424500 fffff800`0357c804 fffffa80`05529680 00000000`00000000 : nt!IopProcessWorkItem+0x3d
    fffff880`03585cb0 fffff800`03524a86 : 41149734`a1d38776 fffffa80`05529680 00000000`00000080 fffffa80`0550e040 : nt!ExpWorkerThread+0x111
    fffff880`03585d40 fffff800`0325db06 : fffff880`0336a180 fffffa80`05529680 fffff880`033750c0 2ca1acc5`7694d6f4 : nt!PspSystemThreadStartup+0x5a
    fffff880`03585d80 00000000`00000000 : fffff880`03586000 fffff880`03580000 fffff880`035859f0 00000000`00000000 : nt!KxStartSystemThread+0x16


    SYMBOL_STACK_INDEX: 0

    SYMBOL_NAME: tdx!IN6_IS_ADDR_LINKLOCAL+29

    FOLLOWUP_NAME: MachineOwner

    DEBUG_FLR_IMAGE_TIMESTAMP: 0

    STACK_COMMAND: .cxr 0xfffff88003584f40 ; kb

    MODULE_NAME: hardware

    IMAGE_NAME: hardware

    FAILURE_BUCKET_ID: X64_IP_MISALIGNED_tdx.sys

    BUCKET_ID: X64_IP_MISALIGNED_tdx.sys

    Followup: MachineOwner
    ---------
    I suspect that whatever is trying to access tdx.sys is what's causing the crash , which suggests this could be your antivirus or network driver possibly ?


    this driver for your network card from Realtek is not the latest version ?
    Rt64win7.sys fffff880`0476e000 fffff880`047a7000 0x00039000 0x4a16bc2e 22/05/2009 15:52:30
    also what antivirus and or third party firewall are you using ?
    Last edited by ickymay; 23 May 2010 at 02:43.
      My Computer


  2. Posts : 11
    Windows 7 x64
    Thread Starter
       #12

    I updated the Retek driver. the Antivirus I using is Microsoft Security Essentials. also ran a check disk and from what I saw there were no errors. here are som of the latest dumps.

    Thanks for the help.
      My Computer


  3. Posts : 1,360
    win7 ultimate / virtual box
       #13

    mcm007 said:
    I updated the Retek driver. the Antivirus I using is Microsoft Security Essentials. also ran a check disk and from what I saw there were no errors. here are som of the latest dumps.

    Thanks for the help.
    whats the exact spec on your memory ?

    cpuz is a great tool for this ?
      My Computer


  4. Posts : 11
    Windows 7 x64
    Thread Starter
       #14

    Here are the specs on the Memory.

    Type: DDR3
    Size: 6144 MB
    Channels Dual
    NB Freq: 2496.0 MHZ

    DRAM Freq: 693.4
    FSB DRAm: 2.10
    CAS# Latency: 9
    RAS# to Cas# Delay 9
    Cycle Time 24
    Row Refresh Cycle Time 74
    Command Rate 1T
      My Computer


  5. Posts : 1,360
    win7 ultimate / virtual box
       #15

    mcm007 said:
    Here are the specs on the Memory.

    Type: DDR3
    Size: 6144 MB
    Channels Dual
    NB Freq: 2496.0 MHZ

    DRAM Freq: 693.4
    FSB DRAm: 2.10
    CAS# Latency: 9
    RAS# to Cas# Delay 9
    Cycle Time 24
    Row Refresh Cycle Time 74
    Command Rate 1T
    can you post model number , found on spd tab of cpuz ?
      My Computer


  6. Posts : 11
    Windows 7 x64
    Thread Starter
       #16

    model number is F3-12800cl9-2gbnq

    the max bandwidth is PC3-10700 (667 mhz)

    Manufacturer is G.Skill

    let me know if you need more info.

    MCM
      My Computer


  7. Posts : 1,360
    win7 ultimate / virtual box
       #17

    mcm007 said:
    model number is F3-12800cl9-2gbnq

    the max bandwidth is PC3-10700 (667 mhz)

    Manufacturer is G.Skill

    let me know if you need more info.

    MCM
    thnx for that and I downloaded the pdf QVL for compatible ram listed by your motherboard manufacturers > Attachment 76084 and if you take a look your RAM is listed >
    G.SKILL F3-12800CL9D-2GBNQ 2048MB(Kit of 2) SS N/A Heat-Sink Package (1333-9-9-9-24) 1.6v
    found (middle of the list) ?

    Can you now check to see you are running at the right voltage ?

    your timings match so if it isn't voltage you may have a bad stick ?

    if voltages match maybe run your system with only one stick and try to force a bluescreen ?

    have you tried taking your CPU out and making sure there are no bent pins or paste on the pins or in the slot ?

    I notice no more .dmp files posted for four days , does that mean you have not had anymore crashes ?
      My Computer


  8. Posts : 11
    Windows 7 x64
    Thread Starter
       #18

    I wish I was not geting any more BSOD, infact is happens every single time I start up. here is the latest one from the 27th and I could not find a minidump of the one from today (june 1st).

    how do I know what the voltage it should be?

    I get nervous about pulling the CPU out and checking it. it's one pretty secure. what is the likleyhood that could be the problem?

    from the CPU-Z application it looks like the memory is running at 1.5v. does that sound right?
      My Computer


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

    mcm007 said:
    I wish I was not geting any more BSOD, infact is happens every single time I start up. here is the latest one from the 27th and I could not find a minidump of the one from today (june 1st).

    how do I know what the voltage it should be?

    I get nervous about pulling the CPU out and checking it. it's one pretty secure. what is the likleyhood that could be the problem?

    from the CPU-Z application it looks like the memory is running at 1.5v. does that sound right?

    This one was caused by memory corruption. to test you memory download memtestx86, burn it to cd, and run for at least 5 passes.

    let us know if you need help

    Ken

    Code:
    Debug session time: Thu May 27 23:04:02.744 2010 (GMT-4)
    System Uptime: 0 days 0:00:14.774
    BugCheck 7F, {7, 80050031, 6f8, fffff88006811655}
    *** WARNING: Unable to verify timestamp for win32k.sys
    *** ERROR: Module load completed but symbols could not be loaded for win32k.sys
    Probably caused by : memory_corruption
    BUGCHECK_STR:  0x7f_7
    PROCESS_NAME:  System
      My Computer


  10. Posts : 1,360
    win7 ultimate / virtual box
       #20

    mcm007 said:
    I wish I was not geting any more BSOD, infact is happens every single time I start up. here is the latest one from the 27th and I could not find a minidump of the one from today (june 1st).

    how do I know what the voltage it should be?

    I get nervous about pulling the CPU out and checking it. it's one pretty secure. what is the likleyhood that could be the problem?

    from the CPU-Z application it looks like the memory is running at 1.5v. does that sound right?
    on the pdf in my post it states it needs 1.6v so this could be causing instability if your running under voltage , this voltage is set by the bios and may or may not be adjustable ?

    is your bios fully up to date ?
      My Computer


 
Page 2 of 3 FirstFirst 123 LastLast

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 10:49.
Find Us