BSOD Occurs upon either launching a game, or trying to validate cache.

[RG Ascent]

Hello!

I had made a thread a while ago and I thought that the solution was found. Sadly, it is starting up once again. I tried to reach out to the first person who helped me but got no response- hence the new thread. Anyway so this is what happens. I go to launch the game, but I get the blue screen. I go to validate the system files (which usually fixes it) and I get a blue screen. So, I am hoping that someone out there can help me!

I have attached the file necessary for y'all to help/

Thanks!

 

[essenbe]

Hello, RG Ascent. There were no dump files in the files you uploaded. Please make sure your computer is configured for small memory dumps. http://www.sevenforums.com/tutorials/174459-dump-files-configure-windows-create-bsod.html

Also, please open an elevated command prompt ( click start, type cmd in the search box, right click on the cmd entry and select run as administrator) in the black box that opens, copy/paste sfc /scannow. If you decide to type it, notice the space between the sfc and the /. It is a system file checker which will scan your system files and attempt to correct any missing or corrupt files. What we want are the results to say windows found no integrity violations. If it says files were found but could not be repaired, close the box, reboot and run it again, after opening the administrative command prompt. You may have to reboot and run it three times for it to repair all system files. If it can't repair them after 3 reboots, let us know.

 

[RG Ascent]

Hello, RG Ascent. There were no dump files in the files you uploaded. Please make sure your computer is configured for small memory dumps. http://www.sevenforums.com/tutorials/174459-dump-files-configure-windows-create-bsod.html

Also, please open an elevated command prompt ( click start, type cmd in the search box, right click on the cmd entry and select run as administrator) in the black box that opens, copy/paste sfc /scannow. If you decide to type it, notice the space between the sfc and the /. It is a system file checker which will scan your system files and attempt to correct any missing or corrupt files. What we want are the results to say windows found no integrity violations. If it says files were found but could not be repaired, close the box, reboot and run it again, after opening the administrative command prompt. You may have to reboot and run it three times for it to repair all system files. If it can't repair them after 3 reboots, let us know.

Hey!

First off let me start by saying thanks for the reply! It means a lot to me. Secondly, I have configured me computer to generate small memory dumps. Now that I have done this do I need to try to trigger the BSOD again?

Secondly, regarding the file checker it resulted with this (even after the third try) http://puu.sh/iat1X/c60054552a.png

Please let me know what else I need to do.

Also, I use to be using a windows 7 theme called dark light or something of that nature (I have been using it for almost a year) and now it is gone? As well as my background. Just a side note. Maybe the dark light theme was causing the BSOD? Who knows.

Once again, thank you for your help.

 

[essenbe]

The sfc scan will remove themes most of the time and may be why you had the errors. Maybe when we get a few dump files we will have an idea of where to look. Make sure you have a Minidump folder in C:/Windows.

 

[RG Ascent]

The sfc scan will remove themes most of the time and may be why you had the errors. Maybe when we get a few dump files we will have an idea of where to look. Make sure you have a Minidump folder in C:/Windows.

Yes, I do have that folder, but it is empty.

 

[essenbe]

OK, good. That is where you told it to put the dump files if you set it for small memory dumps. I just wanted to make sure the folder existed.

 

[RG Ascent]

Ok so what do I need to do from here? Thanks!

 

[essenbe]

I guess just wait for a few dump files then upload the BSOD posting instructions here.