BSOD: ntsokrnl.exe(+more) - happens randomly

Page 3 of 4 FirstFirst 1234 LastLast

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

    Not getting any adequate reason for the BSODs. All the drivers are failing here are the latest versions. The display driver (ATI driver this time, next to latest version) and the intel XHCI driver (latest version).

    Suggesting you some common steps ....

    Scan the system for possible virus infection with the following programs.


    Are you overclocking? As you are getting BSODs, you should stop overclocking and run all the hardware components like CPU, GPU and RAM to their default settings. Also set the BIOS to default, too.
    How To Clear CMOS (Reset BIOS)

    Test your RAM modules for possible errors.
    How to Test and Diagnose RAM Issues with Memtest86+
    Run memtest for at least 8 passes, preferably overnight.

    Is the computer hot? Report us the heat of the computer after a couple of hours of your normal usage. Upload a screenshot of the summery tab of Speccy.

    Let us know the results.
      My Computer


  2. Posts : 22
    Windows 7 Home Premium 64bit
    Thread Starter
       #22

    both virus scanners found nothing. overclocking nothing. I reset cmos. memtest cleared 7.5 passes over 10 hours last week, but i'll run it again tonight. temps were at/below average yesterday but I'll keep an eye on them today.

    if this is a hardware issue where do you think is the best place to start?
      My Computer


  3. Posts : 22
    Windows 7 Home Premium 64bit
    Thread Starter
       #23

    I updated the intel chipset drivers(two?) days ago, and after that the problems seemed to have stopped. Today I got an all too familiar BSOD and I was kind of sad.

    temps for everything are fine, memtest ran 8 passes with 0 errors
      My Computer


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

    The BSOD is caused by the latest version of the display driver.
    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck D1, {0, b, 8, 0}
    
    *** WARNING: Unable to verify timestamp for nvlddmkm.sys
    *** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
    Probably caused by : nvlddmkm.sys ( nvlddmkm+18d968 )
    
    Followup: MachineOwner
    ---------
    Earlier I suggested you to use that version, but as it is causing the issues there, I would suggest you to uninstall the installed version of display driver totally, as suggested earlier; and then install 314.22 WHQL.
      My Computer


  5. Posts : 22
    Windows 7 Home Premium 64bit
    Thread Starter
       #25

    oh when I put in my gpu again(switched out old for new) I guess I just auto piloted and put in the newest drivers

    with that said skype was randomly using 30% of my cpu ALL the time and I didn't notice it. I updated it and now it's using less than 1%.. so that's cool.
      My Computer


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

    If it BSODs again with the latest version auto installed again, we will have a look.
      My Computer


  7. Posts : 22
    Windows 7 Home Premium 64bit
    Thread Starter
       #27

    reverted back to 314.22 WHQL drivers and went about 4 full days without a blue screen. this crash happened while playing league of legends for about 2-3 hours. temps were fine(ive been monitoring them like a hawk).

    =(
      My Computer


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

    Something very expected.
    Code:
    BugCheck D1, {0, 2, 1, fffff8800165aea1}
    
    *** WARNING: Unable to verify timestamp for bflwfx64.sys
    *** ERROR: Module load completed but symbols could not be loaded for bflwfx64.sys
    *** WARNING: Unable to verify timestamp for e22w7x64.sys
    *** ERROR: Module load completed but symbols could not be loaded for e22w7x64.sys
    Probably caused by : hardware ( bflwfx64+2c65 )
    
    Followup: MachineOwner
    ---------
    Bigfoot Networks Bandwidth Control Wireless NDIS Light Weight Filter driver causes issues, which is included in Killer. Search in http://www.killergaming.com/support/...ad_type=1&os=7 for any update and see if it helps. Pay due attention to this part there ......
    NOTE: If you are coming from Version 1 software (6.1.x.x), this software will require you to uninstall your current version. You may see several entries for Qualcomm Atheros software in your Programs list. You need only uninstall QUALCOMM ATHEROS PERFORMANCE SUITE. This will uninstall all other entries.
      My Computer


  9. Posts : 22
    Windows 7 Home Premium 64bit
    Thread Starter
       #29

    hal.dll bluescreen happened with just minecraft running.

    nvlddmkm.sys happened while I was asleep. I had the computer locked(windows+L), no gpu demanding programs running at all.
      My Computer


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

    Code:
    Unable to load image \SystemRoot\system32\DRIVERS\nvlddmkm.sys, Win32 error 0n2
    *** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck F7, {2b99021e8a41, 2b992ddfa232, ffffd466d2205dcd, 0}
    
    Probably caused by : nvlddmkm.sys ( nvlddmkm+1769d6 )
    
    Followup: MachineOwner
    ---------
    The display driver is crashing over any version .... so it is to be checked deeply now.

    Stress test the Graphics Card using Furmark.
    Video Card - Stress Test with Furmark

    Test your RAM modules for possible errors.
    How to Test and Diagnose RAM Issues with Memtest86+
    Run memtest for at least 8 passes, preferably overnight.

    Stress test the CPU.
    Hardware - Stress Test With Prime95

    Is the computer hot? Report us the heat of the computer after a couple of hours of your normal usage. Upload a screenshot of the summery tab of Speccy.

    Check if the Power Supply Unit (PSU) supplying adequate power to the computer or not.
    eXtreme Power Supply Calculator
    Also let us know about the wattage of the PSU.

    The Bugcheck code (Stop 0xF7) itself indicates to malware. Scan the system for possible virus infection with the following programs, again.


    If all failed, I'd recommend you to Consider a Clean Reinstall - Factory OEM Windows 7

    Let us know the results.
    Motherboard next: Z87-GD65 GAMING (MS-7845)



      My Computer


 
Page 3 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 04:14.
Find Us