I have been getting multiple BSODS since day one

Page 1 of 6 123 ... LastLast

  1. Posts : 30
    Windows 7 Home premium 64bit
       #1

    I have been getting multiple BSODS since day one


    Hello Sevenforums! I built my computer about 2 and half weeks ago and from day one I have been getting multiple BSODs. These BSODs are the following:
    1.SYSTEM_SERVICE_EXCEPTION (X4)
    2.IQRL_NOT_LESS_OR_EQUAL (X4)
    3.nvlddmkm.sys
    4.MEMORY_MANAGEMENT(X2)

    It also comes up with Windows has detected a problem and has shutdown to prevent damage.(I think that's what it says)
    (Please note that (X*) is how many times it has occurred since I started recording the BSODs which was about a week and a half ago)

    I can't seem to notice any pattern for when they occur besides when I had chrome, I am now just using IE10. Please let me know if there is something I can do to provide you more information to fix these problems.

    Thanks in advance for any help you can provide, Luke
      My Computer


  2. Posts : 30
    Windows 7 Home premium 64bit
    Thread Starter
       #2

    Here are my system specs:

    RAM: G.Skill Ripjaws Z F3-12800CL9Q-16GBZL 16GB

    Motherboard: MSI Z87-GD65 Gaming Motherboard

    CPU: Intel Core i7 4770K

    CPU Cooler: Swiftech H220 All-In-One Liquid Cooler

    GPU: EVGA GeForce GTX 780 Superclocked 3GB

    HDD: Western Digital WD Black 2TB WD2002FAEX

    SSD: Samsung 840 Pro Series 256GB SSD Retail Box

    PSU: Seasonic X-1250 80Plus Gold 1250W

    Case: CoolerMaster CM Storm Stryker Case

    Optical Drive: LG GH24NS95 24x SATA DVD-RW Drive

    OS: Microsoft Windows 7 Home Premium
      My Computer


  3. Posts : 9,606
    Win7 Enterprise, Win7 x86 (Ult 7600), Win7 x64 Ult 7600, TechNet RTM on AMD x64 (2.8Ghz)
       #3

    Welcome Luke :)

    From your specs, looks like you built a fine rig.

    I am sure several of our BSOD Team members will be here shortly to help you.

    How about sharing some pics Show Us Your Rig [5]
      My Computer


  4. Posts : 30
    Windows 7 Home premium 64bit
    Thread Starter
       #4

    DocBrown said:
    Welcome Luke :)

    From your specs, looks like you built a fine rig.

    I am sure several of our BSOD Team members will be here shortly to help you.

    How about sharing some pics Show Us Your Rig [5]
    Hello Doc, I will do that. You mean post them on that thread right?
      My Computer


  5. Posts : 9,606
    Win7 Enterprise, Win7 x86 (Ult 7600), Win7 x64 Ult 7600, TechNet RTM on AMD x64 (2.8Ghz)
       #5

    Yes that is where most of us show off our custom builds
      My Computer


  6. Arc
    Posts : 35,373
    Microsoft Windows 10 Pro Insider Preview 64-bit
       #6

    Hello luke1426.

    Klif Mini-Filter fre_wnet_x86 (Kaspersky)/Kaspersky Lab Driver is causing the BSODs there.
    Code:
    fffff880`0e3119b8  fffff880`032d2b7eUnable to load image \SystemRoot\system32\DRIVERS\klif.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for klif.sys
    *** ERROR: Module load completed but symbols could not be loaded for klif.sys
     klif+0x1fb7e
    Uninstall Kaspersky using Kaspersky Removal Tool. Use Microsoft Security Essentials as your antivirus with windows inbuilt firewall, and free MBAM as the on demand scanner.
    Download, install and update those, and then run full system scans with both of them, one by one.

    The display driver is causing some issues, too.
    Code:
    fffff880`0e3115b8  fffff880`04ffdc1aUnable to load image \SystemRoot\system32\DRIVERS\nvlddmkm.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for nvlddmkm.sys
    *** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
     nvlddmkm+0x1dfc1a
    And the driver is the latest version.
    Code:
    fffff880`04e1e000 fffff880`0590d000   nvlddmkm T (no symbols)           
        Loaded symbol image file: nvlddmkm.sys
        Image path: \SystemRoot\system32\DRIVERS\nvlddmkm.sys
        Image name: nvlddmkm.sys
        Timestamp:        Sun Jul 14 00:13:31 2013 (51E19FD3)
        CheckSum:         00AC2C5E
        ImageSize:        00AEF000
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    The latest version of Nvidia display driver is known to be buggy in some cases. Install the WHQL 314.22 only which is much more stable.

    • Uninstall All nvidia items in Control Panel > Programs and features
      • 3D Vision Control Driver
      • 3D Vision Driver
      • Graphics Driver
      • HD Audio Driver
      • PhysX
      • nvidia Update

      (Are you using nvidia chipset drivers? If so, dont uninstall anything other than those are listed).
    • Now follow Drivers - Clean Left over Files after Uninstalling
    • Boot normally now. Go to Drivers - Download NVIDIA Drivers, Download 314.22 WHQL. While installing, Select Custom (Advanced) install. In the next page, follow this settings:


    Free up the startup. Windows does not need any other program to auto start with it, but the auto start programs often conflicts and causes various problems including BSODs.

    1. Click on the Start button
    2. Type “msconfig (without quotes), click the resulting link. It will open the System Configuration window.
    3. Select the “Startup” tab.
    4. Deselect all items other than the antivirus.
    5. Apply > OK
    6. Accept then restart.

    Let us know the results.
    _______________________________________________________________________________
    BSOD ANALYSIS:
    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 50, {fffff9000309398f, 8, fffff9000309398f, 2}
    
    
    Could not read faulting driver name
    Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+43836 )
    
    Followup: MachineOwner
    ---------
    
    0: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    PAGE_FAULT_IN_NONPAGED_AREA (50)
    Invalid system memory was referenced.  This cannot be protected by try-except,
    it must be protected by a Probe.  Typically the address is just plain bad or it
    is pointing at freed memory.
    Arguments:
    Arg1: fffff9000309398f, memory referenced.
    Arg2: 0000000000000008, value 0 = read operation, 1 = write operation.
    Arg3: fffff9000309398f, If non-zero, the instruction address which referenced the bad memory
        address.
    Arg4: 0000000000000002, (reserved)
    
    Debugging Details:
    ------------------
    
    
    Could not read faulting driver name
    
    READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800032c4100
    GetUlongFromAddress: unable to read from fffff800032c41c0
     fffff9000309398f 
    
    FAULTING_IP: 
    +0
    fffff900`0309398f ??              ???
    
    MM_INTERNAL_CODE:  2
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
    
    BUGCHECK_STR:  0x50
    
    PROCESS_NAME:  Origin.exe
    
    CURRENT_IRQL:  0
    
    TRAP_FRAME:  fffff8800e3116f0 -- (.trap 0xfffff8800e3116f0)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000000
    rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff9000309398f rsp=fffff8800e311880 rbp=0000000000000000
     r8=fffff80003017000  r9=0000000000000000 r10=fffffffffffffffe
    r11=0000000000000008 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up ei ng nz na po nc
    fffff900`0309398f ??              ???
    Resetting default scope
    
    LAST_CONTROL_TRANSFER:  from fffff800031095d4 to fffff8000308cc00
    
    FAILED_INSTRUCTION_ADDRESS: 
    +0
    fffff900`0309398f ??              ???
    
    STACK_TEXT:  
    fffff880`0e311588 fffff800`031095d4 : 00000000`00000050 fffff900`0309398f 00000000`00000008 fffff880`0e3116f0 : nt!KeBugCheckEx
    fffff880`0e311590 fffff800`0308ad2e : 00000000`00000008 fffff900`0309398f 00000000`00000000 0000000d`0d47e76c : nt! ?? ::FNODOBFM::`string'+0x43836
    fffff880`0e3116f0 fffff900`0309398f : 00000000`00000001 00000000`00000000 00000000`000000ab fffffa80`109467d0 : nt!KiPageFault+0x16e
    fffff880`0e311880 00000000`00000001 : 00000000`00000000 00000000`000000ab fffffa80`109467d0 00000000`000000ab : 0xfffff900`0309398f
    fffff880`0e311888 00000000`00000000 : 00000000`000000ab fffffa80`109467d0 00000000`000000ab 00000000`00000000 : 0x1
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    nt! ?? ::FNODOBFM::`string'+43836
    fffff800`031095d4 cc              int     3
    
    SYMBOL_STACK_INDEX:  1
    
    SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+43836
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: nt
    
    IMAGE_NAME:  ntkrnlmp.exe
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  5147d9c6
    
    FAILURE_BUCKET_ID:  X64_0x50_BAD_IP_nt!_??_::FNODOBFM::_string_+43836
    
    BUCKET_ID:  X64_0x50_BAD_IP_nt!_??_::FNODOBFM::_string_+43836
    
    Followup: MachineOwner
    ---------
      My Computer


  7. Posts : 30
    Windows 7 Home premium 64bit
    Thread Starter
       #7

    Thanks Arc, what about the 320.49 - WHQL driver the other one isn't there for the GTX 780
      My Computer


  8. Arc
    Posts : 35,373
    Microsoft Windows 10 Pro Insider Preview 64-bit
       #8

    If yours a newer GPU, the older drivers (prior to some new incorporation to the driver's bundle) will not be supported for your GPU. In that case you may try 320.18 WHQL.

    But the primary thing is to remove Kaspersky. We need to know how it is running with Kaspersky free environment.

    For teh display driver, at a maximum you may need to wait for the next release.
      My Computer


  9. Posts : 30
    Windows 7 Home premium 64bit
    Thread Starter
       #9

    I really don't get why Kaspersky is causing it. I've had it on my laptop for a bit over a year and my brother ahs had it on his custom desktop for about a year as well and nothings happened.
      My Computer


  10. Arc
    Posts : 35,373
    Microsoft Windows 10 Pro Insider Preview 64-bit
       #10

    luke1426 said:
    I really don't get why Kaspersky is causing it. I've had it on my laptop for a bit over a year and my brother ahs had it on his custom desktop for about a year as well and nothings happened.
    It is difficult to understand why it happens, but it happens. It is not a must that Kaspersky is to cause the same trouble in all the systems, but it causes issues in some.
      My Computer


 
Page 1 of 6 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 02:03.
Find Us