Windows 10: Random BSODs with various bug checks, possibly a driver is at fault.

Discus and support Random BSODs with various bug checks, possibly a driver is at fault. in Windows 10 BSOD Crashes and Debugging to solve the problem; For the past few days someone I know has been getting various bsods at random times. Whether it be sitting idle or playing a game. I've been using... Discussion in 'Windows 10 BSOD Crashes and Debugging' started by Goobert, Dec 19, 2015.

  1. Goobert Win User

    Random BSODs with various bug checks, possibly a driver is at fault.


    For the past few days someone I know has been getting various bsods at random times. Whether it be sitting idle or playing a game.
    I've been using teamviewer and I have been trying to figure out what the deal is for a few days now and I can't figure out what's going on here.
    I've never looked into blue screens so much in my life before this and I've just about given up.
    From what I've gathered, this could possibly be a bad driver since this is a Windows 10 upgrade from a Windows 8.1, but I can't figure out how to identify it.
    It started happening after a blue screen while playing a game. The computer itself is a prebuilt.
    The bsod checkers I've used consistently point to ntoskrnl.exe being the reason for it. But I've gotten WDFLDR.sys, hal.dll, HDAudBus.sys and such along with it. However they have not appeared since (I've been trying to fix them by updating various drivers).
    We've been fine for the past 2 days, then it happened again 3 times. A fourth time recently when I tried using that Dm Log Collector (and the computer was idle for hours just fine).
    Can anyone point out any suspicious drivers that I should uninstall or update? Or perhaps any other issues?


    :)
     
    Goobert, Dec 19, 2015
    #1

  2. Random BSOD's - Multiple Bug Checks

    HI Robert.

    I'm also receiving this issue when I load a game called Phantasy Star Online 2. I upgraded my system to Windows 10 and of all the games i play this is the first one to do this.

    I get the error message on ntoskrnl.exe+14dd00 thats the address its hit 3 times now.

    I attempted to update the game to see if this resolved the issue. As my system runs 4 1tb HDD in Raid i don't want them to corrupt with continues crashes.

    I plan to upgrade my graphics card soon and was hoping to hold out till i buy it to format the machine and start again. I think what i will test in the mean time is reinstalling the full game. I believe
    the crashes are directly related to bad drivers since the upgrade. Hopefully if this is a known issue with Windows 10 then it will be looked at.

    I always found it best to do a clean install of a OS rather than upgrading so that would be my suggestion to you. Did you upgrade from Windows 7 or 8?
     
    Robert Liam Whyte 2020, Dec 19, 2015
    #2
  3. Random BSOD's - Multiple Bug Checks

    Overview:

    I have been experiencing many BSODs. These can happen at random and sometimes in high intensive video games. I say again sometimes because this can happen when just browsing the web. Many different Bug checks
    have appeared so instead of posting every one I will post one of each.

    Tests I have tried:

    At first I thought that my computer had bad hardware and as so I tried many tests and solutions. I did Windows memtest three separate times. Every time it was fine. I tried 3D Mark to test if it could possible
    be the graphics card, the computer got through the first test no problem (which was with no SLI - see specs below) but the second time I tried it with SLI the computer crashed. I thought it might be the SLI bridge. Replacing it with a spare solved the issue
    when I ran it the second time. I still suspect is might be the second graphics card though as sometimes the display driver crashes and recovers within two second. Still not sure.

    Specifications:

    • i7 4770k
    • 2x GTX 780 ti in SLI
    • Asus Hero VII
    • 2 Samsung SSD's (250 and 500 GB) Both are EVO
    • 4 TB Western Digital Black Hard Drive
    • 1200 W Corsair power supply
    Bug Checks:

    1.

    081615-7171-01.dmp 8/16/2015 7:28:37 PM PAGE_FAULT_IN_NONPAGED_AREA
    0x00000050 fffff802`f9c5b140 00000000`00000010
    fffff802`f9c5b140 00000000`00000002 NTFS.sys
    NTFS.sys+e29d NT File System Driver Microsoft® Windows® Operating System
    Microsoft Corporation 10.0.10240.16384 (th1.150709-1700)
    x64 ntoskrnl.exe+14dd00 C:\WINDOWS\Minidump\081615-7171-01.dmp
    8 15 10240 373,816 8/16/2015 7:29:21 PM

    2.

    081615-7906-01.dmp 8/16/2015 4:28:24 PM SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
    0x1000007e ffffffff`c0000005 fffff800`802969c1
    ffffd000`260d37c8 ffffd000`260d2fe0 ntoskrnl.exe
    ntoskrnl.exe+21a9c1 NT Kernel & System Microsoft® Windows® Operating System
    Microsoft Corporation 10.0.10240.16430 (th1.150807-2049)
    x64 ntoskrnl.exe+21a9c1 C:\WINDOWS\Minidump\081615-7906-01.dmp
    8 15 10240 384,056 8/16/2015 4:29:23 PM

    3.

    081515-6906-01.dmp 8/15/2015 11:08:49 AM IRQL_NOT_LESS_OR_EQUAL
    0x0000000a 00000000`0007afb8 00000000`00000002
    00000000`00000000 fffff803`857ac4df ntoskrnl.exe
    ntoskrnl.exe+14dd00 NT Kernel & System Microsoft® Windows® Operating System
    Microsoft Corporation 10.0.10240.16430 (th1.150807-2049)
    x64 ntoskrnl.exe+14dd00 C:\WINDOWS\Minidump\081515-6906-01.dmp
    8 15 10240 372,960 8/15/2015 11:10:47 AM

    4.

    081315-8171-01.dmp 8/13/2015 5:53:30 PM UNEXPECTED_KERNEL_MODE_TRAP
    0x0000007f 00000000`00000008 ffffd001`27eb2b30
    ffffd000`22f70ed0 fffff803`2c88db69 x64
    C:\WINDOWS\Minidump\081315-8171-01.dmp 8 15
    10240 379,824 8/13/2015 5:54:20 PM

    5.

    081215-6875-01.dmp 8/12/2015 7:19:42 PM SYSTEM_SERVICE_EXCEPTION
    0x0000003b 00000000`c0000005 fffff801`d35f32b2
    ffffd000`222859f0 00000000`00000000 debutfilterx64.sys
    debutfilterx64.sys+32b2 x64 ntoskrnl.exe+14dd00
    C:\WINDOWS\Minidump\081215-6875-01.dmp 8 15
    10240 368,152 8/12/2015 7:20:17 PM

    6.

    081115-6781-01.dmp 8/11/2015 9:29:49 PM DRIVER_OVERRAN_STACK_BUFFER
    0x000000f7 00002a80`20d2c3e0 00004e3f`03799308
    ffffb1c0`fc866cf7 00000000`00000000 ntoskrnl.exe
    ntoskrnl.exe+14dd00 NT Kernel & System Microsoft® Windows® Operating System
    Microsoft Corporation 10.0.10240.16430 (th1.150807-2049)
    x64 ntoskrnl.exe+14dd00 C:\WINDOWS\Minidump\081115-6781-01.dmp
    8 15 10240 372,408 8/11/2015 9:30:22 PM

    7.

    081015-6750-01.dmp 8/10/2015 8:28:44 AM PAGE_FAULT_IN_NONPAGED_AREA
    0x00000050 ffffe002`049e8008 00000000`00000000
    fffff800`13d7608d 00000000`00000000 filecrypt.sys
    filecrypt.sys+9922570a Windows sandboxing and encryption filter
    Microsoft® Windows® Operating System Microsoft Corporation
    10.0.10240.16384 (th1.150709-1700) x64 ntoskrnl.exe+14d220
    C:\WINDOWS\Minidump\081015-6750-01.dmp 8 15
    10240 372,024 8/10/2015 8:29:23 AM

    Any help is much appreciated thank you!
     
    Robert Donoghue, Dec 19, 2015
    #3
  4. axe0 New Member

    Random BSODs with various bug checks, possibly a driver is at fault.

    Hi Goobert,

    Welcome to the 10forums.

    What has been tried to solve the bluescreens?
    Could you provide some description of what happens when the crash occurs and what you/this person is/are doing?

    Please check Realtek for driver updates for the Realtek network drivers
    Driver Reference Table - rt640x64.sys
    Code: ffffd000`21613830 fffff800`a79897d0Unable to load image \SystemRoot\System32\drivers\rt640x64.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for rt640x64.sys *** ERROR: Module load completed but symbols could not be loaded for rt640x64.sys rt640x64+0x197d0 2: kd> lmvm rt640x64 start end module name fffff800`a7970000 fffff800`a7a55000 rt640x64 T (no symbols) Loaded symbol image file: rt640x64.sys Image path: \SystemRoot\System32\drivers\rt640x64.sys Image name: rt640x64.sys Timestamp: Thu Oct 01 12:34:33 2015 (560D0C39) CheckSum: 000F03D5 ImageSize: 000E5000 Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4[/quote] Please uninstall everything of Nvidia using Display Driver Uninstaller and install new drivers from Nvidia. Be sure the clean install box is checked and only install the Graphics driver and the PhysX driver.
    Attachment 54564
    Code: ffffd000`223f3a18 fffff800`97513189Unable 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+0x1c3189 2: kd> lmvm nvlddmkm start end module name fffff800`97350000 fffff800`97e47000 nvlddmkm T (no symbols) Loaded symbol image file: nvlddmkm.sys Image path: \SystemRoot\system32\DRIVERS\nvlddmkm.sys Image name: nvlddmkm.sys Timestamp: Tue Nov 24 19:15:37 2015 (5654A949) CheckSum: 00ABBCF5 ImageSize: 00AF7000 Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4[/quote]



    Random BSODs with various bug checks, possibly a driver is at fault. [​IMG]
    Diagnostic Test
    Random BSODs with various bug checks, possibly a driver is at fault. [​IMG]
    RAM TEST

    Random BSODs with various bug checks, possibly a driver is at fault. [​IMG]
    Run MemTest86+ - Test RAM - Windows 10 Forums


    Random BSODs with various bug checks, possibly a driver is at fault. [​IMG]
    Note
    Random BSODs with various bug checks, possibly a driver is at fault. [​IMG]


    MemTest86+ needs to be run for at least 8 passes for conclusive results. Set it running before you go to bed and leave it overnight. We're looking for zero errors here. Even a single error will indicate RAM failure.
    Code: Probably caused by : memory_corruption[/quote]
    Please fill in the system specs of this person you are trying to help, can I call him/her your friend or how may I call him/her?
    Please follow this tutorial and download the tool. The tool will give you detailed information about your system specs, please fill in your system specs more completely.How to fill in your system specs:

    Random BSODs with various bug checks, possibly a driver is at fault. [​IMG]


    Random BSODs with various bug checks, possibly a driver is at fault. [​IMG]
     
  5. Goobert Win User
    Please uninstall everything of Nvidia using Display Driver Uninstaller and install new drivers from Nvidia. Be sure the clean install box is checked and only install the Graphics driver and the PhysX driver.

    Code: ffffd000`223f3a18 fffff800`97513189Unable 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+0x1c3189 2: kd> lmvm nvlddmkm start end module name fffff800`97350000 fffff800`97e47000 nvlddmkm T (no symbols) Loaded symbol image file: nvlddmkm.sys Image path: \SystemRoot\system32\DRIVERS\nvlddmkm.sys Image name: nvlddmkm.sys Timestamp: Tue Nov 24 19:15:37 2015 (5654A949) CheckSum: 00ABBCF5 ImageSize: 00AF7000 Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4[/quote]
    Please fill in the system specs of this person you are trying to help, can I call him/her your friend or how may I call him/her?[/quote] Thanks for the very thorough guide on fixing this. The two drivers you posted and the ways of updating them are exactly what I needed and I'll give them a shot as soon as the computer is available. I'll also post the specs later.

    To attempt to fix this, I figured Realtek was messing something up, so I updated any drivers related to it, as well as the network adapter as those seem to commonly cause crashes. However this didn't seem to fix the issue.

    Code: Driver Reference Table - rt640x64.sys[/quote] I didn't use this link to find the drivers, so I'll try this one instead, as well as that Windows driver updater.

    Code: Display Driver Uninstaller Download version 17.0.8.6 The person said they uninstalled the Nvidia drivers and reinstalled, but I don't think they did it as clean as this tool. I'll give this a go as well.

    There's no consistency with the crashes. The computer could crash within minutes of starting up, or within hours of staying idle or gaming. The crashes also seemed to stop for a few days before returning like usual.
     
    Goobert, Dec 20, 2015
    #5
  6. axe0 New Member
    With Windows driver update you mean what exactly? Device manager?
     
  7. Goobert Win User
    Wow, I honestly have no idea. I swear there was a link in that post to some driver updating program but I don't see it there now.
    But it looked sketchy and I've heard about driver updater programs causing problems so I didn't do it.

    Working on the Nvidia display drivers and realtek drivers right now.


    Here are the system specs in the mean time.
     
    Goobert, Dec 20, 2015
    #7
  8. Goobert Win User

    Random BSODs with various bug checks, possibly a driver is at fault.

    Code: Win10 Auto Installation Program (SID:1779114)[/quote] This is what I chose to update for the Realtek network drivers. Is this correct? I already had this installed so the fact that it's outdated seems strange.

    I did a clean install of Nvidia's drivers as instructed.
     
    Goobert, Dec 20, 2015
    #8
  9. axe0 New Member
    Please put the system specs in your 'My System Specs', that way it is easier for everyone to check them.
    Below in every post on the left side, there you can find 'My System Specs'. If you click on it with your post, you see the option 'Update your System Specs', click on it and you will get to the page where you can update your system specs.

    I only add the time for comparisation, it doesn't mean the drivers are outdated.
    Sometimes a reinstallation of a driver helps, because a driver may have become corrupted.
     
  10. Goobert Win User
    Alright I added the specs of the computer.

    Doing a full reinstall of the Nvidia Drivers has helped the computer last a lot longer until a blue screen (about 5-6 hours).

    However it's still happening. I re did the Log DM Collector Tool with the new crashes.
     
    Goobert, Dec 21, 2015
    #10
  11. axe0 New Member
    What are the settings of driver verifier?
     
  12. Goobert Win User
    Here's everything in Driver Verifier. Is this what you need?
     
    Goobert, Dec 22, 2015
    #12
  13. axe0 New Member

    Random BSODs with various bug checks, possibly a driver is at fault.

    Yes, next question would be how you come with those settings?
     
  14. Goobert Win User
    I followed some video on youtube, apparently there's more to do than just the automatic settings lol.

    I did it again except this time I checked the settings I/O verification, Force Pending I/O Requests and IRP Logging. Then I chose all the drivers except Microsoft ones.
    There hasn't been a crash yet under these settings.
     
    Goobert, Dec 23, 2015
    #14
  15. axe0 New Member
    *Thumbs
    I'll post my standard driver verifier post in case you need some info





    Random BSODs with various bug checks, possibly a driver is at fault. [​IMG]
    Diagnostic Test
    Random BSODs with various bug checks, possibly a driver is at fault. [​IMG]
    DRIVER VERIFIER

    Random BSODs with various bug checks, possibly a driver is at fault. [​IMG]
    Warning Please make a backup of your important files and get your rescue media or create one.
    Please create a restore point.
    Please follow this tutorial to run driver verifier.

    Some windows drivers are blamed in a few crashes, but that usually means that a 3rd party driver is actually the cause.
    Driver verifier stresses your drivers and will crash your pc if any driver fails due to a violation.

    Driver verifier should be performed for a max of 48 hours, or when you have a bluescreen, whatever comes first.

    If driver verifier has found a violation and you can't get back into windows normally, try to boot into safe mode and reset in safe mode driver verifier, or in the troubleshooting options open command prompt and type verifier /reset.


    Random BSODs with various bug checks, possibly a driver is at fault. [​IMG]
    Note Your system will act very sluggishly while driver verifier is enabled, this is normal as your drivers will be being subjected to heavy testing in order to make them crash.
     
