New build, watchdog violation during boot

JerryK007 · 12 Jan 2023

Details of the problem:
Windows 11 extremely slow boot and frequent BSOD with DPC WATCHDOG VIOLATION during boot.
1 out of 5 finalizes the boot process and runs stable once booted.
Boot disk is an AMD RAID set with 2 NVME 980 PRO
Two RAID sets connected to LSI 9361-8i
New build fresh windows 11 pro workstation no apps installed except office365 and hardware related software.

Desktop:
* New Custom Build
* Windows 11 Pro Workstation version 22H2 OS build 22621.1105
* Memory 256GB, Processor AMD Threadripper Pro 5955WX
* Latest ASRock WRX80 Creator (non beta) Bios v 5.01
* Enable/Disable PrimoCache no difference

Considering:
* Latest ASRock WRX80 Creator Beta Bios v 6.06
* Disabling TPM ? – Do have the SCEP Certificate enrollment initialization for Local system via https://AMD-KeyId-578c545f7969514212...lates/Aik/scep failed: errors
SFC /scannow run without errors No memtest jet

All drivers up to date compared with Driver Fusion.
All help appreciated

James · 12 Jan 2023

Welcome to Tenforums

Have you installed any possibly dodgy or malicious content recently. Slow start ups and BSODs can often be affects from such software, or incorrect, broken or missing drivers.

I hope these issues can be solved through this forum and thread, especially with your brand new computer into play.

-James

itsme1 · 12 Jan 2023

As it is a new build, and if I understand correctly there are 2 nvme ssd on the mainboard raid possibility, not on the LSI 9361-8i controller board, you should unraid and install windows 11 on the 2 samsung 980 pro. This way you will be able to know if it is a hardware or software problem. If you no longer have the DPC WATCHDOG VIOLATION problem on the 2 installations of windows 11 on each samsung ssd, and since it was a clean install on your raid config, the problem is most likely with the raid config.

- - - Updated - - -

You can also, before installing 11 on the 2 Samsungs, disconnect the LSI 9361-8i card to see what is happening.

axe0 · 13 Jan 2023

Hi there,

I would not recommend any driver update software to use or compare whether your drivers are the latest drivers, that info is only partially useful since the latest driver is not necessarily the best driver.

0x133 arg 1=1 implies that multiple DPCs failed to complete within a allotted time, typically from multiple drivers. Considering it only took a few minutes before these crashes occurred, I would suggest a clean boot to see if that has impact.

Diagnostics Test

Clean boot

Please try the following, note that these instructions have not yet been updated for Windows 11 so some instructions may be inaccurate:

Open taskmanager
- Go to the tab startup
- disable everything
Search msconfig and open it
- Go to the tab services
- Check 'hide microsoft services'
- Uncheck all other services
- Click apply and click ok
Reboot if asked

See if the problem persist, if the problem does not persist enable in the startup tab in taskmanager 1 item and in the services tab in msconfig also 1 service, reboot and see if the problem persist. Keep doing this until you find the culprit or there is nothing left.
If the problem still persist, try booting in safe mode and see if the problem still persist

zbook · 13 Jan 2023

The mini dump file debugging displayed two misbehaving drivers.

1) Run these bat scripts and post share links into this thread using one drive, drop box, or google drive

tuneup plus
diskpar info

https://www.tenforums.com/attachment...p_plus_log.bat

https://www.tenforums.com/attachment...iskparinfo.bat

2) Reinstall or uninstall and reinstall:

fancyccv PrimoCache Driver c:\windows\system32\drivers\rxfcv.sys

rcbottom AMD-RAID Bottom Service c:\windows\system32\drivers\rcbottom.sys

3) See the ReFS event viewer reports related to:
file or folder is "Medium Allocator"

ASRock > WRX80 Creator

Download PrimoCache

PrimoCache User Manual

Code:

Name	AMD-RAID Bottom Device
Manufacturer	Advanced Micro Devices, Inc.
Status	OK
PNP Device ID	PCI\VEN_1022&DEV_B000&SUBSYS_A801144D&REV_00\6&C6A3E6E&0&00100019
Memory Address	0xD0600000-0xD06FFFFF
IRQ Channel	IRQ 4294967278
IRQ Channel	IRQ 4294967277
IRQ Channel	IRQ 4294967276
IRQ Channel	IRQ 4294967275
IRQ Channel	IRQ 4294967274
Driver	C:\WINDOWS\SYSTEM32\DRIVERS\RCBOTTOM.SYS (9.3.2.158, 100,17 KB (102.576 bytes), 08/09/2022 10:40)

Code:

Event[305]
  Log Name: System
  Source: Microsoft-Windows-ReFS
  Date: 2023-01-12T03:21:40.6470000Z
  Event ID: 135
  Task: N/A
  Level: Error
  Opcode: Info 
  Keyword: N/A
  User: S-1-5-18
  User Name: NT AUTHORITY\SYSTEM
  Computer: XTREME-PC01
  Description: 
Volume E: is formatted as ReFS but ReFS is unable to mount it; ReFS encountered status The volume repair was not successful..

Code:

Event[300]
  Log Name: System
  Source: Microsoft-Windows-ReFS
  Date: 2023-01-12T03:20:33.0190000Z
  Event ID: 131
  Task: N/A
  Level: Error
  Opcode: Info 
  Keyword: N/A
  User: S-1-5-18
  User Name: NT AUTHORITY\SYSTEM
  Computer: XTREME-PC01
  Description: 
The file system structure on volume E: cannot be corrected.

Event[301]
  Log Name: System
  Source: Microsoft-Windows-ReFS
  Date: 2023-01-12T03:20:34.0040000Z
  Event ID: 135
  Task: N/A
  Level: Error
  Opcode: Info 
  Keyword: N/A
  User: S-1-5-18
  User Name: NT AUTHORITY\SYSTEM
  Computer: XTREME-PC01
  Description: 
Volume E: is formatted as ReFS but ReFS is unable to mount it; ReFS encountered status The volume repair was not successful..

Event[302]
  Log Name: System
  Source: Microsoft-Windows-ReFS
  Date: 2023-01-12T03:20:34.0040000Z
  Event ID: 133
  Task: N/A
  Level: Error
  Opcode: Info 
  Keyword: N/A
  User: S-1-5-18
  User Name: NT AUTHORITY\SYSTEM
  Computer: XTREME-PC01
  Description: 
The file system detected a checksum error and was not able to correct it. The name of the file or folder is "Medium Allocator".

Code:

rxfcv.sys    Fri Dec 31 05:10:20 2021 (61CEE51C)

Code:

rcbottom.sys Fri Aug 19 14:59:45 2022 (62FFEBB1)

JerryK007 · 14 Jan 2023

Short update and thanks all for your contributions to my problem.
Removed PrimoCache – issue remained
Removed LSI 9361-8i adapter – issue remained
No dodgy software installed – but removed anything that was not necessary – issue remained
Clean boot as per instructions – issue remained
Reading through the AMD Raid documentation there are three sets of Raid drivers depending on the chipset / processor / drive combination: NVMe_CC / NVMe_DID / RAID_SATA all with the exact same driver names inside (x3), thanks AMD!
I probably used the first set that I found in NVMe_CC while I needed DID. Just a few minutes of RTFM would have saved me many hours…
Fresh install with the NVMe_DID drivers and she is flying
Now testing only with the AMD Raid, once satisfied will add the LSI adaptor and PrimoCache back
If that all works well will close this thread.