"Couldn't update to Windows 8.1 - 0xC1900101 - 0x40017"

HI Robert,

I just finished disabling it in the BIOS again then booting into Windows to start the upgrade again, and it still failed.

It's almost as if the upgrade teases me with the mouse pointer appearing during both install/update phases, but still blue screens with this same error and IRQ Not Less or Equal.

I was able to find the dmp file, but unfortunately it did not provide any useful information:

On Sat 6/13/2015 3:30:42 AM GMT your computer crashed

crash dump file: C:\Windows\Minidump\setupmem.dmp

This was probably caused by the following module: ntoskrnl.exe (nt+0x150CA0)

Bugcheck code: 0xA (0x828000B, 0x2, 0x0, 0xFFFFF8014EF39A27)

Error: IRQL_NOT_LESS_OR_EQUAL

file path: C:\Windows\system32\ntoskrnl.exe

product: Microsoft® Windows® Operating System

company: Microsoft Corporation

description: NT Kernel & System

Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.

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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

Conclusion

One crash dump has 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.

still blue screens with this same error and IRQ Not Less or Equal.

Unfortunately as your third-party dump analyzer is telling you that is just a generic symptom and you will need to get more detailed clues about what it means.  Or make a better guess about what to change to see if that works.  Looks like your BIOS gives you a plethora of possibilities that latter way.

Otherwise my approach is always to look for whatever diagnostics would have been created by these events and get some clues from them.  When I don't know exactly what to look for I just use file searches based on timestamp, e.g. dir/od  would show the files in the current directory ordered by date.  That sort would be done regardless of what you were using for your date and time formats.  However, if you were using a sortable date and time format you could list the files in your whole drive and then sort that list (but then later have to go back and find out what directory the files came from.)  In fact, since you know what the date would be you could just filter that out in a pipeline regardless of your date format and then (in effect) sort using just the time field provided it was sortable (e.g. showing 24 hour clock times instead of AM and PM times) but of course since the events you were interested in occurred within minutes you could even filter out that effect too and then perhaps not even bother to sort your list.   Using PowerShell to do the same filtering and sorting would be better I suppose.   In fact, I think that PowerShell is available even in a command only boot.  That could help create the most accurate lists of recent changes and thus help you see what to look at.

More simply but less generally you could instead try getting into Event Viewer and see what clues you could find in it.  Etc.  In a command shell Event Viewer would be started by entering eventvwr.exe

HTH

Robert

I too have tried everything I can (without having to take my system apart) and have the same issue.

One last thing someone mentioned is the wireless "card" causing this which now also includes the IRQ Less than or Equal error... or something similar.

In order for me to remove the wireless "card" I would have to remove the motherboard from the case since it is secured by a screw on the bottom of the motherboard.  (Asus P9X79_DELUXE).

Is it true that you have to have 8.1 in order to upgrade to 10?

Please MS,  fix this.

my motherboard is P9x79PRO, it seems to be the culprit, I yet to try disable the wireless in BIOS, what is this wireless issue you mentioned, do you happen to have the source? cheers.

I was able to find the dmp file, but unfortunately it did not provide any useful information:

On Sat 6/13/2015 3:30:42 AM GMT your computer crashed

crash dump file: C:\Windows\Minidump\setupmem.dmp

This was probably caused by the following module: ntoskrnl.exe (nt+0x150CA0)

Bugcheck code: 0xA (0x828000B, 0x2, 0x0, 0xFFFFF8014EF39A27)

Error: IRQL_NOT_LESS_OR_EQUAL

file path: C:\Windows\system32\ntoskrnl.exe

product: Microsoft® Windows® Operating System

company: Microsoft Corporation

description: NT Kernel & System

Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.

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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

---

Conclusion

---

One crash dump has 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.

and how did you find that minidump? how to enable it? I didn't find any solution for enabling that despite the fact I got minidump enabled in the system.