Solved Getting random BSOD pretty much daily

ughel2048 · Jan 19, 2024

I did reboot after running DDU since I wanted to disable Safe Mode. Do I have to do anything else now? Didn't have a BSOD for now but I will tell you if it happens again. Thanks for the help

zbook · Jan 19, 2024

Please post a new V2 share link into the newest post,

ughel2048 · Jan 19, 2024

Here is the download link to V2: DESKTOP-ADMIN-(2024-01-19_17-29-46).zip

zbook · Jan 19, 2024

Find a flash drive that you can format (> or = 8 GB).

Create a bootable Windows 11 Media Creation Tool (MCT) (Windows 11 iso).

Download Official Windows 11 ISO file from Microsoft Tutorial

This tutorial will show you how to download an official Windows 11 ISO file from Microsoft. Microsoft provides ISO files for Windows 11 to download. You can use these ISO files to clean install or in-place upgrade Windows 11. The Flight Hub can also help you keep updated on which Windows 11...

www.elevenforum.com

Download Windows 11

ughel2048 · Jan 19, 2024

I have done both

zbook · Jan 19, 2024

Today is Jan 19.
There were two BSOD on Jan 18.

Plan to run chkdsk /b /v overnight while sleeping from the bootable flash drive.

Boot to the flash drive > Windows Recovery Environment (RE) > command prompt > type:

bcdedit | find "osdevice"

(Record the drive letter.)

chkdsk /b /v W: (change the drive letter to the drive letter displayed in the earlier result)

Post a new V2 share link after completing the chkdsk and for any new BSOD.

Code:

Event[23324]
  Log Name: System
  Source: Microsoft-Windows-Ntfs
  Date: 2024-01-19T15:06:18.5260000Z
  Event ID: 98
  Task: N/A
  Level: Error
  Opcode: Info 

  Keyword: N/A
  User: S-1-5-18
  User Name: NT-AUTORIT─T\SYSTEM
  Computer: DESKTOP-Admin
  Description:
Volume C: (\Device\HarddiskVolume2) needs to be taken offline to perform a Full Chkdsk.  Please run "CHKDSK /F" locally via the command line, or run "REPAIR-VOLUME <drive:>" locally or remotely via PowerShell.

zbook · Jan 19, 2024

Make 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

Search for C:\Windows\memory.dmp > save to downloads folder > zip > post a share link

ughel2048 · Jan 19, 2024

If I would boot into my USB Drive it would show me the options to install windows again, how would I open WinRE from there?

zbook · Jan 19, 2024

1) boot to the Windows 11 iso
2) it may take 5 minutes displaying the windows icon
3) Use the default settings for language, time, currency, and keyboard
4) click next
5) In the left lower corner click Repair your computer
6) click troubleshooting
7) click command prompt
You should see a pop up with title bar: Administrator: X:\windows\system32\cmd.exe

zbook · Jan 19, 2024

Unless you're running chkdsk /b /v now please perform post #27

ughel2048 · Jan 19, 2024

Memory Dump File MEMORY.DMP
V2 DESKTOP-ADMIN-(2024-01-20_01-41-02).zip

Ran the stuff while I booted from the iso file and did both of those things after

zbook · Jan 19, 2024

The memory dump is very large.

Please compress /zip the file > post a new link

The logs did not report a new chkdsk result.

Please run:

https://www.tenforums.com/attachments/bsod-crashes-debugging/317041d1612147952-batch-files-use-bsod-debugging-chkdskfromevent.bat

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

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

Start the tool with these settings:

a) select all non-Microsoft drivers
b) select no Microsoft drivers
c) Select the three tests in the Ten Forums tutorial

Plan to run the tool with various customized tests during the next 48 hours.

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.

zbook · Jan 19, 2024

1) Uninstall Glasswire using the applicable uninstall tool:

gwdrv GlassWire Driver c:\windows\system32\drivers\gwdrv.sys

How to completely uninstall GlassWire

Run the Programs and Features program to uninstall the GlassWire program. Uninstall GlassWire If you want to completely remove GlassWire then remove or rename all GlassWire folders and data. Restart Windows. Install the latest version of the GlassWire installer. If you do not have it...

forum.glasswire.com

How to uninstall the GlassWire program from Windows Programs and Features

Once at the Programs and Features window appears, you can select GlassWire and uninstall it: To uninstall GlassWire either: A. Use the Uninstall button Select GlassWire Click on the Uninstall/Change button above the list of programs. B. Use the GlassWire shortcut menu Right-click...

