Windows 7 random BSOD's


  1. Posts : 5
    Windows 7
       #1

    Windows 7 random BSOD's


    Hi Guys,

    Hope someone can help, Running Windows 7 ultimate 64bit and seem to be getting the BSOD quite often, seem to always occur when I'm playing videos or browsing using Firefox. Attached is the last minidump file.

    Thanks for any help, if anymore info is needed please let me know. :)
      My Computer


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

    bezz01 said:
    Hi Guys,

    Hope someone can help, Running Windows 7 ultimate 64bit and seem to be getting the BSOD quite often, seem to always occur when I'm playing videos or browsing using Firefox. Attached is the last minidump file.

    Thanks for any help, if anymore info is needed please let me know. :)

    Hi and welcome
    this crash was probably caused by hardware. specifically your tcpip.sys I also noticed that the date on your BIOS is 2003 that will cause you no end of problems

    I would
    run a system file check type cmd in search>right click and run as admin>
    sfc /scannow

    re-install updage the networking driver.

    Since there was memory involved download memtestx86 and run for 5 passes


    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\010610-17437-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 (2 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
    Machine Name:
    Kernel base = 0xfffff800`02c1f000 PsLoadedModuleList = 0xfffff800`02e5ce50
    Debug session time: Wed Jan  6 11:53:16.601 2010 (GMT-5)
    System Uptime: 0 days 0:25:57.164
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    .........................
    Loading User Symbols
    Loading unloaded module list
    .....
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck D1, {30d73a0d, 2, 1, fffff88001679de4}
    
    Probably caused by : hardware ( tcpip!TcpPreValidatedReceive+344 )
    
    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: 0000000030d73a0d, memory referenced
    Arg2: 0000000000000002, IRQL
    Arg3: 0000000000000001, value 0 = read operation, 1 = write operation
    Arg4: fffff88001679de4, address which referenced memory
    
    Debugging Details:
    ------------------
    
    
    WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002ec70e0
     0000000030d73a0d 
    
    CURRENT_IRQL:  2
    
    FAULTING_IP: 
    tcpip!TcpPreValidatedReceive+344
    fffff880`01679de4 c00000          rol     byte ptr [rax],0
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    
    BUGCHECK_STR:  0xD1
    
    PROCESS_NAME:  System
    
    TRAP_FRAME:  fffff88002fdc7b0 -- (.trap 0xfffff88002fdc7b0)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=0000000030d73a0d rbx=0000000000000000 rcx=0000000000000162
    rdx=0000000000000176 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff88001679de4 rsp=fffff88002fdc940 rbp=0000000000000000
     r8=000000000000d490  r9=0000000000000180 r10=0000000030d73a0d
    r11=fffff88002fdc9fa r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up ei ng nz na po nc
    tcpip!TcpPreValidatedReceive+0x344:
    fffff880`01679de4 c00000          rol     byte ptr [rax],0 ds:00000000`30d73a0d=??
    Resetting default scope
    
    MISALIGNED_IP: 
    tcpip!TcpPreValidatedReceive+344
    fffff880`01679de4 c00000          rol     byte ptr [rax],0
    
    LAST_CONTROL_TRANSFER:  from fffff80002c90469 to fffff80002c90f00
    
    STACK_TEXT:  
    fffff880`02fdc668 fffff800`02c90469 : 00000000`0000000a 00000000`30d73a0d 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
    fffff880`02fdc670 fffff800`02c8f0e0 : 00000000`00000000 00000000`8d9d713f 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
    fffff880`02fdc7b0 fffff880`01679de4 : fffffa80`0277d490 fffffa80`00000000 fffffa80`03bf0440 fffff880`0165d47a : nt!KiPageFault+0x260
    fffff880`02fdc940 fffff880`0165c3c7 : fffffa80`03bf25c0 fffffa80`027726c0 fffffa80`027725c0 00000000`00000000 : tcpip!TcpPreValidatedReceive+0x344
    fffff880`02fdc9f0 fffff880`0165c499 : fffff880`02fdcb70 fffff880`0176c9a0 fffff880`02fdcb80 00000000`00000001 : tcpip!IppDeliverListToProtocol+0x97
    fffff880`02fdcab0 fffff880`0165c990 : 00000000`00000000 fffff800`02c98052 00000000`00000000 fffff880`02fdcb70 : tcpip!IppProcessDeliverList+0x59
    fffff880`02fdcb20 fffff880`01635702 : fffffa80`018d5040 fffff880`00e4077d 00000000`00000000 fffffa80`02726ad0 : tcpip!IppReceiveHeaderBatch+0x231
    fffff880`02fdcc00 fffff800`02f8a527 : fffffa80`02726ad0 fffff800`02e345f8 fffffa80`018d5040 fffffa80`0276ea90 : tcpip!IppLoopbackTransmit+0x72
    fffff880`02fdcc40 fffff800`02c9e161 : fffff800`02e34500 fffff800`02f8a504 fffffa80`018d5040 fffff800`02e345f8 : nt!IopProcessWorkItem+0x23
    fffff880`02fdcc70 fffff800`02f34166 : 00000001`00000002 fffffa80`018d5040 00000000`00000080 fffffa80`018459e0 : nt!ExpWorkerThread+0x111
    fffff880`02fdcd00 fffff800`02c6f486 : fffff880`009e7180 fffffa80`018d5040 fffff880`009f1f40 006c006c`0064002e : nt!PspSystemThreadStartup+0x5a
    fffff880`02fdcd40 00000000`00000000 : fffff880`02fdd000 fffff880`02fd7000 fffff880`02fdc9b0 00000000`00000000 : nt!KxStartSystemThread+0x16
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    tcpip!TcpPreValidatedReceive+344
    fffff880`01679de4 c00000          rol     byte ptr [rax],0
    
    SYMBOL_STACK_INDEX:  3
    
    SYMBOL_NAME:  tcpip!TcpPreValidatedReceive+344
    
    FOLLOWUP_NAME:  MachineOwner
    
    IMAGE_NAME:  hardware
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  0
    
    MODULE_NAME: hardware
    
    FAILURE_BUCKET_ID:  X64_IP_MISALIGNED
    
    BUCKET_ID:  X64_IP_MISALIGNED
    
    Followup: MachineOwner
    ---------
      My Computer


  3. Posts : 5
    Windows 7
    Thread Starter
       #3

    Thanks for the help,

    I've updated the BIOS and the suggested drivers and also ran the memtest which showed no problems, yet I still seem to be experiencing crashes.

    latest minidump attached, any ideas?

    Thanks again.
      My Computer


  4. Posts : 5,705
    Win7 x64 + x86
       #4

    I would first suggest updating these 2 older drivers:
    Code:
    BS_I2c64.sys Mon Dec 11 02:48:39 2006 - This is probably a program from BIOSTAR
    BIOS64.sys   Sat Jun 07 20:12:00 2003 - This is probably a  BIOSTAR I/O driver file
    If no updates are available, then I'd suggest removing the programs that they are associated with.
    Worst case, use Autoruns (free here: Autoruns for Windows ) to disable those drivers (I don't know what affect this will have on the system). But I consider this the most likely reason for your crashes due to the low level that these drivers appear to work at (which makes them more susceptible to compatibility issues with Win7).

    Beyond that, the error points to USBPORT.SYS, a component of the Windows Operating System.
    So, I'd try this stuff:
    - run SFC.EXE /SCANNOW from an elevated (Run as administrator) Command Prompt
    - try using other USB ports (if these are the on the front, try the back. If they're on the side, try the other side).
    - remove all USB devices, then try them one-by-one to see if you can "force" the BSOD.
    - let us know the exact make and model of your system so we can see if there's any built in USB devices.
    - please upload this file so someone can check for USB devices and problem areas:
    MSINFO32:
    Please go to Start and type in "msinfo32.exe" (without the quotes) and press Enter
    Save the report as an .nfo file, then zip up the .nfo file and upload/attach the .zip file with your next post.

    If you're having difficulties with the format, please open an elevated (Run as administrator) Command Prompt and type "msinfo32 /nfo C:\Users\Public\Desktop\TEST.NFO" (without the quotes) and press Enter. Then navigate to the C:\Users\Public\Desktop directory to retrieve the TEST.NFO file. If you have difficulties with making this work, please post back.
      My Computer


  5. Posts : 5
    Windows 7
    Thread Starter
       #5

    Thanks for the help,

    The sfc scan has not shown any problems. Will check the USB ports and driver files.

    nfo file is attached.

    Thanks
      My Computer


  6. Posts : 5,705
    Win7 x64 + x86
       #6

    Sorry, but the system info file is unreadable.
    Could you try this?:
    If you're having difficulties with the format, please open an elevated (Run as administrator) Command Prompt and type "msinfo32 /nfo C:\Users\Public\Desktop\TEST.NFO" (without the quotes) and press Enter. Then navigate to the C:\Users\Public\Desktop directory to retrieve the TEST.NFO file.
      My Computer


  7. Posts : 5
    Windows 7
    Thread Starter
       #7

    nfo file attached.

    Thanks
      My Computer


  8. Posts : 5
    Windows 7
    Thread Starter
       #8

    Not sure if this helps, but ran another sfc scan. results say there are some corrupted files unable to be fixed.

    Log attached.
      My Computer


  9. Posts : 5,705
    Win7 x64 + x86
       #9

    There are problems with these devices:
    Code:
    WAN Miniport (L2TP)    ROOT\MS_L2TPMINIPORT\0000    This device is not working properly because Windows cannot load the drivers required for this device.
    WAN Miniport (PPTP)    ROOT\MS_PPTPMINIPORT\0000    This device is not working properly because Windows cannot load the drivers required for this device.
    Go into Device Manager, right click on each one and select "Uninstall".
    Then reboot the system and check to see if the problem is solved.

    Finally, there's an enormous number of errors attributed to avgwdsvc.exe - a component of your AVG Internet Security. Please do the following:
    Anti-Virus Removal:
    Please do the following:
    - download a free antivirus for testing purposes: Free AntiVirus
    - uninstall the AVG from your system
    - remove any remnants of AVG using this free tool: http://www.avg.com/us-en/download-tools
    - IMMEDIATELY install and update the free antivirus
    - check to see if this fixes the BSOD's
      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 00:44.
Find Us