PC Bugs noticed so far

hiyagasriiniyavan

Club Captain
Joined
Aug 11, 2014
Online Cricket Games Owned
  1. Don Bradman Cricket 14 - Steam PC
when others invite me in onlile game i can't able to join from i bought a game in stream onwards,why any solution?
 

Shamsheer Haider

School Cricketer
Joined
Dec 30, 2019
Yeah the game just seems to have problems rendering one particular screen in resolutions above 1080p. We've had this phenomena confirmed by a few people now.





Just for reference, I've attached menu screen that crashes it. If you can get past that screen (through a myriad of saving, exiting, restarting and resolution-changing..) the rest works fine.

Dear All,

who are facing that issue. I want to share my experience. I was also facing the same issue. Now my game is working well and not crashes even during career mode. For smooth working follow the following steps.

go to control panel
go to window defender firewall
Allow an app or feature through windows defender firewall
Scroll down and select ashes app.
Also, find screenshot for more clearance.
 

Attachments

  • Ashes Solution.PNG
    Ashes Solution.PNG
    32.3 KB · Views: 2

troll3y

Club Cricketer
Joined
Jan 31, 2013
Location
Melbourne, Australia
Profile Flag
Sri Lanka
Online Cricket Games Owned
  1. Don Bradman Cricket 14 - Steam PC
TLDR: Tentatively I'm going to say I might have solved it with Nvidia Control Panel.

@Dutch It's happened before only with DBC 17 and Ashes. In the past I've spent hours on the phone with tech support from where I bought the PC trying to get to the bottom of it. With DBC 17 the solution suggested was:"play a different game." :lol Although I did solve it eventually it's been that long I can't remember exactly what I did. Recently had to install a new SSD and Windows, so any settings I may have had preventing it might have been removed. I did initially think it could be the controller, when playing DBC 17, but tried it with other games and there was no problem. Unistalled and reinstalled the controller with Ashes and still the issue persisted.

@beechcroft I do have WhoCrashed but it's not really helped me get to the bottom of it. I did try it in unison with the driver Verifier progam on Windows and an issue with the driver for my headset was highlighted. I uninstalled and reinstalled. Still crashed. Like the when I tested the controller on other games, I have had no issues with my headset. It is only Big Ant games (Ashes & DBC 17) that have caused this issue of consistent BSOD. No issues when playing the likes of Doom, GTA V, Wolfenstein, Dishonored 2, Prey on the highest graphical settings, where I'd expect to encounter the same problem.

ANYWAY, I have the FPS counter on my screen to keep track of the frames per second when playing PUBG. So it also appears in other games. With Ashes one thing that had always confused me was why it would be over 200. When the games first loads it's four figures! I just assumed it's a bad reading by Steam or I don't understand fully how it works and what it displays. Having exhausted all other options (controller, headset, drivers, adjust power settings, switching to a different 4-way plug adapter) I thought I'd have a look into that. I went into the Nvidia Control Panel and changed the VSync setting from 3D Application Setting to Adaptive. I did change a couple of other settings but VSync relates to the FPS. Lo and behold when I fired the game up the FPS was capped at 60. Played 20+ overs. No crash. Then, I'm not sure why (I think my monitor/graphics card may reset my display when playing the game because the refresh rate goes from 144 to 120), when I next loaded the game up the high FPS returned. Crash. Went back and made sure the settings were how I had them and I've just played a session without a crash. The FPS was limited to 60.

Someone who knows more about this sort of thing than me might be able to give a reason for this making a difference - my layman's logic is, perhaps, trying to process all those frames causes my GPU to overpower/overheat and crash the system.

I'm going to keep an eye on it but I've not been able to play as far as 10 overs without a crash for a few weeks and it had even started happening just using the academy. So there's definitely an improvement.

CC:@MattW@BigAntStudios this might be of interest to you

THANK YOU!! Your post has been a big help, even though I still haven't yet solved my crashing issues entirely.

I have only just installed Ashes Cricket on my laptop (which is my only new device with an adequate GPU: a GTX 1050 Ti), but for whatever reason(s) the game always crashes after 5 minutes and 40 seconds, no matter what I am doing within the game. I'm still just updating all the teams! Thanks to your posts, I forcefully updated my NVIDIA driver (after both Windows and NVIDIA GeForce Experience lied about there being an update) and fiddled around in the NVIDIA Control Panel (although my one doesn't have "Adaptive" as an option under Vertical sync. After manually limiting the GPU's frame rate in the NVIDIA Control Panel to 400, I was able to play for a luxurious 6 minutes and 45 seconds before crashing.

With the updated NVIDIA driver, I also managed to overlay the frame rate in the corner, so I can now monitor it (as long as I remember to look at it every couple of seconds). With some more trialling and erroring, I reckon I'll be able to eventually eliminate these crashes entirely.

Thanks again!
 

troll3y

Club Cricketer
Joined
Jan 31, 2013
Location
Melbourne, Australia
Profile Flag
Sri Lanka
Online Cricket Games Owned
  1. Don Bradman Cricket 14 - Steam PC
Nope. Back to 5 minutes 40 seconds, still merely updating Best Teams, so the FPS is hovering between 80 and 85 fps. My hard drive fan was spinning like crazy, though, so I'm still tweaking NVIDIA Control Panel options to take as much strain off as possible.

Edit: Stumps on day 1 of this particular test. I have updated all teams, which is a minor victory, but the game is still crashing at 5 minutes 40 seconds regardless of what I am doing (or not doing). At exactly 2 minutes, my fan goes into overdrive until a few seconds after the inevitable crash at 5:40. Something is causing the fan to go berzerk, but I can't figure out what. I did change the Vertical Sync setting to Adaptive after I installed the new driver and that option became available, but that hasn't helped.

WhoCrashed Report:

Code:
Windows version: Windows 10, 10.0, version 2009, building: 19042
Windows dir: C:\WINDOWS
Hardware: XPS 15 9570, Dell Inc. 0D0T05
CPU: GenuineIntel(R) Core(TM) i7-8750H CPU @ 2.2GHz 8664, level: 6
12 logical processors, active mask: 4095
RAM: 16902221824 bytes (15.7GB)

No valid crash dumps have been found on your computer

Some time tomorrow, I'll copy out all the NVIDIA Control Panel settings. I have a feeling that, much like @wasteyouryouth, it will be some seemingly innocuous setting(s) in the NVIDIA Control Panel that will solve the whole conundrum.

Any help from anyone would be much appreciated. Thanks.
 
Last edited:

Users who are viewing this thread

Top