Having a bunch of random BSOD (most caused by ntsokrnl.exe)

Page 3 of 7 FirstFirst 12345 ... LastLast

  1. Posts : 13,934
    Windows 10 Pro X64 21H1 19043.1503

    There is a full memory dump: 7/21/2020 8:25:49 PM 981.79 C:\Windows\MEMORY.DMP

    Copy that to another location, zip it and upload to Google Drive the post a link to it here please. Hoping it's a Driver Verifier generated dump.
      My Computers

  2. Posts : 32
    Windows 10 H
    Thread Starter

    Here's the link: Google Drive: Sign-in
      My Computer

  3. Posts : 13,934
    Windows 10 Pro X64 21H1 19043.1503

    I can't get it, requires me to sign in. You need to make it public.
      My Computers

  4. Posts : 32
    Windows 10 H
    Thread Starter

    Hmm weird. Try it now File Dump.zip - Google Drive
      My Computer

  5. Posts : 13,934
    Windows 10 Pro X64 21H1 19043.1503

    Much better, thanks.

    Wrong file. I need C:\Windows\MEMORY.DMP
      My Computers

  6. Posts : 32
    Windows 10 H
    Thread Starter

    Third time is the charm File Dump2.zip - Google Drive
      My Computer

  7. Posts : 13,934
    Windows 10 Pro X64 21H1 19043.1503

    Got the dump but Driver Verifier wasn't enabled when it occurred, rats!
      My Computers

  8. Posts : 32
    Windows 10 H
    Thread Starter

    Oh no!! =(

    - - - Updated - - -

    I got a new memory dump while driver verfifier was running,...hopefully theres something here: File Dump3.zip - Google Drive
      My Computer

  9. Posts : 13,934
    Windows 10 Pro X64 21H1 19043.1503

    It was another
    An attempt was made to access a pageable (or completely invalid) address at an
    interrupt request level (IRQL) that is too high.  This is usually
    caused by drivers using improper addresses.
    If a kernel debugger is available get the stack backtrace.
    Arg1: ffffffffffffff8b, memory referenced
    Arg2: 0000000000000002, IRQL
    Arg3: 0000000000000000, bitfield :
        bit 0 : value 0 = read operation, 1 = write operation
        bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
    Arg4: fffff80154ffb392, address which referenced memory
    Gather Information

    Examine the name of the driver if that was listed on the blue screen.

    Check the System Log in Event Viewer for additional error messages that might help pinpoint the device or driver that is causing the error. For more information, see Open Event Viewer. Look for critical errors in the system log that occurred in the same time window as the blue screen.

    Driver Verifier

    Driver Verifier is a tool that runs in real time to examine the behavior of drivers. For example, Driver Verifier checks the use of memory resources, such as memory pools. If it sees errors in the execution of driver code, it proactively creates an exception to allow that part of the driver code to be further scrutinized. The driver verifier manager is built into Windows and is available on all Windows PCs. To start the driver verifier manager, type Verifer at a command prompt. You can configure which drivers you would like to verify. The code that verifies drivers adds overhead as it runs, so try and verify the smallest number of drivers as possible. For more information, see Driver Verifier.
    Nothing in event viewer other than another 3B BSOD around the same time.

    I'd say try Driver Verifier again but try verifying the smallest number of drivers you can. I suspect it's the Intel WiFi.

    Follow the instructions in this link: Enable and Disable Driver Verifier in Windows 10

    In Part Two, Step 4, select all Intel drivers.
      My Computers

  10. Posts : 32
    Windows 10 H
    Thread Starter

    Here's my first memory dump right after my first BSOD running the verifier with only intel drivers

    File Dump4.zip - Google Drive

    - - - Updated - - -

    Here's one more before I turn off the verifier:

    File Dump5.zip - Google Drive
      My Computer


  Related Discussions
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd
All times are GMT -5. The time now is 07:32.
Find Us

Windows 10 Forums