Question I've been getting the same repeated BSoD but can't find a solution this time around ?

Toggle sidebar Toggle sidebar
Beanconscript

Beanconscript

Feb 8, 2024
6
0
10
Hi all, I've had plenty of Blue Screens in the past and managed to finally reduce them from happening every 10 minutes to around once over month or two. Not great, but leagues better than before. Well now after around 3 years of this, DPC_WATCHDOG_VIOLATION has become a repetitive annoyance for me. Below I will attach a OneDrive file with all relevant information I know to add but if you would like to help and know of any more relevant information I could include, let me know and I'll be sure to add it in there. Thanks. (All have the event ID of 41 and all but one are bug check code 307.)


https://1drv.ms/f/s!AqJCDnFgMzYiyCunTFygM9kKuDtN?e=CxO2Kv


System Specs

Motherboard: Tuf Gaming B450M Plus Gaming
CPU: Ryzen 3600
GPU: Gigabyte RTX 2060
CPU cooler: Stock
Ram: 4x 8Gb Corsair Vengeance 3000 Mhz (under clocked to 2133 MHZ to fix previous BSoD issues)
SSD/HDD: 512 M.2 (C drive) 2 TB seagate HDD, 512 Samsung SATA drive, 256 Inland SATA drive, 14 TB WD DAS over C cable
PSU: I forgot : /
Chassis: NZXT basic case
OS: Win 10
Monitor: cheapo acer and asus
 
Last edited:
Sort by date Sort by votes
Welcome to the forums, newcomer!

I went through your .dmp files using WinDbg;
your BSoD's are created by PSHED, dxgmms2 and ntkrnlmp. I'm curious where you sourced the installer for your OS.

As for your build, can you please pass on the specs to your build like so:
CPU:
CPU cooler:
Motherboard:
Ram:
SSD/HDD:
GPU:
PSU:
Chassis:
OS:
Monitor:
include the age of the PSU apart from it's make and model. BIOS version for your motherboard at this moment of time.

Edit; I noticed you edited in your specs.

PSU: I forgot : /
We will need to know it's make and model as well as it's age.

Ram: 4x 8Gb Corsair Vengeance 3000 Mhz (under clocked to 2133 MHZ to fix previous BSoD issues)
Can you take pictures of the ram kit(s)? Inspect for PCB revisions on the ram kits if you got 2x(2x8GB) kits.
 
Upvote 0 Downvote
Lutfij said:
Welcome to the forums, newcomer!

I went through your .dmp files using WinDbg;
your BSoD's are created by PSHED, dxgmms2 and ntkrnlmp. I'm curious where you sourced the installer for your OS.

As for your build, can you please pass on the specs to your build like so:
CPU:
CPU cooler:
Motherboard:
Ram:
SSD/HDD:
GPU:
PSU:
Chassis:
OS:
Monitor:
include the age of the PSU apart from it's make and model. BIOS version for your motherboard at this moment of time.

Edit; I noticed you edited in your specs.

PSU: I forgot : /
We will need to know it's make and model as well as it's age.

Ram: 4x 8Gb Corsair Vengeance 3000 Mhz (under clocked to 2133 MHZ to fix previous BSoD issues)
Can you take pictures of the ram kit(s)? Inspect for PCB revisions on the ram kits if you got 2x(2x8GB) kits.
Click to expand...
I can take some pictures of the RAM in an hour or two but cannot right now. As far as PSU goes I honestly have no recollection as its about 5 years old and I am not exactly sure how to check. Not sure what you mean by "sourced the installer for your OS. If you mean the install image, then from a windows install image i got from microsoft. Not really sure what you mean if you could elaborate.


E: added a bunch of pics of my ram to the onedrive.
 
Last edited:
Upvote 0 Downvote
The dumps are not all 0x133, there is a 0x139 in there too - this indicates that a LIST structure has been corrupted and these are memory resident structures. The 0x133 indicates that a single DPC (typically used as the back-end of device interrupt processing) ran for too long. In these dumps however there are no references to third party drivers.

Your most recent BSOD was a 0x133 which means that the kernel dump stored is for that BSOD. Could you then please upload the kernel dump? It's the file C:\Windows\Memory.dmp and it will be large. There will be much more information in that kernel dump.

