Windows 10: BSOD when playing cs:go, error 0x000000ef

Hey guys,
All of a sudden my computer have started to crash when playing games, mainly csgo. It started happening about a week ago. I just installed windows 10, but if i remember correctly it started happening in windows 7 as well, right before i went and installed 10. This tells me it's probably a hardwareproblem. I was thinking temperature maybe (I did clean it, with no results tho). I don't have too much knowledge about computers in general, so was hoping someone here can help me.
Best regards, .

:)

 

CRITICAL_PROCESS ERROR

1.the error code is 0x000000EF

The error message is CRITICAL_PROCESS_DIED2.when I am playing games like border lands 2 and TF2. 3.the model is 700-410

 

Blue screen of death when playing cs go 4:3

Hi Evan,

Blue screen errors may occur due to a system failure or a hardware issue on your PC. Since the issue started after an update, there are possibilities that some of the drivers on your computer are outdated. To resolve your concern, we suggest that you update
the graphics card drivers by following the steps below:

• Select the Start button, type Device Manager, and select it from the list of results.
• Expand one of the categories to find the name of your device, then right-click (or tap and hold) it, and select Update Driver. For graphics cards, expand the Display adapters category, right-click your graphics card
  and select Update Driver.
• Select Search automatically for updated driver software.
• If Windows doesn't find a new driver, you can try looking for one on the device manufacturer's website and follow their instructions.

If you are still getting a blue screen error, you may visit this
link and follow the provided solutions.

Should you need further assistance, you can reply to this thread anytime.

 

Hi Twamse,

Welcome to the 10forums.

There is quite some activity of drivers used with the file system.
This usually means problems with your hard drive(s).
Please test your hard drive(s) using SeaTools and chkdsk.
With SSD's, only run chkdsk.
With SeaTools, prefered to run the SMART, short generic and long generic tests.
If the hard drive tests are clean, please check your system files.






Diagnostics Test

HDD & SSD TEST


Run SeaTools to check the integrity of your HDD. SeaTools for DOS and Windows - How to Use - Windows 7 Help Forums



Note Do not run SeaTools on an SSD as the results will be invalid.



Run chkdsk Disk Check - Windows 7 Help Forums






Diagnostics Test

System File Check
Please try following:

• Open an admin command prompt
• Copy/paste "sfc/scannow" (without quotes) and press enter
• When it finished reboot your system
• Open again an admin command prompt
• Enter sfc/scannow again

If sfc/scannow does NOT say "Windows Resource Protection did not find any integrity violation" after the second SFC, please upload the cbs.log file located at {windows partition}\Windows\Logs\CBS\, if the file is too large try a 3rd party uploader like dropbox, onedrive, google drive, mediafire etc.
System File Check(SFC a.k.a. Windows Resource Protection) needs to have your system rebooted in order for sfc to try to fix the problems that it finds.



Please fill in your system specsPlease follow this tutorial and download the tool. The tool will give you detailed information about your system specs, please fill in your system specs more completely including PSU and cooling system.How to fill in your system specs:

 

Hey again,
When I ran the SeaTools tests the SMART was fine, but the short and long generic failed. The chkdsk test also find errors. I've copy/pasted the log in here (not sure if you need, or even if it's the right one?). Thanks for quick answer and assistance, much appreciated, *Smile

Chkdsk was executed in scan mode on a volume snapshot.


Checking file system on C:


Stage 1: Examining basic file system structure ...
Found 0xa clusters allocated to file "\Users\twams\AppData\Local\Google\Chrome\User Data\Local State <0x10,0x5e9f8>" at offset "0" marked as free
... repaired online.

414464 file records processed. File verification completed.

4090 large file records processed.
0 bad file records processed.
Stage 2: Examining file name linkage ...
Found an unneeded link ($FILE_NAME: "LOCALS~1") in index "$I30" of directory "\Users\twams\AppData\Local\Google\Chrome\User Data <0x5,0x59079>"
... repaired online.

482612 index entries processed. Index verification completed.
Found corrupt basic file structure for "\Users\twams\AppData\Local\Google\Chrome\User Data\LOCALS~1 <0x10,0x5e9f8>"
... repaired online.
Found lost file "\Users\twams\AppData\Local\Google\Chrome\User Data\Local State <0x10,0x5e9f8>"; requesting reconnection to index "$I30" of directory "\Users\twams\AppData\Local\Google\Chrome\User Data <0x5,0x59079>"
... queued for offline repair.
Found a file "\Users\twams\AppData\Local\Google\Chrome\User Data\Local State <0x10,0x5e9f8>" with bad links
was not able to send command for self-healing due to lack of memory.

Stage 3: Examining security descriptors ...
Security descriptor verification completed.

34075 data files processed. CHKDSK is verifying Usn Journal...
Usn Journal verification completed.
Windows has found problems and some were fixed online;
the remaining problems must be fixed offline.
Please run chkdsk /spotfix to fix the issues.


488282111 KB total disk space.
108585352 KB in 151940 files.
105616 KB in 34076 indexes.
497755 KB in use by the system.
65536 KB occupied by the log file.
379093388 KB available on disk.


4096 bytes in each allocation unit.
122070527 total allocation units on disk.
94773347 allocation units available on disk.


----------------------------------------------------------------------




Stage 1: Examining basic file system structure ...


Stage 2: Examining file name linkage ...
Index entry LOCALS~1 of index $I30 in file 0x59079 points to unused file 0x5e9f9.
Deleting index entry LOCALS~1 in index $I30 of file 364665.
CHKDSK is scanning unindexed files for reconnect to their original directory.
Recovering orphaned file LOCALS~1 (387576) into directory file 364665.
Recovering orphaned file LOCALS~1 (387576) into directory file 364665.
There is no NTFS file name attribute in file 0x5e9f8.
Correcting minor file name errors in file 387576.
1 unindexed files recovered to original directory.
"chkdsk /scan" is aborting due to self-healing command failure: 00000000
"chkdsk /f" will be required to repair the volume.


Stage 3: Examining security descriptors ...

 

The hard drive is faulty/failing.

Please backup your data as soon as possible and replace the hard drive.