• Some users have recently had their accounts hijacked. It seems that the now defunct EVGA forums might have compromised your password there and seems many are using the same PW here. We would suggest you UPDATE YOUR PASSWORD and TURN ON 2FA for your account here to further secure it. None of the compromised accounts had 2FA turned on.
    Once you have enabled 2FA, your account will be updated soon to show a badge, letting other members know that you use 2FA to protect your account. This should be beneficial for everyone that uses FSFT.

BSODs in Windows 10

Q

qwertyaas

Gawd
Joined
Jun 25, 2007
Messages
787
Starting yesterday, I have been getting BSODs in Windows 10. Varies from being under load to doing nothing at all.

Currently running windows built in memtest with no errors yet.

Everything boots up fine but system just locks up. Unsure if it's the RX480 since there's no artifacting or display issues.

Could the PSU be going bad?


Specs:
1055T
GA-870A-UD3
Corsair XMS 2x2GB, Kingston HyperX 2x2GB
Kingston HyperX 3k SSD
Seagate 2TB HDD
Sapphire Nitro RX480 4GB
Corsair 520HX
CM 690
 
Hard to say w/o an actual crash dump analysis.
There are few utilities that do that, like 'WhoCrashed' or MS WinDbg.
 
any oc? did you check event viewer or catch the bsod code, maybe disable auto restart. you should also test your battery cause a dying one will cause weird problems.
 
Am i reading 4 sticks of ram from 2 different companies?

I was gonna say I've only ever had BSOD's vista+ due to ram issues, but you mentioned the memtesting.

I would say 1. make sure you have each companies ram in their respective channels, they are typically colour coded, but that is counter intuitive, you would want each brand to have one in each colour. More specifically in the exact order that would have Brand A sharing a bank, and Brand B sharing the other bank.
Then if that does SFA, 2. take one pair (mfg) out and then see.
Ever since dual channel+ ram became a thing it became way harder to have more sticks in a machine without causing issues. It can be done for sure, but as a rule I dont ever populate more than 2 banks, just seems shit goes sideways often when you use those other slots.
 
ashmelev75 said:
Hard to say w/o an actual crash dump analysis.
There are few utilities that do that, like 'WhoCrashed' or MS WinDbg.
Click to expand...
Sorry, see below:

Per WhoCrashed:

On Tue 10/31/2017 6:22:53 PM your computer crashed
crash dump file: C:\WINDOWS\Minidump\103117-8625-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x16C580)
Bugcheck code: 0x4E (0x99, 0xB7D40, 0x3, 0x1CFF5C)
Error: PFN_LIST_CORRUPT
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that the page frame number (PFN) list is corrupted.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

On Tue 10/31/2017 6:22:53 PM your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x4E (0x99, 0xB7D40, 0x3, 0x1CFF5C)
Error: PFN_LIST_CORRUPT
Bug check description: This indicates that the page frame number (PFN) list is corrupted.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

pendragon1 said:
any oc? did you check event viewer or catch the bsod code, maybe disable auto restart. you should also test your battery cause a dying one will cause weird problems.
Click to expand...

Removed OC so running stock as I usually do during the summer. See above for WhoCrashed dump analysis

travm said:
Am i reading 4 sticks of ram from 2 different companies?

I was gonna say I've only ever had BSOD's vista+ due to ram issues, but you mentioned the memtesting.

I would say 1. make sure you have each companies ram in their respective channels, they are typically colour coded, but that is counter intuitive, you would want each brand to have one in each colour. More specifically in the exact order that would have Brand A sharing a bank, and Brand B sharing the other bank.
Then if that does SFA, 2. take one pair (mfg) out and then see.
Ever since dual channel+ ram became a thing it became way harder to have more sticks in a machine without causing issues. It can be done for sure, but as a rule I dont ever populate more than 2 banks, just seems shit goes sideways often when you use those other slots.
Click to expand...

I have been running with 2 separate pairs of RAM since Vista and never has an issue. They are each in their dual channel slot. Each are a pair and clocked the same.



I reseated my sticks last night, ran Window Memory Diag with no errors. Ran HDTune on my SSD and HDD, no errors and benchmark looked fine. Ran Y-Cruncher through first 4 tests stressing CPU and Memory load and no crash. Ran full Defender and MalwareBytes scans with no detection.

Odd. Maybe it was just needing to reseat my sticks? If it was BSODing prior while in Idle, I can't see how stressing CPU/RAM/HDD to 100% wouldn't crash if it was RAM or PSU related...
 
ashmelev75 said:
First, you need to run memtest to make sure there are no memory issues. Then you need to run chkdsk to fix the disk errors that cause BSOD.
Click to expand...

Will run both tonight. Assuming W10 built in Memory Diagnostics is pretty bad compared to memtest?
 
PFN_LIST_CORRUPT BSOD is a common problem on Gigabyte GA-870A-UD3 in Windows due to RAM voltage sag, rev3.1 was (supposedly) made to fix some of those issues. If MemTest fails, bump the voltage of the RAM up by 0.5v, re-test and see if that helps -- it did for me, though I never mixed RAM vendors. The northbridge on those boards also run rather hot, so that further adds to the list of troubleshooting. I had a rev2.0 of this board and was super happy to finally retire the thing. The straw that broke the camels back for me was putting another LSI 2008 SAS card in the box into the second x16 PCI-E slot and it making both of the x1 completely stop working (they're shared apparently). I used one of those x1 slots for an Intel NIC, and I didn't want to have to deal with that Realtek NIC and its stupidity negotiating 100mbit links to the Netgear GS724Tv2 it was attached to on my network. For a time, I actually ran an unmanaged switch between it and the central switch, just so it'd negotiate gigabit... That board is just annoyingly built.
 
Farkle said:
PFN_LIST_CORRUPT BSOD is a common problem on Gigabyte GA-870A-UD3 in Windows due to RAM voltage sag, rev3.1 was (supposedly) made to fix some of those issues. If MemTest fails, bump the voltage of the RAM up by 0.5v, re-test and see if that helps -- it did for me, though I never mixed RAM vendors. The northbridge on those boards also run rather hot, so that further adds to the list of troubleshooting. I had a rev2.0 of this board and was super happy to finally retire the thing. The straw that broke the camels back for me was putting another LSI 2008 SAS card in the box into the second x16 PCI-E slot and it making both of the x1 completely stop working (they're shared apparently). I used one of those x1 slots for an Intel NIC, and I didn't want to have to deal with that Realtek NIC and its stupidity negotiating 100mbit links to the Netgear GS724Tv2 it was attached to on my network. For a time, I actually ran an unmanaged switch between it and the central switch, just so it'd negotiate gigabit... That board is just annoyingly built.
Click to expand...

That could explain it.

Oddly been running this for... close to 7 years(!) and this is my first problem with it. Then again, I'm not using any of the PCI slots other than for my GPU. I actually haven't had an issue since reseating the sticks - atleast with normal usage/gaming and stress testing.

Going to run memtest still once I find an empty usb stick that I should have hidden all over.
 
You must log in or register to reply here.
Back
Top