6-month Old Desktop PC BSOD

z790 · Jun 6, 2024

Here is the DropBox link for V2 log collector: Dropbox

I would like some help trying to diagnose BSOD issues please.

22 May: PC restarted with no BSOD but a minidump was produced.

01 June: BSOD after being woken from sleep (STOP CODE: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED - minidump was produced.

06 June: PC froze completely and restarted itself after about 30 seconds. No BSOD but a minidump was produced.

Thanks

cereberus · Jun 6, 2024

z790 said:
Here is the DropBox link for V2 log collector: Dropbox

I would like some help trying to diagnose BSOD issues please.

22 May: PC restarted with no BSOD but a minidump was produced.

01 June: BSOD after being woken from sleep (STOP CODE: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED - minidump was produced.

06 June: PC froze completely and restarted itself after about 30 seconds. No BSOD but a minidump was produced.

Thanks

Disable fast start, fully shutdown pc and restart. This normally sorts this type of issue.

z790 · Jun 6, 2024

cereberus said:
Disable fast start, fully shutdown pc and restart. This normally sorts this type of issue.

Alright thanks I've disabled fast start and done a shutdown. Will let you know how it goes.

FreeBooter · Jun 6, 2024

If new device drivers or system services have been added recently, try removing or updating them. Try to determine what changed in the system that caused the new bug check code to appear.
Look in Device Manager to see if any devices are marked with an exclamation point (!), which indicates a problem. Review the events log displayed in the properties for any faulting device driver. Try to update the related driver.
Check the System Log in Event Viewer for additional error messages that might help pinpoint the device or driver that is causing the error. Look for critical errors in the system log that occurred in the same time window as the blue screen.
If you recently added hardware to the system, try removing or replacing it. Or check with the manufacturer to see if any patches are available.
Install Windows updates.
If you are overclocking (pushing the components beyond their design) you should revert to default at least until the crashing is solved. If you don't know what it is you probably are not overclocking.
Use SpeedFan to monitor temperatures in computers, overheating can cause BSOD.
Use Memtest86+ disc to check system memory's (RAM's) for errors.
Use CrystalDiskInfo to check SMART health report of the hard disk drive (HDD).

Open the Command Prompt with administrative privileges and execute bellow commands one at a time.

Code:

Dism /online /cleanup-image /restorehealth



Sfc /scannow


Chkdsk C: /f

For dumps to be produced, The following should be correct

Page file must be on the same drive as your operating system

Page file base allocation size must be greater than installed physical RAM

Windows Error Reporting (WER) system service should be set to MANUAL

Set page file to system managed on the OS drive

Set system crash/recovery options to "kernel memory dump"

User account control must be running.

Sometimes SSD drives with older firmware do not create DMPS (update firmware)

Cleaner applications like Ccleaner delete DMP files so dont run them until you are fixed.

Bad Physical RAM may prevent the data from being saved and written to a file on reboot. If you suspect bad RAM run Memtest from this wiki

Full memory dumps can also be deleted (in win 7) if your HD space is under 25 gigs, but if you configured your system as the above suggests, you should not be generating full dumps.

zbook · Jun 6, 2024

Please perform the following steps:

1) Run Tuneup plus > post a share link

https://www.tenforums.com/attachments/bsod-crashes-debugging/360139d1645183596-batch-files-use-bsod-debugging-tuneup_plus_log.zip

Batch files for use in BSOD debugging - Windows 10 Help Forums

Information This thread is for use by the BSOD team to store batch files that can be used to collect additional data, fix settings or anything else that is useful in debugging BSOD problems in Windows 10. The way I see it working is the first

www.tenforums.com

Batch files for use in BSOD debugging - Windows 10 Help Forums

Information This thread is for use by the BSOD team to store batch files that can be used to collect additional data, fix settings or anything else that is useful in debugging BSOD problems in Windows 10. The way I see it working is the first

www.tenforums.com

2) Create a new restore point:

