Hi! Guys, I have the following configuration:
Ryzen 5 1600AF (Stock)
Aorus B450 M (Came updated from the store I bought it with bios f60)
RTX 2060 Galax EX White
2x8gb 3000mhz Crucial Ballistix RGB Tracer blt8g4d30aet4k (XMP On)
SSD MX500 500GB
HD WD 1TB
PSU XPG Core Reactor 750W
I bought this motherboard about 10 days ago, it already came with bios f60 installed, but it is causing me problems. In the bios, I made few changes, I just enabled secure boot, activated xmp and nothing else, the rest of the settings left the default.
Yesterday, just browsing the internet, out of nowhere the system froze, the screen did not turn off, it remained lit, the mouse and keyboard stopped working, but they remained energized.
A few seconds later the blue screen of death appeared, giving the error DPC_WATCHDOG_VIOLATION, then restarting. I analyzed the event checker, there was only the blue screen information, that the system had been turned off abruptly and etc, there was no other error, no error 43, referring to vga and no other error about other peripherals, like usb, disks rigid and so on.
In the reliability monitor option, I had the following information:
Fonte
Windows
Resumo
Encerramento inesperado
Data
21/03/2022 07:25
Status
Não informado
Assinatura do problema
Nome de Evento de Problema: BlueScreen
Código: 133
Parâmetro 1: 0
Parâmetro 2: 501
Parâmetro 3: 500
Parâmetro 4: fffff806660fa320
Versão do SO: 10_0_19044
Service Pack: 0_0
Produto: 256_1
Versão do sistema operacional: 10.0.19044.2.0.0.256.48
Identificação da Localidade: 1046
I also ran 2 programs to check the bluescreen information, one was bluescreenview and the other was whocrashed. The first only shows this information:
==================================================
Dump File : 032122-7671-01.dmp
Crash Time : 21/03/2022 07:24:57
Bug Check String :
Bug Check Code : 0x00000133
Parameter 1 : 00000000`00000000
Parameter 2 : 00000000`00000501
Parameter 3 : 00000000`00000500
Parameter 4 : fffff806`660fa320
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+3f7620
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 10.0.19041.1586 (WinBuild.160101.0800)
Processor : x64
Crash Address : ntoskrnl.exe+3f7620
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\032122-7671-01.dmp
Processors Count : 12
Major Version : 15
Minor Version : 19041
Dump File Size : 4.412.724
Dump File Time : 21/03/2022 07:25:32
==================================================
In the whocrashed, in addition to the DPC_WATCHDOG_VIOLATION, it says that the problem was a third-party driver, referring to the realtek network driver, rt640x64.sys.
Crash Dump Analysis
Crash dumps are enabled on your computer.
Crash dump directories:
C:\Windows
C:\Windows\Minidump
On Mon 21/03/2022 07:24:57 your computer crashed or a problem was reported
Crash dump file: C:\Windows\Minidump\032122-7671-01.dmp (Minidump)
Bugcheck code: 0x133(0x0, 0x501, 0x500, 0xFFFFF806660FA320)
Bugcheck name: DPC_WATCHDOG_VIOLATION
Driver or module in which error occurred: rt640x64.sys (rt640x64+0x5ed3)
File path: C:\Windows\System32\drivers\rt640x64.sys
Description: Realtek 8125/8136/8168/8169 NDIS 6.40 64-bit Driver
Product: Realtek 8125/8136/8168/8169 PCI/PCIe Adapters
Company: Realtek
Bug check description: The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL or above. This could be caused by either a non-responding driver or non-responding hardware. This bug check can also occur because of overheated CPUs (thermal issue).
Analysis: This is likely caused by a hardware problem, but there is a possibility that this is caused by a misbehaving driver.
This bugcheck indicates that a timeout has occurred. This may be caused by a hardware failure such as a thermal issue or a bug in a driver for a hardware device.
Read this article on thermal issues
A full memory dump will likely provide more useful information on the cause of this particular bugcheck. A third party driver was identified as the probable root cause of this system error.
It is suggested you look for an update for the following driver:
rt640x64.sys (Realtek 8125/8136/8168/8169 NDIS 6.40 64-bit Driver , Realtek ).
Google query: rt640x64 Realtek DPC_WATCHDOG_VIOLATION
On Mon 21/03/2022 07:24:57 your computer crashed or a problem was reported
Crash dump file: C:\Windows\MEMORY.DMP (Kernel memory dump)
Bugcheck code: 0x133(0x0, 0x501, 0x500, 0xFFFFF806660FA320)
Bugcheck name: DPC_WATCHDOG_VIOLATION
Driver or module in which error occurred: rt640x64.sys (rt640x64+0x5ed3)
File path: C:\Windows\System32\drivers\rt640x64.sys
Description: Realtek 8125/8136/8168/8169 NDIS 6.40 64-bit Driver
Product: Realtek 8125/8136/8168/8169 PCI/PCIe Adapters
Company: Realtek
Bug check description: The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL or above. This could be caused by either a non-responding driver or non-responding hardware. This bug check can also occur because of overheated CPUs (thermal issue).
Analysis: This is likely caused by a hardware problem, but there is a possibility that this is caused by a misbehaving driver.
This bugcheck indicates that a timeout has occurred. This may be caused by a hardware failure such as a thermal issue or a bug in a driver for a hardware device.
Read this article on thermal issues
A full memory dump will likely provide more useful information on the cause of this particular bugcheck. A third party driver was identified as the probable root cause of this system error.
It is suggested you look for an update for the following driver:
rt640x64.sys (Realtek 8125/8136/8168/8169 NDIS 6.40 64-bit Driver , Realtek ).
Google query: rt640x64 Realtek DPC_WATCHDOG_VIOLATION
I took advantage and updated the driver with the one available on the gigabyte website, as it is more current than the one installed on windows 10, so far it is working normally, but I have already noticed that the system is not stable, because a problem of the type was not for happen.
I read several threads here on the forum about bios, and what I noticed is that most always recommend that on this motherboard the user uses bios only for the generation of his cpu. In my case that I have a 1600af, the ideal serial to bios released for the pinnacle ridge generation, from what I read here would be the F4, correct?
The problem is that my motherboard is on F60, what would the rollback procedure be like, in my situation? It's clear that on f60 my system is unstable, I don't mind going back to an older bios, as long as it stays stable, as I intend to stay with 1600af for a long time. I apologize for the long personal text, but I'm very frustrated these last few months with amd, if I knew I would have so much headache I would stay at intel, at least with her I never had these types of problems that I'm currently having.
