Random BSODs started about month and a half ago

AbsyntheM1nded · Apr 15, 2024

Hi guys/girls,

Hoping someone can help me out here. My computer started acting up about a month and a half ago. It would randomly BSOD and immediately restart without me being able to look at the screen for the error code. It also never created a minidump even though it was set up to create one. I tried changing it to a regular dump file, same result, no dmp file ever created. Event viewer only shows dreaded error id 41 with the 0x8000400000000002 which doesn't tell me much without a dmp file.

There is no pattern to the BSODs. Sometimes i'm just browsing the web, some times i am playing games, some times the computer is just idle. There is no time pattern either. Some times it happens 3 times in 1 hour, some times it won't happen for days on end.

The only change to the system was an rtx 4060 which i put in like 3 months ago. My ram was running on xmp profile 1 and the card was OCed. I immediately dialed all of those back to standard once the problem started, yet the problem persisted.

I ran memtest overnight for 8 passes, no issues. I ran occt cpu and gpu stress test 3 times each, no issue. I thought maybe a driver got screwed up, i've had this rig forever and hadn't done a clean format in 3+ years (i know, for shame) so I ran driver verifier, instant crash. So i reinstalled windows.

After reinstalling windows it ran absolutely fine for 3 weeks, and this week it started with the random crashing again. Again no dmp file created even though it is set up to. I even changed the page file sizing to manual to make sure there was no issue there. Again no dmp files.

Then today is BSODed and booted into my BIOs, which was a first and had me somewhat worried.

Windows 11 pro 64-bit version 23H2 (22631.3447)

All drivers are up to date, bios is flashed to latest version. and i've included my collector log plus tuneup.

At this point i'm a bit stumped. I originally thought my PSU was giving out, but then i feel like i would crash more while playing games. Maybe one of my HDs is failing? The rig is fairly old. everything except the rtx4060 is from 2019 and the SSD the OS is installed on is from 2017 or 18 even.

Any help or insight would be appreciated.

zbook · Apr 16, 2024

Please perform the following steps:

1) Run HD Tune (free or trial) (all drives) > post images or share links

HD Tune website

HD Tune

www.hdtune.com

a) Health
b) Benchmark
c) Full error scan

2) Run Sea Tools for Windows Long Generic test > post images or share links

https://www.seagate.com/content/dam/seagate/migrated-assets/www-content/support-content/downloads/seatools/_shared/downloads/100869623_B.pdf

https://www.seagate.com/content/dam/seagate/migrated-assets/www-content/support-content/downloads/seatools/_shared/downloads/SeaToolsWindowsInstaller.exe

3) The BIOS Version/Date American Megatrends International, LLC. F65c, 2023-12-25

Upgrade the BIOS to the most up to date non-beta BIOS

Code:

------------------------
Disk & DVD/CD-ROM Drives
------------------------
      Drive: C:
 Free Space: 347.8 GB
Total Space: 487.1 GB
File System: NTFS
      Model: INTEL SSDPEKNW512G8

      Drive: D:
 Free Space: 554.9 GB
Total Space: 953.9 GB
File System: NTFS
      Model: WDC WD10EZEX-08WN4A0

      Drive: E:
 Free Space: 538.2 GB
Total Space: 953.9 GB
File System: NTFS
      Model: CT1000MX500SSD1

AbsyntheM1nded · Apr 16, 2024

Flashed BIOS to latest version. My bad, I did not see they released a new one in march.

Ran the hd tune and seagate tests. All passed. Screens attached

zbook · Apr 16, 2024

The surface / error scans were incomplete.

Please run them overnight as needed.

The non-Windows drive testing can be done anytime.

This is an alternative software:

Check Hard Disk for Bad Sectors | Scan Disk on Windows

Macrorit Disk Scanner is a free and smart disk scanner helps you fast check bad sectors, scan disk, surface test and mark the location of bad sectors when disk failure happens to Windows

macrorit.com

HDTune can run on one drive while Macrorit runs on another.

AbsyntheM1nded · Apr 17, 2024

