Windows 10: BSOD When Perform Windows 10 Upgrading

Discus and support BSOD When Perform Windows 10 Upgrading in Windows 10 BSOD Crashes and Debugging to solve the problem; Dear All, I have just installed WinDbg and would need some advice from my dump file (setupmem.dmp). I am trying to upgrade my OS 10 1803 to 1903 and... Discussion in 'Windows 10 BSOD Crashes and Debugging' started by cyliyu, Aug 24, 2019.

  1. cyliyu Win User

    BSOD When Perform Windows 10 Upgrading


    Dear All,

    I have just installed WinDbg and would need some advice from my dump file (setupmem.dmp).
    I am trying to upgrade my OS 10 1803 to 1903 and BSOD appeared.
    The dump file pointed to WIN8_DRIVER_FAULT, but I have difficulties identify which driver causing the fault.
    Thanks in advance.

    Code: Microsoft (R) Windows Debugger Version 10.0.18362.1 X86 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [D:\$WINDOWS.~BT\Sources\Rollback\setupmem.dmp] Kernel Bitmap Dump File: Kernel address space is available, User address space may not be available. ************* Path validation summary ************** Response Time (ms) Location Deferred SRV*D:\SymCache*http://msdl.microsoft.com/download/symbols Symbol search path is: SRV*D:\SymCache*http://msdl.microsoft.com/download/symbols Executable search path is: Windows 10 Kernel Version 18362 MP (4 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 18362.1.amd64fre.19h1_release.190318-1202 Machine Name: Kernel base = 0xfffff805`0a200000 PsLoadedModuleList = 0xfffff805`0a6432f0 Debug session time: Mon Aug 12 16:54:35.471 2019 (UTC + 8:00) System Uptime: 0 days 0:07:29.265 Loading Kernel Symbols ..Page 20000084d too large to be in the dump file. ...Page 20000084d too large to be in the dump file. ......Page 200000852 too large to be in the dump file. .Page 20000084d too large to be in the dump file. .Page 20000084d too large to be in the dump file. ..Page 200000852 too large to be in the dump file. .Page 20000084d too large to be in the dump file. .Page 200000852 too large to be in the dump file. .Page 20000084d too large to be in the dump file. ..Page 200000852 too large to be in the dump file. .Page 20000084d too large to be in the dump file. .Page 20000084d too large to be in the dump file. .Page 200000852 too large to be in the dump file. .Page 200000852 too large to be in the dump file. .Page 20000084d too large to be in the dump file. ...Page 200000852 too large to be in the dump file. .Page 20000084d too large to be in the dump file. .Page 200000852 too large to be in the dump file. .Page 200000852 too large to be in the dump file. .Page 20000084d too large to be in the dump file. .Page 20000084d too large to be in the dump file. .Page 200000852 too large to be in the dump file. .Page 200000852 too large to be in the dump file. .Page 20000084d too large to be in the dump file. .Page 200000852 too large to be in the dump file. .Page 200000852 too large to be in the dump file. .Page 200000852 too large to be in the dump file. .Page 20000084d too large to be in the dump file. .Page 20000084d too large to be in the dump file. .Page 20000084d too large to be in the dump file. .Page 200000852 too large to be in the dump file. .Page 200000852 too large to be in the dump file. .Page 20000084d too large to be in the dump file. .Page 200000852 too large to be in the dump file. .Page 200000852 too large to be in the dump file. .Page 200000852 too large to be in the dump file. .Page 20000084d too large to be in the dump file. .Page 20000084d too large to be in the dump file. .Page 200000852 too large to be in the dump file. .Page 200000852 too large to be in the dump file. .Page 200000852 too large to be in the dump file. .Page 20000084d too large to be in the dump file. .Page 20000084d too large to be in the dump file. .Page 20000084d too large to be in the dump file. .Page 20000084d too large to be in the dump file. .Page 20000084d too large to be in the dump file. .Page 20000084d too large to be in the dump file. .Page 200000852 too large to be in the dump file. .Page 20000084d too large to be in the dump file. .Page 20000084d too large to be in the dump file. . Page 200000852 too large to be in the dump file. .Page 200000852 too large to be in the dump file. .Page 20000084d too large to be in the dump file. .Page 20000084d too large to be in the dump file. .Page 20000084d too large to be in the dump file. .Page 20000084d too large to be in the dump file. .Page 20000084d too large to be in the dump file. .Page 20000084d too large to be in the dump file. .Page 20000084d too large to be in the dump file. .Page 20000084d too large to be in the dump file. .Page 200000852 too large to be in the dump file. .Page 200000852 too large to be in the dump file. .Page 200000852 too large to be in the dump file. .Page 200000853 too large to be in the dump file. .Page 200000853 too large to be in the dump file. .Page 200000853 too large to be in the dump file. .Page 200000853 too large to be in the dump file. .Page 200000853 too large to be in the dump file. .Page 200000853 too large to be in the dump file. .Page 200000853 too large to be in the dump file. .Page 200000853 too large to be in the dump file. .Page 200000852 too large to be in the dump file. .Page 200000853 too large to be in the dump file. .Page 200000853 too large to be in the dump file. .Page 200000853 too large to be in the dump file. .Page 200000853 too large to be in the dump file. .Page 200000852 too large to be in the dump file. .Page 200000853 too large to be in the dump file. .Page 200000853 too large to be in the dump file. .Page 200000852 too large to be in the dump file. .Page 200000853 too large to be in the dump file. .Page 200000853 too large to be in the dump file. .Page 200000853 too large to be in the dump file. .Page 200000853 too large to be in the dump file. .Page 200000852 too large to be in the dump file. .Page 200000852 too large to be in the dump file. .Page 200000853 too large to be in the dump file. .Page 200000852 too large to be in the dump file. ..Page 200000853 too large to be in the dump file. .Page 200000853 too large to be in the dump file. .Page 200000853 too large to be in the dump file. .Page 200000852 too large to be in the dump file. .Page 200000853 too large to be in the dump file. .Page 200000852 too large to be in the dump file. .Page 200000853 too large to be in the dump file. .Page 200000853 too large to be in the dump file. .Page 200000853 too large to be in the dump file. .Page 200000852 too large to be in the dump file. .Page 200000852 too large to be in the dump file. .Page 200000852 too large to be in the dump file. .Page 200000853 too large to be in the dump file. .Page 200000853 too large to be in the dump file. .Page 200000853 too large to be in the dump file. .Page 200000853 too large to be in the dump file. .Page 200000853 too large to be in the dump file. ...Page 200000853 too large to be in the dump file. .Page 200000853 too large to be in the dump file. ..... ................................................................ ....................Page 2001f0dd4 too large to be in the dump file. ........ Loading User Symbols Loading unloaded module list ............ For analysis of this file, run !analyze -v 3: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* DRIVER_PNP_WATCHDOG (1d5) A driver has failed to complete a Pnp operation within a specific time. Arguments: Arg1: 0000006900630070, First few character of the service associated with the devnode. Arg2: ffffc386a9148aa0, Pointer to the nt!TRIAGE_PNP_WATCHDOG on Win10 RS4 and higher. Arg3: ffffb08fec9d6140, Thread responsible for the Pnp Watchdog. Arg4: 000000000005a562, Milliseconds elapsed since the watchdog was armed. Debugging Details: ------------------ Implicit thread is now ffffb08f`ec9d6140 KEY_VALUES_STRING: 1 PROCESSES_ANALYSIS: 1 SERVICE_ANALYSIS: 1 STACKHASH_ANALYSIS: 1 TIMELINE_ANALYSIS: 1 DUMP_CLASS: 1 DUMP_QUALIFIER: 401 BUILD_VERSION_STRING: 18362.1.amd64fre.19h1_release.190318-1202 SYSTEM_MANUFACTURER: System manufacturer SYSTEM_PRODUCT_NAME: System Product Name SYSTEM_SKU: SKU SYSTEM_VERSION: System Version BIOS_VENDOR: American Megatrends Inc. BIOS_VERSION: 2104 BIOS_DATE: 08/13/2013 BASEBOARD_MANUFACTURER: ASUSTeK COMPUTER INC. BASEBOARD_PRODUCT: P8Z77-V DELUXE BASEBOARD_VERSION: Rev 1.xx DUMP_TYPE: 1 BUGCHECK_P1: 6900630070 BUGCHECK_P2: ffffc386a9148aa0 BUGCHECK_P3: ffffb08fec9d6140 BUGCHECK_P4: 5a562 FAULTING_THREAD: ffffb08fec9d6140 CPU_COUNT: 4 CPU_MHZ: daf CPU_VENDOR: GenuineIntel CPU_FAMILY: 6 CPU_MODEL: 3a CPU_STEPPING: 9 CPU_MICROCODE: 6,3a,9,0 (F,M,S,R) SIG: 20'00000000 (cache) 20'00000000 (init) BLACKBOXBSD: 1 (!blackboxbsd) BLACKBOXNTFS: 1 (!blackboxntfs) BLACKBOXPNP: 1 (!blackboxpnp) BLACKBOXWINLOGON: 1 DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT BUGCHECK_STR: 0x1D5 PROCESS_NAME: System CURRENT_IRQL: 1 ANALYSIS_SESSION_HOST: HOME-PC ANALYSIS_SESSION_TIME: 08-25-2019 09:23:34.0192 ANALYSIS_VERSION: 10.0.18362.1 x86fre LOCK_ADDRESS: fffff8050a65d6e0 -- (!locks fffff8050a65d6e0) Resource @ nt!PiEngineLock (0xfffff8050a65d6e0) Exclusively owned Contention Count = 34 NumberOfExclusiveWaiters = 2 Threads: ffffb08fec9d6140-01<*> Threads Waiting On Exclusive Access: ffffb08fec8d8080 ffffb08fee76e080 1 total locks PNP_TRIAGE_DATA: Lock address : 0xfffff8050a65d6e0 Thread Count : 1 Thread address: 0xffffb08fec9d6140 Thread wait : 0x13cf LAST_CONTROL_TRANSFER: from fffff8050a23b7e2 to fffff8050a3c35a6 STACK_TEXT: ffffc386`a7a5a2f0 fffff805`0a23b7e2 : ffff9b00`8314b180 ffffb08f`ffffffff ffff9b00`8314b101 ffffb08f`ec9d6140 : nt!KiSwapContext+0x76 ffffc386`a7a5a430 fffff805`0a23ae74 : ffffb08f`00000003 00000000`00000000 fffffb65`00000000 fffffb65`00000000 : nt!KiSwapThread+0x3f2 ffffc386`a7a5a4d0 fffff805`0a23a615 : ffffb08f`eecc7204 fffff805`00000000 00000000`00000000 00000000`00000000 : nt!KiCommitThreadWait+0x144 ffffc386`a7a5a570 fffffb65`02303d0c : ffffb08f`eed05180 00000000`0000000d ffffb08f`00000000 fffffb65`023ca100 : nt!KeWaitForSingleObject+0x255 ffffc386`a7a5a650 fffffb65`023038f9 : ffffb08f`eecc72c0 ffffc386`a7a5a828 ffffb08f`eecec080 ffffb08f`f2e070c8 : win32kbase!RIMSignalOnPnpNotificationAndWait+0x22c ffffc386`a7a5a6c0 fffff805`0aa08ff9 : ffffda0f`5373d3e0 00000000`00000000 ffffb08f`00000000 fffff805`00000001 : win32kbase!RIMDeviceNotify+0x129 ffffc386`a7a5a730 fffff805`0a8802d8 : ffffc386`a7a5a858 00000000`00000000 ffffda0f`5373d3e0 00000000`ffffffff : nt!PnpNotifyDriverCallback+0xdfae1 ffffc386`a7a5a7e0 fffff805`0aa795d3 : ffffc386`a7a5aa49 fffff805`0a8efda0 00000000`4b706e50 fffff805`0a56a06d : nt!PnpNotifyTargetDeviceChange+0x170 ffffc386`a7a5a8a0 fffff805`0aa792df : ffffda0f`572ab660 ffffda0f`581cc110 ffffb08f`f3cef9a0 ffffc386`a7a5aa08 : nt!PipSendTargetDeviceQueryRemoveNotification+0x97 ffffc386`a7a5a900 fffff805`0aa78f4d : ffffda0f`581cc110 00000000`00000000 00000000`00000000 ffffda0f`58bffc60 : nt!PipProcessQueryRemovalInKernelMode+0x3f ffffc386`a7a5a950 fffff805`0aa061ad : 00000000`00000052 ffffc386`a7a5aa49 00000000`00000000 00000000`00000052 : nt!PiProcessQueryAndCancelRemoval+0x151 ffffc386`a7a5a9c0 fffff805`0a8f4c0a : ffffc386`a7a5ab10 ffffb08f`ec9daa00 ffffc386`a7a5ab00 ffffda0f`00000052 : nt!PnpProcessQueryRemoveAndEject+0xe404d ffffc386`a7a5aab0 fffff805`0a880b38 : ffffda0f`56cde370 ffffda0f`58bffc60 ffffda0f`58bffc60 00000000`00000000 : nt!PnpProcessTargetDeviceEvent+0xea ffffc386`a7a5aae0 fffff805`0a2c4855 : ffffb08f`ec876c80 ffffb08f`ec9d6140 ffffb08f`ec876c80 ffffb08f`f3e46f10 : nt!PnpDeviceEventWorker+0x2d8 ffffc386`a7a5ab70 fffff805`0a32f725 : ffffb08f`ec9d6140 00000000`00000080 ffffb08f`ec87c040 7e5192dc`6d1c8876 : nt!ExpWorkerThread+0x105 ffffc386`a7a5ac10 fffff805`0a3c3e6a : fffff805`05f37180 ffffb08f`ec9d6140 fffff805`0a32f6d0 d305d9e3`b835925a : nt!PspSystemThreadStartup+0x55 ffffc386`a7a5ac60 00000000`00000000 : ffffc386`a7a5b000 ffffc386`a7a55000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x2a STACK_COMMAND: .thread 0xffffb08fec9d6140 ; kb THREAD_SHA1_HASH_MOD_FUNC: 52c148ca4851f706fcea164a9e9f06701d5af99b THREAD_SHA1_HASH_MOD_FUNC_OFFSET: ecb7ac05a5b92b94e0be01e9302bb7cedb4d6346 THREAD_SHA1_HASH_MOD: 0f0be269c950d53de8384214815273a9d782a1b2 FOLLOWUP_IP: win32kbase!RIMSignalOnPnpNotificationAndWait+22c fffffb65`02303d0c ?? ??? SYMBOL_STACK_INDEX: 4 SYMBOL_NAME: win32kbase!RIMSignalOnPnpNotificationAndWait+22c FOLLOWUP_NAME: MachineOwner MODULE_NAME: win32kbase IMAGE_NAME: win32kbase.sys DEBUG_FLR_IMAGE_TIMESTAMP: 0 BUCKET_ID_FUNC_OFFSET: 22c FAILURE_BUCKET_ID: 0x1D5_win32kbase!RIMSignalOnPnpNotificationAndWait BUCKET_ID: 0x1D5_win32kbase!RIMSignalOnPnpNotificationAndWait PRIMARY_PROBLEM_CLASS: 0x1D5_win32kbase!RIMSignalOnPnpNotificationAndWait TARGET_TIME: 2019-08-12T08:54:35.000Z OSBUILD: 18362 OSSERVICEPACK: 0 SERVICEPACK_NUMBER: 0 OS_REVISION: 0 SUITE_MASK: 272 PRODUCT_TYPE: 1 OSPLATFORM_TYPE: x64 OSNAME: Windows 10 OSEDITION: Windows 10 WinNt TerminalServer SingleUserTS OS_LOCALE: USER_LCID: 0 OSBUILD_TIMESTAMP: 1972-02-02 16:33:06 BUILDDATESTAMP_STR: 190318-1202 BUILDLAB_STR: 19h1_release BUILDOSVER_STR: 10.0.18362.1.amd64fre.19h1_release.190318-1202 ANALYSIS_SESSION_ELAPSED_TIME: b7ea ANALYSIS_SOURCE: KM FAILURE_ID_HASH_STRING: km:0x1d5_win32kbase!rimsignalonpnpnotificationandwait FAILURE_ID_HASH: {d6edc993-5df6-6c70-13af-f11a2f842301} Followup: MachineOwner ---------[/quote]

    :)
     
    cyliyu, Aug 24, 2019
    #1
  2. Nordic Win User

    Windows 10 upgrade problem, no input accepted

    I really hate having to come here and ask for help, but I really am stumped. It hurts my geek pride. I have a PC with fairly modern hardware in it. It has a p8p67 pro in it. I have tried upgrading windows 10 on it twice now. Both times I have had the same result.

    After windows finishes upgrading it goes to the log in/set up screen. I can't do anything. No keyboard or mouse input is accepted.

    I will list some, or hopefully all, of the troubleshooting steps I have tried:
    • Move keyboard and mouse to different USB ports.
    • Try different keyboard or mouse.
    • Restart computer, repeatedly.
    • Google for related issues.
    • Update Bios, because why not.
    • Create boot media and revert to windows 7.
    The windows 10 system restore boot media works fine with keyboard and mouse. All USB ports work in windows 7. I don't know what is wrong. I suspect that windows 10 is lacking a driver of some sort, but since the computer accepts no input I have no way of checking for which driver let alone installing it.

    Please help me figure this out. If I have to revert back to windows 7 again, I am not going to get it upgraded to windows 10. Thank you in advanced.
     
    Nordic, Aug 24, 2019
    #2
  3. Mussels Win User
    Windows 10 upgrade problem, no input accepted

    i've seen this when the stock USB drivers went kaput. Only ever seen it once - i used a PCI USB 2.0 card and connected the mouse and keyboard to that, and manually updated the USB 2/USB 3 drivers.
     
    Mussels, Aug 24, 2019
    #3
  4. Ahhzz Win User

    BSOD When Perform Windows 10 Upgrading

    Windows 10 Tweaks

    Pressing “Windows+Pause Break” (it’s up there next to scroll lock) opens the “System” Window.

    Windows 10: In the new version of Windows, Explorer has a section called Quick Access. This includes your frequent folders and recent files. Explorer defaults to opening this page when you open a new window. If you’d rather open the usual This PC, with links to your drives and library folders, follow these steps:

    • Open a new Explorer window.
    • Click View in the ribbon.
    • Click Options.
    • Under General, next to “Open File Explorer to:” choose “This PC.”
    • Click OK


    credit to Lifehacker.
     
    Ahhzz, Aug 24, 2019
    #4
