locked
Windows 7 BSOD with various errors RRS feed

  • Question

  • I've been getting random BSODs for over a year now - I can make it happen quickly if I have 2 flash video players open at the same time, but otherwise it happens randomly about once a day - sometime when the machine is otherwise idle.  Since this started, I have updated the CPU, Motherboard, GPU, and memory.   Both hard drives pass various SeaTools tests, memory passes memcheck-x86 (I only let it run for a few hours, but the BSODs happened before and after I got new memory so I don't think that's it).

    system info file:
    https://skydrive.live.com/redir?resid=99251859AF20C190!106

    last few DMP files
    https://skydrive.live.com/redir?resid=99251859AF20C190!107

    Info from the latest BSOD via WinDbg (messages are usually a bit different) is below.

    I have literally replaced or tested everything on this computer.  the only remaining option I can think of is an OS reinstall which I *really* don't want to do.  Any suggestions would be appreciated.  thanks.

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

    KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
    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: c0000005, The exception code that was not handled
    Arg2: 8c978885, The address that the exception occurred at
    Arg3: 910f05c0, Trap Frame
    Arg4: 00000000

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


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

    FAULTING_IP:
    fltmgr!TreeFindNodeOrParent+11
    8c978885 8b4110          mov     eax,dword ptr [ecx+10h]

    TRAP_FRAME:  910f05c0 -- (.trap 0xffffffff910f05c0)
    ErrCode = 00000000
    eax=1df57e2f ebx=00000000 ecx=1df57e2f edx=00000000 esi=89e9ebe8 edi=89e9ec14
    eip=8c978885 esp=910f0634 ebp=910f0634 iopl=0         nv up ei pl nz na po nc
    cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010202
    fltmgr!TreeFindNodeOrParent+0x11:
    8c978885 8b4110          mov     eax,dword ptr [ecx+10h] ds:0023:1df57e3f=????????
    Resetting default scope

    CUSTOMER_CRASH_COUNT:  1

    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

    BUGCHECK_STR:  0x8E

    PROCESS_NAME:  nvSCPAPISvr.ex

    CURRENT_IRQL:  0

    LAST_CONTROL_TRANSFER:  from 8c9788ed to 8c978885

    STACK_TEXT:  
    910f0634 8c9788ed 89e9ec14 87dcda58 00000000 fltmgr!TreeFindNodeOrParent+0x11
    910f064c 8c971340 89e9ec14 87dcda58 00000000 fltmgr!TreeLookup+0x17
    910f068c 8c97140a 89e9ebe8 87dcda58 00000000 fltmgr!GetContextFromStreamList+0x50
    910f06a8 92e4d32b 87dcda58 89e9ebe8 910f06dc fltmgr!FltGetStreamContext+0x34
    WARNING: Stack unwind information not available. Following frames may be wrong.
    910f06d4 92e58c39 00000000 d5203034 910f0700 klif+0x1432b
    910f0754 8c970324 873b1ed0 910f0778 87dc3490 klif+0x1fc39
    910f07bc 8c973512 003b1e70 873b1e70 1000000c fltmgr!FltpPerformPostCallbacks+0x24a
    910f07d0 8c973b46 873b1e70 8736a4d0 910f0810 fltmgr!FltpProcessIoCompletion+0x10
    910f07e0 8c97429c 8720e828 8736a4d0 873b1e70 fltmgr!FltpPassThroughCompletion+0x98
    910f0810 8c9878c9 910f0830 00000000 00000000 fltmgr!FltpLegacyProcessingAfterPreCallbacksCompleted+0x33a
    910f085c 83a4e5be 8720e828 8836d008 87e3b690 fltmgr!FltpCreate+0x2db
    910f0874 92ed1a85 873b2500 87e3b690 8736a4d0 nt!IofCallDriver+0x63
    910f08a0 92ed1c35 87e3b690 0036a4d0 910f08c8 mozy+0x3a85
    910f08b0 83a4e5be 87e3b690 8736a4d0 873b255c mozy+0x3c35
    910f08c8 83c5d427 a799693c 910f0a70 00000000 nt!IofCallDriver+0x63
    910f09a0 83c3cc2e 87785a38 c5921488 872be610 nt!IopParseDevice+0xed7
    910f0a1c 83c4d040 00000000 910f0a70 00000040 nt!ObpLookupObjectName+0x4fa
    910f0a78 83c6fcd1 00b3f76c 86921488 00000001 nt!ObOpenObjectByName+0x165
    910f0c24 83a5527a 00b3f76c 00b3f744 00b3f79c nt!NtQueryAttributesFile+0x121
    910f0c24 77377094 00b3f76c 00b3f744 00b3f79c nt!KiFastCallEntry+0x12a
    00b3f79c 00000000 00000000 00000000 00000000 0x77377094


    STACK_COMMAND:  kb

    FOLLOWUP_IP:
    klif+1432b
    92e4d32b ??              ???

    SYMBOL_STACK_INDEX:  4

    SYMBOL_NAME:  klif+1432b

    FOLLOWUP_NAME:  MachineOwner

    MODULE_NAME: klif

    IMAGE_NAME:  klif.sys

    DEBUG_FLR_IMAGE_TIMESTAMP:  4daeb73f

    FAILURE_BUCKET_ID:  0x8E_klif+1432b

    BUCKET_ID:  0x8E_klif+1432b

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

    Saturday, August 18, 2012 8:51 PM

Answers

  • Just make a sytem repair...boot it in your installer them make a system repair..hope it will be ok..

    just give me feedback.. I will guide you!!

    • Marked as answer by Nicholas Li Thursday, August 30, 2012 3:40 AM
    Sunday, August 19, 2012 1:56 PM

All replies

  • Also, here's the basic system info (and yes, I have 2x4GB DIMMS but I only have a 32-bit OS):

    System Information report written at: 08/18/12 16:09:37
    System Name: OOMA
    [System Summary]

    Item    Value    
    OS Name    Microsoft Windows 7 Ultimate    
    Version    6.1.7601 Service Pack 1 Build 7601    
    Other OS Description     Not Available    
    OS Manufacturer    Microsoft Corporation    
    System Name    OOMA    
    System Manufacturer    Gigabyte Technology Co., Ltd.    
    System Model    Z68A-D3H-B3    
    System Type    X86-based PC    
    Processor    Intel(R) Core(TM) i5-2400 CPU @ 3.10GHz, 3301 Mhz, 4 Core(s), 4 Logical Processor(s)    
    BIOS Version/Date    Award Software International, Inc. F11, 10/12/2011    
    SMBIOS Version    2.4    
    Windows Directory    F:\Windows    
    System Directory    F:\Windows\system32    
    Boot Device    \Device\HarddiskVolume2    
    Locale    United States    
    Hardware Abstraction Layer    Version = "6.1.7601.17514"    
    User Name    OOMA\Jon    
    Time Zone    Eastern Daylight Time    
    Installed Physical Memory (RAM)    8.00 GB    
    Total Physical Memory    3.17 GB    
    Available Physical Memory    1.64 GB    
    Total Virtual Memory    6.34 GB    
    Available Virtual Memory    4.57 GB    
    Page File Space    3.17 GB    
    Page File    F:\pagefile.sys   

    Saturday, August 18, 2012 8:57 PM
  • Just make a sytem repair...boot it in your installer them make a system repair..hope it will be ok..

    just give me feedback.. I will guide you!!

    • Marked as answer by Nicholas Li Thursday, August 30, 2012 3:40 AM
    Sunday, August 19, 2012 1:56 PM