Did all the drives again in Macrorit and came back with no errors. Included pics and the scan log

zbook · Apr 17, 2024

1) Please run HD Sentinel (trial version): (all drives) (these tab results are instantaneous)

Hard Disk Sentinel - HDD health and temperature monitoring

Monitoring hard disk health and temperature. Test and repair HDD problems, predict disk failure.

www.hdsentinel.com

a) Overview
b) Temperature
c) SMART

2) Post a new V2 share link into the newest post

3) Create a new restore point

Create System Restore Point in Windows 11 Tutorial

This tutorial will show you how to manually create a restore point in Windows 11. Turning on system protection for a drive allows System Restore to include the drive when restore points are created so you can undo undesired system changes by reverting to a previous point in time. System...

www.elevenforum.com

4) Read this link on Windows Driver Verifier (WDV):

Enable and Disable Driver Verifier in Windows 10

How to Enable and Disable Driver Verifier in Windows 10

www.tenforums.com

Code:

Event[2327]
  Log Name: System
  Source: disk
  Date: 2024-04-03T22:51:37.7970000Z
  Event ID: 153
  Task: N/A
  Level: Warning
  Opcode: N/A
  Keyword: Classic,
  User: N/A
  User Name: N/A
  Computer: leroy
  Description:
The IO operation at logical block address 0x3f024df8 for Disk 0 (PDO name: \Device\0000003b) was retried.

Event[2328]
  Log Name: System
  Source: disk
  Date: 2024-04-03T22:53:40.4710000Z
  Event ID: 153
  Task: N/A
  Level: Warning
  Opcode: N/A
  Keyword: Classic,
  User: N/A
  User Name: N/A
  Computer: leroy
  Description:
The IO operation at logical block address 0x3f027dd8 for Disk 0 (PDO name: \Device\0000003b) was retried.

Event[2329]
  Log Name: System
  Source: disk
  Date: 2024-04-03T22:57:21.3060000Z
  Event ID: 153
  Task: N/A
  Level: Warning
  Opcode: N/A
  Keyword: Classic,
  User: N/A
  User Name: N/A
  Computer: leroy
  Description:
The IO operation at logical block address 0x3f02d3f8 for Disk 0 (PDO name: \Device\0000003b) was retried.

Event[2330]
  Log Name: System
  Source: disk
  Date: 2024-04-03T23:01:13.0490000Z
  Event ID: 153
  Task: N/A
  Level: Warning
  Opcode: N/A
  Keyword: Classic,
  User: N/A
  User Name: N/A
  Computer: leroy
  Description:
The IO operation at logical block address 0x3f032e58 for Disk 0 (PDO name: \Device\0000003b) was retried.

Event[2331]
  Log Name: System
  Source: disk
  Date: 2024-04-03T23:01:43.0380000Z
  Event ID: 153
  Task: N/A
  Level: Warning
  Opcode: N/A
  Keyword: Classic,
  User: N/A
  User Name: N/A
  Computer: leroy
  Description:
The IO operation at logical block address 0x3f033a10 for Disk 0 (PDO name: \Device\0000003b) was retried.

Event[2332]
  Log Name: System
  Source: disk
  Date: 2024-04-03T23:05:00.6920000Z
  Event ID: 153
  Task: N/A
  Level: Warning
  Opcode: N/A
  Keyword: Classic,
  User: N/A
  User Name: N/A
  Computer: leroy
  Description:
The IO operation at logical block address 0x3f038750 for Disk 0 (PDO name: \Device\0000003b) was retried.

Code:

Event[2286]
  Log Name: System
  Source: disk
  Date: 2024-04-03T19:13:13.0960000Z
  Event ID: 153
  Task: N/A
  Level: Warning
  Opcode: N/A
  Keyword: Classic,
  User: N/A
  User Name: N/A
  Computer: leroy
  Description:
The IO operation at logical block address 0xf2d7418 for Disk 0 (PDO name: \Device\0000003b) was retried.