Create System Restore Point in Windows 11

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

3) Uninstall and reinstall the Nvidia GPU drivers nvlddmkm.sys using Display Driver Uninstaller (DDU) and reinstall from the Nvidia website

Display Driver Uninstaller: How to use

How to Use Display Driver Uninstaller to Uninstall any Installed Display Driver

www.sevenforums.com

Display Driver Uninstaller (DDU) download latest version 18.1.1.0

Official Display Driver Uninstaller (DDU) download website. DDU is a driver removal utility that can help you completely uninstall AMD/NVIDIA/INTEL graphics card drivers and packages from your system, trying to remove all leftovers (including registry keys, folders and files, driver store).

www.wagnardsoft.com

Download The Latest Official NVIDIA Drivers

Download the latest official NVIDIA drivers to enhance your PC gaming experience and run apps faster.

www.nvidia.com

4) The BIOS Version/Date American Megatrends International, LLC. FHc, 9/11/2023

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

Code:

Name    NVIDIA GeForce RTX 4070
PNP Device ID    PCI\VEN_10DE&DEV_2786&SUBSYS_41141458&REV_A1\4&8BD6E8D&0&0008
Adapter Type    NVIDIA GeForce RTX 4070, NVIDIA compatible
Adapter Description    NVIDIA GeForce RTX 4070
Adapter RAM    (1,048,576) bytes
Installed Drivers    C:\Windows\System32\DriverStore\FileRepository\nv_dispsig.inf_amd64_72bcbd9fe0ef4539\nvldumdx.dll,C:\Windows\System32\DriverStore\FileRepository\nv_dispsig.inf_amd64_72bcbd9fe0ef4539\nvldumdx.dll,C:\Windows\System32\DriverStore\FileRepository\nv_dispsig.inf_amd64_72bcbd9fe0ef4539\nvldumdx.dll,C:\Windows\System32\DriverStore\FileRepository\nv_dispsig.inf_amd64_72bcbd9fe0ef4539\nvldumdx.dll
Driver Version    32.0.15.5585
INF File    oem44.inf (Section079 section)
IRQ Channel    IRQ 4294967255
Driver    C:\WINDOWS\SYSTEM32\DRIVERSTORE\FILEREPOSITORY\NV_DISPSIG.INF_AMD64_72BCBD9FE0EF4539\NVLDDMKM.SYS (32.0.15.5585, 57.86 MB (60,675,192 bytes), 6/06/2024 3:06 AM)

Code:

nvlddmkm.sys Fri Jun 23 16:22:34 2023 (64960D1A)

z790 · Jun 7, 2024

zbook said:
Please perform the following steps:

1) Run Tuneup plus > post a share link

https://www.tenforums.com/attachments/bsod-crashes-debugging/360139d1645183596-batch-files-use-bsod-debugging-tuneup_plus_log.zip

Batch files for use in BSOD debugging - Windows 10 Help Forums

Information This thread is for use by the BSOD team to store batch files that can be used to collect additional data, fix settings or anything else that is useful in debugging BSOD problems in Windows 10. The way I see it working is the first

www.tenforums.com

Batch files for use in BSOD debugging - Windows 10 Help Forums

Information This thread is for use by the BSOD team to store batch files that can be used to collect additional data, fix settings or anything else that is useful in debugging BSOD problems in Windows 10. The way I see it working is the first

www.tenforums.com

2) Create a new restore point:

Create System Restore Point in Windows 11

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

3) Uninstall and reinstall the Nvidia GPU drivers nvlddmkm.sys using Display Driver Uninstaller (DDU) and reinstall from the Nvidia website

Display Driver Uninstaller: How to use

How to Use Display Driver Uninstaller to Uninstall any Installed Display Driver

www.sevenforums.com

Display Driver Uninstaller (DDU) download latest version 18.1.1.0

