Random BSODs

Page 1 of 3 123 LastLast

  1. Posts : 17
    Windows 7 Ultimate x64
       #1

    Random BSODs - When waching movies, browsing internet, etc


    Hello,

    I got my laptop about a month ago, and up until two weeks ago it was running fine.
    Symptoms started with random reboots, but now it's getting to the point where it'll display BSODs almost every hour, for no apparent reason.
    Attached are minidumps, hope someone'll help me out.

    Thanks in advance,

    Kim
    Last edited by Algapaf; 07 Sep 2012 at 18:37.
      My Computer


  2. Posts : 15,026
    Windows 10 Home 64Bit
       #2

    Welcome

    All your dumps show different causes

    Lets start with avgntflt.sys caused by Avira. Remove Avira using Uninstall a program in Control Panel, clean up after with Avira registry cleaner, and replace with Microsoft Security Essentials - Free Antivirus for Windows to run with Windows firewall turned on.
    Code:
    Microsoft (R) Windows Debugger Version 6.12.0002.633 X86
    Copyright (c) Microsoft Corporation. All rights reserved.
    
    
    Loading Dump File [C:\Users\Yusra\Downloads\algaf\090812-19328-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    
    Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
    Executable search path is: 
    Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
    Machine Name:
    Kernel base = 0xfffff800`02654000 PsLoadedModuleList = 0xfffff800`02898670
    Debug session time: Sat Sep  8 04:45:01.635 2012 (UTC + 6:00)
    System Uptime: 0 days 0:07:46.291
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ......................................
    Loading User Symbols
    Loading unloaded module list
    .......
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 1E, {ffffffffc0000005, fffff800026e5fbf, 0, ffffffffffffffff}
    
    Unable to load image avgntflt.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for avgntflt.sys
    *** ERROR: Module load completed but symbols could not be loaded for avgntflt.sys
    Probably caused by : avgntflt.sys ( avgntflt+1f35 )
     
    Followup: MachineOwner
    ---------
    
    2: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    KMODE_EXCEPTION_NOT_HANDLED (1e)
    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.
    Arguments:
    Arg1: ffffffffc0000005, The exception code that was not handled
    Arg2: fffff800026e5fbf, The address that the exception occurred at
    Arg3: 0000000000000000, Parameter 0 of the exception
    Arg4: ffffffffffffffff, Parameter 1 of the exception
    
    Debugging Details:
    ------------------
    
    
    EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
    
    FAULTING_IP: 
    nt!IoGetRelatedDeviceObject+5f
    fffff800`026e5fbf 488b12          mov     rdx,qword ptr [rdx]
    
    EXCEPTION_PARAMETER1:  0000000000000000
    
    EXCEPTION_PARAMETER2:  ffffffffffffffff
    
    READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002902100
     ffffffffffffffff 
    
    ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
    
    BUGCHECK_STR:  0x1E_c0000005
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    
    PROCESS_NAME:  avguard.exe
    
    CURRENT_IRQL:  0
    
    LAST_CONTROL_TRANSFER:  from fffff8000271dd88 to fffff800026d31c0
    
    STACK_TEXT:  
    fffff880`1b99c9b8 fffff800`0271dd88 : 00000000`0000001e ffffffff`c0000005 fffff800`026e5fbf 00000000`00000000 : nt!KeBugCheckEx
    fffff880`1b99c9c0 fffff800`026d2842 : fffff880`1b99d198 00000000`00000008 fffff880`1b99d240 fffffa80`0773d720 : nt! ?? ::FNODOBFM::`string'+0x48d3d
    fffff880`1b99d060 fffff800`026d114a : 00000000`00000000 fffffa80`071edc70 fffffa80`00000001 00000000`0a000001 : nt!KiExceptionDispatch+0xc2
    fffff880`1b99d240 fffff800`026e5fbf : fffff800`029ad4ee 00000000`00000000 00000000`00000000 fffffa80`07013f30 : nt!KiGeneralProtectionFault+0x10a
    fffff880`1b99d3d8 fffff800`029ad4ee : 00000000`00000000 00000000`00000000 fffffa80`07013f30 fffffa80`07737400 : nt!IoGetRelatedDeviceObject+0x5f
    fffff880`1b99d3e0 fffff800`026d2453 : ffffffff`800003dc fffffa80`0cf48850 fffff880`1b99d728 00000000`00000008 : nt!NtSetInformationFile+0x1bc
    fffff880`1b99d500 fffff800`026cea10 : fffff880`064baf35 fffffa80`00000000 00000000`00000001 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
    fffff880`1b99d708 fffff880`064baf35 : fffffa80`00000000 00000000`00000001 00000000`00000000 00000000`0d120b30 : nt!KiServiceLinkage
    fffff880`1b99d710 fffffa80`00000000 : 00000000`00000001 00000000`00000000 00000000`0d120b30 00000000`0000000e : avgntflt+0x1f35
    fffff880`1b99d718 00000000`00000001 : 00000000`00000000 00000000`0d120b30 00000000`0000000e 00000000`00000011 : 0xfffffa80`00000000
    fffff880`1b99d720 00000000`00000000 : 00000000`0d120b30 00000000`0000000e 00000000`00000011 00000000`0000f400 : 0x1
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    avgntflt+1f35
    fffff880`064baf35 ??              ???
    
    SYMBOL_STACK_INDEX:  8
    
    SYMBOL_NAME:  avgntflt+1f35
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: avgntflt
    
    IMAGE_NAME:  avgntflt.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4f9644cb
    
    FAILURE_BUCKET_ID:  X64_0x1E_c0000005_avgntflt+1f35
    
    BUCKET_ID:  X64_0x1E_c0000005_avgntflt+1f35
    
    Followup: MachineOwner
    ---------
    
    2: kd> lmvm avgntflt
    start             end                 module name
    fffff880`064b9000 fffff880`064d9000   avgntflt T (no symbols)           
        Loaded symbol image file: avgntflt.sys
        Image path: avgntflt.sys
        Image name: avgntflt.sys
        Timestamp:        Tue Apr 24 12:14:35 2012 (4F9644CB)
        CheckSum:         0001CE81
        ImageSize:        00020000
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    Another one shows athrx.sys which is caused by atheros get and update for it. Productname: Driver for Atheros CB42/CB43/MB42/MB43 Network Adapter Description: Atheros Extensible Wireless LAN device driver Company: Atheros Communications, Inc. File size: Various
    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 1000007E, {ffffffffc0000005, fffff800026dc265, fffff8801b1744a8, fffff8801b173d00}
    
    Unable to load image athrx.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for athrx.sys
    *** ERROR: Module load completed but symbols could not be loaded for athrx.sys
    Probably caused by : vwififlt.sys ( vwififlt!FilterSendNetBufferListsComplete+151 )
    
    Followup: MachineOwner
    ---------
    
    0: 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: fffff800026dc265, The address that the exception occurred at
    Arg3: fffff8801b1744a8, Exception Record Address
    Arg4: fffff8801b173d00, 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: 
    nt!KeAcquireSpinLockRaiseToDpc+55
    fffff800`026dc265 f0480fba2900    lock bts qword ptr [rcx],0
    
    EXCEPTION_RECORD:  fffff8801b1744a8 -- (.exr 0xfffff8801b1744a8)
    ExceptionAddress: fffff800026dc265 (nt!KeAcquireSpinLockRaiseToDpc+0x0000000000000055)
       ExceptionCode: c0000005 (Access violation)
      ExceptionFlags: 00000000
    NumberParameters: 2
       Parameter[0]: 0000000000000000
       Parameter[1]: ffffffffffffffff
    Attempt to read from address ffffffffffffffff
    
    CONTEXT:  fffff8801b173d00 -- (.cxr 0xfffff8801b173d00)
    rax=0000000000000002 rbx=0000000000000002 rcx=fffdfa800b465608
    rdx=fffff80002845e80 rsi=fffffa800b465600 rdi=fffff80002845e80
    rip=fffff800026dc265 rsp=fffff8801b1746e0 rbp=fffdfa800b465608
     r8=00000000000070f8  r9=0000000000000000 r10=fffff80002654000
    r11=00000000000002d3 r12=0000000000000001 r13=0000000000000001
    r14=fffff880035e8110 r15=fffff88003c4d5a0
    iopl=0         nv up ei pl nz na pe nc
    cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010202
    nt!KeAcquireSpinLockRaiseToDpc+0x55:
    fffff800`026dc265 f0480fba2900    lock bts qword ptr [rcx],0 ds:002b:fffdfa80`0b465608=????????????????
    Resetting default scope
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    
    PROCESS_NAME:  System
    
    CURRENT_IRQL:  2
    
    ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
    
    EXCEPTION_PARAMETER1:  0000000000000000
    
    EXCEPTION_PARAMETER2:  ffffffffffffffff
    
    READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002902100
     ffffffffffffffff 
    
    FOLLOWUP_IP: 
    vwififlt!FilterSendNetBufferListsComplete+151
    fffff880`035e1201 488b0d086f0000  mov     rcx,qword ptr [vwififlt!WPP_GLOBAL_Control (fffff880`035e8110)]
    
    BUGCHECK_STR:  0x7E
    
    LAST_CONTROL_TRANSFER:  from fffff8800187e3c9 to fffff800026dc265
    
    STACK_TEXT:  
    fffff880`1b1746e0 fffff880`0187e3c9 : fffffa80`0b465600 00000000`00000001 fffffa80`077412e0 00000000`00000600 : nt!KeAcquireSpinLockRaiseToDpc+0x55
    fffff880`1b174730 fffff880`035e1201 : fffffa80`0b46aa78 00000000`00000001 00000000`00000000 fffffa80`0eab8030 : ndis!NdisFreeCloneNetBufferList+0x149
    fffff880`1b174760 fffff880`0193421d : fffffa80`0aca91a0 00000000`00000000 00000000`00000001 fffff880`035e19c0 : vwififlt!FilterSendNetBufferListsComplete+0x151
    fffff880`1b1747b0 fffff880`03c8f228 : fffffa80`0aca91a0 00000000`00000000 00000000`00000000 fffff880`1b174840 : ndis!NdisMSendNetBufferListsComplete+0x6d
    fffff880`1b1747f0 fffffa80`0aca91a0 : 00000000`00000000 00000000`00000000 fffff880`1b174840 fffffa80`077412e0 : athrx+0x43228
    fffff880`1b1747f8 00000000`00000000 : 00000000`00000000 fffff880`1b174840 fffffa80`077412e0 00000000`00000000 : 0xfffffa80`0aca91a0
    
    
    SYMBOL_STACK_INDEX:  2
    
    SYMBOL_NAME:  vwififlt!FilterSendNetBufferListsComplete+151
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: vwififlt
    
    IMAGE_NAME:  vwififlt.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bcc3a
    
    STACK_COMMAND:  .cxr 0xfffff8801b173d00 ; kb
    
    FAILURE_BUCKET_ID:  X64_0x7E_vwififlt!FilterSendNetBufferListsComplete+151
    
    BUCKET_ID:  X64_0x7E_vwififlt!FilterSendNetBufferListsComplete+151
    
    Followup: MachineOwner
    ---------
    Another dump shows USBPORT.SYS see if this tutorial is useful:
    USB Driver - General Fix for Problems
    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 1E, {0, 0, 0, 0}
    
    Probably caused by : USBPORT.SYS ( USBPORT!USBPORT_DereferenceDeviceHandle+d1 )
    
    Followup: MachineOwner
    ---------
    Please upload your msinfo32.nfo file. To get this:

    • Click on the Start
    • Type msinfo32 into the Search programs and files box
    • When it opens, go to File, Save
    • Save as msinfo32.nfo and save in a place you will remember
    • Let it finish the process of gathering and saving the system info
    • Right click the .nfo file, click send to compressed (zipped) folder
    • Upload the .zip file here.

    Post back once you've done the above
      My Computer


  3. Posts : 17
    Windows 7 Ultimate x64
    Thread Starter
       #3

    Updated the Atheros driver, replaced Avira with Avast (I had problems with MSE before)

    The USB fix is in progress.
    However, I can't seem to find the msiinfo32 you requested.

    Edit: I was mistyping it, so here you are ^^
      My Computer


  4. Posts : 15,026
    Windows 10 Home 64Bit
       #4

    Algapaf said:
    Updated the Atheros driver, replaced Avira with Avast (I had problems with MSE before)

    The USB fix is in progress.
    However, I can't seem to find the msiinfo32 you requested.

    Edit: I was mistyping it, so here you are ^^
    Thanks :)

    I see that you have no BSOD demanding programs installed.

    The best way to get drivers is to download them from the manufacturers website.

    May I add that Avast! is also a known cause of blue screen.
    Let us know what problems you had with MSE in details please.

    Observe your computer and let me know if you're getting more blue screens
      My Computer


  5. Posts : 17
    Windows 7 Ultimate x64
    Thread Starter
       #5

    Uninstalled the driver searching software.
    Here are the latest minidumps ...
      My Computer


  6. Posts : 15,026
    Windows 10 Home 64Bit
       #6

    Is the USB fix done? cause I saw you got a bsod on that one again

    PS: I am preparing my next post. Please wait for a while
      My Computer


  7. Posts : 17
    Windows 7 Ultimate x64
    Thread Starter
       #7

    I followed all the steps, everything went fine, I'm going to run everything normally until something else pops up :/
      My Computer


  8. Posts : 15,026
    Windows 10 Home 64Bit
       #8

    Okay Wait till I get back to you with the next steps, in that between if you have more bsods upload them.
      My Computer


  9. Posts : 15,026
    Windows 10 Home 64Bit
       #9

    As the dumps indicate usbport.sys (or any other usb related sys), you need to turn on usb selective suspense.
    USB Selective Suspend - Turn On or Off

    Keep us posted
      My Computer


  10. Posts : 17
    Windows 7 Ultimate x64
    Thread Starter
       #10

    Selective Suspend has been on since the beginning ..
      My Computer


 
Page 1 of 3 123 LastLast

  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 03:34.
Find Us