Multiple BSOD before and while attempting to Install Windows 10

DevoidOfHope said:

I actually managed to generate a memory dump file from the BSOD!!

I have put it on Google Drive, accessible from this link: 120318-2718-01.dmp - Google Drive

Finally something to work with I hope...

Unfortunately it is an empty file. It looks like the system may have tried to generate something but then never did. Is there a memory.dmp file in the C:\windows folder? If so, share that one.

Have to get input from the guys that analyze BSOD's but the dump has a bug check E3 (Resource not owned).

You mentioned in your opening post a cheap PCI wifi card. Have you uninstalled it as part of your tear down.

Do you still have your Window 7 boot media?

You were using Windows 7. Was that Home, Pro or Ultimate?

Your spec says you are using Education. Is that correct?

Could you please try a clean install of Windows 10 Home, delete all partitions and skip entering the product key.

I've had a look at the memory dump.

It confirms the BSOD was triggered by a thread trying to release a resource which it did not own hence the bugcheck E3

Code:

RESOURCE_NOT_OWNED (e3)
A thread tried to release a resource it did not own.
Arguments:
Arg1: ffffd50b7a4499e8, Address of resource
Arg2: ffffd50b7ce1d040, Address of thread
Arg3: ffffd50b7dc0c9f0, Address of owner table if there is one
Arg4: 0000000000000002

The resource appears to be the Windows Defender process:

Code:

1: kd> !mex.eres -v ffffd50b7a4499e8
nt!_ERESOURCE @ ffffd50b7a4499e8
Contention count: 8

Shared owners: 1
    Process     Thread           Time
    =========== ================ ====
    MsMpEng.exe ffffd50b7ecf2700    0

Exclusive Waiters: 0
Shared Waiters: 0

The thread it belongs to is not the one trying to release it.

Is there anyway you can disable Windows Defender or update it. Try searching google for issues relating to failure to install W10 with Windows Defender running.