Event[2287]
  Log Name: System
  Source: disk
  Date: 2024-04-03T19:25:36.0040000Z
  Event ID: 153
  Task: N/A
  Level: Warning
  Opcode: N/A
  Keyword: Classic,
  User: N/A
  User Name: N/A
  Computer: leroy
  Description:
The IO operation at logical block address 0xe804250 for Disk 0 (PDO name: \Device\0000003b) was retried.

Event[2288]
  Log Name: System
  Source: disk
  Date: 2024-04-03T19:25:46.9030000Z
  Event ID: 153
  Task: N/A
  Level: Warning
  Opcode: N/A
  Keyword: Classic,
  User: N/A
  User Name: N/A
  Computer: leroy
  Description:
The IO operation at logical block address 0xe804670 for Disk 0 (PDO name: \Device\0000003b) was retried.

Event[2289]
  Log Name: System
  Source: disk
  Date: 2024-04-03T19:26:19.6170000Z
  Event ID: 153
  Task: N/A
  Level: Warning
  Opcode: N/A
  Keyword: Classic,
  User: N/A
  User Name: N/A
  Computer: leroy
  Description:
The IO operation at logical block address 0xe805350 for Disk 0 (PDO name: \Device\0000003b) was retried.

Event[2290]
  Log Name: System
  Source: disk
  Date: 2024-04-03T19:28:29.1170000Z
  Event ID: 153
  Task: N/A
  Level: Warning
  Opcode: N/A
  Keyword: Classic,
  User: N/A
  User Name: N/A
  Computer: leroy
  Description:
The IO operation at logical block address 0xe8085d0 for Disk 0 (PDO name: \Device\0000003b) was retried.

Event[2291]
  Log Name: System
  Source: disk
  Date: 2024-04-03T19:30:03.1680000Z
  Event ID: 153
  Task: N/A
  Level: Warning
  Opcode: N/A
  Keyword: Classic,
  User: N/A
  User Name: N/A
  Computer: leroy
  Description:
The IO operation at logical block address 0xe80aa70 for Disk 0 (PDO name: \Device\0000003b) was retried.

Event[2292]
  Log Name: System
  Source: disk
  Date: 2024-04-03T19:30:39.9830000Z
  Event ID: 153
  Task: N/A
  Level: Warning
  Opcode: N/A
  Keyword: Classic,
  User: N/A
  User Name: N/A
  Computer: leroy
  Description:
The IO operation at logical block address 0xe80b8e8 for Disk 0 (PDO name: \Device\0000003b) was retried.

Code:

Event[2274]
  Log Name: System
  Source: disk
  Date: 2024-04-03T18:53:10.7780000Z
  Event ID: 153
  Task: N/A
  Level: Warning
  Opcode: N/A
  Keyword: Classic,
  User: N/A
  User Name: N/A
  Computer: leroy
  Description:
The IO operation at logical block address 0xf2b9f00 for Disk 0 (PDO name: \Device\0000003b) was retried.

Event[2275]
  Log Name: System
  Source: disk
  Date: 2024-04-03T18:57:47.2110000Z
  Event ID: 153
  Task: N/A
  Level: Warning
  Opcode: N/A
  Keyword: Classic,
  User: N/A
  User Name: N/A
  Computer: leroy
  Description:
The IO operation at logical block address 0x5b1f98 for Disk 0 (PDO name: \Device\0000003b) was retried.

Event[2276]
  Log Name: System
  Source: disk
  Date: 2024-04-03T19:00:13.3570000Z
  Event ID: 153
  Task: N/A
  Level: Warning
  Opcode: N/A
  Keyword: Classic,
  User: N/A
  User Name: N/A
  Computer: leroy
  Description:
The IO operation at logical block address 0xf2c43e0 for Disk 0 (PDO name: \Device\0000003b) was retried.

Event[2277]
  Log Name: System
  Source: disk
  Date: 2024-04-03T19:00:18.8110000Z
  Event ID: 153
  Task: N/A
  Level: Warning
  Opcode: N/A
  Keyword: Classic,
  User: N/A
  User Name: N/A
  Computer: leroy
  Description:
