Fresh install pfn list corrupt BSOD

[kd4kmz_dk]

For over a year now I have had bsod issues so I decided to do a fresh install of windows 10, usually when it does bsod its always a different error but pfn list corrupt is a pretty common one. I have done all the usual sfc/ scannow and check ram with memtest86. All of these issues started when I replaced my cpu motherboard and ram, and I recently replaced my gpu thinking it might be the gpu but its still giving me issues. Im at a loss here and I have no idea what could be causing this considering I have checked everything and even done several fresh installs of windows including the most recent on today on 3/31/2018. I will include the latest dmp file if anyone can look at it and help i would greatly appreciate it.

https://www.dropbox.com/s/6l5gpnaqfolvjcm/033118-33125-01.dmp?dl=0

Update: here is another dmp file from a crash that happend only a few hours later

https://www.dropbox.com/s/e16lg3zj59tv0iz/040118-29875-01.dmp?dl=0

Update 2: I have fixed the dropbox links so the dmp files are able to be downloaded by anyone and have listed below my pc specs if that helps.

PC Summary
Operating System
Windows 10 Home 64-bit
CPU
Intel Core i7 7700K @ 4.20GHz 33 °C
Kaby Lake 14nm Technology
RAM
16.0GB Dual-Channel Unknown @ 1065MHz (15-15-15-36)
Motherboard
MSI Z270-A PRO (MS-7A71) (U3E1) 35 °C
Graphics
VG248 (1920x1080@144Hz)
ASUS PB278 (2560x1440@59Hz)
BenQ GL2460 (1920x1080@60Hz)
4095MB NVIDIA GeForce GTX 1080 (Gigabyte) 48 °C
Storage
111GB Samsung SSD 850 EVO 120GB (SSD) 26 °C
931GB Seagate ST1000DM003-1ER162 (SATA) 27 °C
Optical Drives
ASUS DRW-24F1ST c
Audio
NVIDIA High Definition Audio

 

[jojesa]

The links you posted requires a login
Could you post your system specs
If you didn't get any errors after running memtest then it could be drivers causing the BSOD.
Make sure your BIOS is up to date. Also, while in the BIOS disable any device you might not be using.

After installing Windows you should allow Windows to finish all updates, including drivers updates.
If any hardware is not working properly then get the drivers from Windows Update Catalog or your motherboard manufacturer.

I suggest you do a clean Windows 10 install using Windows 10 installation media

 

[kd4kmz_dk]

The links you posted requires a login
Could you post your system specs
If you didn't get any errors after running memtest then it could be drivers causing the BSOD.
Make sure your BIOS is up to date. Also, while in the BIOS disable any device you might not be using.

After installing Windows you should allow Windows to finish all updates, including drivers updates.
If any hardware is not working properly then get the drivers from Windows Update Catalog or your motherboard manufacturer.

I suggest you do a clean Windows 10 install using Windows 10 installation media

I went ahead and fixed the links so you should be able to download them now. As far as bios I made sure to update that to the newest version and my windows was also updated to with the most current updates and it still crashed. Like I said this has been going on for almost a year now. I did contact corsair yesterday and they said they would be able to replace my ram but if you or anyone could take a look at the dmp files and see if there might be another cause I would appreciate it. As for drivers being the issue I have tried updating all my drivers and the reason I did a clean install was to see if it still crashed without anything besides the standard drivers and sure enough it still did. Im at a loss here and hope you or anyone here can help and if all else fails I hope replacing the ram fixes it.

 

[johnbl]

memory_corruption_one_bit

you will want to run memtest86 to confirm your memory timings in bios and your RAM is ok.

 

[kd4kmz_dk]

memory_corruption_one_bit

you will want to run memtest86 to confirm your memory timings in bios and your RAM is ok.

I have ran memtest86 several times for several passes and never get any errors but I contacted corsair just incase and they said they would replace my ram for me so hopefully that fixes it is that the only thing that looked off about the dmps to you?

 

[johnbl]

your ram looks like CMK16GX4M2B3000C15
Speed 2133MHz

you might want to check to see the timings and voltages are set correctly in bios
https://www.newegg.com/Product/Product.aspx?Item=N82E16820233852
since they don't match the newegge product info
-------------
I would run a malwarebytes scan, and download the intel processor diagnostics and see if it reports any problem.

these one bit error problems can be hard to find. They can be in the RAM, they can occur in the cpu (but you generally get a different bugcheck)

sometimes different RAM slots will have slightly different ram timings that can lead to these type of errors.
IE you may pull out all of your ram put then in different slots and never see the problem again.
generally, the ram slots the closest to the CPU will work just a bit faster than the ones further away. (we are talking about a few nanoseconds difference)

