How to produce BSOD data for posting here if Win 10 will not boot?

Page 1 of 2 12 LastLast

  1. Posts : 112
    64-bit Windows 10 Pro 1909
       #1

    How to produce BSOD data for posting here if Win 10 will not boot?


    My 64-bit Windows 10 Pro 1809 system has been booting and working fine. Then I created a clone of the entire system disk (120 GB Samsung SSD) using Acronis Disk Director 12.5 booted from a flash drive. When this was finished, I removed the backup device and the DD flash drive and rebooted.

    Now I always get a BSOD "IO1 Initialization Failed" . Every time. Even if I remove all other peripherals except the same old USB keyboard and mouse.

    To state the obvious, I made ZERO changes. No driver changes, no hardware changes, nothing. But of course I must emphatically SCREAM: "Windows 10 1809 is the foulest, MOST bug-ridden piece of binary excrement in software history!"

    For example, there's the absurdly evil "enhancement" to the file association configuration system (one must calculate one's own hash values to change many default file associations in the registry - unless you have special software to do it). Then there's the non-stop catastrophe of bugs that includes:

    (1) Random flashing of windows and the task bar.
    (2) Random flashing of "Not Responding" in application window title bar every half-second or so.
    (3) Application windows that will not show up when you press its task bar item.
    (4) Disappearing application windows that you cannot restore, even if you try to cascade or tile them.

    I won't go on. I've tried all the suggested solutions: Disabling various services, disabling various drivers, disabling various Windows features, such as mouse stuff and easy access stuff, and every other suggestion I've found. A few of those have produced small or moderate improvements, but all of these issues still occur - VERY OFTEN!

    Anyway, I've read the BSOD posting instructions, but they do not cover how to obtain the information in question if the OS won't boot at all (due to the "IO1 Initialization Failed" BSOD). Should I try to force a Safe Mode boot by resetting the computer three times? Or should I boot up the MS Win 10 install drive? If the latter, what extra operations/steps/commands must I perform in order to obtain the correct info to post?

    And may I suggest that this situation be covered in the BSOD Posting Instructions stickie?

    Thanks
      My Computers


  2. Posts : 112
    64-bit Windows 10 Pro 1909
    Thread Starter
       #2

    NOTE: The abort booting 3 times to enter safe mode IS NOT WORKING. I always get the above BSOD.
      My Computers


  3. Posts : 112
    64-bit Windows 10 Pro 1909
    Thread Starter
       #3

    Cannot boot Win 10 1809 due to "IO1 Initialization Failed" !


    My 64-bit Windows 10 Pro 1809 system has been booting and working fine. Then I created a clone of the entire system disk (120 GB Samsung SSD) using Acronis Disk Director 12.5 booted from a flash drive. When this was finished, I removed the backup device and the DD flash drive and rebooted.

    Now I always get a BSOD "IO1 Initialization Failed". Every time! Even if I remove all other peripherals except the same old USB keyboard and mouse. This error also makes it impossible to enter Safe Mode; no matter how many times I interrupt the boot process, I always get "IO1 Initialization Failed".

    I began a BSOD thread, here, but received no reply on how to provide the required info. Please see that thread to learn what I've tried already.

    So I booted up a Live linux (Zorin OS 12.2) and browsed around the system disk in question, but no BSOD dump was created, even after a dozen attempts. And since I cannot boot into that system at all, and no one has responded to my BSOD thread, I don't know how to obtain the other info for posting there.

    I tried using EasyRecovery for Windows 10, which has helped many times in the past. It reports that it corrected any problems it found, and re-installed the MBR and boot loader. But every boot still gives the same "IO1 Initialization Failed". I also tried booting TWO older cloned copies of that system -- on different disks -- that worked perfectly, but now they are both producing the same error as well!

    I've run chkdisk, tested my RAM, and disconnected everything except the bare minimum hardware required to function, with no luck. I've performed a lot of google searches looking for support, but I could find nothing of ANY value at all. Even Microsoft says, here: "There is very little information available to analyze this error." Thanks, cretins!

    There's no way I'll waste my time requesting support from Microsoft, of course. They seem to make it a point to refuse to offer any help other than "Re-install Windows" or other totally useless crap suggestions. But dammit, the system was working perfectly prior to making a backup!!

    I need some high-end expert help, please. Please?
      My Computers


  4. Posts : 14,046
    Windows 11 Pro X64 22H2 22621.1848
       #4

    You could try running Kyhi's rescue iso. It's based on Windows 10. You can run SFC and DISM from it's command prompt using the parameters that tell it where the OS is.

    See here: Windows 10 Recovery Tools - Bootable Rescue Disk from KYHI

    You create a bootable flash drive. When you boot it, your normal boot drive may or may not be C:. Open a Command Prompt then run

    (replace d: with the letter of your normal boot drive)

    dism /image:d:\ /Cleanup-Image /StartComponentCleanup

    dism /image:d:\ /Cleanup-Image /Cleanup-Image /RestoreHealth


    sfc /scannow /offwindir=d:\windows /offbootdir=d:\
      My Computers


  5. Posts : 112
    64-bit Windows 10 Pro 1909
    Thread Starter
       #5

    Ztruker said:
    You could try running Kyhi's rescue iso. It's based on Windows 10. You can run SFC and DISM from it's command prompt using the parameters that tell it where the OS is...
    Thank you, Ztruker, for your response! Thank you! I'll do just as you so kindly suggest, and I'll report back.
      My Computers


  6. Posts : 545
    seL4
       #6

    Since you cannot boot into Windows I would suggest that you use another computer to create a bootable Windows usb.

    Once that is done boot to the USB drive and follow the prompts until you see the option to "Repair your computer" (This is also when you see the option to "Install Now" - which you should not do.)

    From there: Advanced Options -> Troubleshoot -> Automatic Repair.
      My Computer


  7. Posts : 112
    64-bit Windows 10 Pro 1909
    Thread Starter
       #7

    Ztruker said:
    ...
    dism /image:d:\ /Cleanup-Image /StartComponentCleanup
    dism /image:d:\ /Cleanup-Image /Cleanup-Image /RestoreHealth

    sfc /scannow /offwindir=d:\windows /offbootdir=d:\
    Hi, Ztruker. The first command worked fine, but even after removing the redundant "/Cleanup-Image" option from the second command, it failed after 90.4 %, with the error message: "The source files could not be found..."

    I've attached a compressed copy of the DISM.log file...
      My Computers


  8. Posts : 112
    64-bit Windows 10 Pro 1909
    Thread Starter
       #8

    Spectrum said:
    Since you cannot boot into Windows I would suggest that you use another computer to create a bootable Windows usb.

    Once that is done boot to the USB drive and follow the prompts until you see the option to "Repair your computer" (This is also when you see the option to "Install Now" - which you should not do.)
    From there: Advanced Options -> Troubleshoot -> Automatic Repair.
    Thanks, Spectrum, I'll try that again. But do you happen to know the correct DISM commands to perform the process suggested by Ztruker for a connected but non-boot system? I've added a folder to the Win10XPE flash drive that contains the extracted contents of the official, unmodified Microsoft 1809 install media to be used as the Source in the appropriate DISM command, but I'm unclear precisely how to specify the commands. I've seen several sites cover the commands, but none that I've found explain how to work with an attached, non-boot system partition.

    Thanks.
      My Computers


  9. Posts : 112
    64-bit Windows 10 Pro 1909
    Thread Starter
       #9

    As expected, Spectrum, the Repair Your Computer process failed with exactly the same message I've been getting 90% of the time I've ever tried it for many years now, ever since Windows 7 came out: It reported that it couldn't repair my computer.

    I've always held that the design of Microsoft's startup repair system would earn an "F" grade from even the most forgiving software development instructor or manager. Why? Because if the target system isn't utterly generic and totally in accord with some obsequious conformist's expectations of a Platonic Ideal of a computer should be, the code makes very stupid decisions about what's "wrong" and how to fix it the Official Microsoft Way. In other words, it's exceptionally moronic.
    Now, please advise how to troubleshoot a "IO1 Initialization Failed" issue. Thanks.
      My Computers


  10. Posts : 545
    seL4
       #10

    The error is reporting that Windows cannot initialize the computer's IO subsystem, so it's failing very early on in the boot process.
    You said you repaired your MBR, but are you using UEFI or BIOS? If you are using UEFI here is a guide on performing that repair.

    If you've already tried that, then I'd say you may want to consider installing 1803 and restoring your data from the backup you recently took.
      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 09:04.
Find Us




Windows 10 Forums