Random BSODs Cannot Identify Reason

[Karmajosn]

To put things short I am new to this forum, and I joined up specifically to solve a problem I am currently experiencing: Random Blue Screen of Deaths, namely those that include both ntkrnpla.exe and win32k.sys. I have rooted these two out after checking the Blue Screen Viewer program.

I presume it is necessary to attach a minidump in order for forum-goers to determine what the problem is? Could the folks here direct me on how I should go about it? Where can I find this folder containing the necessary data? How can I attach it?

Moving on to the specifics, my computer currently has these specifications:
CPU: Pentium Dual Core E5700 @ 3GHz
GPU: Nvidia GT640
RAM: 4GB(3GB Usable)
Memory: 500GB

I have experienced the blue screens while playing certain video games, namely Assassin's Creed 3, 4, and World of Tanks. BSODs happen after playing the two ACs, while a BSOD happens while playing WoT. (While playing WoT, I experience freezing, sound stuttering, followed by the BSOD)

I am currently performing an anti-virus scan using Avast, deleting useless programs, and searching up some solutions. I thought about running a test for the RAM, but I do not think I should do it, since after reading the guide it says it requires a blank CD rom, some other things, that I do not quite think I should touch just yet.

Any other tips are gladly appreciated. If I could get some help to find the cause it would be great.

 

[the great randini]

win32k.sys = Multi-User Win32 Driver file.

ntkrnpla.exe = ntkernal

it will either be a bad driver, corrupted os or a rootkit. Did you recently update any drivers? Have you had to hack the registry to try to improve performance?

a nice lightweight scanner I like for finding rootkits = Rougekiller or HitManPro

How to run a system file check to repair a damaged os


start Driver Verifier

You should only run Driver Verifier on test computers, or computers you are testing and debugging. To get the most benefit from Driver Verifier, you should use a kernel debugger and connect to the test computer. See Windows Debugging.
1.Open a Command Prompt window (Run as administrator) and type verifier to open the Driver Verifier Manager.

2.Select Create standard settings (default) and click Next.

You can also choose Create custom settings to select from predefined settings, or to select individual options. See Driver Verifier Options and Selecting Driver Verifier Options for more information.


3.Select a driver or drivers to verify.

4 select all

5. reboot and it will run

http://msdn.microsoft.com/en-us/library/windows/hardware/ff545448(v=vs.85).aspx#how_to_start_dv