The IO operation at logical block address 0xf2c4600 for Disk 0 (PDO name: \Device\0000003b) was retried.

Event[2278]
  Log Name: System
  Source: disk
  Date: 2024-04-03T19:01:59.6910000Z
  Event ID: 153
  Task: N/A
  Level: Warning
  Opcode: N/A
  Keyword: Classic,
  User: N/A
  User Name: N/A
  Computer: leroy
  Description:
The IO operation at logical block address 0xf2c6d40 for Disk 0 (PDO name: \Device\0000003b) was retried.

Event[2279]
  Log Name: System
  Source: disk
  Date: 2024-04-03T19:06:52.9350000Z
  Event ID: 153
  Task: N/A
  Level: Warning
  Opcode: N/A
  Keyword: Classic,
  User: N/A
  User Name: N/A
  Computer: leroy
  Description:
The IO operation at logical block address 0x5b1f98 for Disk 0 (PDO name: \Device\0000003b) was retried.

Event[2280]
  Log Name: System
  Source: disk
  Date: 2024-04-03T19:07:41.8270000Z
  Event ID: 153
  Task: N/A
  Level: Warning
  Opcode: N/A
  Keyword: Classic,
  User: N/A
  User Name: N/A
  Computer: leroy
  Description:
The IO operation at logical block address 0xf2cf2e0 for Disk 0 (PDO name: \Device\0000003b) was retried.

Event[2281]
  Log Name: System
  Source: disk
  Date: 2024-04-03T19:09:44.5180000Z
  Event ID: 153
  Task: N/A
  Level: Warning
  Opcode: N/A
  Keyword: Classic,
  User: N/A
  User Name: N/A
  Computer: leroy
  Description:
The IO operation at logical block address 0xf2d22c0 for Disk 0 (PDO name: \Device\0000003b) was retried.

Event[2282]
  Log Name: System
  Source: disk
  Date: 2024-04-03T19:09:56.7750000Z
  Event ID: 153
  Task: N/A
  Level: Warning
  Opcode: N/A
  Keyword: Classic,
  User: N/A
  User Name: N/A
  Computer: leroy
  Description:
The IO operation at logical block address 0xf2d2780 for Disk 0 (PDO name: \Device\0000003b) was retried.

Code:

Event[2259]
  Log Name: System
  Source: disk
  Date: 2024-04-03T18:12:08.9200000Z
  Event ID: 153
  Task: N/A
  Level: Warning
  Opcode: N/A
  Keyword: Classic,
  User: N/A
  User Name: N/A
  Computer: leroy
  Description:
The IO operation at logical block address 0xf27de80 for Disk 0 (PDO name: \Device\0000003b) was retried.

Event[2260]
  Log Name: System
  Source: disk
  Date: 2024-04-03T18:12:29.3850000Z
  Event ID: 153
  Task: N/A
  Level: Warning
  Opcode: N/A
  Keyword: Classic,
  User: N/A
  User Name: N/A
  Computer: leroy
  Description:
The IO operation at logical block address 0xf27e660 for Disk 0 (PDO name: \Device\0000003b) was retried.

Event[2261]
  Log Name: System
  Source: disk
  Date: 2024-04-03T18:13:51.1630000Z
  Event ID: 153
  Task: N/A
  Level: Warning
  Opcode: N/A
  Keyword: Classic,
  User: N/A
  User Name: N/A
  Computer: leroy
  Description:
The IO operation at logical block address 0xf280640 for Disk 0 (PDO name: \Device\0000003b) was retried.

Event[2262]
  Log Name: System
  Source: disk
  Date: 2024-04-03T18:26:14.1040000Z
  Event ID: 153
  Task: N/A
  Level: Warning
  Opcode: N/A
  Keyword: Classic,
  User: N/A
  User Name: N/A
  Computer: leroy
  Description:
The IO operation at logical block address 0xf292848 for Disk 0 (PDO name: \Device\0000003b) was retried.