some ram need two clock cycles for the command rate, this is one of the rams secondary timings and is often set to 1T by default in the bios when it should be set to 2T (2 clock cycles to issue a command)
on most motherboards it is the fifth bios ram clock timing. (but the order is not standardized after the first 4 timings)

memory_corruption_one_bit

you will want to run memtest86 to confirm your memory timings in bios and your RAM is ok.

I have ran memtest86 several times for several passes and never get any errors but I contacted corsair just incase and they said they would replace my ram for me so hopefully that fixes it is that the only thing that looked off about the dmps to you?

 

[kd4kmz_dk]

your ram looks like CMK16GX4M2B3000C15
Speed 2133MHz

you might want to check to see the timings and voltages are set correctly in bios
https://www.newegg.com/Product/Product.aspx?Item=N82E16820233852
since they don't match the newegge product info
-------------
I would run a malwarebytes scan, and download the intel processor diagnostics and see if it reports any problem.

these one bit error problems can be hard to find. They can be in the RAM, they can occur in the cpu (but you generally get a different bugcheck)

sometimes different RAM slots will have slightly different ram timings that can lead to these type of errors.
IE you may pull out all of your ram put then in different slots and never see the problem again.
generally, the ram slots the closest to the CPU will work just a bit faster than the ones further away. (we are talking about a few nanoseconds difference)

some ram need two clock cycles for the command rate, this is one of the rams secondary timings and is often set to 1T by default in the bios when it should be set to 2T (2 clock cycles to issue a command)
on most motherboards it is the fifth bios ram clock timing. (but the order is not standardized after the first 4 timings)

memory_corruption_one_bit

you will want to run memtest86 to confirm your memory timings in bios and your RAM is ok.

I have ran memtest86 several times for several passes and never get any errors but I contacted corsair just incase and they said they would replace my ram for me so hopefully that fixes it is that the only thing that looked off about the dmps to you?

ok so ran malwarebtyes and it found nothing also ran the intel processor diagnostics and it passed all the tests

as far as the ram speed from what I understand that is the base clock speed. to get the 3000 that they advertise I have to enable xmp not sure if this would change anything but I can try it if you think it might help.

as far as the clock cycles thing im actually not to sure what you are talking about or how to check/change that (im a pc novice when it comes to bios stuff lol)

 

[johnbl]

you might try these timings in bios
15-17-17-35 -2T

the last timing is the command rate. it is generally indicated by 1N or 1T (the n or t = clock cycles)
try and changing it to 2N or 2T. it will give the electronics 1 extra clock tick to set up the memory addressing lines to become stable. (1 nanosecond longer)

sometimes you can dig thru the technical specs for your memory stick and find the secondary timings requirements.
(their are 12 timings, but most specs only show the first 4, it is pretty common for cheaper memory sticks to have 2T command rates)

your ram looks like CMK16GX4M2B3000C15
Speed 2133MHz

you might want to check to see the timings and voltages are set correctly in bios
https://www.newegg.com/Product/Product.aspx?Item=N82E16820233852
since they don't match the newegge product info
-------------
I would run a malwarebytes scan, and download the intel processor diagnostics and see if it reports any problem.

these one bit error problems can be hard to find. They can be in the RAM, they can occur in the cpu (but you generally get a different bugcheck)

sometimes different RAM slots will have slightly different ram timings that can lead to these type of errors.
IE you may pull out all of your ram put then in different slots and never see the problem again.
generally, the ram slots the closest to the CPU will work just a bit faster than the ones further away. (we are talking about a few nanoseconds difference)

some ram need two clock cycles for the command rate, this is one of the rams secondary timings and is often set to 1T by default in the bios when it should be set to 2T (2 clock cycles to issue a command)
on most motherboards it is the fifth bios ram clock timing. (but the order is not standardized after the first 4 timings)

memory_corruption_one_bit

you will want to run memtest86 to confirm your memory timings in bios and your RAM is ok.

I have ran memtest86 several times for several passes and never get any errors but I contacted corsair just incase and they said they would replace my ram for me so hopefully that fixes it is that the only thing that looked off about the dmps to you?

ok so ran malwarebtyes and it found nothing also ran the intel processor diagnostics and it passed all the tests

as far as the ram speed from what I understand that is the base clock speed. to get the 3000 that they advertise I have to enable xmp not sure if this would change anything but I can try it if you think it might help.

as far as the clock cycles thing im actually not to sure what you are talking about or how to check/change that (im a pc novice when it comes to bios stuff lol)

 

[kd4kmz_dk]

you might try these timings in bios
15-17-17-35 -2T

the last timing is the command rate. it is generally indicated by 1N or 1T (the n or t = clock cycles)
try and changing it to 2N or 2T. it will give the electronics 1 extra clock tick to set up the memory addressing lines to become stable. (1 nanosecond longer)

