BSOD after exiting games

Hello and welcome xixo22 now just so we know when you ran the memtest how many passes did you run it for?? If it was for less than 8 passes then you will have to run it all over again because anything less than 8 is no good as a test.

You also mention that you have reverted back to 7 after trying 10 now did you clean that drive thoroughly before reinstalling 7? I ask because I personally always wipe a drive before I use it again to avoid any carry through of the stuff one has been running on it.

Again personally I think that the 10 set up is causing so many problems it seems to those who have tried the upgrade and then go back to 7.

I would also run these after reseating all sticks and cards

https://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html

https://www.sevenforums.com/tutorials/433-disk-check.html< if necessary include the /f and /r in the command line as per Option2 >in safe mode if need be

if nothing there then these

https://www.malwarebytes.org/mwb-download/index.html

http://www.superantispyware.com/

http://www.bleepingcomputer.com/download/adwcleaner/

ADW download from bleepingcomputer delete any rubbish found with the malware scans

NB If anyone is runningKaspersky security it may rant about ADW - just ignore it or disable it for awhile

These are what I consider the very basic stuff to try before one goes on to test drives etc

Ok that will be good to get the memtest out of the way - overnight is the way to go my pic is for your info .

Now you might even try this little ditty of mine while you are at re seating the sticks and cards.

SLOT CLEANING

Now as for the slots to clean them use a strip of old credit card about1/2 inch wide nip the corners off one end - preferably round them offhold a piece of thin lint free cloth over the end dab on some form ofalcohol - isopropyl alcohol (if you want to be pedantic) but any ethanol basedalcohol even methylated spirits (called rubbing alcohol in the US) are good and GENTLYswipe along the slots.

This can also be done for the GPU slot/s and also the contacts of thesticks or cards - not the stick but some lint free cloth of course. See my picfor the sick but please be very gentle doing it if you are in any doubt -please ask before doing it but I use this all the time and have yet to damageanything. Plus make sure the card/sticks contacts are clean too but begentle
It is a pity though the drive was not wiped / cleaned before the 7 was pus back in as it could be corrupted with left over 10 stuff.

In the meantime if you have any fresh dump files seeing those would be handy and I will revisit the old stuff.

Ok mate good to see the RAM is ok but the dump is coming up with an error that is all too often seen - see the files and it can be anything from an update to hardware issues so it looks like we shall have to keep plodding on

Code:

ADDITIONAL_DEBUG_TEXT:  
You can run '.symfix; .reload' to try to fix the symbol path and load symbols.
MODULE_NAME: nt
FAULTING_MODULE: fffff80002e56000 nt
DEBUG_FLR_IMAGE_TIMESTAMP:  55b0009e
WRITE_ADDRESS: unable to get nt!MmSpecialPoolStart
unable to get nt!MmSpecialPoolEnd
unable to get nt!MmPagedPoolEnd
unable to get nt!MmNonPagedPoolStart
unable to get nt!MmSizeOfNonPagedPoolInBytes
 fffffa80fa3c2c48 
CURRENT_IRQL:  0
FAULTING_IP: 
nt+4a1e2
fffff800`02ea01e2 4c017668        add     qword ptr [rsi+68h],r14
CUSTOMER_CRASH_COUNT:  1
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
BUGCHECK_STR:  0xA
ANALYSIS_VERSION: 6.3.9600.17336 (debuggers(dbg).150226-1500) amd64fre
LAST_CONTROL_TRANSFER:  from fffff80002ec5869 to fffff80002ec62c0
STACK_TEXT:  
fffff880`0319a5d8 fffff800`02ec5869 : 00000000`0000000a fffffa80`fa3c2c48 00000000`00000002 00000000`00000001 : nt+0x702c0
fffff880`0319a5e0 00000000`0000000a : fffffa80`fa3c2c48 00000000`00000002 00000000`00000001 fffff800`02ea01e2 : nt+0x6f869
fffff880`0319a5e8 fffffa80`fa3c2c48 : 00000000`00000002 00000000`00000001 fffff800`02ea01e2 00000000`00000000 : 0xa
fffff880`0319a5f0 00000000`00000002 : 00000000`00000001 fffff800`02ea01e2 00000000`00000000 00000000`00000000 : 0xfffffa80`fa3c2c48
fffff880`0319a5f8 00000000`00000001 : fffff800`02ea01e2 00000000`00000000 00000000`00000000 00000000`00000000 : 0x2
fffff880`0319a600 fffff800`02ea01e2 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x1
fffff880`0319a608 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt+0x4a1e2

STACK_COMMAND:  kb
FOLLOWUP_IP: 
nt+4a1e2
fffff800`02ea01e2 4c017668        add     qword ptr [rsi+68h],r14
SYMBOL_STACK_INDEX:  6
SYMBOL_NAME:  nt+4a1e2
FOLLOWUP_NAME:  MachineOwner
IMAGE_NAME:  ntoskrnl.exe
BUCKET_ID:  WRONG_SYMBOLS
FAILURE_BUCKET_ID:  WRONG_SYMBOLS
ANALYSIS_SOURCE:  KM
FAILURE_ID_HASH_STRING:  km:wrong_symbols
FAILURE_ID_HASH:  {70b057e8-2462-896f-28e7-ac72d4d365f8}
Followup: MachineOwner