Thema:

Random BSODs with various bug checks, possibly a driver is at fault.

Loading...
  1. Random BSODs with various bug checks, possibly a driver is at fault. - Similar Threads - Random BSODs various

  2. BSOD Bug Check

    in Windows 10 Gaming
    BSOD Bug Check: Hello,i got for the first time a bluescreen and now im a bit worried what just happend if something is broke:i played valorant some time, and after that i closed the game and played one fall guys match, i also closed after that fall guys and instanly got a bluescreen.Here:For...
  3. BSOD Bug Check

    in Windows 10 Gaming
    BSOD Bug Check: hello, i have been having issues with my pc restarting itself every once in a while. i replaced the memory roughly a year ago and this did not resolve the issues. i will provide specs as well and minidumps. i also analyzed the memory.dmp file and ran verifier to see which...
  4. BSOD Bug Check

    in Windows 10 Software and Apps
    BSOD Bug Check: hello, i have been having issues with my pc restarting itself every once in a while. i replaced the memory roughly a year ago and this did not resolve the issues. i will provide specs as well and minidumps. i also analyzed the memory.dmp file and ran verifier to see which...
  5. Ntoskrnl.exe bsod with various bug check strings

    in Windows 10 BSOD Crashes and Debugging
    Ntoskrnl.exe bsod with various bug check strings: Hello, I've been experiencing BSODs and noticed on BlueScreenView that the issues I have mostly come from ntoskrnl.exeI've tried SFC it had a problem but was already fixed according to CMD and Memory Diagnostic which showed no errors in Event Viewer. I seriously do not know...
  6. Ntoskrnl.exe bsod with various bug check strings

    in Windows 10 Gaming
    Ntoskrnl.exe bsod with various bug check strings: Hello, I've been experiencing BSODs and noticed on BlueScreenView that the issues I have mostly come from ntoskrnl.exeI've tried SFC it had a problem but was already fixed according to CMD and Memory Diagnostic which showed no errors in Event Viewer. I seriously do not know...
  7. Ntoskrnl.exe bsod with various bug check strings

    in Windows 10 Software and Apps
    Ntoskrnl.exe bsod with various bug check strings: Hello, I've been experiencing BSODs and noticed on BlueScreenView that the issues I have mostly come from ntoskrnl.exeI've tried SFC it had a problem but was already fixed according to CMD and Memory Diagnostic which showed no errors in Event Viewer. I seriously do not know...
  8. Random BSOD - Bug Check 0x133 DPC_WATCHDOG_VIOLATION

    in Windows 10 BSOD Crashes and Debugging
    Random BSOD - Bug Check 0x133 DPC_WATCHDOG_VIOLATION: Hi all My PC has Windows 10 20H2, and randomly shows BSOD with the exact same error DPC_WATCHDOG_VIOLATION Some snippets of my errors: ******************************************************************************* *...
  9. Random BSOD On Burst With Different Bug Check

    in Windows 10 BSOD Crashes and Debugging
    Random BSOD On Burst With Different Bug Check: Hi, recently, I have been getting random BSOD on a burst. The laptop would randomly crashes one time and crashes again soon later, and then goes on working fine for the next 4 - 5 days without issues. Then after a period of time it would happen again. I have ran checkdisk...
  10. BSOD Bug Check

    in Windows 10 BSOD Crashes and Debugging
    BSOD Bug Check: Ever since I installed the Windows 10 1903 update last 6/19/19 my Windows 10 Professional computer has started crashing seemingly at random and always displaying the same BSOD stopCode: ATTEMPTED_WRITE_TO_READONLY_MEMORY (be) Before I installed the aforementioned update, I...