Official Display Driver Uninstaller (DDU) download website. DDU is a driver removal utility that can help you completely uninstall AMD/NVIDIA/INTEL graphics card drivers and packages from your system, trying to remove all leftovers (including registry keys, folders and files, driver store).

www.wagnardsoft.com

Download The Latest Official NVIDIA Drivers

Download the latest official NVIDIA drivers to enhance your PC gaming experience and run apps faster.

www.nvidia.com

4) The BIOS Version/Date American Megatrends International, LLC. FHc, 9/11/2023

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

Code:

Name NVIDIA GeForce RTX 4070 PNP Device ID PCI\VEN_10DE&DEV_2786&SUBSYS_41141458&REV_A1\4&8BD6E8D&0&0008 Adapter Type NVIDIA GeForce RTX 4070, NVIDIA compatible Adapter Description NVIDIA GeForce RTX 4070 Adapter RAM (1,048,576) bytes Installed Drivers C:\Windows\System32\DriverStore\FileRepository\nv_dispsig.inf_amd64_72bcbd9fe0ef4539\nvldumdx.dll,C:\Windows\System32\DriverStore\FileRepository\nv_dispsig.inf_amd64_72bcbd9fe0ef4539\nvldumdx.dll,C:\Windows\System32\DriverStore\FileRepository\nv_dispsig.inf_amd64_72bcbd9fe0ef4539\nvldumdx.dll,C:\Windows\System32\DriverStore\FileRepository\nv_dispsig.inf_amd64_72bcbd9fe0ef4539\nvldumdx.dll Driver Version 32.0.15.5585 INF File oem44.inf (Section079 section) IRQ Channel IRQ 4294967255 Driver C:\WINDOWS\SYSTEM32\DRIVERSTORE\FILEREPOSITORY\NV_DISPSIG.INF_AMD64_72BCBD9FE0EF4539\NVLDDMKM.SYS (32.0.15.5585, 57.86 MB (60,675,192 bytes), 6/06/2024 3:06 AM)

Code:

nvlddmkm.sys Fri Jun 23 16:22:34 2023 (64960D1A)

Wow didn't realise I was using a beta BIOS. I've updated it to the latest stable version FI. I've attached the tuneup log.

zbook · Jun 7, 2024

Tuneup plus results were good.

Monitor the computer using: View Reliability History in Windows 11 Tutorial

RJARRRPCGP · Jun 7, 2024

Sounds like "Raptor Lake rapid-degradation syndrome".

(especially 14-gen Core i9!)

Usually sudden crashes out-of-the-blue. It can be within a 6-month period. Possibly not even 1 year before hardware failure.

This is something I have been seeing reports about.

Update:

Looks like 14th-gen Core i7s are affected, too!

z790 · Jun 16, 2024

zbook said:
Tuneup plus results were good.

Monitor the computer using: View Reliability History in Windows 11 Tutorial

I got another BSOD. Here's the minidump: Dropbox

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED (7e)
This is a very common BugCheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff8043bc80d0f, The address that the exception occurred at
Arg3: ffffc001d4a67798, Exception Record Address
Arg4: ffffc001d4a66fb0, Context Record Address

Debugging Details:
------------------