Event[2263]
  Log Name: System
  Source: disk
  Date: 2024-04-03T18:27:03.1720000Z
  Event ID: 153
  Task: N/A
  Level: Warning
  Opcode: N/A
  Keyword: Classic,
  User: N/A
  User Name: N/A
  Computer: leroy
  Description:
The IO operation at logical block address 0xf293b40 for Disk 0 (PDO name: \Device\0000003b) was retried.

Event[2264]
  Log Name: System
  Source: disk
  Date: 2024-04-03T18:28:20.8530000Z
  Event ID: 153
  Task: N/A
  Level: Warning
  Opcode: N/A
  Keyword: Classic,
  User: N/A
  User Name: N/A
  Computer: leroy
  Description:
The IO operation at logical block address 0xf2959a0 for Disk 0 (PDO name: \Device\0000003b) was retried.

Event[2265]
  Log Name: System
  Source: disk
  Date: 2024-04-03T18:34:24.8280000Z
  Event ID: 153
  Task: N/A
  Level: Warning
  Opcode: N/A
  Keyword: Classic,
  User: N/A
  User Name: N/A
  Computer: leroy
  Description:
The IO operation at logical block address 0xf29e7a0 for Disk 0 (PDO name: \Device\0000003b) was retried.

Event[2266]
  Log Name: System
  Source: disk
  Date: 2024-04-03T18:41:51.9320000Z
  Event ID: 153
  Task: N/A
  Level: Warning
  Opcode: N/A
  Keyword: Classic,
  User: N/A
  User Name: N/A
  Computer: leroy
  Description:
The IO operation at logical block address 0xf2a9600 for Disk 0 (PDO name: \Device\0000003b) was retried.

Event[2267]
  Log Name: System
  Source: disk
  Date: 2024-04-03T18:43:16.4510000Z
  Event ID: 153
  Task: N/A
  Level: Warning
  Opcode: N/A
  Keyword: Classic,
  User: N/A
  User Name: N/A
  Computer: leroy
  Description:
The IO operation at logical block address 0xf2ab700 for Disk 0 (PDO name: \Device\0000003b) was retried.

Event[2268]
  Log Name: System
  Source: disk
  Date: 2024-04-03T18:46:43.6490000Z
  Event ID: 153
  Task: N/A
  Level: Warning
  Opcode: N/A
  Keyword: Classic,
  User: N/A
  User Name: N/A
  Computer: leroy
  Description:
The IO operation at logical block address 0xf2b0848 for Disk 0 (PDO name: \Device\0000003b) was retried.

Event[2269]
  Log Name: System
  Source: disk
  Date: 2024-04-03T18:48:20.4220000Z
  Event ID: 153
  Task: N/A
  Level: Warning
  Opcode: N/A
  Keyword: Classic,
  User: N/A
  User Name: N/A
  Computer: leroy
  Description:
The IO operation at logical block address 0xf2b2dc0 for Disk 0 (PDO name: \Device\0000003b) was retried.

Code:

Event[2239]
  Log Name: System
  Source: disk
  Date: 2024-04-03T15:34:17.7890000Z
  Event ID: 153
  Task: N/A
  Level: Warning
  Opcode: N/A
  Keyword: Classic,
  User: N/A
  User Name: N/A
  Computer: leroy
  Description:
The IO operation at logical block address 0x4c35f240 for Disk 0 (PDO name: \Device\0000003b) was retried.

Event[2240]
  Log Name: System
  Source: disk
  Date: 2024-04-03T15:35:45.0160000Z
  Event ID: 153
  Task: N/A
  Level: Warning
  Opcode: N/A
  Keyword: Classic,
  User: N/A
  User Name: N/A
  Computer: leroy
  Description:
The IO operation at logical block address 0x4c361440 for Disk 0 (PDO name: \Device\0000003b) was retried.

Event[2241]
  Log Name: System
  Source: disk
  Date: 2024-04-03T15:37:31.3340000Z
  Event ID: 153
  Task: N/A
  Level: Warning
  Opcode: N/A
  Keyword: Classic,
  User: N/A
  User Name: N/A
  Computer: leroy
  Description:
