BSOD and crashes

Hello my dear potential saviors,
I am a newbie as far as real software talk goes but I have been having a problem and due to my lack of cash you are my last resort before I turn my otherwise beautiful PC to a professional for days unend. So, here it goes... I bought this PC (all the parts were bought seperately from the same store and they put it all together, so it's not a brand pc)approximately 2 years ago (2y+) and from day 1 every time it booted it would go on Blue Screen restart by it self and after that it would work like a charm. I called a technician who run some tests on the hardware and the drivers only to find that my Hard disk was busted by design and brought me a new one. Of course that didn't do anything to fix the problem. He ran some more tests and everything seemed fine. After he left the problem persisted but since it only happened once every boot I rolled with it. So instead of shutting it down I decided to put the PC on sleep mode so that I would avoid the BS and it worked for a long time. However a new problem appeared, now the PC would randomly reboot by its own. It freezes and decides to go in something like a sleep mode where nothing shows on the screen but I can hear it run. Now the BS takes muuuuch longer to come up and reboot so i can go on with my business and the random crashes continue even after that. I have updated every driver from graphics to motherboards. All the updates. And I have scanned it for malware and it's clean. I have attached all the minidumps I found and the DxDiag. Sorry for the huge text. Please help me.

 

Ukitake:

Here is a breakdown of the processes listed as the cause of your blue screens:

ntoskrnl.exe 15
dxgkrnl.sys 22
Ntfs.sys 3
win32k.sys 1
dxgmms1.sys 1

ntoskrnl.exe, Ntfs.sys, and win32k.sys are more or less generic ones that tend to show up in every group of mini-dumps. When you examine your mini-dump files in BlueScreen View, you can make a list like the above and easily see that in this case, for example, dxgkrnl.sys 22 is where you need to start. Google that, and you will find all you need to fix your problem or at least to get started. Once you have a firm grasp of the problem, then you can come in and get specific about how to do what or whatever.

I just Googled, and this looks like a common problem. I think you should be able to really narrow down your effort by looking over the threads. In the mean time, someone may come along who is familiar with your specific circumstance...