Multiple BSOD's playing CS:GO, each one shows a different cause.

Page 2 of 2 FirstFirst 12

  1. Posts : 26,869
    Windows 11 Pro
       #11

    Not a problem at all. Just whenever you want to.
      My Computer


  2. Posts : 9
    Windows 7 Professional x64 Service Pack 1
    Thread Starter
       #12

    Okay, seems like I was having some multiple problems there, that's why I was getting all those different BSODs.

    I've tried to install an older nVidia driver (version 344.11) with the method you shared, but I still had BSODs and crashes.

    Then, reading further info, I found here that some devices may have problems if their nVidia settings are configured to adjust the power state of the GPU according to the current/previewed load it's experiencing. I set that to max performance and the crashes disminshed a lot. For example, I haven't had any of those crashes-without-info yet. Although I'm still geting crashes, but now all show the same exception error: 0xc0000005, which seems to be that the application has tried to write in a part of the memory which is not allowed to be used by normal apps. Now I don't know if it's an OS problem or it's that any RAM stick is faulty. I have thought about taking one of the two RAM sticks out, and try to play, and if it still happens, then try the another onle but solo, which is quicker than a full Windows reinstall.

    Anyway, if you have any idea, I will apreciate it so much.


    EDIT: I uploaded an attachment to this post with the last BSOD which indicates the 0xc0000005 exception, but I can't fully understand it.
      My Computer


  3. Posts : 26,869
    Windows 11 Pro
       #13

    I really don't believe that post has anything to do with your problem. The post is 3 years old and the poster was running a 460. The cards today and the drivers are a different animal, plus his post was about a specific game.

    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.
      My Computer


  4. Posts : 9
    Windows 7 Professional x64 Service Pack 1
    Thread Starter
       #14

    I've ran it 4 times, and every time I did, it showed in the ending message that there was some files could not be repaired. And games, audio driver (AUDIODG.EXE, audioeng.dll), still crash because of 0xc0000005 exception. Last log is attached (I think the CBS.txt file was acumulating the logs).
      My Computer


  5. Posts : 9
    Windows 7 Professional x64 Service Pack 1
    Thread Starter
       #15

    I don't want to celebrate it too quickly, but I think I have managed to fix it, I will report in when I'm sure about it
      My Computer


  6. Posts : 26,869
    Windows 11 Pro
       #16

    OK, let us know. I hope whatever you did works. I would like to know what fixed it.
      My Computer


  7. Posts : 25,847
    Windows 10 Pro. 64/ version 1709 Windows 7 Pro/64
       #17

    I would also like to know what fix the problem.
    Plus that information could help many others.
      My Computer


  8. Posts : 9
    Windows 7 Professional x64 Service Pack 1
    Thread Starter
       #18

    essenbe said:
    OK, let us know. I hope whatever you did works. I would like to know what fixed it.
    Layback Bear said:
    I would also like to know what fix the problem.
    Plus that information could help many others.
    Of course, I was waiting to make sure that the problem was solved, since I couldn't play CS:GO since I fixed it (?), I've only tested it with Sniper Elite v2, and I have been able to pass the first mission two times without any crash or error.

    I thought I could search these errors with that exception code (0xc0000005) from the oldest entries in the event viewer (I never deleted them, so I could see all the info since I had the PC) to see if I could determine if I had installed anything that was causing the error or if any other thing happened. I saw that the errors started to happen December 8th of 2014 (08/12/2014), and I went to Programs and Features to see what was installed in that day, and the apps I installed that day were:

    • Fraps (remove only)
    • Crysis
    • GamespyComrade
    • .NET Framework 1.1

    But it was so strange, because I could also see that there was installed the Microsoft .NET Framework 4.5.2 on December 6th (06/08/2014, 2 days before). Also, when uninstalling .NET Framework 1.1, the uninstaller asked me for admin privileges, so it popped the window to ask me for those privileges, and I saw that the Verified Publisher field showed that the application's publisher was unknown, so I suspect that application was either:

    1. a very old version of .NET Framework that was either in conflict with the newer one or that was deprecated and didn't work well
    2. an illegitimate version of the software
    3. simply malware

    I also uninstalled GamespyComrade, but I don't think it was the problem of it, because it's simply a client for Crysis to be able to play online. The .NET Framework fact was more weird.








    Summary


    ISSUE 1:



    The CTD that didn't show the app-stopped-working message was caused, very probabily, by the nVidia driver setting that was letting the applications to change the performance and power
    consumption dinamically, because it's likely that if it was being changed a lot of times ingame, it eventually crashed with no reason, apparently.

    Setting (sorry, it's in spanish, if you know how to change the language to english, I'd upload another image in english):






    ISSUE 2:

    The problem that caused SOME BSODS (I couldn't determine if all the BSODS were because of the first issue or the second one) with that famous exception code (0xc0000005), along with all the dozens of crashes per day showing the exact same exception code seemed to be that .NET Framework 1.1. I found out because it was installed the same day the errors started to happen (I emphasize on this because I think it could be useful for someone who's having similar problems, but the reasons are not the same), and all that was diagnosticated starting from the very beginning of the event viewer logs.
    I can't take a screenshot of the errors of that day because it seems like the registers were deleted along with the .NET Framework installation, I'm sorry for that, but I can say there were like 5 or 6 errors showing different app crashes with the same exception code




    Now I have to be sure if the problem has been completely fixed, and try to restore/revert all the changes back (the things I said I did, in the OP, that weren't successful) I did and see if the problems are gone just because of these two reasons I posted in the end. I'll mark as solved when I do so, if you don't mind :)


    Sorry for my horrible english and many thanks to essenbe for the patience and for helping me.
      My Computer


  9. Posts : 26,869
    Windows 11 Pro
       #19

    No problem at all, but you seem to be the one who did the work. That is an extremely common error code. Good investigative work. I think your English is very good. Please do mark it solved whenever you think it is. I look forward to hearing from you.
      My Computer


 
Page 2 of 2 FirstFirst 12

  Related Discussions
Our Sites
Site Links
About Us
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 20:04.
Find Us