IQRL Not less or equal

did another clean install just because I can. Didn't touch anything other than mobo drivers update and NVidia drivers.
Still, display goes out on startup and presumably BSOD. heres another dm collector. thanks!

Ztruker said:

Most recent dump indicates a Corsair problem:

Code:

*** WARNING: Unable to verify timestamp for CorsairVBusDriver.sys
*** ERROR: Module load completed but symbols could not be loaded for CorsairVBusDriver.sys
Probably caused by : CorsairVBusDriver.sys ( CorsairVBusDriver+14bb )

Disable CorsairLink4, F:\UTILITIES\Corsair Link\CorsairLink4.exe -startup in Startup tab of Task Manager. See if that resolves the problem. Looks to be some kind of dashboard, definitely not required.

If disabling fixes it you can look for an updated version or uninstall it (this would be my choice).

Checked a couple more dumps and they all show the same problem.

OK
I updated all my drivers including the Bluetooth drivers direct from asrock's product page for my motherboard.
Still got a crash on boot.

I think I might be hardware related but I have no idea where to start. I ran memtest overnight and a few hours and 0 errors.
I reseated the GPU.

another dm collector.

axe0 said:

A BSOD occured because driver verifier is enabled blaming the bluetooth drivers.
Check ASRock for drivers and disable driver verifier

• Open an admin command prompt
• Enter "verifier/reset" (without quotes)

Code:

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

Use !analyze -v to get detailed debugging information.

BugCheck C4, {2000, fffff801a1b71e73, 0, 426d6342}

*** WARNING: Unable to verify timestamp for bcbtums.sys
*** ERROR: Module load completed but symbols could not be loaded for bcbtums.sys
*** WARNING: Unable to verify checksum for win32k.sys
Probably caused by : bcbtums.sys ( bcbtums+1e73 )

Verify Flags Level 0x03a5efbb

  STANDARD FLAGS:
    [X] (0x00000000) Automatic Checks
    [X] (0x00000001) Special pool
    [X] (0x00000002) Force IRQL checking
    [X] (0x00000008) Pool tracking
    [X] (0x00000010) I/O verification
    [X] (0x00000020) Deadlock detection
    [X] (0x00000080) DMA checking
    [X] (0x00000100) Security checks
    [X] (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
    [X] (0x00002000) Invariant MDL checking for stack
    [X] (0x00004000) Invariant MDL checking for driver
    [X] (0x00008000) Power framework delay fuzzing
    [X] (0x00010000) Port/miniport interface checking
    [X] (0x00040000) Systematic low resources simulation
    [ ] (0x00080000) DDI compliance checking (additional)
    [X] (0x00200000) NDIS/WIFI verification
    [X] (0x00800000) Kernel synchronization delay fuzzing
    [X] (0x01000000) VM switch verification
    [X] (0x02000000) Code integrity checks

    [X] Indicates flag is enabled


Summary of All Verifier Statistics

  RaiseIrqls           0x6d
  AcquireSpinLocks     0x2f37
  Synch Executions     0x7
  Trims                0x3e5

  Pool Allocations Attempted             0x4aa5
  Pool Allocations Succeeded             0x4aa5
  Pool Allocations Succeeded SpecialPool 0x4aa5
  Pool Allocations With NO TAG           0x24
  Pool Allocations Failed                0x0

  Current paged pool allocations         0x79 for 00087D8C bytes
  Peak paged pool allocations            0x79 for 003DEACA bytes
  Current nonpaged pool allocations      0xf51 for 0057F81E bytes
  Peak nonpaged pool allocations         0xf51 for 0058F81E bytes

  Execute pool type count                0x0
  Execute page protection count          0x0
  Execute page mapping count             0x0
  Execute-Write section count            0x0
  Section alignment failures             0x0

fffff801a3bf4520: Unable to get MiVisibleState

Yes I disabled verifier with that method after every boot crash to get back to normal operation so I can write these. Did you mean something else? I only turn it on when I am ready to test for bsod. When I am installing /updating things verifier is turned off. I guess the one or two times I was actually able to boot with verifier were flukes..

Should I just run normally and see if I get no BSOD with out using verifier? I haven't gotten a BSOD since disabling oc, but then again I also haven't done anything like gaming and I have only spend a few hours doing this.

axe0 said:

Again: disable driver verifier BEFORE you continue!

• Open an admin command prompt
• Enter "verifier/reset" (without quotes)

Sure, I will now just run the pc normally and see if I blue screen. I never had issues getting out of crash loops, but maybe verifier crashes aren't representative of crashes resulting from normal computer use.

axe0 said:

When you have applied a suggestion, you should use your system under normal circumstances with NO tests unless otherwise specified.

Using tools like driver verifier without proper guidance can cause serious problems on a system like forcing a user to reinstall Windows all over again, because the user does not know how to get back in Windows after a BSOD boot loop caused by driver verifier.

Yeah I got a friend who bsod'd with verifier and he has never bsod'd normally. He is pretty tech savvy and knows how to get out of a crash loop. Since I do not use Bluetooth would it be a problem if I just uninstalled the Bluetooth driver while I'm at it? or is it an essential thing for the system?

axe0 said:

Driver verifier can cause crashes under any circumstances, it really does not matter because it can be any driver violating something.