In one dump there is a networking operation in progress, so your third-party network adapter driver will have been involved. There are some indications that a PnP device was involved, (we see the Windows classpnp.sys driver called) this could indicate a USB device (although we don't see any USB drivers called) or it could be a PCIe device - perhaps a WiFi card? Your LAN driver (rt640x64.sys) is old, dating from May 2019...
Code: 
8: kd> lmDvmrt640x64
Browse full module list
start             end                 module name
fffff800`85b50000 fffff800`85bfd000   rt640x64   (deferred)             
    Mapped memory image file: c:\windbgsymbols\rt640x64.sys\5CE7AF86ad000\rt640x64.sys
    Image path: \SystemRoot\System32\drivers\rt640x64.sys
    Image name: rt640x64.sys
    Browse all global symbols  functions  data
    Timestamp:        Fri May 24 11:47:02 2019 (5CE7AF86)
    CheckSum:         000B965B
    ImageSize:        000AD000
    File version:     9.1.410.2015
    Product version:  9.1.410.2015
    File flags:       8 (Mask 3F) Private
    File OS:          40004 NT Win32
    File type:        3.6 Driver
    File date:        00000000.00000000
    Translations:     0000.04b0
    Information from resource tables:
        CompanyName:      Realtek                                        
        ProductName:      Realtek 8125/8136/8168/8169 PCI/PCIe Adapters                                        
        InternalName:     rt640x64.sys
        OriginalFilename: rt640x64.sys
        ProductVersion:   9.001.0410.2015
        FileVersion:      9.001.0410.2015
        FileDescription:  Realtek 8125/8136/8168/8169 NDIS 6.40 64-bit Driver                                        
        LegalCopyright:   Copyright (C) 2019 Realtek Semiconductor Corporation. All Right Reserved.
If you are cable connected to your router you should look for an update to this driver. If you are using a wireless card then check for an updated driver for that.

I don't like the look of the pins in some of those RAM pictures. I would clean them up before you reinsert them. It would also be well worth running a thorough RAM test on there too...
  1. Download Memtest86 (free), use the imageUSB.exe tool extracted from the download to make a bootable USB drive containing Memtest86 (1GB is plenty big enough). Do this on a different PC if you can, because you can't fully trust yours at the moment.
  2. Then boot that USB drive on your PC, Memtest86 will start running as soon as it boots.
  3. If no errors have been found after the four iterations of the 13 different tests that the free version does, then restart Memtest86 and do another four iterations. Even a single bit error is a failure.
Bad RAM could certainly be the root cause here so we do need to try and eliminate that before looking further.
 
Upvote 0 Downvote
ubuysa said:
The dumps are not all 0x133, there is a 0x139 in there too - this indicates that a LIST structure has been corrupted and these are memory resident structures. The 0x133 indicates that a single DPC (typically used as the back-end of device interrupt processing) ran for too long. In these dumps however there are no references to third party drivers.

Your most recent BSOD was a 0x133 which means that the kernel dump stored is for that BSOD. Could you then please upload the kernel dump? It's the file C:\Windows\Memory.dmp and it will be large. There will be much more information in that kernel dump.

In one dump there is a networking operation in progress, so your third-party network adapter driver will have been involved. There are some indications that a PnP device was involved, (we see the Windows classpnp.sys driver called) this could indicate a USB device (although we don't see any USB drivers called) or it could be a PCIe device - perhaps a WiFi card? Your LAN driver (rt640x64.sys) is old, dating from May 2019...
Code: 
8: kd> lmDvmrt640x64
Browse full module list
start             end                 module name
fffff800`85b50000 fffff800`85bfd000   rt640x64   (deferred)            
    Mapped memory image file: c:\windbgsymbols\rt640x64.sys\5CE7AF86ad000\rt640x64.sys
    Image path: \SystemRoot\System32\drivers\rt640x64.sys
    Image name: rt640x64.sys
    Browse all global symbols  functions  data
    Timestamp:        Fri May 24 11:47:02 2019 (5CE7AF86)
    CheckSum:         000B965B
    ImageSize:        000AD000
    File version:     9.1.410.2015
    Product version:  9.1.410.2015
    File flags:       8 (Mask 3F) Private
    File OS:          40004 NT Win32
    File type:        3.6 Driver
    File date:        00000000.00000000
    Translations:     0000.04b0
    Information from resource tables:
        CompanyName:      Realtek                                       
        ProductName:      Realtek 8125/8136/8168/8169 PCI/PCIe Adapters                                       
        InternalName:     rt640x64.sys
        OriginalFilename: rt640x64.sys
        ProductVersion:   9.001.0410.2015
        FileVersion:      9.001.0410.2015
        FileDescription:  Realtek 8125/8136/8168/8169 NDIS 6.40 64-bit Driver                                       
        LegalCopyright:   Copyright (C) 2019 Realtek Semiconductor Corporation. All Right Reserved.
If you are cable connected to your router you should look for an update to this driver. If you are using a wireless card then check for an updated driver for that.

I don't like the look of the pins in some of those RAM pictures. I would clean them up before you reinsert them. It would also be well worth running a thorough RAM test on there too...
  1. Download Memtest86 (free), use the imageUSB.exe tool extracted from the download to make a bootable USB drive containing Memtest86 (1GB is plenty big enough). Do this on a different PC if you can, because you can't fully trust yours at the moment.
  2. Then boot that USB drive on your PC, Memtest86 will start running as soon as it boots.
  3. If no errors have been found after the four iterations of the 13 different tests that the free version does, then restart Memtest86 and do another four iterations. Even a single bit error is a failure.
Bad RAM could certainly be the root cause here so we do need to try and eliminate that before looking further.
Click to expand...
Unfortunatly I don't have any other machine to test my ram with but I believe that this is likely the issue as its been the center of my crashes in the past. However I did recently test my memory using Prime-95 which I am including the result file of in the onedrive folder as well, not sure if it does any good however as it just lists everything as passed. Would it be worth attempting to run memtest on this PC or going another route? as previously mentioned, my ram is underclocked because in testing it pretty much stopped my crashing, along with updating my BIOS and a few drivers. This was back in 2019 though now.
 
Upvote 0 Downvote
Beanconscript said:
as previously mentioned, my ram is underclocked because in testing it pretty much stopped my crashing, along with updating my BIOS and a few drivers. This was back in 2019 though now.
Click to expand...
Ah, I must have missed that. If your RAM is only stable when underclocked then you can be pretty sure that your RAM is the source of your problems. Any hardware that is not stable at stock frequencies and voltages is suspect.
 
Upvote 0 Downvote
SkyNetRising said:
Can you show screenshots from CPU-Z - memory and spd sections?
(upload to imgur.com and post link)

Probably need to increase DRAM voltage to 1.35V.
Make sure Command Rate is set to 2T.
If that doesn't fix it, then try with two ram modules instead.
Click to expand...
I suspect my ram is causing my issues now and have begun to run memtest and prime95 to see if i can verify that they are in fact the problem. I'll take your advice, though could you explain why increasing DRAM voltage will help?
 
Upvote 0 Downvote
ubuysa said:
Ah, I must have missed that. If your RAM is only stable when underclocked then you can be pretty sure that your RAM is the source of your problems. Any hardware that is not stable at stock frequencies and voltages is suspect.
Click to expand...
sorry for the late reply, I recently had a problem after a blue screen in which i couldn't boot to windows and nothing would fix it. Eventually I took out one of my ram kits and suddenly it booted and I've bee running on 1 kit ever since (2x 8Gbs) the weird thing is that both of these kits are the same and were bought nearly 4 years apart. My first kit had problems immediately that were fixed by underclocking and I had really no problems for the longest time, then even after I got the second kit I was fine for a month or 2, then suddenly I start having problems. What are the odds that both kits are messed up?
 
Upvote 0 Downvote
RAM really should only ever be bought in packs of matched sets so that all the timings align. When you buy RAM 4 years apart, even if you manage to find exactly the same part number, you run the risk of problems. Mismatched RAM is a major cause of the BSODs that I see.
 
Upvote 0 Downvote
You must log in or register to reply here.

TRENDING THREADS

Latest posts

Moderators online

Share this page

COMPANY
RESOURCES
FOLLOW
Top Bottom