forum.glasswire.com

2) Uninstall and reinstall:

e1i68x64 Intel(R) PRO/1000 PCI Express Network Connection Driver I c:\windows\system32\drivers\e1i68x64.sys

3) Uninstall the Nvidia GPU driver using DDU

Reinstall a driver version different from: 31.0.15.4665 and 31.0.15.4633

4) Make a new restore point

5) Start WDV with the steps in post #32

Code:

gwdrv    GlassWire Driver    c:\windows\system32\drivers\gwdrv.sys

Code:

Name    [00000001] Intel(R) I211 Gigabit Network Connection
Adapter Type    Ethernet 802.3
Product Type    Intel(R) I211 Gigabit Network Connection
Installed    Yes
PNP Device ID    PCI\VEN_8086&DEV_1539&SUBSYS_85F01043&REV_03\6&14BB3B56&0&0000020B
Last Reset    1/20/2024 1:10 AM
Index    1
Service Name    e1i68x64
Driver    C:\WINDOWS\SYSTEM32\DRIVERS\E1I68X64.SYS (12.19.1.32, 562.50 KB (576,000 bytes), 5/7/2022 11:37 AM)

Code:

Name    NVIDIA GeForce RTX 3070 Ti
PNP Device ID    PCI\VEN_10DE&DEV_2482&SUBSYS_88131043&REV_A1\4&1FC990D7&0&0019
Adapter Type    NVIDIA GeForce RTX 3070 Ti, NVIDIA compatible
Adapter Description    NVIDIA GeForce RTX 3070 Ti
Adapter RAM    (1,048,576) bytes
Installed Drivers    C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispig.inf_amd64_72a60bcfb646da4c\nvldumdx.dll,C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispig.inf_amd64_72a60bcfb646da4c\nvldumdx.dll,C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispig.inf_amd64_72a60bcfb646da4c\nvldumdx.dll,C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispig.inf_amd64_72a60bcfb646da4c\nvldumdx.dll
Driver Version    31.0.15.4665
INF File    oem32.inf (Section071 section)
Driver    C:\WINDOWS\SYSTEM32\DRIVERSTORE\FILEREPOSITORY\NV_DISPIG.INF_AMD64_72A60BCFB646DA4C\NVLDDMKM.SYS (31.0.15.4665, 56.03 MB (58,756,216 bytes), 1/17/2024 8:54 PM)

x BlueRobot · Jan 20, 2024

ughel2048 said:
Do I have to do anything else now? Didn't have a BSOD for now but I will tell you if it happens again. Thanks for the help

No, I would just use the machine as you normally would for the next few days and see if it crashes again.

P.S. Driver Verifier isn't going to be helpful with a Stop 0x133 and will likely just cause false positives because of the settings being recommended. You also haven't had any additional crashes since removing that broadcast driver. In addition to that, there is no evidence either to suggest that any of the drivers mentioned by zbook are causing issues.

zbook · Jan 20, 2024

When available please update the progress with the steps in post #33.

ughel2048 · Jan 21, 2024

I'll do the steps if I experience another BSOD, until now I didn't have any issues

zbook · Jan 21, 2024

The WDV testing method is more efficient than the watch and wait.

The tool was designed to find misbehaving drivers.

It allows the user to more quickly determine whether there are misbehaving drivers, or malfunctioning hardware.

With the backup images and restore points it's in your best interest to benefit from using the Microsoft Windows tool.

x BlueRobot · Jan 21, 2024

zbook said:
The WDV testing method is more efficient than the watch and wait.

No it isn't, Driver Verifier is not designed to test against Stop 0x133 bugchecks and the settings you're suggesting are completely irrelevant! They're for testing bugs with IRP handling; one of which just produces an additional log file and doesn't even test anything.

The user has reported no crashes for the past few days since removing that one problematic driver.

zbook · Jan 21, 2024

For future viewers:

The above comments in post #34 and #38 are incorrect.

In our forum the immediate short term and long term are important.

The misbehaving drivers in the latest crash (Debug session time: Thu Jan 18 11:31:09.278 2024 (UTC - 6:00)) were not troubleshooted and could have been tested using WDV.

WDV is very useful for BSOD bugcheck 133.

The (WDV) tool is designed to stress test drivers.

It can provide a quicker and more thorough assessment and indicate whether misbehaving drivers were or were not troubleshooted.