Solved BSOD trying to update to Windows 8.1

Today I tried to update my Windows 8 PRO /WMC to Windows 8.1

I am running the VL edition as Windows 8 as it was installed from the IT department at my university.

The dumps don't have anything recent in there, but im may be related to why I cannot update to 8.1 ( using the iso).

Thanks for the help!

Some more info:

When trying to do the upgrade the process bsods with "KMODE_EXCEPTION_NOT_HANDLED"
After the restart the upgrade fails with the following error code: 0xc1900101-0x4000d

I'm sorry for the delay in responding to this topic, I have been very busy over the last week.
If you still need help with this problem, please post back and run the analysis for you.

Hi, I managed to install 8.1 after a clean install of eight.

Although it would be much appreciated to know what was causing my previous issues encase it is a specific driver that should be updated.

You had a series of BSOD's on 20 and 21 May that I haven't looked at.
Then, on 03 Jun you had one more.
As there are only dump files (and not a complete set of reports), here's what I've got (remember, this is from before you installed 8.1):

AMD OverDrive (AODDriver2.sys) is either a stand-alone application, or a component of the AMD VISION Engine Control Center. This driver is known to cause BSOD's on some Windows systems.

Please un-install all AMD/ATI video stuff from Control Panel...Programs...Un-install a program
Then, download (but DO NOT install) a fresh copy of the ATI drivers from Global Provider of Innovative Graphics, Processors and Media Solutions | AMD (in the upper right corner of the page)
Use this procedure to install the DRIVER ONLY: ATI video cards - DRIVER ONLY installation procedure - Sysnative Forums

If the device (AODDriver or AODDriver4.01) remains a problem, open Device Manager, select the "View" item.
Then select "Show hidden devices" and scroll down to the Non-Plug and Play Drivers section.
Locate the AODDriver entry, right click on it and select "Un-install". Reboot for changes to take affect.

Click to expand...

Sometimes the driver remains and continues to cause BSOD's. If this is the case for you, post back and we'll give further instructions for safely removing it.

If overclocking, please stop. Remove the overclock and return the system to stock/standard values while we're troubleshooting. Once the system is stable again, feel free to resume the overclocking.

I've noted some issues with the Wireless Button Driver recently - but quite enough to state that it's a BSOD cause. Please keep an eye on it.

In short, IMO, it's most likely that AMD OverDrive was the cause. I'll run the May memory dumps in order to see if anything else pops up.....

The May memory dumps blame bridge.sys (a Windows driver). The more likely culprit was your wireless drivers - and they've been known to have some BSOD issues in the past. As they didn't show up in the June memory dump, I suspect that you fixed that issue back in May.

Good luck!

Okay.
Thanks. I believe that I was running the AMD BETA driver which would explain why it would be caused AMD Catalyst.

I was not overclocking as this is an laptop, but yes the "Overdrive" feature is present in AMD CCC.

As for the WiFi, it occasionally does give me trouble when windows starts out of sleep mode, It won't let me connect to any AP.

I have since updated the WiFi drivers from the HP website and updated the AMD CCC.

I haven't had any issues yet.

Thanks for letting me know what was causing the the problem!