KEY_VALUES_STRING: 1

    Key  : AV.Fault
    Value: Read

    Key  : Analysis.CPU.mSec
    Value: 1343

    Key  : Analysis.Elapsed.mSec
    Value: 24108

    Key  : Analysis.IO.Other.Mb
    Value: 10

    Key  : Analysis.IO.Read.Mb
    Value: 0

    Key  : Analysis.IO.Write.Mb
    Value: 35

    Key  : Analysis.Init.CPU.mSec
    Value: 156

    Key  : Analysis.Init.Elapsed.mSec
    Value: 36783

    Key  : Analysis.Memory.CommitPeak.Mb
    Value: 101

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0x1000007e

    Key  : Bugcheck.Code.TargetModel
    Value: 0x1000007e

    Key  : Failure.Bucket
    Value: AV_nt!MiZeroLocalPages

    Key  : Failure.Hash
    Value: {3491c7d3-2e59-afd4-fd99-9f4a8e930510}

    Key  : Hypervisor.Enlightenments.ValueHex
    Value: 1417df84

    Key  : Hypervisor.Flags.AnyHypervisorPresent
    Value: 1

    Key  : Hypervisor.Flags.ApicEnlightened
    Value: 0

    Key  : Hypervisor.Flags.ApicVirtualizationAvailable
    Value: 1

    Key  : Hypervisor.Flags.AsyncMemoryHint
    Value: 0

    Key  : Hypervisor.Flags.CoreSchedulerRequested
    Value: 0

    Key  : Hypervisor.Flags.CpuManager
    Value: 1

    Key  : Hypervisor.Flags.DeprecateAutoEoi
    Value: 1

    Key  : Hypervisor.Flags.DynamicCpuDisabled
    Value: 1

    Key  : Hypervisor.Flags.Epf
    Value: 0

    Key  : Hypervisor.Flags.ExtendedProcessorMasks
    Value: 1

    Key  : Hypervisor.Flags.HardwareMbecAvailable
    Value: 1

    Key  : Hypervisor.Flags.MaxBankNumber
    Value: 0

    Key  : Hypervisor.Flags.MemoryZeroingControl
    Value: 0

    Key  : Hypervisor.Flags.NoExtendedRangeFlush
    Value: 0

    Key  : Hypervisor.Flags.NoNonArchCoreSharing
    Value: 1

    Key  : Hypervisor.Flags.Phase0InitDone
    Value: 1

    Key  : Hypervisor.Flags.PowerSchedulerQos
    Value: 0

    Key  : Hypervisor.Flags.RootScheduler
    Value: 0

    Key  : Hypervisor.Flags.SynicAvailable
    Value: 1

    Key  : Hypervisor.Flags.UseQpcBias
    Value: 0

    Key  : Hypervisor.Flags.Value
    Value: 21631230

    Key  : Hypervisor.Flags.ValueHex
    Value: 14a10fe

    Key  : Hypervisor.Flags.VpAssistPage
    Value: 1

    Key  : Hypervisor.Flags.VsmAvailable
    Value: 1

    Key  : Hypervisor.RootFlags.AccessStats
    Value: 1

    Key  : Hypervisor.RootFlags.CrashdumpEnlightened
    Value: 1

    Key  : Hypervisor.RootFlags.CreateVirtualProcessor
    Value: 1

    Key  : Hypervisor.RootFlags.DisableHyperthreading
    Value: 0

    Key  : Hypervisor.RootFlags.HostTimelineSync
    Value: 1

    Key  : Hypervisor.RootFlags.HypervisorDebuggingEnabled
    Value: 0

    Key  : Hypervisor.RootFlags.IsHyperV
    Value: 1

    Key  : Hypervisor.RootFlags.LivedumpEnlightened
    Value: 1

    Key  : Hypervisor.RootFlags.MapDeviceInterrupt
    Value: 1

    Key  : Hypervisor.RootFlags.MceEnlightened
    Value: 1

    Key  : Hypervisor.RootFlags.Nested
    Value: 0

    Key  : Hypervisor.RootFlags.StartLogicalProcessor
    Value: 1

    Key  : Hypervisor.RootFlags.Value
    Value: 1015

    Key  : Hypervisor.RootFlags.ValueHex
    Value: 3f7

    Key  : WER.OS.Branch
    Value: ni_release

    Key  : WER.OS.Version
    Value: 10.0.22621.1


BUGCHECK_CODE:  7e

BUGCHECK_P1: ffffffffc0000005

BUGCHECK_P2: fffff8043bc80d0f

BUGCHECK_P3: ffffc001d4a67798

BUGCHECK_P4: ffffc001d4a66fb0

FILE_IN_CAB:  061724-14203-01.dmp

