Multiple BSOD before and while attempting to Install Windows 10

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...

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.

@philc43 Dang, I'll check for another. The empty one was in C:\Windows\Minidump.

@philc43 Alright I have another dump, MEMORY.dmp from C:\Windows:

MEMORY.DMP - Google Drive

Caledon Ken said:

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

I did yeah, everything is out that can be, barring my mouse and keyboard.

I'm interested as to why Ubuntu runs but Windows is having so many problems. It would make me think that the installer is a problem if I hadn't tried different versions on different USBs. I am still unable to open Firefox in Ubuntu though, not sure if that is related.

I was using Windows 7 Home, and I don't have access to that boot media anymore.

And I get the license for the OS through my school, and the only version they have is Windows 10 Education, Version 1703 (March 2017).

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.