Getting a BSOD related to ntoskrnl.exe fairly often

Page 1 of 5 123 ... LastLast

  1. Posts : 23
    Windows 7 Home Premium 64bit.
       #1

    Getting a BSOD related to ntoskrnl.exe fairly often


    I've been getting this BSOD for about a month now, maybe a bit longer. Some days it's fine, other days it'll crash several times per day. I'm not sure if this is related, but recently I've been getting lag time on my restart. It'll take ~15 seconds after windows 7 starts up where it will hang on a black screen before letting me do anything. Normally this is instantaneous.

    I've noticed it most when I'm playing video games, specifically on the BYOND engine, but I'm not sure that's the cause. I'm not terribly opposed to doing an OSRI, but I'd like to avoid it if at all possible.

    I should mention that I recently upgraded my video card, motherboard, and graphics card, all of which shouldn't be causing problems. These problem didn't happen at all prior to the upgrade, though, so it could be a problem with the new drivers. Not 100% sure. Thanks.
      My Computer


  2. Posts : 2,781
    Windows 10 Pro x64
       #2

    Hiya and welcome to SevenForums!
    Code:
    BugCheck 3B, {c0000005, fffff80002dfc9cc, fffff8800aaa8ed0, 0}
    
    Probably caused by : Pool_Corruption ( nt!ExDeferredFreePool+100 )
    
    Followup: Pool_corruption
    Code:
    BugCheck 1E, {ffffffffc0000005, fffff88003044fb0, 0, 0}
    
    Unable to load image bflwfx64.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for bflwfx64.sys
    *** ERROR: Module load completed but symbols could not be loaded for bflwfx64.sys
    Probably caused by : bflwfx64.sys ( bflwfx64+f4eb )
    Code:
    BugCheck 3B, {c0000005, 20802068, fffff8800a1f7ba0, 0}
    
    Unable to load image 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
    Probably caused by : nvlddmkm.sys ( nvlddmkm+1e1d55 )
    Code:
    BugCheck 18, {fffffa800c767f30, fffffa801068eb50, 1, 1000000000000}
    
    Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+4874a )
    Code:
    BugCheck 1E, {0, 0, 0, 0}
    
    Unable to load image 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
    Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::UnreferenceDmaBuffer+7d )
    Code:
    BugCheck 3B, {c0000005, fffff880016343dd, fffff8800bc378b0, 0}
    
    Probably caused by : NETIO.SYS ( NETIO!NsiEnumerateObjectsAllParametersEx+24f )
    Code:
    BugCheck 50, {fffff260c0ac58f0, 0, fffff960000cde00, 7}
    
    
    Could not read faulting driver name
    Probably caused by : memory_corruption
    
    Followup: memory_corruption
    Code:
    BugCheck 3B, {c0000005, fffff80002c6cf37, fffff8800975bc10, 0}
    
    Probably caused by : ntkrnlmp.exe ( nt!AlpcpQueueIoCompletionPort+2c7 )
    Code:
    BugCheck 3B, {c0000005, fffff9600016e912, fffff8800d470080, 0}
    
    Probably caused by : win32k.sys ( win32k!DWP_GetEnabledPopup+3e )
    Run Display Driver Uninstaller(DDU)
    Make sure you tick the Uninstall C:/AMD and C:/NIVIDA folders while you are in DDU when you are done running DDU install your graphics driver again. This is the guide for DDU: Display Driver Uninstaller: How to use


    Run sfc /scannow and chkdsk /r.
    Install the latest updates from Windows Update.

    Do the exact same steps for chkdsk /r but instead of typing in sfc /scannow type chkdsk /r.

    SFC /SCANNOW Command - System File Checker

    Run MemTest86+, it must be MemTest86+ for 8 passes. RAM - Test with Memtest86+

    Update your DirectX drivers.

    Update your Bigfoot Networks Bandwidth Control Wireless NDIS Light Weight Filter driver.
      My Computer


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

    Alrighty, I used DDU to uninstall my video card drivers and reinstalled them, ran system file checker and chkdsk, both of which were fine. I ran memtest86+ for 8 passes, roughly 16 hours, couldn't update my directx drivers as they're already up to date, and I installed the Killer network suite, which should fix the Bigfoot Networks Bandwidth Control Wireless NDIS Lightweight Filter driver issue. Time to see if this works.
      My Computer


  4. Posts : 2,781
    Windows 10 Pro x64
       #4

    Okay.
      My Computer


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

    Just got another one today.

    Edit: Make that two within an hour.
    Last edited by Reyjakai; 29 Jul 2015 at 16:29.
      My Computer


  6. Posts : 2,781
    Windows 10 Pro x64
       #6

    Hmm,
    Code:
    BugCheck 3B, {c0000005, fffff960001053f1, fffff8800a261f50, 0}
    
    Probably caused by : win32k.sys ( win32k!GreGetBounds+6d )
    Code:
    BugCheck 3B, {c0000005, fffff80002cce416, fffff8800cbfee50, 0}
    
    Probably caused by : memory_corruption
    
    Followup: memory_corruption
    Still memory corruption, did MemTest86+ pass?
      My Computer


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

    Yeah, I ran it for 8 passes without any errors.
      My Computer


  8. Posts : 2,781
    Windows 10 Pro x64
       #8

    Was it MemTest86+ or MemTest86?
      My Computer


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

    It was Memtest86+. Version 5.01, the one from Memtest86+ - Advanced Memory Diagnostic Tool.
      My Computer


  10. Posts : 2,781
    Windows 10 Pro x64
       #10

    Hmm, did any CD:s come with your 60GB SSD?
      My Computer


 
Page 1 of 5 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 04:32.
Find Us