F5F Stay Refreshed Hardware Desktop Repeated blue screen issues following RAM installation

Repeated blue screen issues following RAM installation

Repeated blue screen issues following RAM installation

I
Inezze009
Senior Member
716
04-08-2016, 06:13 AM
#1
Hello, I recently increased my PC's RAM capacity to take advantage of the recent price drop. The upgrade went from 2x8 gigabytes at 3200MHz to 4x8 gigabytes. All units are identical, and I ran Memtest86 which showed three clean results. The system crashes during startup, displaying PFN_List_Corrupt, and keeps doing so until I enter BIOS. There it confirms a reset and asks me to re-enable XMP. Once done, everything works properly. Is there a more lasting solution than repeatedly accessing BIOS? Thanks ahead.
I
Inezze009
04-08-2016, 06:13 AM #1

Hello, I recently increased my PC's RAM capacity to take advantage of the recent price drop. The upgrade went from 2x8 gigabytes at 3200MHz to 4x8 gigabytes. All units are identical, and I ran Memtest86 which showed three clean results. The system crashes during startup, displaying PFN_List_Corrupt, and keeps doing so until I enter BIOS. There it confirms a reset and asks me to re-enable XMP. Once done, everything works properly. Is there a more lasting solution than repeatedly accessing BIOS? Thanks ahead.

B
BMW1313
Member
56
04-15-2016, 08:07 PM
#2
It's time to check the RAM setup. Test the new RAM by inserting it into the old slots. If successful, swap the old RAM into the vacant positions.
B
BMW1313
04-15-2016, 08:07 PM #2

It's time to check the RAM setup. Test the new RAM by inserting it into the old slots. If successful, swap the old RAM into the vacant positions.

J
juniorhockey
Member
171
04-15-2016, 08:25 PM
#3
It seems the drivers weren’t updated. After rebooting, the system didn’t crash. Since the firmware was current, it’s unclear what caused the problem. I’ll keep an eye out for similar issues. No worries about the fix—just stay alert. Thanks!
J
juniorhockey
04-15-2016, 08:25 PM #3

It seems the drivers weren’t updated. After rebooting, the system didn’t crash. Since the firmware was current, it’s unclear what caused the problem. I’ll keep an eye out for similar issues. No worries about the fix—just stay alert. Thanks!