The title Error message is NOT the only one I've seen. But it's the last one I saw.
I've been having BSOD's sadly, ever since I bought the computer, but never knew who to ask.
I replaced the Graphics Card after I bought the system, and don't know if the BSOD's Started before or after I installed the card.
The zipped folder is attached
It is odd that both of our BSOD data collection tool does not contain lots of important data for you. Without those data we cannot assist you properly, and I am not aware of any more way to get those.
Should I run both again after a crash, and post back?
I had a crash, right after I said that.
New Message: Page_Fault_in_Non_Page_Area
Last edited by picky; 22 Jun 2015 at 00:53. Reason: fixed my noob mistakes
There are multiple different BSOD codes there, so it may be a memory related issue. It would be better to check the health of the RAM sticks at first.
Test your RAM modules for possible errors. Run memtest86+ for at least 8 consecutive passes.
If it start showing errors/red lines, stop testing. A single error is enough to determine that something is going bad there.
Let us know. It would be better if you can take a camera snap of the memtest86+ screen before closing the program and let us see that image.
We will decide our next steps depending on the result.
__________________________________________________________
Code:BugCheck 50, {fffff8800d054328, 0, fffff800030f5cf3, 0} Could not read faulting driver name Probably caused by : ntkrnlmp.exe ( nt!RtlDispatchException+1f3 ) Followup: MachineOwner ---------Code:BugCheck A, {fffffa80287c20f0, 2, 1, fffff8000314c0b6} Probably caused by : memory_corruption ( nt!MiReleaseConfirmedPageFileSpace+86 ) Followup: MachineOwner ---------Code:BugCheck 7F, {8, 80050031, 406f8, fffff800031b8540} Probably caused by : ntkrnlmp.exe ( nt!KiDoubleFaultAbort+b2 ) Followup: MachineOwner ---------
Run: 3 Errors: 64
Don't know if I need to keep it running still, or not.
Quote