BSODs when playing games in general, especially BF4 (WHEA 19)


  1. Posts : 2
    Windows 7 64bit
       #1

    BSODs when playing games in general, especially BF4 (WHEA 19)


    Hi there
    So for some months now my PC's getting some random crashes when playing any type of 3d game, and when playing Battlefield 4 in particular, these crashes turn into BSODs, each one with a different related system file, as seen in the logs. The most common crashes result only in a sudden Crash to Desktop, usually with no error warning, as if I just hit alt+f4. Some times when playing Wildstar the game would report "memory could not be read". When I tested ArcheAge beta the game simply froze along with the entire computer, and I had to restart it by holding down the power button. I kept a GPU-Z log of my last BF4 session, and it does not seem to be a heat issue, the highest temperature was 60șC. This GPU is brand new and my last one also seemed to suffer from the same problem. My last PC also had similar issues, and since then I switched PSU, Mobo, Processor and GPU (twice). The only parts I kept this whole were the RAM and my two hard drives, so maybe they are what's causing all this. I should note that some of the appcrashes and the latest BSOD were linking to ATI and DirectX system files. Those, however, are up-to-date.

    Recently I was trying to settle this once and for all and I found that a very specific error ocurred whenever I played: WHEA-Logger event ID 19, internal parity error. Fortunately I saved some of my event viewer logs from last december, back when I had another GPU, and they also reported many WHEA 19s. When coming back now from the BSOD the event viewer reports dozens of other errors too.

    My PSU voltage readings are fine, I contacted Corsair about them (model CX600). I have nothing overclocked except for the one issued by Sapphire on my R9 270 Boost and OC edition.

    I would really appreciate your help with this one.
      My Computer


  2. Posts : 2
    Windows 7 64bit
    Thread Starter
       #2

    Update: Tried to run prime95 on blend mode, worked for less than 3 minutes then the application stopped working. Event id 1000, exception code 0xc000001d. No BSOD, just "application has stopped working". The PC seemed fine, even with CPU load to 100% it managed to stay functional.

    Just like when gaming (and subsequently crashing) many WHEA-Logger errors (id 19) were reported seconds before the appcrash.
      My Computer


 

  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 12:46.
Find Us