-
Content Count
5,344 -
Joined
-
Last visited
-
Days Won
2
Posts posted by steviejay69
-
-
Just now, HamilkarBarkas said:Ok, so what is the issue?
You're saying the B450/AMD RX combo is the problem. That is exactly my setup.
I have built 4 top to bottom different PC systems and the only issue I have had that was persistent in this game was the DX12 fogging not working. That would cause a lockup (CTRL-ALT-DEL, kill process.) It was fixed around 1.06 or 1.07 I think, fairly early on.
I have had less CTD issues than I can count on 1 hand. None of them replicable, most occurred after testing a patch without restarting or as a result of buggy online sessions.
I have used Nvidia previously (GTX970, GTX770, GTX650Ti) and I can safely say that the GTX970 was by far THE most problematic to get working and keep working and not have terrible frame rate issues or frequent random CTDs or drop from fullscreen, stutter, etc. We are now going back through various iterations to F1 2014 with those GPUs (possibly apples and oranges).
One thing I have done with the AMD GPUs is strip the heatsink off and renew the TIM - it's fairly simple to do.
I do agree that the AGESA and chipset drivers are a minefield for AM4. But I have built only on B450 and only used Ryzen 2xxx. All I do is follow the OEM recommendations for the particular AM4 CPU that I have with respect to whether I install updates or not (UEFI or chipset drivers and I follow SOP as outlined). I also ONLY use Gigabyte boards - I have had issues with MSI, ASRock and ASUSTek and I find their support not as good, IME. Memory I stick with Corsair or Crucial (Micron).
-
3 minutes ago, HamilkarBarkas said:... and it still crashes... in other modes as well and still really randomly. One time you get to lap 28 without issues, the next time it stops after 2 laps.
However, one oberservation on Civ VI (yeah, turns out that one crashes too but at least points at display driver while doing so) and some digging made it appear to me that B450 and RX580/590 combo is quite a tricky thing. Situation made even worse by faulty AMD drivers. Actually many people report problems and already did a lot of testing and nothing ever helped. Unless a radical change: replacing GPU with a Nvidia one.
https://community.amd.com/thread/239328
Unfortunately none is available to me right now but I think I will order one very soonish.
What really pushed me into the direction of the GPU being faulty (or at least the driver causing issues since multiple versions) is that one time Civ VI and F1 2019 showed a very similar graphic error where the game kept running but everything was saturized with yellow colors. Vanished after restarting the game but still an interesting thing to see. I can't really pinpoint this one but somewhere between GPU, driver, maybe also DX something goes wrong. RAM is something I do rule out by now, firstly because RAM fails mean usually BSOD and not CTD. Secondly no issues were found while testing and thirdly changes applied to the settings did not change anything for worse or better.
Corrupt save game file would have been "nice" as it means that it could have been solved easily by starting a new career. But that does really not explain the random crashing while driving. If the save were to blame and should crash while loading or saving, not while running and not minding the save game at all. The good news might be that it is not a F1 2019 issue.
I've read the thread and can categorically say this is not hardware.
My system specs:
AMD Ryzen 7 2700
16GB Corsair Vengeance (2x 8GB, DDR4-3200)
Gigabyte B450M H (UEFI r1.0)
8GB XFX RX580 Black Edition
512GB Silicon Power NVMe
750GB Seagate Momentus XT SSHD
2TB Seagate Barracuda HDD
550W EVGA Supernova G2 (80 Gold) PSU
-
10 hours ago, SamTuCan1 said:I already have port forwarding set up. It has reduced the instance of this happening but hasnt stopped it. I have also done all recommended trobleshooting but it still happens randomly
Poor connections to a lobby is likely the issue. The internet isn't a reliable path for connections and people's geographical locations and connections vary. Lobbies are random to some degree.
-
4 minutes ago, Reecewat96 said:IV been playing f1 2019 and loved every minute of it but since the latest a.i update the game is non play able as the a.i just want to ram you off the track IV tried lowering the difficulty and still have the same results, IV loved F1 ever since I was a boy but this game is killing the love for the sport
Any help with dealing with this will be of great help
Please do not post in TA with an opinion of the gameplay, this has been flagged for moving to GD. Thanks.
-
1
-
-
This board is very old and you are using an Insider build of Windows 10.
Please revert to 1909 (18363.720 at time of writing).
There are no updated drivers on the Gigabyte website.
I have repacked your BIOS file to the AMI Aptio IV UEFI version 1n you should follow the instructions below) doing so will remove any overclock of your CPU. Please load setup defaults after flashing, save and exit then re-enter desired settings before save and exit to reinstall Windows. Looking at your dxdiag, it would appear you are still on Award BIOS.
Quote- If your BIOS is AWARD BIOS, please use FLASHEFI_autoexec.bat to update U1n BIOS
- If you have already updated UEFI BIOS before, please use Efiflash_autoexec.bat to update U1n BIOS
- Some GIGABYTE utilities are not supported under UEFI BIOS architecture. Please remove Smart6, Dynamic Energy Saver, Smart TPM, and Touch BIOS utilities before updating the BIOS.
AMD WHQL Recommended (20.2.2) Realtek UAD (8586), LAN (please donate to StationDrivers if you find these drivers work great!)
Your chipset drivers should be detected by Windows 10 inbox / WU.
Please do a clean install of Windows whilst disconnected from the internet (download the drivers and MCT first).
G29/G432 should use latest GHub software.
You should be able to play with DX12 no problem. An SSD would speed up the system no end.
-
5 hours ago, SamTuCan1 said:I am waiting to play weekly event at Bahrain but seems to be stuck in the first screen where players and signal strength are listed. It has been 34 minutes as i write this and quite a few of them, there are 9 dont look like they have much signal strength. It is a situation i have never encountered before, ill attatch a screen shot of the screen i am looking at? I am playing on PC via Steam, V1.22
Without meaning to sound rude, if everyone looks like they've got a weak connection, the first thing you should check is you.
It's not (necessarily) about how good your internet connection to your ISP is, it's your connection to the lobby, usually NAT (firewall).
Play wired, reserve or set static addresses on your network, configure port forwarding. Restart your router occasionally, turn off unnecessary log files (good housekeeping). Check your connection performance before each session (easy, bookmark a link to a test site or check using your phone).
-
15 minutes ago, Maddawg1936 said:Thanks Steve! I thought this was for all Technical Assistance all platforms Sorry.
It's not your fault, the site layout is confusing.
Games should be at the top of the forum level, then TS should be prominent once you have navigated to the correct game.
-
1
-
-
17 minutes ago, UP100 said:RaceNet on the other hand is down every week 😛
Codies will most likely be unable to benefit from reinventing the wheel. That's why there are frameworks and APIs that can be used.
Doesn't really alter the fact that Steam should improve.
-
1
-
-
36 minutes ago, UP100 said:..Why? Steamworks is such an amazing tool that I cannot understand why would anyone want to remove it.
Because Steam is slow to fix issues / vulnerabilities, has occasional outages. It also extends support to older OSes. It should not be supporting W7, but Vista support was only discontinued when there were no longer a significant proportion of gamers using the OS. I feel this decision to drop support will take longer with W7.
It is still 32-bit compatible (many games are not), there is no good reason for this. 64-bit W7 was mainstream long before the end of support. Pure 32-bit CPUs ended production around 2006 (Intel Core 2 and higher, discounting Intel Atom variants which was around 5 years later, not that anyone would game on them - AMD earlier in 2004 went 64-bit with K8 and higher) and here we are still straddling architectures in 2020.
-
1
-
-
tl/dr LESS BUGS
-
8 hours ago, CaptainCheeseca said:Thanks for all the help Stevie. I finally solved the issue. I decided to try a clean install again. However, this time I went to documents where there were a few game files that don't normally get deleted. I deleted those too, including something to do with hardware config. This time, when I reinstalled the game, it worked absolutely fine. Thanks again.
Can’t believe it was something so obvious that I’ve suggested so many times before!
Errors and omissions excepted!
-
1
-
-
I just installed rFactor2 as well and no effect observed. PCARS is a prime candidate.
-
Maybe the career save is corrupt between different versions of the game?
Wouldn't explain the crashing in other modes.
@HamilkarBarkas I know you're reluctant but;
a) thanks for reinstalling Windows (I hope it was clean and not 'Reset My PC')
b) we can't assume the hardware is good (especially given a) ) and I'm sorry, but "all my other games work fine" isn't definitive. Memory loading is different and files are stored on different parts of a drive.
One last thing to try before I'm going to insist on hardware checks - Start|Control Panel|Power Options|Choose what the power buttons do|Change settings that are currently unavailable|Shutdown settings and UNCHECK 'Turn on Fast Startup'
More assumptions, Steam and game installed to C:\ and you are using an Administrator account (not running as Admin).
-
Just now, UP100 said:Yeh my game kept freezing, but you did just punt me off the track on the final proper corner 😁 For some reason the game ghosted me on your screen... it was probably scared of the freeze I had earlier?
Well, when people teleport and then ghost all over the shop....terrible game 😛
-
1 hour ago, CaptainCheeseca said:I updated vantage. didnt work. I uninstalled vantage, still nothing. At this point, i'm starting to think nothing can be done. Apart from apps like Steam, a startup called LenovoUtilityUWP is also enabled.
LenovoUtilityUWP will no doubt be linked to a driver (a bit like the Realtek Audio Console or the Intel Command Center (?) )
Is there a monitor driver? Can't see one on the product page. However, uninstall the Nvidia drivers until you go back to a Microsoft Default Adapter then try the Lenovo Nvidia and Intel drivers.
Nvidia (Lenovo), oddly PhysX (Lenovo) standalone? Intel (Lenovo) as well.
-
5 minutes ago, HamilkarBarkas said:Completely reinstalled windows... crashed before I could roll out of the garage.
edit: of course without any sort of error message
Is this Career or any mode?
-
3 minutes ago, UP100 said:Lobby now over, thanks everyone! 🙂
I got 1 race! @UP100 your lag from my car 🙂
-
I'm installing Assetto Corsa now and the Steamworks redistributable is there again. Will see what happens.
Assetto Corsa nor Steamworks redistributable affected it this time, so needs testing with PCARS/PCARS2.
-
1. A description of the issue. Please include any error codes here.
I downloaded and installed Project CARS (PCARS) and RaceRoom Racing Experience (R3E), this cause the Steamworks Redistributables to be downloaded also.
After the download was complete, the Thrustmaster T300 wheel did not detect or show up in the Thrustmaster CP, the DOR was set to 900, moving the wheel side to side was not registered. This did not affect the Fanatec Clubsport v1 pedals (they were detected fine). Exiting the CP and redetecting the wheel the DOR was set to 870/880(?) setting manually to 360 was possible but the wheel still did not register.
I had to reboot and repeat before the CP was back to normal.
2. What version of the game you are using (Shown on the start screen in the bottom left corner of the screen)
1.22
3. Game-mode?
Did not attempt to start the game as was checking registration of wheel and pedals in Thrustmaster and Fanatec CPs.
4. Are you able to recreate the issue? If so, please include recreation steps on how you encountered this issue.
No. I haven't tried to redownload the games - it's about 50GB of data. I might be prompted to if someone else can. I don't have PCARS2 to test if that's similar, but R3E is free and there are bonus content available to play this weekend (hint: other gamers please try)
5. How often do you see this problem? Is it the only time or does it always happen?
See 4
6. Have you tried any troubleshooting? We recommend the steps here as a starting point for any issues. Please let us know what troubleshooting methods you have tried while creating this post.
See 1
7. Any accessories you are using (gamepad, wheel etc)
T300 is Firmware v30, driver is 2020_TTRS1 (PS wheel - Acelith Rim)
8. Any screenshots or video of the issue? If the video is long, please include a timestamp for when the issue appears.
Unfortunately, no. I was getting ready for a league race on F1 when I discovered the issue. A full troubleshooting and video would have been too time consuming at that point.
This may go some way to sorting out the issues with Thrustmaster devices if it is replicable.
-
6 hours ago, mchriss said:I have had an issue with the game crashing my PC, and trying every thing I could think of. My PC hardware can handle it, so what is it? Today I limited the frame rate to 60 FPS and it worked! Now it is just a combination of detail and frame rate. I can run with high detail and 60 FPS with no crashes. I can not run any but the slightest overclock. The game looks good and smooth with these settings.
When troubleshooting, overclocking is not recommended. Buy the performance you want, don't expect to gain it somehow. This applies to GPUs too.
If we are going down the route of VSYNC, then YES, you SHOULD use VSYNC. The game allows you to select the detected modes for your display.
VSYNC OFF is not recommended, overdriving (sending more frames than can be displayed) a display will not be useful.
If your game settings and hardware means you create an average 80FPS then run the game at 75Hz, or 60Hz. By running uncapped, all you do is place extra stress on the hardware for no benefit. Consequently, if your hardware can produce >150FPS you need a 120 or 144Hz display. Using the settings wisely can give a desired target framerate. Running resolutions over 1080 and multiple displays will bring those framerates down rapidly anyway.
Freesync and G-SYNC displays still use V-SYNC, the display will compensate for the variable frame rate to give a smooth picture. Some Freesync displays can be detected by Nvidia hardware. DP connection is advisable, over HDMI the results are variable.
The in-game frame limiter does not always work (in cutscenes and menus). It sometimes does not work until the game or PC is restarted.
10 hours ago, pedroesbo2001 said:Hi, during this past weeks i'been testing and doing everything you told me but the issue is still there. I don't really know what it could be, it is very frustrating trying to play the game and not being able to do it. Is there anything else i could do?
Most of the above.
-
13 hours ago, Trans-Nation eSports said:I know this question is probably being asked quite frequently at this point, but we're staring down the barrell of a possible F1 cancellation period due to Covid-19. Is there in any shape or form any indication as to when we will know if there is or is not gonna be an F1 2020 for Playstation 4/PC/Xbox One, and if not... are we gonna at least get an F1 2020 skin/chassis patch for 2019 so we can at least have the Alpha Tauri and other new liveries/body shapes for the game? SO basically add a 2020 function with the same tracks etc.
I think by this time last year we had snippets of what was to come for F1 2019... I think at least a message from Lee would be accomodating more than anything.
I'd also prefer this not to stem into a full scale discussion, so I'd appreciate if moderators and such would reply to this, or Codemasters higher ups.
Send an email then, don't post in a public forum? (The red squiggly lines are spellcheck flags, FYI.)
-
On 3/12/2020 at 5:23 PM, GZRCacasa said:Yeah, believe it or not those are the latest drivers
Identify your board?
MS-7B79 = MSI X470 GAMING PRO? If YES > UEFI
-
1 hour ago, CaptainCheeseca said:Thanks for replying, Steve.
I did as you asked. Updated all the drivers and the BIOS. Reinstalled the graphics driver afterwards and rebooted. The issue is still there. Is there anything more I can do? Updated Dxdiag page is attached.
Try this. If it still doesn't work, can you uninstall any Lenovo Vantage apps then check the msconfig for startups like that (Vantage)?
-
20 minutes ago, HamilkarBarkas said:For F1 2019 it actually got worse. Apart from the "regular ingame crashes" it now crashes within while loading after a practice session or while being in the motorhome. Which never ever happened before...
I would also appreciate a response from Codemasters. Are there more patches coming or am I stuck with what can be considered a non working version?
Definitely corruption going on dude. Clean install of Windows is the only way to find out what the issue is.
F1 2019 PC - CTD issue still happening with patch 1.22
in Technical Assistance
Posted
If the B450/RX combo were bad, I should have issues. I don't.
Yes, it wasn't me that wanted it both ways, first of all denying it could be faulty hardware, which is exactly where I directed you after all the easy avenues were exhausted. You simply can't start any support assuming the hardware is faulty otherwise there is a lot of needless time spent checking for something which should not exist statistically 97% of the time in all the individual components.
But the easy checks proved faultless, so the next avenue is to reset the software. This is where the 'fun' begins.
A clean install methodology is not observed by many (and Microsoft is to blame here with it's always connected philosophy and it's driver base of 'do no harm' - there is a distinct difference between WHQL drivers that do not crash a system and OEM drivers (or reference drivers) that actually make the device PERFORM as intended (or should, given the competence of the driver developers).
Great tools like Wagnard's DDU fill this problem by running scripts to remove old files and registry entries that poor installers do not remove on uninstallation. He recommends the tool to be run in SAFE MODE without internet.
When installing drivers, DO NOT connect the machine to the internet as there is a good chance a WU or W10 inbox driver will install silently WITHOUT removing a possibly conflicting OEM driver or overwriting key parts of it to revert the performance back to 'do no harm' rather than 'as intended'.
I always disable the 'hidden' Fast Startup option in the Power Options. I have seen it exhibit very strange behaviour with some drivers as the machine is not "Shut Down", it is suspended to disk. You may argue this is poor driver design or it is unexpected behaviour. If you were around in the Windows 98 era and onwards (as I was) you will know that suspension, hibernation and resumption thereof are one of the most frustrating experiences, given specifics of hardware. Disabling the Advanced System Setting of Hardware|Device Installation Settings can stop some 'bad' drivers loading, some need forcible blocking with the wushowhide.diagcab tool.
The next thing is proper testing of memory. Due to how Memtest works, memory must be tested in a minimum config scenario. That means individual banks of DRAM, current gen means one stick at a time, some older configs meant one bank at a time (sometimes a minimum of 2 modules were required). The amount of reserved memory when testing multiple banks at once can mean small areas are not tested and some channel timings mean that errors can escape detection. It is the only memory testing tool I trust and I know it is not 100% infallible, but it does detect obvious seating errors straightaway and some errors only occur after extended testing, so 4 passes are used. Even one single error bit means the memory is FAULTY.
Hard drives, most modern hard drives are only able to be diagnosed with manufacturer tools that will do their utmost to hide the fact that a drive is failing. SMART tests can only tell you the condition of a drive at the time of the test, they cannot detect imminent drive failure and they will not detect errors once the drive diagnostics and firmware have chosen to 'hide' errors in the hope that the drive will survive in a fashion until the warranty has expired (usually well before the MTBF under normal usage).
SSDs are different but here the manufacturers will use TLC and QLC with over-provisioning. Same applies.
These caveats aside, generally firmware updates are not visible unless using the manufacturer diagnostic / monitor tool. These are a dual-edged sword, sometimes shortcomings in either the design or component quality is masked by firmware or occasionally reliability and performance is revised and optimised. I prefer to remain optimistic and update, but many users never run these tools and therefore may suffer errors or small data losses because of the lack of that very update.
Motherboards are the final piece of the jigsaw. The same thing applies. Firmware is crucial. AMD AGESA and Intel microcode. Hugely important in correcting CPU errata and the way the chipset integrates with the CPU and hardware features. AM4 is without a doubt the most ambitious technology ever attempted. Intel just release minor revisions to CPUs (Tick-Tock) and issue new chipsets each time. AMD picked an architecture that they knew was scalable (and shrinkable) and enabled a chipset so "open" that it supported those revisions and refreshes at a time when Intel's release cadence dropped (failure to hit yield on 10nm and 7nm).
So I 'get' that the drivers and firmware updates were going to be not only necessary, but need the inevitable and ubiquitous bug-fixing and tweaking.
So I reiterate that it *must* be something causing corruption or faulting in your setup.
It is possible that anything you've done hasn't met the process I describe with the experience I have. You can see why I have to be 'to the point' as much as possible (it gets lengthy).
I know you are grateful for the help, but equally I have the courage of my convictions because I back it with experience; six years of these games and many more years dealing with general PC issues.
I have never said the game does not have issues, but I don't encounter the majority of issues that people bring to the TA forums repeatedly. TA would benefit from concentrating on gameplay bugs or 'proven' graphical or controller issues.
I certainly can't agree with the view expressed in that Reddit thread that there are fundamental issues with B450 / RX. I have unearthed a specific flaw in another ASUS B450 board that I PMed the owner with, it was specific to that ASUS board.
The RX cards (like any) aren't without their issues. There are 'Known Issues' relating to Polaris in each driver release that go unfixed, but I don't encounter them and certainly not in the context of this game. When trying to solve issues I load the latest releases (optional or otherwise). When my issues are resolved, I stick until the base recommended driver overtakes my build (as I have nothing to fix) and as long as nothing new breaks that's good for me. But I know my regression point then for testing (generally the last recommended release).