[SOLVED] Upgrading windows 8.1 to windows 10 failing

Uninstall ESET Security completely.
Reboot the machine.
Try the upgrade again and report the result.
 
Still getting my original problem. Since the first install failed, when I run the install again, it flashes the "preparing" window showing 100%, then the window disappears and nothing more happens. The only way i have been able to run the install all the way through again is to wait for a day or two and it will work again, no idea why.
 
Go to Control Panel - Internet options
Open tab Connections and click LAN settings.
Post a screenshot of the window that appears.
 
The information in your screenshot is good.
Remove all unnecessary devices from your computer and try Windows upgrade again.
 
I disconnected everything except the mouse, keyboard and monitor. I started the install and the "preparing" window pops up. It goes to 100%, then disappears and nothing else happens.
When it does work, it opens up a larger install window and checks for updates and runs through install questions. Then it does the install, does a restart, and that is when I get the BSOD that says some sort of stop error occurred - "Kmode exception not handled" Once that occurs, then I end up where things are now, it doesn't start the install routine. Not sure how to get it to reset.

Thanks
 

Attachments

  • 20200929_144030.jpg
    20200929_144030.jpg
    294.6 KB · Views: 5
Download
51c02d182f93d-whocrashed32.jpg
WhoCrashed and move the executable to your desktop.
Double-click "whocrashedSetup.exe" to install the tool.
'WhoCrashed' will start automatically when the installation is finished. Click the button Analyze.

When done, copy and paste the content in the window "Report" in your next reply.
 
Here is the info. it doesn't look like it picked up the crashes of the last month.
Thanks


Computer name: THE-SPOT
Windows version: Windows 8.1 , 6.3, build: 9600
Windows dir: C:\Windows
Hardware: Inspiron 3847, Dell Inc., 088DT1
CPU: GenuineIntel Intel(R) Core(TM) i5-4460 CPU @ 3.20GHz Intel8664, level: 6
4 logical processors, active mask: 15
RAM: 8501190656 bytes (7.9GB)




Crash Dump Analysis



Crash dumps are enabled on your computer.

Crash dump directories:
C:\Windows
C:\Windows\Minidump

On Mon 6/6/2016 9:10:45 AM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\060616-30390-01.dmp
This was probably caused by the following module: rtsustor.sys (0xFFFFF801671B18C0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF801671B18C0, 0xFFFFD00133A314E0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\drivers\rtsustor.sys
product: Realtek USB Mass Storage Driver for 2K/XP/Vista/Win7/Win8
company: Realtek Semiconductor Corp.
description: Realtek USB Mass Storage Driver for 2K/XP/Vista/Win7/Win8
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a storage driver or controller driver. Since there is no other responsible driver detected, this could be pointing to a malfunctioning drive or corrupted disk. It's suggested that you run CHKDSK.



On Mon 6/6/2016 9:10:45 AM your computer crashed or a problem was reported
crash dump file: C:\Windows\MEMORY.DMP
This was probably caused by the following module: rtsustor.sys (0xFFFFF801671B18C0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF801671B18C0, 0xFFFFD00133A314E0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\drivers\rtsustor.sys
product: Realtek USB Mass Storage Driver for 2K/XP/Vista/Win7/Win8
company: Realtek Semiconductor Corp.
description: Realtek USB Mass Storage Driver for 2K/XP/Vista/Win7/Win8
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a storage driver or controller driver. Since there is no other responsible driver detected, this could be pointing to a malfunctioning drive or corrupted disk. It's suggested that you run CHKDSK.





Conclusion



2 crash dumps have been found and analyzed. No offending third party drivers have been found. Connsider using WhoCrashed Professional which offers more detailed analysis using symbol resolution. Also configuring your system to produce a full memory dump may help you.


Read the topic general suggestions for troubleshooting system crashes for more information.

Note that it's not always possible to state with certainty whether a reported driver is responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.
 
I seached for the rtsustor.sys driver, but it doesn't look like it is there anymore
That was mentioned in a problem on 6/6/2016, more than 4 years ago. It might be related as you mentioned error 0xC0000005 in your initial post.
Please create a new thread in the section BSOD, Crashes, Kernel Debugging
Post in your first message a link to this thread so other helpers know what already has been done.
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top