BSOD everytime I try to play any games.

Hi and welcome to SF!

I don't want to say this but this is probably hardware issue after I see a lot of stop code 124 and 50 in the DMPs with hardware is directly being blamed even though we still are unsure what piece of hardware is faulty, might be more than 1.
For the stop code 124, please read this article to know what it means and first basic steps to try:
https://www.sevenforums.com/crash-loc...-what-try.html
Stop code 116 is graphic card issue. First approach is to update the driver. When upgrading your graphic driver you MUST remove all traces of the current driver. In order to do that we recommend using Guru3D - Driver Sweeper

When it is removed then download and install the fresh copy.
Please read this article for few things to try to fix that stop code as well as some stress tests that are very benefit for you.
https://www.sevenforums.com/crash-loc...eshooting.html
SiWinAcc.sys was blamed in one DMP, it is your Silicon Image driver - comes with package for the SIxxx, it's date from 2007 is too old to run window 7 stably.

Code:

fffff880`01413000 fffff880`0142d000   SI3132   SI3132.sys   Thu Oct 04 01:39:29 2007 (4703E1E1)
fffff880`0187f000 fffff880`01887000   SiRemFil SiRemFil.sys Thu Jun 21 02:42:10 2007 (46798312)
fffff880`01498000 fffff880`014a1000   SiWinAcc SiWinAcc.sys Fri Jun 15 07:02:02 2007 (4671D6FA)

Even though the following stress tests are mentioned in the articles above, but I will post in again, make sure to run these stress tests:
Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Boot from the CD, and leave it running for at least 5 or 6 passes.
Try this free stress test: Free Software - GIMPS

Prime95 Setup:
- extract the contents of the zip file to a location of your choice
- double click on the executable file
- select "Just stress testing"
- select the "Blend" test. If you've already run MemTest overnight you may want to run the "Small FFTs" test instead.
- "Number of torture test threads to run" should equal the number of CPU's times 2 (if you're using hyperthreading).
The easiest way to figure this out is to go to Task Manager...Performance tab - and see the number of boxes under CPU Usage History
Then run the test for 6 to 24 hours - or until you get errors (whichever comes first).
The Test selection box and the stress.txt file describes what components that the program stresses.

Furmak for your graphic card:
Try this free video stress test: FurMark: VGA Stress Test, Graphics Card and GPU Stability Test, OpenGL Benchmark and GPU Temperature | oZone3D.Net

FurMark Setup:
- If you have more than one GPU, select Multi-GPU during setup
- In the Run mode box, select "Stability Test" and "Log GPU Temperature"
Click "Go" to start the test
- Run the test until the GPU temperature maxes out - or until you start having problems (whichever comes first).
- Click "Quit" to exit

Now, let's eliminate some software that are known for potentially causing BSODs so that somehow it can make your computer less miserable:
Please remove any CD virtualization programs such as Daemon Tools and Alcohol 120%. They use a driver, found in your dmp, sptd.sys, that is notorious for causing BSODs. Use this SPTD uninstaller when you're done: DuplexSecure - Downloads
Remove Eset Node32 for now and replace by Microsoft Security Essential:
How to uninstall or remove ESET Nod32 antivirus totally?

BUGCHECK SUMMARY:

Code:

BugCheck 50, {fffff6fa4006edc0, 0, fffff80002c80e75, 5}


Could not read faulting driver name
Probably caused by : memory_corruption ( nt!MiInPageSingleKernelStack+a1 )

Followup: MachineOwner
---------
BugCheck 1A, {8886, fffffa8006d952a0, fffffa8006d472d0, 201}

Unable to load image \SystemRoot\system32\DRIVERS\SiWinAcc.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for SiWinAcc.sys
*** ERROR: Module load completed but symbols could not be loaded for SiWinAcc.sys
Probably caused by : SiWinAcc.sys ( SiWinAcc+102e )

Followup: MachineOwner
---------
BugCheck 50, {ffffffff8348184d, 1, fffff80002c70ed6, 5}


