Windows 10: Windows Driver Verifier BSOD

Discus and support Windows Driver Verifier BSOD in Windows 10 BSOD Crashes and Debugging to solve the problem; So I have an old Alienware Aurora R1 and after about 5 years the liquid cooling tube burst and fried the motherboard. I figured it was time for an... Discussion in 'Windows 10 BSOD Crashes and Debugging' started by Metaphorce, Nov 24, 2015.

  1. Windows Driver Verifier BSOD


    So I have an old Alienware Aurora R1 and after about 5 years the liquid cooling tube burst and fried the motherboard. I figured it was time for an upgrade anyway, but I liked the case and didn't want to buy a new PC. So I got an ASRock Z97M Pro4 with an Intel Core-i5 4690K. I tried overclocking it and I would leave prime95 v26.6 running and it would be fine... until I came back and woke up the monitor. Then I'd get a BSOD (my first sign that it was something video card related). I'm still using the nvidia Geforce GTX 260 that came with the original PC because I don't really use it for gaming. After having other un-related problems, I formatted my system drive and did a fresh install of Windows 10. I tried to install the most recent drivers (v341.92), but Windows Update wasn't having that and replaced it with v341.74 (really not a fan of these mandatory "updates"). I reset the BIOS to the initial, un-overclocked configuration. Then I ran Driver Verifier and it immediately gave me a BSOD. I looked at the crash dump and I'm pretty sure the BSODs are video card-related, but I have no idea what the exact problem is or how to fix it. I haven't been getting BSODs except when running Driver Verifier or when overclocking my CPU. I've attached the minidump generated by driver verifier in the hopes that someone here can figure out how to fix this. Thanks.

    :)
     
    Metaphorce, Nov 24, 2015
    #1
  2. XP ROCKS. Win User

    Driver Verifier shows BSOD with "Driver Verifier Detected Violation" but doesn't create dump file

    Swap the mouse out.
     
    XP ROCKS., Nov 24, 2015
    #2
  3. XP ROCKS. Win User
    Driver Verifier shows BSOD with "Driver Verifier Detected Violation" but doesn't create dump file

    "That's weird because the crash occured after rebooting with driver verifier
    (I didn't have any other BSOD today). I guess I will check it tomorrow and see if dmp changes. Thanks for now <3

    BUGCHECK_STR: 0x3B

    PROCESS_NAME: bootim.exe<== Boot immersive menu

    CURRENT_IRQL: 0

    ANALYSIS_SESSION_HOST: GLOOMY

    The error is probably transient in nature, but you never can tell when it might re-occur or how bad it might be, the next time around.... fwiw.
     
    XP ROCKS., Nov 24, 2015
    #3
  4. axe0 New Member

    Windows Driver Verifier BSOD

    Hi Metaphorce,

    Welcome to the 10forums.

    Please uninstall everything of Nvidia graphics 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: ffffd001`fc34cf88 fffff800`545f02c0Unable to load image \SystemRoot\system32\DRIVERS\nvlddmkm.sys, Win32 error 0n2 *** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys nvlddmkm+0x2c0 2: kd> lmvm nvlddmkm start end module name fffff800`545f0000 fffff800`55289000 nvlddmkm (no symbols) Loaded symbol image file: nvlddmkm.sys Image path: \SystemRoot\system32\DRIVERS\nvlddmkm.sys Image name: nvlddmkm.sys Timestamp: Mon Jun 29 21:13:29 2015 (559198D9) CheckSum: 00C4F3E2 ImageSize: 00C99000 Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4[/quote]
     
  5. [/quote] On my last Windows 10 installation, I tried using DDU and installing the 341.92 driver (just the graphics and PhysX) and after I was finished Windows Update automatically installed 341.74.
    This time after running DDU when I tried to install the 341.92 driver it just said "Installation Failed" and gave no other information (super helpful). I retried running it as an administrator and running it in compatibility mode and it still failed. So I tried completely removing the video card from my system (I'm currently using the Intel HD Graphics 4600 built into my motherboard) and then running Driver Verifier again. And it immediately gave me the BSOD with the "DRIVER_VERIFIER_DETECTED_VIOLATION" error again. So I've attached that crash dump.
     
    Metaphorce, Nov 30, 2015
    #5
  6. axe0 New Member
    Why exactly are you enabling driver verifier?
    It shouldn't been needed unless it is for developing or there can't be any driver found.
     
  7. axe0 New Member
    If I'm correct, a WinTV USB tuner driver has been flagged
    Driver Reference Table - hcw89.sys
    Please update the drivers for it.
    Code: ffffd001`0d10ef88 fffff800`059701f8Unable to load image \SystemRoot\system32\DRIVERS\hcw89.sys, Win32 error 0n2 *** ERROR: Module load completed but symbols could not be loaded for hcw89.sys hcw89+0x1f8 3: kd> lmvm hcw89 start end module name fffff800`05970000 fffff800`05af8080 hcw89 (no symbols) Loaded symbol image file: hcw89.sys Image path: \SystemRoot\system32\DRIVERS\hcw89.sys Image name: hcw89.sys Timestamp: Tue Jul 10 16:53:40 2012 (4FFC41F4) CheckSum: 001960F8 ImageSize: 00188080 Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4[/quote]
     
  8. Windows Driver Verifier BSOD

    I've been following the instructions in this thread. I started using driver verifier because I was getting BSODs when overclocking (I reset the BIOS to the defaults before I started debugging) at voltages/speeds that shouldn't have caused crashes. And since driver verifier keeps giving me a BSOD immediately when I start up that means there is a problem with one or more of my drivers.
    I have a Hauppauge WinTV-HVR-2250 installed in a PCI slot. Could that be the problem? I'm not even using it, so I could take it out and see if driver verifier gives me a BSOD. In the previous section of the crash dump you quoted earlier, it said that there was an error with the nvidia nvlddmkm.sys file. Do you think a problem with the WinTV tuner could somehow also mess up my graphics card?
     
    Metaphorce, Nov 30, 2015
    #8
  9. axe0 New Member
    I think the Hauppauge WinTV-HVR-2250 is the cause of the crashes and caused the nvidia driver to be flagged.
    That is for me how it looks like at the moment.
     
  10. So I installed the latest driver for the WinTV-HVR-2250 and ran driver verifier again. I've attached the new crash dump. This time - according to BlueScreenView.exe - dfx12x64.sys caused the BSOD. This is driving me crazy.
     
    Metaphorce, Dec 1, 2015
    #10
  11. I took the WinTV card out of my computer and ran driver verifier again but didn't have it check dfx12x64.sys. Still got an immediate BSOD which BlueScreenView reported as being caused by wdcsam64.sys. Ran driver verifier again and didn't have it check either of those two, this time I got a BSOD that BlueScreenView reported as being caused by rtwlanu.sys (I've included that crash dump - the previous one got deleted when I had to use system restore to disable driver verifier). Ran driver verifier again and excluded all 3 of those from the list of drivers to check and finally didn't get a BSOD. So what the heck does that mean? Driver verifier's given me BSODs for 5 different drivers now. I'm about to just give up and go back to Windows 7.
     
    Metaphorce, Dec 1, 2015
    #11
  12. axe0 New Member
    It simply means you need to update your drivers once in a while.

    I'll let ya know what drivers they are, later
     
  13. axe0 New Member

    Windows Driver Verifier BSOD

    rtwlanu.sys is from the Edimax AC1200 Wireless LAN USB adapter driver.
    With USB network drivers, it is strongly recommended to keep the drivers up to date.
    If there are no updates available, I suggest to not use the USB adapter while troubleshooting.
    Code: 1: kd> lmvm rtwlanu start end module name fffff800`91400000 fffff800`917b5000 rtwlanu T (no symbols) Loaded symbol image file: rtwlanu.sys Image path: \SystemRoot\System32\drivers\rtwlanu.sys Image name: rtwlanu.sys Timestamp: Mon Feb 16 07:42:38 2015 (54E1915E) CheckSum: 0039A1D7 ImageSize: 003B5000 Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4[/quote] dfx12x64.sys is the audio driver for DFX Audio Enhancer.
    Update the software of DFX Audio Enhancer.
    Code: 1: kd> lmvm dfx12x64 start end module name fffff800`89c70000 fffff800`89c7a000 dfx12x64 T (no symbols) Loaded symbol image file: dfx12x64.sys Image path: \SystemRoot\system32\drivers\dfx12x64.sys Image name: dfx12x64.sys Timestamp: Tue Aug 28 21:10:34 2012 (503D17AA) CheckSum: 00010BD9 ImageSize: 0000A000 Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4[/quote]
     
Thema:

Windows Driver Verifier BSOD

Loading...
  1. Windows Driver Verifier BSOD - Similar Threads - Driver Verifier BSOD

  2. driver verifier results bsod

    in Windows 10 BSOD Crashes and Debugging
    driver verifier results bsod: i keep gettings bsod with the error code whe_uncorrectable error i am preety sure its a driver issue because i ran alot of tests and everything seems fine i will link a one drive link with my specs and a minidump file of a driver verifier bsod....
  3. Troubleshooting BSODs with Driver Verifier

    in Windows 10 BSOD Crashes and Debugging
    Troubleshooting BSODs with Driver Verifier: Hello, I've been having all sorts for BSODs in the past few months. Not a while ago I went deep into finding out the root cause of those. I stress tested my CPU, GPU, PSU and RAM and found no errors, so I moved on to Windows' verifier. I ran the tool with all sorts of test,...
  4. bsod with driver verifier

    in Windows 10 Drivers and Hardware
    bsod with driver verifier: hello, so i have been experiencing some bsod, I've recently built a pc and installed windows 10 on a new ssd but here and there i would get a bsod around 3 a day mostly starts up again when i can sleep my pc or restart/shutoff ive gotten several errors such as ntoskrnl.exe...
  5. BSOD, Driver Verifier DMPS

    in Windows 10 Drivers and Hardware
    BSOD, Driver Verifier DMPS: I've been getting BSOD's recently so I ran through the walkthrough of doing Driver Verifier and getting the DMPS files and I don't know what to do now aside from upload them here. DMPS : https://1drv.ms/u/s!AjNELGZRwSGSh2_gmVIliIogHJq-?e=m5Zny8 System Information :...
  6. BSOD hidclass with driver verifier

    in Windows 10 Drivers and Hardware
    BSOD hidclass with driver verifier: memory. dmp hi:) I have tried to enable driver verifier to check the stability of my computer, and every time I have got this bsod correlated to "hidclass.sys". Some help? Thanks a lot...
  7. BSOD after Driver Verifier

    in Windows 10 BSOD Crashes and Debugging
    BSOD after Driver Verifier: Been trying to find out why my system was bogging down to a halt sometimes after I did the October Update a few days ago. Here is my original thread about the issue. Log: DESKTOP-BL497SV-(2019-02-26_20-18-10).zip 127883
  8. BSOD driver verifier analysis

    in Windows 10 BSOD Crashes and Debugging
    BSOD driver verifier analysis: I used the driver verifier to get a bsod to figure out which of my drivers is a problem. Can someone please analyze this dump and tell me what the problem is? Link PC specs if needed: OS Name: Microsoft Windows 10 Pro 10.0.17134 Build 17134 Processor: Intel(R)...
  9. Driver Verifier for a BSOD

    in Windows 10 BSOD Crashes and Debugging
    Driver Verifier for a BSOD: Hello, I used driver verifier to find out why i'm having freeze and BSOD, there is my DMP file, I hope someone can help me out https://1drv.ms/u/s!Ansh37cgsCUtiWNq5QmTy7pI3giE Thanks !...
  10. Driver Related BSOD - Driver Verifier

    in Windows 10 BSOD Crashes and Debugging
    Driver Related BSOD - Driver Verifier: I recently started a new job and was given a new Dell Laptop. I am having seemingly randomly BSOD issues. Some days it doesn't happen at all and some days it can happen up to ten times. I've got several BSOD errors (mainly CRITICAL PROCESS DIED). I believe it's a driver...