EXCEPTION_RECORD:  ffffc001d4a67798 -- (.exr 0xffffc001d4a67798)
ExceptionAddress: fffff8043bc80d0f (nt!MiZeroLocalPages+0x000000000000026f)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

CONTEXT:  ffffc001d4a66fb0 -- (.cxr 0xffffc001d4a66fb0)
rax=ffff9b8000000000 rbx=ffffffffffffffff rcx=00000000000019c8
rdx=ffff9c400001b800 rsi=fffff8043c66b040 rdi=5400003f7bffffff
rip=fffff8043bc80d0f rsp=ffffc001d4a679d0 rbp=ffff878d975fbbb0
 r8=0000000000000000  r9=ffffc001d4a67870 r10=0000000000000010
r11=ffffc001d4a679a0 r12=0000000000000000 r13=0000000000000000
r14=bfffa7673fffffd0 r15=c0000be73fffffd0
iopl=0         nv up ei pl zr na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00050246
nt!MiZeroLocalPages+0x26f:
fffff804`3bc80d0f 498b4618        mov     rax,qword ptr [r14+18h] ds:002b:bfffa767`3fffffe8=????????????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

READ_ADDRESS: fffff8043c71c4a8: Unable to get MiVisibleState
Unable to get NonPagedPoolStart
Unable to get NonPagedPoolEnd
Unable to get PagedPoolStart
Unable to get PagedPoolEnd
unable to get nt!MmSpecialPagesInUse
 ffffffffffffffff

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%p referenced memory at 0x%p. The memory could not be %s.

EXCEPTION_CODE_STR:  c0000005

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  ffffffffffffffff

EXCEPTION_STR:  0xc0000005

STACK_TEXT:
ffffc001`d4a679d0 fffff804`3bd93b0f     : ffff878d`974fc090 ffff878d`00000003 00000000`00000000 00000000`00000000 : nt!MiZeroLocalPages+0x26f
ffffc001`d4a67ae0 fffff804`3bc0e957     : ffff878d`978d6040 00000000`00000080 fffff804`3bd939a0 00000000`00000000 : nt!MiZeroNodePages+0x16f
ffffc001`d4a67b30 fffff804`3be1f3b4     : ffffd580`4d556180 ffff878d`978d6040 fffff804`3bc0e900 00000000`00000000 : nt!PspSystemThreadStartup+0x57
ffffc001`d4a67b80 00000000`00000000     : ffffc001`d4a68000 ffffc001`d4a61000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x34


SYMBOL_NAME:  nt!MiZeroLocalPages+26f

MODULE_NAME: nt

IMAGE_VERSION:  10.0.22621.3733

STACK_COMMAND:  .cxr 0xffffc001d4a66fb0 ; kb

IMAGE_NAME:  ntkrnlmp.exe

BUCKET_ID_FUNC_OFFSET:  26f

FAILURE_BUCKET_ID:  AV_nt!MiZeroLocalPages

OS_VERSION:  10.0.22621.1

BUILDLAB_STR:  ni_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {3491c7d3-2e59-afd4-fd99-9f4a8e930510}

Followup:     MachineOwner
---------

zbook · Jun 16, 2024

1) Create a new restore point:

Create System Restore Point in Windows 11

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

2) Read this tutorial 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

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 and 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.

z790 · Jun 18, 2024

zbook said:
1) Create a new restore point:

Create System Restore Point in Windows 11

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

2) Read this tutorial 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

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 and 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.

So it had another BSOD whilst running driver verifier. Here is the new V2 link: Dropbox

verifier settings:

Code:

Verifier Flags: 0x00100610

  Standard Flags:

    [ ] 0x00000001 Special pool.
    [ ] 0x00000002 Force IRQL checking.
    [ ] 0x00000008 Pool tracking.
    [X] 0x00000010 I/O verification.
    [ ] 0x00000020 Deadlock detection.
    [ ] 0x00000080 DMA checking.
    [ ] 0x00000100 Security checks.
    [ ] 0x00000800 Miscellaneous checks.
    [ ] 0x00020000 DDI compliance checking.

  Additional Flags:

    [ ] 0x00000004 Randomized low resources simulation.
    [X] 0x00000200 Force pending I/O requests.
    [X] 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.
    [ ] 0x00040000 Systematic low resources simulation.
    [ ] 0x00080000 DDI compliance checking (additional).
    [ ] 0x00200000 NDIS/WIFI verification.
    [ ] 0x00800000 Kernel synchronization delay fuzzing.
    [ ] 0x01000000 VM switch verification.
    [ ] 0x02000000 Code integrity checks.

  Internal Flags:

    [X] 0x00100000 Extended Verifier flags (internal).

    [X] Indicates flag is enabled.

  Boot Mode:

    Persistent

  Rules:

    All rules are using default settings

  Verified Drivers:

    npcap.sys
    ctiio64.sys
    camodriver.sys
    vacrnckd.sys
    nvlddmkm.sys
    igdkmdn64.sys
    netwtw14.sys
    ialpss2_i2c_adl.sys
    teedriverw10x64.sys
    rt25cx21x64.sys
    iccwdt.sys
    ialpss2_gpio2_adl.sys
    hideventfilter.sys
    nvvad64v.sys
    nvmoduletracker.sys
    nvvhci.sys
    amdtools64.sys
    iocbios2.sys
    nvhda64v.sys
    rtkvhd64.sys
    dump_dumpstorport.sys
    dump_stornvme.sys
    dump_dumpfve.sys
    gdrv3.sys
    mpksldrv.sys

Thanks for your help!

zbook · Jun 18, 2024

z790 said:
So it had another BSOD whilst running driver verifier. Here is the new V2 link: Dropbox

Thanks for your help!

The V2 commands were posted in the share link.

Please repost with V2 results.

z790 · Jun 18, 2024

zbook said:
The V2 commands were posted in the share link.

Please repost with V2 results.

Dropbox

www.dropbox.com

zbook · Jun 18, 2024

Please restart WDV with these customized tests:

Code:

    [ ] 0x00000001 Special pool.
    [ ] 0x00000002 Force IRQL checking.
    [ ] 0x00000008 Pool tracking.
    [ ] 0x00000020 Deadlock detection.
    [ ] 0x00000080 DMA checking.
    [ ] 0x00000100 Security checks.
    [ ] 0x00000800 Miscellaneous checks.
    [ ] 0x00020000 DDI compliance 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.

zbook · Jun 18, 2024

It's 3am here > heading to bed> will check the thread later in the day

z790 · Jun 18, 2024

zbook said:
Please restart WDV with these customized tests:

Code:

[ ] 0x00000001 Special pool. [ ] 0x00000002 Force IRQL checking. [ ] 0x00000008 Pool tracking. [ ] 0x00000020 Deadlock detection. [ ] 0x00000080 DMA checking. [ ] 0x00000100 Security checks. [ ] 0x00000800 Miscellaneous checks. [ ] 0x00020000 DDI compliance 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.

ok im running verifier again with those new settings and i didnt get any immediate BSOD. here are the /querysettings

Code:

C:\Users\allen>verifier /querysettings