Could not read faulting driver name
Probably caused by : hardware ( nt! ?? ::FNODOBFM::`string'+42f98 )

Followup: MachineOwner
---------
BugCheck 7F, {8, 80050033, 6f8, fffff80002c864e2}

Probably caused by : memory_corruption

Followup: memory_corruption
---------
BugCheck 116, {fffffa800957b4e0, fffff880045a7c80, 0, 2}

Unable to load image \SystemRoot\system32\DRIVERS\atikmpag.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for atikmpag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmpag.sys
Probably caused by : atikmpag.sys ( atikmpag+6c80 )

Followup: MachineOwner
---------
BugCheck 124, {0, fffffa800bf63038, 0, 0}

Probably caused by : hardware

Followup: MachineOwner
---------

Regard,

Tuan

updated the SPTD application

Oh no, you don't update it, you uninstall it for me please. After removing Deamon tool, please open the tool I told you to download and click "Uninstall" for me please. You are trying to get rid of sptd.sys, not update it.

Secondly, I've not seen you remove Eset completely, because I still see it in the loaded driver. Please follow the instruction I gave you to completely remove it.

Code:

fffff880`01423000 fffff880`0143d000   SI3132   SI3132.sys   Thu Oct 04 01:39:29 2007 (4703E1E1)
fffff880`0187f000 fffff880`01887000   SiRemFil SiRemFil.sys Thu Jun 21 02:42:10 2007 (46798312)
fffff880`014a8000 fffff880`014b1000   SiWinAcc SiWinAcc.sys Fri Jun 15 07:02:02 2007 (4671D6FA)

I haven't seen you update the driver as required, Window 7 won't able to run on system that has driver at least 2 years old.

Final question, DID YOU OVERCLOCK ANYTHING? If so, please go to BIOS (F2 at startup) and hit reset everything to default.

I really suspect the graphic card, try to see if you can borrow a friend or somewhere different graphic card to try on yours, because the graphic card driver is still blamed and there are some stop codes that are potentially caused by graphic card. You can try to re-install graphic card driver again. Also update the directx as well:
Download details: DirectX End-User Runtime

Code:

BugCheck 119, {1, a2000000, 0, 0}

Unable to load image \SystemRoot\system32\DRIVERS\atikmpag.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for atikmpag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmpag.sys
Unable to load image \SystemRoot\system32\DRIVERS\atikmdag.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for atikmdag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
Probably caused by : dxgmms1.sys ( dxgmms1!VidSchiVerifyDriverReportedFenceId+ad )

Followup: MachineOwner
---------
BugCheck 1A, {41287, 150b00001c, 0, 0}

Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+42be5 )

Followup: MachineOwner
---------
BugCheck 1000007E, {ffffffffc0000005, fffff80002c99274, fffff880009a9968, fffff880009a91d0}

Probably caused by : memory_corruption ( nt!MiUnlinkFreeOrZeroedPage+1ca )

Followup: MachineOwner
---------
BugCheck 1000007E, {ffffffffc0000005, fffff80002cca805, fffff88003b2a618, fffff88003b29e80}

Probably caused by : rdyboost.sys ( rdyboost!ST_STORE<SMD_TRAITS>::StDmCurrentRegionSet+9b )

Followup: MachineOwner
---------
BugCheck 7F, {8, 80050033, 6f8, fffff880016db2b0}

Probably caused by : memory_corruption

Followup: memory_corruption
---------
BugCheck C4, {91, 0, fffffa800c148060, 0}

Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+4904 )

Followup: MachineOwner
---------

Please do this and tell me the result:
SFC /SCANNOW Command - System File Checker

Good Luck,

Tuan

Have you tried to go to this website to download the newest driver? I believe they have all you need
Silicon Image - Support

Again, you haven't answer my question: Do you overclock anything? If you are unsure or you don't know, or if you know, just go to BIOS when startup and hit reset everything to default value. The symptom looks like overclocking or Overheating to me.

Use the SpeedFan - Access temperature sensor in your computer to keep track of your computer temperature please

No need to change anything in BIOS, you said you did reset to default value, that sounds good.
It's possible that you might need to do a clean install of window 7, but before doing that, please enable driver verifier, then do everything that you like and wait for system to crash. Driver Verifier will flag bad drivers so that we can narrow down the cause. With a tons of stop codes above, it's hard to say which component of system are not working properly.

Follow this instruction:
Driver Verifier - Enable and Disable

Using Driver Verifier is an iffy proposition. Most times it'll crash and it'll tell you what the driver is. But sometimes it'll crash and won't tell you the driver. Other times it'll crash before you can log in to Windows. If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.

So, I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).

Regard,

Tuan

I will ask for you about that because I've used such that large Ram amount. Good night and let us if anything happend