The IO operation at logical block address 0x4c363dc0 for Disk 0 (PDO name: \Device\0000003b) was retried.

Event[2242]
  Log Name: System
  Source: disk
  Date: 2024-04-03T15:43:33.9510000Z
  Event ID: 153
  Task: N/A
  Level: Warning
  Opcode: N/A
  Keyword: Classic,
  User: N/A
  User Name: N/A
  Computer: leroy
  Description:
The IO operation at logical block address 0x4c36cb40 for Disk 0 (PDO name: \Device\0000003b) was retried.

Event[2243]
  Log Name: System
  Source: disk
  Date: 2024-04-03T15:45:36.6340000Z
  Event ID: 153
  Task: N/A
  Level: Warning
  Opcode: N/A
  Keyword: Classic,
  User: N/A
  User Name: N/A
  Computer: leroy
  Description:
The IO operation at logical block address 0x4c36fb20 for Disk 0 (PDO name: \Device\0000003b) was retried.

AbsyntheM1nded · Apr 17, 2024

Hi Zbook,

additional info added. I've also did a new log collector and attached it as requested and made sure to create a new restore point post checks.

I've read the article on driver verifier as well as requested.

zbook · Apr 17, 2024

Please recheck the links so that there are 3 for each drive.
(there were 2 wdc and missing intc)

AbsyntheM1nded · Apr 17, 2024

Butterfingered one of the files it seems. Let me recheck. Seems like saved the wd as the intel overview, so i've reattached the correct one.

The other ones seem to all be correct though. 3 CTs 3 WDs

zbook · Apr 17, 2024

1) For WDC: Hard disk case: communication errors

2) Create a new restore point

3) Post a new V2 share link into the newest post

4) Plan to run WDV for 48 hours with various customized tests.

Start the tool with these settings:

a) test all non-Microsoft drivers
b) test no Microsoft drivers
c) start the testing with the 3 customized tests in the TF link

Each time the tool is restarted if there is no immediate BSOD then open administrative command prompt and copy an paste:

verifier /querysettings

Post a share link.

For any BSOD post a new V2 share link into the newest post.

During the troubleshooting WDV can run continuously in the background until the testing is modified.

AbsyntheM1nded · Apr 19, 2024

Hi Zbook,

I will double check the cables on all HDs just to be sure, and I'll try to get all the tests finished over the weekend into early next week. I have a few busy days ahead of me so, hopefully I can squeeze it all in. But there might be a slight delay before my updated post.

I would just like to say thanks in advance for coaching me through this, it is definitely appreciated!

zbook · Apr 19, 2024

WDV has approximately 22 customized tests.

They will be selected in groups.

Some may or may not be selected.

Start the testing with the 3 customized tests in the TF link.

If there is no immediate BSOD then open administrative command prompt and copy and paste:

verifier /querysettings

Post a share link.

For any BSOD post a new V2 share link into the newest post.

For each WDV restart new customized tests will be posted.

Then post either a querysettings or a V2 share link.

WDV can run continuously in the background.

AbsyntheM1nded · Wednesday at 8:28 PM

Hey zbook, been a busy week so I have not managed to run verifier for a full 24 hour block as, unfortunately, I use this computer for work and the verifier really slows it down.

I could run the basic no microsoft drivers test for about 10 hours overnight no issue. I've added the verifier /query result.

When i try to run it with the 4 microsoft drivers it suggest in the verifier instructions it instantly BSODs and BSOD loops until we get to system restore. I've added an updated log for that one too.

I'm hoping to run verifier for a longer stretch tonight overnight as I have meetings until about 3pm so that should give me at least 16 hours or so where it runs.

zbook · Wednesday at 10:31 PM

1) Each time WDV is started if there is no immediate BSOD then open administrative command prompt and copy and paste:

verifier /querysettings

Post a share link.

2) The command used in the post #13 share link was verifier /query.

Please use: verifier /querysettings.

