BSOD when updating to Windows 10 Anniversary Update

Page 1 of 2 12 LastLast

  1. Posts : 10
    valerokai
       #1

    BSOD when updating to Windows 10 Anniversary Update


    Hey everyone,

    I experienced this issue yesterday when attempting to upgrade to the Windows 10 Anniversary Update. About 70% through, a Blue Screen appeared with the error code IRQL_NOT_LESS_OR_EQUAL. I have used Bluescreenview to find the address that caused the problem, which appears to be ntoskrnl.exe+149f90, and caused by the driver ntoskrnl.exe. I have attempted to use the tool provided by the forums for blue screens, however as it was during an update the minidump copying failed as the minidump is located in C:\$WINDOWS.~BT\Sources\Rollback\setupmem.dmp. I have uploaded the minidump to setupmem.dmp - Google Drive.

    After the bluescreen occured, a screen appeared that read it was reverting changes, and windows booted normally afterwards, however without updating.

    Thanks, and I appreciate any help.
      My Computer

  2. axe0's Avatar
    Posts : 14,790
    Windows 10 Pro
       #2

    Please also upload the zip :)
      My Computers


  3. Posts : 10
    valerokai
    Thread Starter
       #3

    Attachment 94157 I've attatched it, but in "It can't find the minidump" I forgot to mention it also produces what seems to be an empty zip file in the process. Again thanks!
      My Computer

  4. axe0's Avatar
    Posts : 14,790
    Windows 10 Pro
       #4

    I forgot to mention it also produces what seems to be an empty zip file in the process
    Important thing you forgot
    I would request you to run the tool again, we need the files for proper analysis.
      My Computers


  5. Posts : 10
    valerokai
    Thread Starter
       #5

    I've tried it many times and each time I get an empty zip file dumped back, with the only error messages in the tool being file not found referring to the minidumps, as they are in the §Windows.BT folder and not Windows/Minidumps for me. I'll try again tomorrow after redownloading the tool again.
      My Computer

  6. axe0's Avatar
    Posts : 14,790
    Windows 10 Pro
       #6

    If it doesn't help we'll gather some files manually :)
      My Computers


  7. Posts : 10
    valerokai
    Thread Starter
       #7

    Downloaded it again and it worked, but I have no idea why or how. Hope this helps.
    Attachment 94276
      My Computer

  8. axe0's Avatar
    Posts : 14,790
    Windows 10 Pro
       #8

    We don't know either, it just happens.

    Please remove / disable items from the startup in taskmanager
    These programs could interfere with the boot process giving you trouble and increase the boot time.

    Please check HP for BIOS updates.

    I have used Bluescreenview to find the address that caused the problem, which appears to be ntoskrnl.exe+149f90, and caused by the driver ntoskrnl.exe.
    Bluescreenview is incorrect, ntoskrnl.exe is 1 of the files of the Windows Kernel. Windows files are defaulted to as the possible cause when there is nothing else to be blamed.




    Diagnostic Test

     DRIVER VERIFIER


    warning   Warning
    Please make a backup of your important files and get your rescue media or create one.
    Please create a restore point.

    Please follow this tutorial to run driver verifier.

    Driver verifier stresses your drivers and will crash your pc if any driver fails due to a violation.

    Driver verifier should be performed for a max of 48 hours, or when you have a bluescreen, whatever comes first.

    If driver verifier has found a violation and you can't get back into windows normally, try to boot into safe mode and reset in safe mode driver verifier, or in the troubleshooting options open command prompt and type verifier /reset.

    Note   Note
    Your system will act very sluggishly while driver verifier is enabled, this is normal as your drivers will be being subjected to heavy testing in order to make them crash.
      My Computers


  9. Posts : 10
    valerokai
    Thread Starter
       #9

    Ran the driver verifier and immediately hit a Blue Screen. I booted into safe mode and ran the command you supplied, and then ran the Blue Screen tool you guys have and have attached the new zip file.
    Attachment 94742
      My Computer

  10. axe0's Avatar
    Posts : 14,790
    Windows 10 Pro
       #10

    This driver, Driver Reference Table - ScpVBus.sys caused the crash, but I do not know what it belongs to.
    Code:
    0: kd> lmvm ScpVBus
    Browse full module list
    start             end                 module name
    fffff801`14e00000 fffff801`14e0e000   ScpVBus  T (no symbols)           
        Loaded symbol image file: ScpVBus.sys
        Image path: \SystemRoot\System32\drivers\ScpVBus.sys
        Image name: ScpVBus.sys
        Browse all global symbols  functions  data
        Timestamp:        Sun May 05 23:31:26 2013 (5186CFAE)
        CheckSum:         00010BD7
        ImageSize:        0000E000
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
      My Computers


 
Page 1 of 2 12 LastLast

  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 05:44.
Find Us




Windows 10 Forums