Windows 10 Installation BSOD

[Lectre]

Hello,

I've recently run into some trouble when doing a fresh install of Windows 10, where during the installation, a BSOD would appear. The BSOD error varies, here is a list of the ones that I have recorded:
PFN_LIST_CORRUPT,
System__ervice Exception,
System_Thread_exception_not_handled,
Kernel security check failure,
irql_not_less_or_equal,
Memory management

The Windows 10 installation on this drive was working perfectly before I attempted a fresh install (I usually do a fresh install every few months). I also had another SSD running Mac OSX that was running perfectly
(Note I have been attempting to install Win10 on this drive for several days, meanwhilst I have been using the Mac OSX drive on the same machine).

From the multitude of errors above, I surmised that the problem would be hardware related, most likely RAM or driver issue;
Here is what I have done to attempt to resolve the issue:

1. Unplugged the SSD with Mac OSX.
2. Reset BIOS Settings to default.
3. Flashed BIOS to the latest version.
3. Reverted all CPU and DRAM overclocking to factory settings.
4. Attempted installation with only one RAM Module (Using a different slot each attempt, then repeating this with the other module).
5. Attempted to use an older GPU.
6. Reformatted the target Windows drive with DISKPART (in case the SSD was the problem).
7. Reformatted the SSD with OSX on it, and attempt to install onto it.
8. Currently Running Memtest86, however, after 6 passes, there are no errors (will wait until 8 before aborting).

None of these produced a different outcome - BSOD during the "Preparing files for installation" phase between 8 - 15%.

My Machine Specs are:
MOBO: Asus z170-A
CPU: i7 6700k @ 4 GHZ
RAM: 2x DDR4 G-Skill Ripjaws V @2400 MHZ
GPU: NVidia 980ti
SSD: 2x Samsung 850

I am attempting the install from a SanDisk Cruzer 64GB USB - I have tried multiple different ISOs and several different ways of writing to the USB.

Realistically the only parts that I have not changed/tested are the CPU and the MOBO, however as I said before, I was using the OSX drive for 2 days with no issues at all until I attempted to install onto that drive.

This thread seems to be very similar: Link

Any help would be greatly appreciated,

Thanks

 

[DRagor]

I would say the problem might be caused be your USB stick itself. Try installing from different USB or DVD and see if that helps.

 

[herrwizo]

Another vote for change of installation media. Redownload the ISO and use a different USB stick.

 

[Lectre]

Alright, I'm going to go buy a brand new USB now, I'll report as soon as I get back

 

[Lectre]

This did not work, It got much further into the "Preparing files for installation" phase (60%), however, I believe this may be due to the new USB being far higher quality than the previous.
The BSOD Error given was: PFN_LIST_CORRUPT

 

[herrwizo]

Could you try a different USB connector? Preferably the one not being the same color as your current one (if you are using USB 3.0, try using older 2.0 connector). It could be a mobo controller issue or BIOS issue.

 

[DRagor]

This did not work, It got much further into the "Preparing files for installation" phase (60%), however, I believe this may be due to the new USB being far higher quality than the previous.
The BSOD Error given was: PFN_LIST_CORRUPT

Which USB port are you using?

 

[DRagor]

Could you try a different USB connector? Preferably the one not being the same color as your current one (if you are using USB 3.0, try using older 2.0 connector). It could be a mobo controller issue or BIOS issue.

Mindreading

 

[Lectre]

I'm using a USB 3.0 port on the Motherboard, I have also tried a USB 2.0 which is also on the Motherboard.

 

[Lectre]

OK, so I managed to get a successful installation. however, I got a BSOD shortly after booting into the new installation
I changed all of my DRAM timings & voltage from auto to what the manufacturer suggested.

Now I'm just using the new installation, waiting for another BSOD so I can get some logs.

 

[herrwizo]

At least you got it installed, that's a big step forward 😉

 

[Lectre]

Here is a link to two MEMORY.dmp files that I collected after two BSODs, hopefully someone who knows what they are looking for will see:
https://livecoventryac-my.sharepoint.com/personal/riglerr_uni_coventry_ac_uk/_layouts/15/guestaccess.aspx?folderid=0ef436ca16dbb4662aeb6dbb5c15449e9&authkey=AWAW7R1BKgwLQYc4l7kkr4Y

 

[Lectre]

BSODs do not happen whilst in Safe mode, which leads me to believe this could be a driver issue. I am going to attempt to install the latest drivers for my system whilst in safe mode, then try again.

 

[herrwizo]

Or disable some devices in BIOS, one by one. Start with sound, then network, then serial and parralel ports, then USB, the onboard video... until the issue goes away, hopefully.

 

[gdmaclew]

Try using BlueScreenView for a better idea of what's causing the crash.

 

[Lectre]

Whilst I had that windows installation , BlueScreenViewer showed that ntoskrnl.exe was the main culprit (90%) of the time. After extensive googling, I could't narrow this down further, nor find a working solution.
Since then I have attempted to Install Ubuntu 16.04 on the same drive, which also failed partway through the installation, multiple times.
I'm not sure what else to try, other than buying new hardware, which i would be very dissapointed in doing as this build is only ~6 months old, not to mention that I still don't know what is causing the issue, and what hardware should be replaced.

Any more advice would be greatly apopreciated.

 

[DRagor]

Ok lets back to basics. You did have this machine working on win 10 earlier, right?
Did you made any hardware changes recently?
If I understand correctly, you tried installing on both SSD? That would rule out bad drive, but what about bad SATA data cable?
Did you had only ONE drive plugged in during install? Having multiple drives is known to pose problems.
Finally what about BIOS settings - check out how your SSD report in BIOS.

 

[Lectre]

1. Yes this machine was working fine on win10 3 days ago.
2. I installed another fan about 3 weeks ago, however the system was working fine for that time. The BSODs only started when I tried a fresh install.
3. Yes I attempted to install on both SSDs, just to make sure, I just tried again with different cables, in different SATA ports and a BSOD still happened (1. Memory_Management, 2. Attempted_to_write_to_read_only_memory).
4. Yes, for all but the first attempt I have only been using one SSD at a time.
5. I have reset BIOS settings to default, I checked that the drives are in AHCI, not RAID.

I am currently researching, proper settings for the Asus z170-A motherboard. So that I know for certain that the bios settings are correct.

 

[DRagor]

One more idea, just to clarify things (you're in a damn hard to resolve problem!) - if you have free HDD lying around, could you try disconnecting SSDs and install Win on HDD? Or maybe install Win 8 (if you have it) on SSD?