3) These were the selected customized tests:

[X] 0x00000001 Special pool.
[X] 0x00000002 Force IRQL checking.
[X] 0x00000008 Pool tracking.
[X] 0x00000020 Deadlock detection.
[X] 0x00000100 Security checks.
[X] 0x00000800 Miscellaneous checks.
[X] 0x00020000 DDI compliance checking.
[X] 0x00080000 DDI compliance checking (additional).

How come the 3 customized tests in the TF link were not selected?

4) If there is a BSOD when WDV is in use please boot into safe mode to turn off the tool.

See the commands in the TF link:

verifier /reset

verifier /bootmode resetonbootfail

Using system restore often results in the loss of the mini dump file so whenever possible use the commands.

5) Uninstall:

parsecudeaudio parsecudeaudio c:\windows\system32\drivers\parsecudeaudio.sys

6) Turn off Windows fast startup:

Turn On or Off Fast Startup in Windows 11 Tutorial

This tutorial will show you how to turn on or off fast startup in Windows 11. There are three startup modes in Windows: Cold (traditional) Wake-from-hibernation Fast Starting with Windows 8.x, the default shutdown and restart scenario has been updated and named fast startup. Fast startup...

www.elevenforum.com

7) Make a new restore point

8) Restart WDV with these customized tests:

[ ] 0x00000010 I/O verification.
[ ] 0x00000080 DMA checking.
[ ] 0x00000200 Force pending I/O requests.
[ ] 0x00000400 IRP logging.
[ ] 0x00002000 Invariant MDL checking for stack.
[ ] 0x00004000 Invariant MDL checking for driver.
[ ] 0x00008000 Power framework delay fuzzing.
[ ] 0x00010000 Port/miniport interface checking.

If there is no immediate BSOD then open administrative command prompt and copy and paste:

verifier /querysettings

Post a share link.

For any BSOD post a new V2 share link into the newest post.

parsecudeaudio.sys Tue May 23 19:09:45 2023 (646D55C9)

AbsyntheM1nded · Thursday at 9:13 AM

Hey, there appears to be some confusion here with the custom commands. the elevenforum driver verifier instruction post specifically mentions not running those I/O verification or force pending I/O request commands as they cause issues?

zbook · Friday at 2:24 AM

That link is only the preference of the writer of that link.

That link has multiple errors.

Do not follow the errors in that link.

That link was written to control.

The Ten Forums (TF) tutorial is used in Eleven Forum, Ten Forums, MicrosoftAnswers, and MicrosoftQ&A.

Please follow the instructions in the TF tutorial.

These are Microsoft links for WDV:

Redirecting

Use Driver Verifier to identify issues - Windows Server

This article introduces how to use Driver Verifier to identify issues.

learn.microsoft.com

When WDV is launched it has Create standard settings already checked:

This includes I/O verification.

Standard Options

The following options together represent the rules that all drivers in the system shouldn't violate.
These options are enabled when you choose to enable standard settings in the Driver Verifier GUI or you specify the /standard switch when you configure Driver Verifier by using the command line.

I/O Verification

When this option is active, Driver Verifier allocates the driver's IRPs from a special pool, and monitors the driver's I/O handling. It detects illegal or inconsistent use of I/O routines.

When I/O Verifier is enabled:

All IRPs allocated through IoAllocateIrp are allocated from special pool, if available.
Checks are made in IoCallDriver, IoCompleteRequest, and IoFreeIrp to catch driver error messages.
All I/O Verifier failures bug check with the code DRIVER_VERIFIER_IOMANAGER_VIOLATION (0xC9).

Please make sure that you follow the Ten Forums tutorial.

It is one of the safest methods to use the tool.

Standard Flags:

0x00000000: Automatic Checks
0x00000001: Special pool
0x00000002: Force IRQL Checking
0x00000008: Pool Tracking
0x00000010: I/O verification
0x00000020: Deadlock detection
0x00000080: DMA checking
0x00000100: Security checks
0x00000800: Miscellaneous checks
0x00020000: DDI compliance checking