BSOD | IRQL_NOT_LESS_OR_EQUAL / MEMORY_MANAGEMENT| ntoskrnl.exe

Page 1 of 6 123 ... LastLast

  1. Fly
    Posts : 42
    Windows 10 2004
       #1

    BSOD | IRQL_NOT_LESS_OR_EQUAL / MEMORY_MANAGEMENT| ntoskrnl.exe


    Hey there,

    (Windows Education 1909 64bit)
    I recently upgraded my Motherboard, CPU and RAM and ever since I've been the two BSOD listed in the title.
    I didn't do a clean install of Windows 10 since I don't want to reconfigure everything again with a clean install.
    I've done a sfc scan and a full chkdsk scan and they haven't found anything.
    I'm going to run memtest overnight on both of the new memory modules soon.

    Is there anything more I should do? I'll place the log collector .zip with the crash dumps in the attachments.

    Thanks

    - - - Updated - - -

    I have run memtest overnight and there were no errors.
      My Computer


  2. Posts : 1,538
    Windows 8.1 Enterprise x64
       #2

    Test drivers with Driver Verifier - Enable and Disable Driver Verifier in Windows 10
      My Computer


  3. Fly
    Posts : 42
    Windows 10 2004
    Thread Starter
       #3

    MrPepka said:
    Test drivers with Driver Verifier - Enable and Disable Driver Verifier in Windows 10
    Hey MrPepka,

    I ran driver verifier as you said and I've been getting a DRIVER_VERIFIER_IOMANAGER_VIOLATION BSOD on startup with "Caused by Address : Wdf01000.sys" after running driver verifier
    I also ran DISM with RestoreHealth (No clue if it restored something or not)

    113019-7984-01.dmp - Google Drive
    Here's the .dmp for the latest BSOD "Wdf01000.sys"
      My Computer


  4. Posts : 1,538
    Windows 8.1 Enterprise x64
       #4

    Update (or uninstall):
    Unified Remote - Download – Unified Remote
      My Computer


  5. Fly
    Posts : 42
    Windows 10 2004
    Thread Starter
       #5

    MrPepka said:
    Update (or uninstall):
    Unified Remote - Download – Unified Remote
    I've uninstalled Unified Remote.
    What do you recommend I do next?
    Should I wait and see if I get another BSOD, or should I perhaps run Driver Verifier again?

    Thanks for the help so far.
      My Computer


  6. Posts : 1,538
    Windows 8.1 Enterprise x64
       #6

    Turn off Driver Verifier and wait for the next BSoD
      My Computer


  7. Posts : 41,480
    windows 10 professional version 1607 build 14393.969 64 bit
       #7

    The opening post V2 was modified.

    Please upload a new V2 and make sure that there are no edits: (There are many files used in the troubleshooting)

    https://www.tenforums.com/tutorials/...dows-10-a.html
    Change Display Language in Windows 10

    BSOD - Posting Instructions
      My Computer


  8. Fly
    Posts : 42
    Windows 10 2004
    Thread Starter
       #8

    zbook said:
    The opening post V2 was modified.

    Please upload a new V2 and make sure that there are no edits: (There are many files used in the troubleshooting)

    https://www.tenforums.com/tutorials/...dows-10-a.html
    Change Display Language in Windows 10

    BSOD - Posting Instructions
    I've reuploaded the V2
      My Computer


  9. Posts : 41,480
    windows 10 professional version 1607 build 14393.969 64 bit
       #9

    1) Uninstall the software related to:

    Code:
    ScpVBus.sys
    	
    Scarlet.Crush Productions Scp Dual Shock 3 Virtual Bus Driver
    	
    http://forums.pcsx2.net/Thread-XInput-Wrapper-for-DS3-and-Play-com-USB-Dual-DS2-Controller?pid=186161#pid186161



    2) Open administrative command prompt and type or copy and paste:
    3) sfc /scannow
    4) dism /online /cleanup-image /scanhealth
    5) dism /online /cleanup-image /restorehealth
    6) sfc /scannow
    7) chkdsk /scan
    8) wmic recoveros set autoreboot = false
    9) wmic recoveros set DebugInfoType = 7
    10) bcdedit /enum {badmemory}

    11) When these have completed > right click on the top bar or title bar of the administrative command prompt box > left click on edit then select all > right click on the top bar again > left click on edit then copy > paste into the thread

    12) Make sure that there is no over clocking while troubleshooting

    13) In the left lower corner search type: system or system control > open system control panel > on the left pane click advanced system settings

    a) > on the advanced tab under startup and recovery > click settings > post an image of the startup and recovery window into the thread

    b) > on the advanced tab under performance > click on settings > on the performance options window > click on the advanced tab > under virtual memory > click on change > post an image of the virtual memory window into the thread


    14) For any BSOD:

    a) run the V2 log collector to collect new log files

    b) open file explorer> this PC > C: > in the right upper corner search for: C:\Windows\memory.dmp
    > if the file size is < 1.5 GB then zip > post a separate share link into the thread using one drive, drop box, or google drive







    Code:
    scpvbus	Scp Virtual Bus Driver	c:\windows\system32\drivers\scpvbus.sys	Kernel Driver	Yes	Manual	Running	OK	Normal	No	Yes
    Code:
    ScpVBus      Scp Virtual Bus Driver Scp Virtual Bus Driver Kernel        Manual     Running    OK         TRUE        FALSE        16.384            12.288      0          05/05/2013 23:31:26    C:\WINDOWS\system32\drivers\ScpVBus.sys          4.096
    Code:
    ScpVBus.sys  Sun May  5 14:31:26 2013 (5186CFAE)
      My Computer


  10. Fly
    Posts : 42
    Windows 10 2004
    Thread Starter
       #10

    zbook said:
    1) Uninstall the software related to:

    Code:
    ScpVBus.sys
    	
    Scarlet.Crush Productions Scp Dual Shock 3 Virtual Bus Driver
    	
    http://forums.pcsx2.net/Thread-XInput-Wrapper-for-DS3-and-Play-com-USB-Dual-DS2-Controller?pid=186161#pid186161



    2) Open administrative command prompt and type or copy and paste:
    3) sfc /scannow
    4) dism /online /cleanup-image /scanhealth
    5) dism /online /cleanup-image /restorehealth
    6) sfc /scannow
    7) chkdsk /scan
    8) wmic recoveros set autoreboot = false
    9) wmic recoveros set DebugInfoType = 7
    10) bcdedit /enum {badmemory}

    11) When these have completed > right click on the top bar or title bar of the administrative command prompt box > left click on edit then select all > right click on the top bar again > left click on edit then copy > paste into the thread

    12) Make sure that there is no over clocking while troubleshooting

    13) In the left lower corner search type: system or system control > open system control panel > on the left pane click advanced system settings

    a) > on the advanced tab under startup and recovery > click settings > post an image of the startup and recovery window into the thread

    b) > on the advanced tab under performance > click on settings > on the performance options window > click on the advanced tab > under virtual memory > click on change > post an image of the virtual memory window into the thread


    14) For any BSOD:

    a) run the V2 log collector to collect new log files

    b) open file explorer> this PC > C: > in the right upper corner search for: C:\Windows\memory.dmp
    > if the file size is < 1.5 GB then zip > post a separate share link into the thread using one drive, drop box, or google drive







    Code:
    scpvbus	Scp Virtual Bus Driver	c:\windows\system32\drivers\scpvbus.sys	Kernel Driver	Yes	Manual	Running	OK	Normal	No	Yes
    Code:
    ScpVBus      Scp Virtual Bus Driver Scp Virtual Bus Driver Kernel        Manual     Running    OK         TRUE        FALSE        16.384            12.288      0          05/05/2013 23:31:26    C:\WINDOWS\system32\drivers\ScpVBus.sys          4.096
    Code:
    ScpVBus.sys  Sun May  5 14:31:26 2013 (5186CFAE)
    Microsoft Windows [Version 10.0.18363.476]
    (c) 2019 Microsoft Corporation. All rights reserved.

    C:\WINDOWS\system32>sfc /scannow

    Beginning system scan. This process will take some time.

    Beginning verification phase of system scan.
    Verification 100% complete.

    Windows Resource Protection did not find any integrity violations.

    C:\WINDOWS\system32>dism /online /cleanup-image /scanhealth

    Deployment Image Servicing and Management tool
    Version: 10.0.18362.1

    Image Version: 10.0.18363.476

    [==========================100.0%==========================] No component store corruption detected.
    The operation completed successfully.

    C:\WINDOWS\system32>dism /online /cleanup-image /restorehealth

    Deployment Image Servicing and Management tool
    Version: 10.0.18362.1

    Image Version: 10.0.18363.476

    [==========================100.0%==========================] The restore operation completed successfully.
    The operation completed successfully.

    C:\WINDOWS\system32>sfc /scannow

    Beginning system scan. This process will take some time.

    Beginning verification phase of system scan.
    Verification 100% complete.

    Windows Resource Protection did not find any integrity violations.

    C:\WINDOWS\system32>chkdsk /scan
    The type of the file system is NTFS.

    Stage 1: Examining basic file system structure ...
    781056 file records processed.
    File verification completed.
    13375 large file records processed.
    0 bad file records processed.

    Stage 2: Examining file name linkage ...
    370 reparse records processed.
    976788 index entries processed.
    Index verification completed.
    0 unindexed files scanned.
    0 unindexed files recovered to lost and found.
    370 reparse records processed.

    Stage 3: Examining security descriptors ...
    Security descriptor verification completed.
    97867 data files processed.
    CHKDSK is verifying Usn Journal...
    35193304 USN bytes processed.
    Usn Journal verification completed.

    Windows has scanned the file system and found no problems.
    No further action is required.

    975266557 KB total disk space.
    850129976 KB in 497614 files.
    302016 KB in 97868 indexes.
    0 KB in bad sectors.
    918145 KB in use by the system.
    65536 KB occupied by the log file.
    123916420 KB available on disk.

    4096 bytes in each allocation unit.
    243816639 total allocation units on disk.
    30979105 allocation units available on disk.

    C:\WINDOWS\system32>wmic recoveros set autoreboot = false
    Updating property(s) of '\\FONSPC\ROOT\CIMV2:Win32_OSRecoveryConfiguration.Name="Microsoft Windows 10 Education|C:\\WINDOWS|\\Device\\Harddisk1\\Partition4"'
    Property(s) update successful.

    C:\WINDOWS\system32>wmic recoveros set DebugInfoType = 7
    Updating property(s) of '\\FONSPC\ROOT\CIMV2:Win32_OSRecoveryConfiguration.Name="Microsoft Windows 10 Education|C:\\WINDOWS|\\Device\\Harddisk1\\Partition4"'
    Property(s) update successful.

    C:\WINDOWS\system32>bcdedit /enum {badmemory}

    RAM Defects
    -----------
    identifier {badmemory}

    C:\WINDOWS\system32>bcdedit /enum {badmemory}
      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 03:00.
Find Us




Windows 10 Forums