Verifier Flags: 0x001209ab

  Standard Flags:

    [X] 0x00000001 Special pool.
    [X] 0x00000002 Force IRQL checking.
    [X] 0x00000008 Pool tracking.
    [ ] 0x00000010 I/O verification.
    [X] 0x00000020 Deadlock detection.
    [X] 0x00000080 DMA checking.
    [X] 0x00000100 Security checks.
    [X] 0x00000800 Miscellaneous checks.
    [X] 0x00020000 DDI compliance checking.

  Additional Flags:

    [ ] 0x00000004 Randomized low resources simulation.
    [ ] 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.
    [ ] 0x00040000 Systematic low resources simulation.
    [ ] 0x00080000 DDI compliance checking (additional).
    [ ] 0x00200000 NDIS/WIFI verification.
    [ ] 0x00800000 Kernel synchronization delay fuzzing.
    [ ] 0x01000000 VM switch verification.
    [ ] 0x02000000 Code integrity checks.

  Internal Flags:

    [X] 0x00100000 Extended Verifier flags (internal).

    [X] Indicates flag is enabled.

  Boot Mode:

    Persistent

  Rules:

    All rules are using default settings

  Extensions:

    wdm: rules.default

  Verified Drivers:

    npcap.sys
    googlehaxm.sys
    ctiio64.sys
    camodriver.sys
    vacrnckd.sys
    nvlddmkm.sys
    igdkmdn64.sys
    ialpss2_i2c_adl.sys
    teedriverw10x64.sys
    rt25cx21x64.sys
    iccwdt.sys
    ialpss2_gpio2_adl.sys
    hideventfilter.sys
    nvvad64v.sys
    nvmoduletracker.sys
    nvvhci.sys
    amdtools64.sys
    iocbios2.sys
    nvhda64v.sys
    rtkvhd64.sys
    dump_dumpstorport.sys
    dump_stornvme.sys
    dump_dumpfve.sys
    gdrv3.sys
    netwtw14.sys

zbook · Jun 18, 2024

Please restart WDV with these customized tests:

Code:

    [ ] 0x00000010 I/O verification.
    [ ] 0x00002000 Invariant MDL checking for stack.
    [ ] 0x00004000 Invariant MDL checking for driver.
    [ ] 0x00008000 Power framework delay fuzzing.
    [ ] 0x00010000 Port/miniport interface checking.
    [ ] 0x00040000 Systematic low resources simulation.
    [ ] 0x00200000 NDIS/WIFI verification.
    [ ] 0x00800000 Kernel synchronization delay fuzzing.
    [ ] 0x01000000 VM switch verification.
    [ ] 0x02000000 Code integrity checks.

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.

z790 · Jun 18, 2024

zbook said:
Please restart WDV with these customized tests:

Code:

[ ] 0x00000010 I/O verification. [ ] 0x00002000 Invariant MDL checking for stack. [ ] 0x00004000 Invariant MDL checking for driver. [ ] 0x00008000 Power framework delay fuzzing. [ ] 0x00010000 Port/miniport interface checking. [ ] 0x00040000 Systematic low resources simulation. [ ] 0x00200000 NDIS/WIFI verification. [ ] 0x00800000 Kernel synchronization delay fuzzing. [ ] 0x01000000 VM switch verification. [ ] 0x02000000 Code integrity checks.

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.

So I'm getting a bsod on restart now. It says driver verifier detected violation it just stuck on that screen it's not restarting

z790 · Jun 18, 2024

Yeah it's stuck on a bsod loop now whenever I turn it off and back on

z790 · Jun 18, 2024

So i managed to fix the bsod loop by logging into windows 10 (i have dual boot as when i upgraded to Win11 i kept windows 10 on my old SSD) and following these instructions:

https://www.reddit.com/r/techsupport/comments/o6a6ph/comment/h2r5c99

I checked the minidumps and there was a new minidump that the bsod loop generated. The minidump suggests that camodriver.sys caused the bsod. This belongs to reincubate camo studio software so i'm going to uninstall it. Here is the link to the newest V2 that includes the BSOD loop minidump: Dropbox

6-month Old Desktop PC BSOD

Member

My Computer

Well-known member

My Computer

Member

My Computer

Well-known member

My Computer

Well-known member

My Computer

Member

Attachments

My Computer

Well-known member

My Computer

Well-known member

My Computers

Member

My Computer

Well-known member

My Computer

Member

My Computer

Well-known member

My Computer

Member

My Computer

Well-known member

My Computer

Well-known member

My Computer

Member

My Computer

Well-known member

My Computer

Member

Attachments

My Computer

Member

My Computer

Member

My Computer

Similar threads