yet another BSOD attack

Page 2 of 4 FirstFirst 1234 LastLast

  1. Posts : 19,383
    Windows 10 Pro x64 ; Xubuntu x64
       #11

    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 1A, {41284, afd4001, 665b, fffff70001080000}
    
    Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+4ad3 )
    
    Followup: MachineOwner
    ---------
    This one is inconclusive. It doesn't point to Kaspersky directly, but it could be triggered by the earlier Kaspersky problem.

    I understand your reluctance to abandon a paid product. Kaspersky isn't alone in triggering BSOD's - I have seen the same issue with AVG, Avast (very common here because its so widely used), Symantec (Norton), Bitdefender and even Avira. There are many systems that have one of these and never experience BSOD's - why that is, I cannot say.

    I think because anti-malware products tend to be intrusive by nature, the Windows system files tend to be sensitive to that behaviour. Perhaps if 3rd party anti-malware products can be set-up less 'aggressively' they may not trigger BSOD's.

    The only product that we have never seen cause BSOD's here, is MSE, but that makes sense because both it and the OS are products of the same company.
      My Computer


  2. Posts : 21
    Windows 7 home premium x64
    Thread Starter
       #12

    that makes perfect sense actually. Thanks again for the help! Will wait for a day or two to see if any more BSOD occur and mark as solved if not.
      My Computer


  3. Posts : 19,383
    Windows 10 Pro x64 ; Xubuntu x64
       #13

    No worries. If you experience BSOD's in that time, just post them here and we'll have a look.
      My Computer


  4. Posts : 21
    Windows 7 home premium x64
    Thread Starter
       #14

    I've unfortunitly just encountered another BSOD attack and attached the new .dmp file. I will re-activate verifier to try and get more data once again.
      My Computer


  5. Posts : 19,383
    Windows 10 Pro x64 ; Xubuntu x64
       #15

    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck D1, {ffffffffffffff8f, 6, 1, fffff8800f1ccf70}
    
    *** WARNING: Unable to verify timestamp for nvlddmkm.sys
    *** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
    Probably caused by : hardware ( nvlddmkm+103f70 )
    
    Followup: MachineOwner
    ---------
    Try updating the Nvidia display driver from here:
    Drivers - Download NVIDIA Drivers
      My Computer


  6. Posts : 21
    Windows 7 home premium x64
    Thread Starter
       #16

    I seem to already be on the latest version of the driver. I will try various older versions and see if it fixes the problem.
      My Computer


  7. Posts : 21
    Windows 7 home premium x64
    Thread Starter
       #17

    I have tried an older version of the driver and still received several BSOD attacks. I have uploaded the new .dmp files to make sure that they also point to the same error.
      My Computer


  8. Posts : 19,383
    Windows 10 Pro x64 ; Xubuntu x64
       #18

    Code:
    fffff880`03046718  fffff800`02ed1c84 nt!KeBugCheckEx+0x104
    fffff880`03046720  fffff880`050bc000*** WARNING: Unable to verify timestamp for nvlddmkm.sys
    *** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
     nvlddmkm+0x85e000
    Yes, it looks like the same problem. Lets back out to the last known stable driver.

    Lets revert to the 314.22 WHQL driver only. Uninstall the following Nvidia items in Control Panel > Programs and Features:

    - 3D Vision Control Driver
    - 3D Vision Driver
    - Graphics Driver
    - HD Audio Driver
    - PhysX
    - Nvidia Update

    Now follow Drivers - Clean Left over Files after Uninstalling
    Reboot. Go to http://www.nvidia.in/Download/index.aspx?lang=en-in, Download 314.22 WHQL. While installing, Select Custom (Advanced) install. In the next page, follow this settings:



    Reboot. Use system as normal.
      My Computer


  9. Posts : 21
    Windows 7 home premium x64
    Thread Starter
       #19

    I have the GTX 770 which was released after the 314.22 driver therefore it is not available for it unless modifying the .inf file from what i have gathered. I have tried the 320.18 driver and got a BSOD error but i was still running driver verifier when that occured.
      My Computer


  10. Posts : 19,383
    Windows 10 Pro x64 ; Xubuntu x64
       #20

    OK. Try running with verifier off for now please. Monitor temperatures closely and report on those please. You can use Speccy for that.

    Speccy - System Information - Free Download
      My Computer


 
Page 2 of 4 FirstFirst 1234 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 17:10.
Find Us