VIDEO_DXGKRNL_FATAL_ERROR Win 19043.1151 Ent

  1. Zardoc's Avatar
    Posts : 506
    Windows 10 Enterprise
       #1

    VIDEO_DXGKRNL_FATAL_ERROR Win 19043.1151 Ent


    Hi guys,

    I'm not the best at reading dmp files so here goes.
    I've been using the same video driver for some time (4 months) without a crash. Yesterday there was a small power surge and soon after the dumps began.

    I don't think that this is the problem because I have a top notch PSU. I restored an image and dmp happened again 5 minutes later.

    So I need your input. Uploaded dmp file.

    Thanks
    Last edited by Zardoc; 09 Aug 2021 at 10:12. Reason: Solved
      My Computer

  2. Zardoc's Avatar
    Posts : 506
    Windows 10 Enterprise
    Thread Starter
       #2

    Bump up Thanks
      My Computer

  3. bljr3's Avatar
    Posts : 2
    Windows 10Pro 21H1 19043.1151 64bit
       #3

    I'm running the same build and I've over the last few week have been noticing some glitches window would just disappear and app permissions changing ,. I thought it was me being a marron you know user error?
      My Computer

  4. Ghot's Avatar
    Posts : 15,701
    Win 10 Home 10.0.19044.1466 (x64) [21H2]
       #4

    Zardoc said:
    Bump up Thanks

    Just for starters I would run...

    sfc /scannow and Dism /Online /Cleanup-Image /RestoreHealth


    Then I would redo the vid card driver (any version).

    DDU Instructions - Nvidia
    1. Get this program, here: Display Driver Uninstaller (DDU) | Wagnardsoft ...get the latest version, and save it to your desktop.
    2. Get the Standard/Game Ready vid card driver here, use the Manual Search: Advanced Driver Search | NVIDIA ...save this to your desktop.
    Unhook the internet completely.
    3. Reboot into Safe Mode and run DDU (Display Driver Uninstaller) choose the "Highly Recommend Option", and just do what it tells you.
    4. After it's done, reboot to normal mode, then just double click the Nvidia driver to install. If it want's to reboot, let it.
    Rehook the internet.

      My Computer

  5. Zardoc's Avatar
    Posts : 506
    Windows 10 Enterprise
    Thread Starter
       #5

    Ghot said:
    Just for starters I would run...
    sfc /scannow and Dism /Online /Cleanup-Image /RestoreHealth
    Then I would redo the vid card driver (any version).

    Hi Ghot,
    Thanks for taking the time and the suggestions but I found the problem and I think a lot of us would have searched in and out, high and low to find it.
    I tried all those trouble shooting details before posting (btw DDU maker lives close to me )

    The problem happened the day before when there was a power surge in the city. I didn't make much of it because it was late at night and I let the system shut down by itself before going to bed.

    Next morning when going to my office the CPU fan was full throttle and that's when I saw I had a crash. I used the Windbg preview to read the dmp. I knew it was driver related but what was the cause ? So I did all the usual acrobatics that you suggested but couldn't fix the problem.

    That's when I decided to post here and ask the crash experts to see what they thought. Meanwhile, I kept on looking at all sorts of possibilities (the best is always to backtrack to remember what you did close to the crash) could be software, driver update etc.

    Then it dawned on me! Could it be that my surge equipment didn't fully protect the system? (I have a power pack and a really good PSU). So I thought, what if the card got a static shock of some sort ? So I turned off the system, unplugged everything and then removed the card swiped my fingers on the PCIe connector, reinstalled everything booted the system
    and, CRASH WAS GONE!!!

    The card had a static shock and just needed to be re seated.

    Problem solved So, boys and girls, keep this one in your troubleshooting tips because you never know what can happen.

    Thanks again GHOT for trying to help me out
      My Computer

  6. Ztruker's Avatar
    Posts : 13,727
    Windows 10 Pro X64 21H1 19043.1266
       #6

    What card are you talking about, the GPU?
      My Computers

  7. Zardoc's Avatar
    Posts : 506
    Windows 10 Enterprise
    Thread Starter
       #7

    Ztruker said:
    What card are you talking about, the GPU?
    ASUS Dual GeForce RTX™ 2070 OC edition 8GB GDDR6 Clock 1410 MHz Memory Clock 1750 MHz
      My Computer

  8. Ztruker's Avatar
    Posts : 13,727
    Windows 10 Pro X64 21H1 19043.1266
       #8

    Okay, thanks.
      My Computers

  9. Zardoc's Avatar
    Posts : 506
    Windows 10 Enterprise
    Thread Starter
       #9

    You're welcome.
      My Computer

  10. Zardoc's Avatar
    Posts : 506
    Windows 10 Enterprise
    Thread Starter
       #10

    Hi everyone,

    Here is an update that I wanted to share with you. I previously posted that my issue had been resolved because of a suspected that the card had initially gotten a static shock and had to be re seated. Well the issue had been resolved, at least i thought it was until last week when the machine crashed again.

    So i decided to closely look at the card because I knew the problem was somewhere around the card, the motherboard or the wiring.

    I started to play around with the card while the machine was running, tugging trying to make it budge a bit but nothing happened.

    Then I started playing around the cables (there are 2 plugs) First cable nothing. As soon as I moved the other cable, crash. I was able to reproduce the crash more than once.

    So, now the suggestion that is giving on most forums with the 20 series RTX cards is not to use the same dual split plug cable for both plugs but rather a single cable for each plug. I already had this type of setup but each cable was a dual split plug with each second plug tywrapped out of commission.

    I found 2 single 8 pin plugs and used those instead. Rebooted tugged on the cables and no crash since.

    I wanted to wait a while before writing about it because I was wrong the first time and did not want to write the same mistake twice.

    So the moral of this story is that nvlddmkm.sys, ntoskrn, DPC_WATCH DOG_VIOLATION are not easy to troubleshoot especially when it's hardware related.

    Check everything extensively
      My Computer


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 17:19.
Find Us




Windows 10 Forums