BlueScreen.. WHY?


  1. Posts : 21
    Windows 7 Ultimate 64-bit
       #1

    BlueScreen.. WHY?


    Hello to everyone in this forum..

    I built a brand new system, with an intel core i7-860 processor, a MSI-GD65 motherboard and 8GB or RAM..

    Yesterday, all of a sudden (I just wanted to shut down), there were some lines on my screen instead, first vertical, then horizontal and so on, and my screen switched off..

    This thing happened again today. I was in the middle of a DVD encoding with ConvertXtoDVD, I suddenly realized it was stuck, and when I terminated the process, it happened again. When it rebooted, I copied the problem signature:

    Problem signature:
    Problem Event Name: BlueScreen
    OS Version: 6.1.7600.2.0.0.256.1
    Locale ID: 1032

    Additional information about the problem:
    BCCode: 3b
    BCP1: 00000000C0000046
    BCP2: FFFFF80002AF17F8
    BCP3: FFFFF880085B00C0
    BCP4: 0000000000000000
    OS Version: 6_1_7600
    Service Pack: 0_0
    Product: 256_1

    Files that help describe the problem:
    C:\Windows\Minidump\011510-16083-01.dmp
    C:\Users\GkScorpio\AppData\Local\Temp\WER-33368-0.sysdata.xml

    Read our privacy statement online:
    Windows 7 Privacy Highlights - Microsoft Windows

    If the online privacy statement is not available, please read our privacy

    statement offline:
    C:\Windows\system32\en-US\erofflps.txt


    I FEAR it may have something to do with my Graphics Card (Powercolor ATI Radeon HD5770). I've installed the Catalyst Drivers from the DVD..
      My Computer


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

    gkscorpio said:
    Hello to everyone in this forum..

    I built a brand new system, with an intel core i7-860 processor, a MSI-GD65 motherboard and 8GB or RAM..

    Yesterday, all of a sudden (I just wanted to shut down), there were some lines on my screen instead, first vertical, then horizontal and so on, and my screen switched off..

    This thing happened again today. I was in the middle of a DVD encoding with ConvertXtoDVD, I suddenly realized it was stuck, and when I terminated the process, it happened again. When it rebooted, I copied the problem signature:

    Problem signature:
    Problem Event Name: BlueScreen
    OS Version: 6.1.7600.2.0.0.256.1
    Locale ID: 1032

    Additional information about the problem:
    BCCode: 3b
    BCP1: 00000000C0000046
    BCP2: FFFFF80002AF17F8
    BCP3: FFFFF880085B00C0
    BCP4: 0000000000000000
    OS Version: 6_1_7600
    Service Pack: 0_0
    Product: 256_1

    Files that help describe the problem:
    C:\Windows\Minidump\011510-16083-01.dmp
    C:\Users\GkScorpio\AppData\Local\Temp\WER-33368-0.sysdata.xml

    Read our privacy statement online:
    Windows 7 Privacy Highlights - Microsoft Windows

    If the online privacy statement is not available, please read our privacy

    statement offline:
    C:\Windows\system32\en-US\erofflps.txt


    I FEAR it may have something to do with my Graphics Card (Powercolor ATI Radeon HD5770). I've installed the Catalyst Drivers from the DVD..

    Hi and welcome

    this one was probably caused by tcpip.sys. I would

    reinstall the networking driver
    run a system file check
    type cmd in search>right click and run as admin>sfc /scannow

    Good Luck

    Ken J+

    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\011410-36145-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    
    Symbol search path is: SRV*d:\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.16385.amd64fre.win7_rtm.090713-1255
    Machine Name:
    Kernel base = 0xfffff800`02c14000 PsLoadedModuleList = 0xfffff800`02e51e50
    Debug session time: Thu Jan 14 20:15:20.659 2010 (GMT-5)
    System Uptime: 0 days 0:46:35.547
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ...................
    Loading User Symbols
    Loading unloaded module list
    .....
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck D1, {20, 2, 0, fffff88001675a10}
    
    Probably caused by : tcpip.sys ( tcpip!TcpTcbSend+7c0 )
    
    Followup: MachineOwner
    ---------
    
    0: 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: 0000000000000020, memory referenced
    Arg2: 0000000000000002, IRQL
    Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
    Arg4: fffff88001675a10, address which referenced memory
    
    Debugging Details:
    ------------------
    
    
    READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002ebc0e0
     0000000000000020 
    
    CURRENT_IRQL:  2
    
    FAULTING_IP: 
    tcpip!TcpTcbSend+7c0
    fffff880`01675a10 8b5920          mov     ebx,dword ptr [rcx+20h]
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    
    BUGCHECK_STR:  0xD1
    
    PROCESS_NAME:  System
    
    TRAP_FRAME:  fffff88005c2f7f0 -- (.trap 0xfffff88005c2f7f0)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=000000000000002d rbx=0000000000000000 rcx=0000000000000000
    rdx=00000000fcf991ed rsi=0000000000000000 rdi=0000000000000000
    rip=fffff88001675a10 rsp=fffff88005c2f980 rbp=0000000000000000
     r8=0000000013600005  r9=fffffa8005072d88 r10=fffffa8005072d70
    r11=0000000000000014 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up ei pl nz na pe nc
    tcpip!TcpTcbSend+0x7c0:
    fffff880`01675a10 8b5920          mov     ebx,dword ptr [rcx+20h] ds:f9a8:00000000`00000020=????????
    Resetting default scope
    
    LAST_CONTROL_TRANSFER:  from fffff80002c85469 to fffff80002c85f00
    
    STACK_TEXT:  
    fffff880`05c2f6a8 fffff800`02c85469 : 00000000`0000000a 00000000`00000020 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
    fffff880`05c2f6b0 fffff800`02c840e0 : 00000000`00000000 00000000`00000000 fffffa80`02833a90 fffffa80`1b22202b : nt!KiBugCheckDispatch+0x69
    fffff880`05c2f7f0 fffff880`01675a10 : 00000000`00000200 ffff0000`04b4a84c 00000016`02998380 00000000`00000000 : nt!KiPageFault+0x260
    fffff880`05c2f980 fffff880`016712b6 : 00000000`00000000 fffffa80`02998380 fffff880`01765128 fffff880`0163f9f6 : tcpip!TcpTcbSend+0x7c0
    fffff880`05c2fc00 fffff880`01678cac : fffffa80`03a98a00 00000000`00000000 00000000`00000000 fffff880`0165c300 : tcpip!TcpFlushDelay+0x316
    fffff880`05c2fce0 fffff880`0165b3c7 : fffffa80`02984707 fffffa80`02859bc0 fffffa80`02984707 00000000`00000000 : tcpip!TcpPreValidatedReceive+0x20c
    fffff880`05c2fd90 fffff880`0165b499 : fffff880`05c2ff10 fffff880`0176b9a0 fffff880`05c2ff20 00000000`00000001 : tcpip!IppDeliverListToProtocol+0x97
    fffff880`05c2fe50 fffff880`0165b990 : fffffa80`03aea670 fffffa80`03aea700 00000000`00000011 fffff880`05c2ff10 : tcpip!IppProcessDeliverList+0x59
    fffff880`05c2fec0 fffff880`0165a821 : 00000000`00000000 fffffa80`02983000 fffff880`0176b9a0 00000000`03b06b01 : tcpip!IppReceiveHeaderBatch+0x231
    fffff880`05c2ffa0 fffff880`01659272 : fffffa80`03b07820 00000000`00000000 fffffa80`03b06b01 00000000`00000001 : tcpip!IpFlcReceivePackets+0x651
    fffff880`05c301a0 fffff880`016726ba : fffffa80`03b06bb0 fffff880`05c302d0 fffffa80`03b06bb0 fffff880`0f170000 : tcpip!FlpReceiveNonPreValidatedNetBufferListChain+0x2b2
    fffff880`05c30280 fffff800`02c9564a : fffffa80`03aea330 fffff880`05c2b000 00000000`00004800 00000000`00000000 : tcpip!FlReceiveNetBufferListChainCalloutRoutine+0xda
    fffff880`05c302d0 fffff880`016720e2 : fffff880`016725e0 fffff880`05c303e0 00000000`0023c302 fffff880`0f1c19d7 : nt!KeExpandKernelStackAndCalloutEx+0xda
    fffff880`05c303b0 fffff880`015470eb : fffffa80`03b07010 00000000`00000000 fffffa80`034e41a0 fffffa80`0439b000 : tcpip!FlReceiveNetBufferListChain+0xb2
    fffff880`05c30420 fffff880`01510fc6 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ndis!ndisMIndicateNetBufferListsToOpen+0xdb
    fffff880`05c30490 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ndis!ndisMDispatchReceiveNetBufferLists+0x1d6
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    tcpip!TcpTcbSend+7c0
    fffff880`01675a10 8b5920          mov     ebx,dword ptr [rcx+20h]
    
    SYMBOL_STACK_INDEX:  3
    
    SYMBOL_NAME:  tcpip!TcpTcbSend+7c0
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: tcpip
    
    IMAGE_NAME:  tcpip.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc26e
    
    FAILURE_BUCKET_ID:  X64_0xD1_tcpip!TcpTcbSend+7c0
    
    BUCKET_ID:  X64_0xD1_tcpip!TcpTcbSend+7c0
    
    Followup: MachineOwner
    ---------
      My Computer


  3. Posts : 21
    Windows 7 Ultimate 64-bit
    Thread Starter
       #3

    That was actually a relief.. First because my motherboard has 2 onboard lan cards so I could use the other one, second because I can think of a possible reason for this mess.. I tried to install a proxy software, which tried to install a virtual network interface. Maybe this is that caused this..

    The system scan came out clean..
      My Computer


  4. Posts : 21
    Windows 7 Ultimate 64-bit
    Thread Starter
       #4

    By the way, I uploaded the dump file from yesterday's crush too. Could you tell me if this was also caused by my network card?
      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 21:22.
Find Us