Now being rather pedantic I would like you to do this to check out the PSU I know it is probably ok but I would like to know for definite

Using HW Info
PART A:
You can test the volts on the PSU with HW Info HWiNFO, HWiNFO32/64 - Download < download the right bit version and close the right handwindow select Sensors and scroll down to the power section where you will seewhat the volts are doing see my pic. Now the section you want will be labeled -for example Asus boards usually have "Nuvoton" and Gigabyte boards"ITE" in any case the section you want will have Vbatt or VBAT in it(dead give away)
The original right hand window shows the machine running and is handy for thatbut for looking at the components in some detail close it and use the main lefthand side panel
FOR OTHER COMPONENTS
PART B:
Open each small square with + in it on the section the components are in andthen click on the individual component/s (it will highlight in blue) - in theright hand side will appear all sorts of details including brands speeds andother essential info that particular device. See pic for example.
Just run PART A: PART B: just will just show very detailed info on other components

Looks ok to me...
Checked the hard drives through HD tune everything was ok (no bad sectors according to that)

Also did chkdsk /r on all my partitions and drives:

• the 500GB(WDC WD5000AAKB-00YSA0) drive has partitions D,E,F
• the 160GB(WDC WD1600AAJB-00J3A0) is G, power on hours
• C: with the system is the SSD -no need to do chkdsk on that one

All partitions finished the 5 stages of chkdsk

Results:

• D: No errors found
• E: No errors found
• F: The second NTFS boot sector is unwriteable
• G: Chkdsk disovered free space marked as allocated in the MFT bitmap and made corrections to the filesystem

The games which after exiting give BSODs are located at E: partition
Also the BSOD doesnt happen everytime i exit a game. From what i observed nothing happens if game is launched less than an hour. Will try to research the time a bit more.

Also before the upgrade the windows was located at the 160GB G: drive. I unplugged all drives and left only the new SSD plugged in on which i made a clean windows install. After the install i plugged the hard drives and forced boot order only from the SSD. So maybe some boot sector lefovers?


EDIT:
around 15:00: a new BSOD, this happened WHILE gaming for like 10 minutes (while playing.rar)
around 17:00 New one while exiting game after about half an hour of playing (after exiting.rar)
around 21:00 unninstalled graphic drivers through DDU and installed nvidia driver 350.12
after a 2 hour gaming session exited the game and got a new BSOD (pointing to drivers or GPU) (after rollback.rar)

Also i checked the temperatures CPU around 50-60 GPU around 60-70 while playing

Hmm that dump ntoskrnl.exe keeps coming up eh? Now it can be just about anything as I mentioned before so it means we still need to look at specific hardware to eliminate each one - as I started with the PSU check the rest will need to be looked at.
By the by the volts look ok though the 5v rail looks to be teetering on the lower end of the voltage range - 4.75v is the lowest at which the system will run. But for the time being we can move on.

Next I would be looking at the hard drive and there are two methods one can use one the WD test WD Support / Downloads / Other Products / Data Lifeguard Diagnostic for Windows and a physical surface test with Partition Wizard Best Free Partition Manager for Windows | MiniTool Partition Free When you run this follow my pic instructions. You just need to make sure you are picking the right drive and hit "Start" when you have set the test up.

PS The surface test will take sometime to do.

Ok mate now we had better run that WD test feature and see what it can see. I am getting towards the point where I think I might ask for someone else to have a look at this because the dump stuff as said previously could be anything at all.

Now just one thing you mentioned just a while ago no need to chkdsk the SSD but I am wondering why?
I chkdsk mine when I get issues that I feel are OS particularly related. It does no harm that I know of and I think if the SSD is a reliable brand - then the life of it should not be affected which is one reason I think people should not run it on a SSD. That is I suppose if one went completely mad and did innumerable scans. If you are worried re this see this CHKDSK on SSD

The only thing I know that is a no no on a SSD is the defrag function it will shorten the life of the drive by it's very nature of running that function. If you want to find how to shut off defrag for that drive then see this Disk Defragmenter Schedule- Turn On or Off

If you want to improve overall performance that tutorial comes from this Optimize Windows 7

But back to where we were I think a chkdsk would be advantageous in your case .