sometimes you can dig thru the technical specs for your memory stick and find the secondary timings requirements.
(their are 12 timings, but most specs only show the first 4, it is pretty common for cheaper memory sticks to have 2T command rates)

your ram looks like CMK16GX4M2B3000C15
Speed 2133MHz

you might want to check to see the timings and voltages are set correctly in bios
https://www.newegg.com/Product/Product.aspx?Item=N82E16820233852
since they don't match the newegge product info
-------------
I would run a malwarebytes scan, and download the intel processor diagnostics and see if it reports any problem.

these one bit error problems can be hard to find. They can be in the RAM, they can occur in the cpu (but you generally get a different bugcheck)

sometimes different RAM slots will have slightly different ram timings that can lead to these type of errors.
IE you may pull out all of your ram put then in different slots and never see the problem again.
generally, the ram slots the closest to the CPU will work just a bit faster than the ones further away. (we are talking about a few nanoseconds difference)

some ram need two clock cycles for the command rate, this is one of the rams secondary timings and is often set to 1T by default in the bios when it should be set to 2T (2 clock cycles to issue a command)
on most motherboards it is the fifth bios ram clock timing. (but the order is not standardized after the first 4 timings)

memory_corruption_one_bit

you will want to run memtest86 to confirm your memory timings in bios and your RAM is ok.

I have ran memtest86 several times for several passes and never get any errors but I contacted corsair just incase and they said they would replace my ram for me so hopefully that fixes it is that the only thing that looked off about the dmps to you?

ok so ran malwarebtyes and it found nothing also ran the intel processor diagnostics and it passed all the tests

as far as the ram speed from what I understand that is the base clock speed. to get the 3000 that they advertise I have to enable xmp not sure if this would change anything but I can try it if you think it might help.

as far as the clock cycles thing im actually not to sure what you are talking about or how to check/change that (im a pc novice when it comes to bios stuff lol)

ok thanks ill give this a shot, I think im still gonna send my ram back since corsair already approved my rma but if I still have the issues with new ram ill try this

 

[johnbl]

it is a good call to get the RMA, it is a pain to remember the settings if the bios gets updated or cleared.
You might want to check to see if the RAM you have selected is on the motherboard qualified vendors list
(the list of modules that they put the proper timings in BIOS)

you might try these timings in bios
15-17-17-35 -2T

the last timing is the command rate. it is generally indicated by 1N or 1T (the n or t = clock cycles)
try and changing it to 2N or 2T. it will give the electronics 1 extra clock tick to set up the memory addressing lines to become stable. (1 nanosecond longer)

sometimes you can dig thru the technical specs for your memory stick and find the secondary timings requirements.
(their are 12 timings, but most specs only show the first 4, it is pretty common for cheaper memory sticks to have 2T command rates)

your ram looks like CMK16GX4M2B3000C15
Speed 2133MHz

you might want to check to see the timings and voltages are set correctly in bios
https://www.newegg.com/Product/Product.aspx?Item=N82E16820233852
since they don't match the newegge product info
-------------
I would run a malwarebytes scan, and download the intel processor diagnostics and see if it reports any problem.

these one bit error problems can be hard to find. They can be in the RAM, they can occur in the cpu (but you generally get a different bugcheck)

sometimes different RAM slots will have slightly different ram timings that can lead to these type of errors.
IE you may pull out all of your ram put then in different slots and never see the problem again.
generally, the ram slots the closest to the CPU will work just a bit faster than the ones further away. (we are talking about a few nanoseconds difference)

some ram need two clock cycles for the command rate, this is one of the rams secondary timings and is often set to 1T by default in the bios when it should be set to 2T (2 clock cycles to issue a command)
on most motherboards it is the fifth bios ram clock timing. (but the order is not standardized after the first 4 timings)

memory_corruption_one_bit

you will want to run memtest86 to confirm your memory timings in bios and your RAM is ok.

I have ran memtest86 several times for several passes and never get any errors but I contacted corsair just incase and they said they would replace my ram for me so hopefully that fixes it is that the only thing that looked off about the dmps to you?

ok so ran malwarebtyes and it found nothing also ran the intel processor diagnostics and it passed all the tests

as far as the ram speed from what I understand that is the base clock speed. to get the 3000 that they advertise I have to enable xmp not sure if this would change anything but I can try it if you think it might help.

as far as the clock cycles thing im actually not to sure what you are talking about or how to check/change that (im a pc novice when it comes to bios stuff lol)

ok thanks ill give this a shot, I think im still gonna send my ram back since corsair already approved my rma but if I still have the issues with new ram ill try this