Thema:

BSOD When Perform Windows 10 Upgrading

Loading...
  1. BSOD When Perform Windows 10 Upgrading - Similar Threads - BSOD Perform Upgrading

  2. MASSIVE Changes in Performance After Upgrading to Windows 10

    in Windows 10 BSOD Crashes and Debugging
    MASSIVE Changes in Performance After Upgrading to Windows 10: I upgraded to Windows 10 Pro from Windows 7 Ultimate via the Installation Media. After the upgrade, it worked properly for about a month, but last few days... it's maybe a week, but now I see MASSIVE changes in performance. A game I play, League of Legends, is waaaay...
  3. How to perform Windows 10 in-place upgrade

    in Windows 10 News
    How to perform Windows 10 in-place upgrade: [ATTACH] [ATTACH]There are several ways to upgrade Windows 10. You can use Windows Update service to download the feature update, or you can create an ISO, or you can use the Media Creation Tool. The last one helps you perform Windows [...] This post How to perform Windows...
  4. [BSoD] BSoD happened when upgrade from TH2 to RS4

    in Windows 10 Drivers and Hardware
    [BSoD] BSoD happened when upgrade from TH2 to RS4: Our software contains optical drive driver, recently, we found that it may cause BSoD when upgrade OS from TH2 to RS4. it shows that the driver file is corrupted. We have two version driver, the two driver does not have any code difference, the only difference is one is...
  5. BSOD's when awaking from sleep, after windows 10 upgrade.

    in Windows 10 BSOD Crashes and Debugging
    BSOD's when awaking from sleep, after windows 10 upgrade.: Hi all, After updating to Windows 10 Pro recently I get a lot of BSOD's (DPC_WATCHDOG_VIOLATION). Mostly when my laptop wakes up from a well deserved moment of sleep. Also I noticed that sometimes the laptop awakens from sleep when I didn't ask it to wake up. Any help...
  6. Random BSOD when performing normal tasks.

    in Windows 10 BSOD Crashes and Debugging
    Random BSOD when performing normal tasks.: Hello, I've built a PC for my parents in August, since then they have been getting random BSODs every day. I went to search on the internet to find the problem, looked at it with BlueScreenView, but I do not understand dumpfiles good enough to find the issue myself. I...
  7. Windows 10 upgrade BSOD

    in Windows 10 BSOD Crashes and Debugging
    Windows 10 upgrade BSOD: Greetings! I just did an upgrade from 8.1 professional to windows 10. I'm having BSODs and am unable to boot into it except in Safe Mode. I'm trying to figure out which driver this is related to. I have disabled many services on boot and feel hopeful that it's just a pesky...
  8. BSOD and overall lack in performance

    in Windows 10 BSOD Crashes and Debugging
    BSOD and overall lack in performance: Hello, I just re-installed Windows 7 on my computer 3 days ago, essentially starting from scratch again with the removal of all my files (exceptions being the ones I stored to a flash drive), and decided to try Windows 10. Ever since I built this PC 3 years ago, I have...
  9. BSOD and overall lack in performance

    in Windows 10 Performance & Maintenance
    BSOD and overall lack in performance: Hello, I just re-installed Windows 7 on my computer 3 days ago, essentially starting from scratch again with the removal of all my files (exceptions being the ones I stored to a flash drive), and decided to try Windows 10. Ever since I built this PC 3 years ago, I have...
  10. Windows 10 Error when upgrading!

    in Windows 10 Installation and Upgrade
    Windows 10 Error when upgrading!: Hello. I am currently trying to upgrade from windows 10 home to windows 10 education using the media create tool. However I am getting this error: 0x80070004 – 0x3000D! The installation failed in the FIRST_BOOT phase with an error during MIGRATE_DATA operation. Not sure...