Hello everyone, about 2 years ago i built a mid-rage gaming pc. I ended up getting 4gb of DDR2 Ram. After putting my computer together, i started to get these BSOD's. I looked them up and they all seemed memory related, so i figured that i had a stick of bad ram. After 2 years of random crashes (Trust me, it wasnt my choice. i wanted to get it fix as fast as i could but it took way to long) I got a GA-990FXA-UD3 Motherboard, along with 16gb of Corsair Vengeance DDR3 ram. I expected this to fix the issue and to never BSOD again.....Well....I was wrong.
I have gotten 2 BSOD's (Along with many other random game crashes and application crashes)One of the BSOD's was a "PFN_LIST_CORRUPT" and the other was "PAGE_FAULT_IN_NONPAGED_AREA". These were 2 of the ones that i have gotten before the memory upgrade.
Down below i have linked 2 snapshots of each Minidump in BlueScreenViewer.In the end, im asking, What can i do to fix this? I am really tired of games crashing or acting up and i feel like i'm wasting money on games that i can only play for 10 mins only to lead to crash.
I have no idea of what it could be. My best guess is my drivers or CPU. I will be upgrading my CPU within a few weeks, but i want to make sure i can fix this. Any help would be appreciated.
really good tech support place, and they are specialists at diagnosing bsods. bluescreenviewer isn't really useful at all, and it needs more in-depth diagnosis. as awesome as tek synicate is, it;s really a community forum, a 'campfire' as logan put it. techsupport forum is a specialist site.
they helped me diagnose my bsod's, and i haven;t had a single one since.
however, i do suggest you run memtest x86, and check your memory
Ok man, Thanks for the help though. I will be posting something there. I really need to fix this!!! I will be runing a memtest over night. Thanks again!
well, i am limited on time, but for the pfn_list. you want to make sure your memory is good (which it should be) as well as your drivers (as a driver could reference an invalid section of memory or memory not alocated to it).
run driver verifier. http://support.microsoft.com/kb/244617
check to see if the crashes happen in safe mode
and if your MB has a ram check on it (most higher end ones do) run it!
Ok, thanks! I just tried to use the Verifier and when i rebooted i BSOD. I tried about 3 times and i kept BSODing. I ended up having to install a fresh windows.
I don't know much about the Verifier.exe, so i guess il to learn how to use it before trying agian (...And i feel like a computer noob right about now.) But i do not think my MB has a ram check on it sadly.
Oh wow! I feel pretty stupid right about now! So, im guessing by my computer BSODing on boot meant that, that driver was faulty? Sorry for so many posts. Tech Support Forum is not taking user sign ups, so thats why im still here..lol
that's weird.... was the website http://www.techsupportforum.com/forums/ ? to register, just click the big green button, it's 100% free.
anyways, for driver verifier, bsoding is the objective, sort of
we want the minidumps out of it, which will tell us what is fucking up.
[quote]*** IMPORTANT - PLEASE READ:
- If the Driver Verifier (DV) finds a violation, it will result in a BSOD
- After re-start, you may not be able to log on to normal Windows ... • Boot into SAFEMODE - tap the F8 key repeatedly during boot-up ... • Select "System Restore" ... • Choose the restore point that you created in step #1
- For Driver Verifier status --- select last option, 1st screen -or- --- type verifier /query (in a cmd/DOS screen) - To turn Driver Verifier off - verifier /reset then re-boot
- The Driver Verifier needs to run as long as possible - even if the status screen appears clear. - All future BSOD dumps must be VERIFIER_ENABLED_MINIDUMPs - otherwise the dump(s) are of no use
If your system does BSOD while the Driver Verifier is running, please retrieve the dump file from c:\windows\minidump, zip it up & attach to your next post.[/quote]
Yeah, its back up. when i tried last night, it said it was closed due to spammers. So i guess they are back up now....kinda odd.
Well, i plain to post on the tech forums after i crash again. Who knows. The installation of windows might have fixed it....I dont think soo, but we can hope.
well, probably shoudl register now, just to be on the safe side. a reinstall might fix it, if it's an issue with windows, but it is more likely another piece of software, or even hardware that's causing it.
[quote=microsoft msdn]
Bug check 0x50 usually occurs after the installation of faulty hardware or in the event of failure of installed hardware (usually related to defective RAM, be it main memory, L2 RAM cache, or video RAM).
Another common cause is the installation of a faulty system service.
Antivirus software can also trigger this error, as can a corrupted NTFS volume.[/quote]
Yep, i went ahead and registered. I honestly think it is hardware. I havent had any crashes yet, but i will see what happends with in the next few days. After reading that, it makes me think its my CPU. I have a AMD Athlon II X4 630....Which... i do not like. I have a feeling it has something to do with my L2 cache, or my non existent L3 cache. I will be replacing that CPU with an FX in a week or two.