I have a newly built PC that was running alright for the first few weeks of use. I have, for the last 2 months though, been slowly trying to diagnose why I've been getting BSODs every so often on my computer. I've tried using dump readers to find and compress the dump files for someone on some website to take a look at, but it appears my computer doesn't create a dump file when it crashes, even though I do have it set to do so. I have tried a CHDSK of the system. I have tried a clean install of windows. Nothing, they still happen. And they're getting more frequent.
The issue usually arises when there's multiple applications trying to open at once. As I'm typing to you now, I don't have skype open. Because it seems whenever it is open things go badly.
There are two BSOD errors I get when my machine crashes
Kernel_Data_Inpage_Error
and
Critical_Process_Died
At this point I'm pretty sure it's a hardware issue, but I have no way to check, because like I said I can't access the dump file this machine is currently creating, even when I set the destination folder to my desktop.
I'm not a specialist under any circumstance, but i'll try and get this thread started on the right foot.
Do you happen to have any extra RAM sticks OP? Try running your PC with only 1 module inserted, if it happens again, do it with the other module. This process will exclude if or if not the RAM (usually cheapest/easiest thing to change in a PC) is what is causing you issues.
I second the RAM swapping, after that I would check your event viewer for any hints of what might be going on. Those two errors usually mark a driver, RAM, or software issue. I'm placing money on the RAM and Drivers part.
So what would I be looking for in the event viewer to identify the issue? Because I swapped both RAM modules out and tried to run the shit out of them but I can't get it to crash.
Ok, so a bit of google magic and such has resulted in my playing with the event viewer, running driver verifier, FINALLY creating a dump file, and when it's read with windbg it comes up with:
Probably caused by : nvlddmkm.sys ( nvlddmkm+8f240a )
More google magic has made this out to be probably due to my Nvidia Drivers, but those are all up to date and they are constantly updated with GeForce Experience. Thing is, I don't know what to do from here. Any more information would be awesome.