BSOD- Libirm

Okay, thanks for clarification.
One concern- it seems if you get a BSOD- it's very hard to recover the computer, have seen this happen before?

libirm said:

Okay, thanks for clarification.
One concern- it seems if you get a BSOD- it's very hard to recover the computer, have seen this happen before?

Click to expand...

Extremely rare.

That link has caused a lot of anxiety in our forums.

It was written to control.




If you have anxiety or extra concerns then make free or pay backup images:

(Acronis, Aoemi, EaseUS, Macrium, Paragon, etc.)

Thanks Z!
I appreciate that reassurance, I will run asap.

Question- Do I try and use my computer as I normally do while it's running on back round?

WDV is designed to stress drivers.
If a misbehaving driver is identified most BSOD occur when the tool is started.
BSOD must be expected at any time while the tool is used.
The computer is used knowing that a BSOD could occur at any time.

The tool can cause performance problems while it stresses drivers.
If there are any major performance problems including very slow boot then comment into this thread and settings can be modified.

libirm said:

Question- Do I try and use my computer as I normally do while it's running on back round?

Click to expand...

Yes.

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

Enable and Disable Driver Verifier in Windows 10 | Tutorials (tenforums.com)



2) Learn the methods to recover from using the tool by booting into safe mode and running one or more of these commands:

verifier /reset

verifier /bootmode resetonbootfail



3) Make a new restore point:




4) When starting the tool:

a) Select all non-Microsoft drivers

b) select no Microsoft drivers

c) Select the three customized tests in the Ten Forums link



5) Plan to run the tool with various customized tests for approximately 48 hours.


6) 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.


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

Thanks again ZBook- unlikely able to do it today or tomorrow-
Interestingly - ESET said it had a update- so I did, it said reboot the machine- I did - then 4 reboots in a row- turn to BSOD
Here are the files I collected-
Tuneup.log
OFFICE-(2024-04-18_14-02-07).zip
041824-7234-01.dmp
041824-6890-01.dmp

1) The BIOS Version/Date American Megatrends Inc. P1.00, 3/16/2020

Upgrade the BIOS: 1.0 > 1.2 (most up to date non-beta BIOS




2) The installed RAM (CMK16GX4M2B3000C15) were not seen on the Qualified Vendor List (QVL)

Memtest86+ was designed to test for malfunctioning RAM.

Memtest86+ was not designed to test for incompatible RAM.

The BSOD so far are typical of malfunctioning or incompatible RAM.

Plan to run WDV to rule out misbehaving drivers.

(there may or may not be misbehaving drivers)

If there are recurrent BSOD after completing WDV testing then plan to swap test RAM on the QVL:



3) The other link that you had viewed got you anxious or worried about a specific WDV customized test.

That should never have happened.

If you have QVL RAM then you can skip WDV testing.

Bios has been updated- no issues thus far-
Will do the WDV next.
Have a great weekend!!!!

When do you plan to start WDV?

What is the availability of QVL RAM for testing purposes?

So it might awhile- I have a very busy weekend and week ahead-
I have the original sticks sent with machine- I can pop them in to test with.
I have also a backup - purchase plan if they don't work as well.
These being on the QVL list for sure!
Thanks Z!

Ok.

If you install QVL RAM and there are no longer BSOD then you've identified the problem.

WDV then is no longer needed however it can be used as preventative maintenance too.

zbook said:

WDV then is no longer needed however it can be used as preventative maintenance too.

Click to expand...

No it can't and I think you've misunderstood what that term means. It's a troubleshooting tool used for identifying common programming bugs with drivers, running it on a regular basis isn't going to prevent those issues from occurring.

WDV can be used for any purpose desired.

okay so here is a update although delayed-

Updated my Bios to the latest version as per MB manufacture.

Also updated my ram to 32 gig with Manufacture QVL. ( Also put them in the right slots- where in 2,4- Put them in 1,3 where they belong-i think.

I have been able to clone my drive no issues- so I hope it continues as such- will keep you informed.

Please monitor the computer using reliability monitor: