Ok so forget about that other problem guys it looks like I have a much bigger one. I start a championship and game crashes with error to desktop randomly, it doesn't matter if I am in the pits, in practice or race. I simply select single player/championship/car/tracks/rules and go. Didn't do anything weird at all to the game yet, it's in mint condition so I have no idea what the problem is. Unfortunately I didn't check what error that was because I rage quit and shut down the pc what can I say I was having a great battle but I will take a screen next time. I have the minidump and have verified the game via steam. My specs are: Intel i7 6700k at 4.0 GHz Corsair H110i Corsair Carbide Clear 600C with 5 Corsair Air Series Magnetic Levitation 140mm PWM Red Led fans MSI Z170A M7 (Up do date drivers including bios update) 16GB (2x8) Corsair Vengeance DDR4 3000MHz CL15 Red Led MSI GTX 1080 Gaming X (OC mode no further overckolck and latest nvidia drivers complete clean install this week) 240GB Kingston UV400 SATA 3 SSD 2x 1TB Seagate SATA 3 HDD 7200rpm 64mb Windows 10 Pro x64 v.1607 fully updated Programs I must have in the background: Logitech Gaming Software latest version for the G810 keyboard and G502 Proteus mouse Logitech Profiler for the G25 Steam for obvious reasons Corsair link for the H110i profile and Memory and Waterblock lighting profile MSI Afterburner for fan profile on GPU Riva Tunner for Afterburner's performance overlay MSI Gaming App for GPU lighting customization Realtek HD Audio Manager Nvidia GeForce Experience for ShadowPlay Capturing All are up to date. Background processes should be the standard windows 10 ones plus the before mentioned software. I am very particular of what runs in the background so I have fully customized the startup processes to run as few as possible, hence I only run Daemon Tools or other stuff manually when needed. There have not been any changes made to the system recently, the game worked fine for the 60 hours or so that I used it, so hopefully we can understand what's happening now. Sorry for the long story but I wanna give as much information as possible to fix this issue since this is why I made this pc. I failed to mention that I get a BSOD once in a while which was not fixed by a clean windows reinstall and there is no chance any of the components are bad have tested everything extensively, so it's either windows doing stupid stuff or another software issue but that BSOD I guess is for another forum. So I am aware that there is a problem within my system witch makes me mad since I am such an OSD when it come's to every thing that moves on my system but anyway I am not sure if the problems are related or not. Most of them pointed to the Realtek Audio drivers and in one instance to the Nvidia driver. I already made a 100% clean Nvidia driver reinstall and tested it but still got BSOD. I just reinstalled clean the Realtek drivers but have no time to further test right now. Here are the minidump files:
The Windows crash dumps if interested: Crash Dump Analysis Crash dump directory: C:\Windows\Minidump Crash dumps are enabled on your computer. On Sat 1/21/2017 9:37:33 AM your computer crashed crash dump file: C:\Windows\Minidump\012117-5468-01.dmp This was probably caused by the following module: hdaudbus.sys (0xFFFFF80234AD2831) Bugcheck code: 0x50 (0xFFFFA6062AF5C2D0, 0x2, 0xFFFFF80234AD2831, 0x2) Error: PAGE_FAULT_IN_NONPAGED_AREA file path: C:\Windows\system32\drivers\hdaudbus.sys product: Microsoft® Windows® Operating System company: Microsoft Corporation description: High Definition Audio Bus Driver Bug check description: This indicates that invalid system memory has been referenced. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time. On Sat 1/21/2017 9:37:33 AM your computer crashed crash dump file: C:\Windows\memory.dmp This was probably caused by the following module: rtkvhd64.sys (RTKVHD64+0x6A06) Bugcheck code: 0x50 (0xFFFFA6062AF5C2D0, 0x2, 0xFFFFF80234AD2831, 0x2) Error: PAGE_FAULT_IN_NONPAGED_AREA file path: C:\Windows\system32\drivers\rtkvhd64.sys product: Realtek(r) High Definition Audio Function Driver company: Realtek Semiconductor Corp. description: Realtek(r) High Definition Audio Function Driver Bug check description: This indicates that invalid system memory has been referenced. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: rtkvhd64.sys (Realtek(r) High Definition Audio Function Driver, Realtek Semiconductor Corp.). Google query: Realtek Semiconductor Corp. PAGE_FAULT_IN_NONPAGED_AREA On Thu 1/19/2017 8:11:45 PM your computer crashed crash dump file: C:\Windows\Minidump\011917-5265-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x14A6F0) Bugcheck code: 0x3B (0xC0000005, 0xFFFFF803EAA9B7AA, 0xFFFF96016EED6DF0, 0x0) Error: SYSTEM_SERVICE_EXCEPTION file path: C:\Windows\system32\ntoskrnl.exe product: Microsoft® Windows® Operating System company: Microsoft Corporation description: NT Kernel & System Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time. On Wed 1/18/2017 9:23:12 AM your computer crashed crash dump file: C:\Windows\Minidump\011817-5812-01.dmp This was probably caused by the following module: win32kbase.sys (win32kbase+0x1F7D1) Bugcheck code: 0x3B (0xC0000005, 0xFFFFE90F4261F7D1, 0xFFFFAC8040086EE0, 0x0) Error: SYSTEM_SERVICE_EXCEPTION file path: C:\Windows\system32\win32kbase.sys product: Microsoft® Windows® Operating System company: Microsoft Corporation description: Base Win32k Kernel Driver Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time. On Sun 1/15/2017 7:49:52 PM your computer crashed crash dump file: C:\Windows\Minidump\011517-5171-01.dmp This was probably caused by the following module: nvlddmkm.sys (nvlddmkm+0x8B993E) Bugcheck code: 0x3B (0x80000003, 0xFFFFF80BC928993E, 0xFFFF92006D2DB920, 0x0) Error: SYSTEM_SERVICE_EXCEPTION file path: C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_3f929cc119e3b994\nvlddmkm.sys product: NVIDIA Windows Kernel Mode Driver, Version 376.33 company: NVIDIA Corporation description: NVIDIA Windows Kernel Mode Driver, Version 376.33 Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 376.33 , NVIDIA Corporation). Google query: NVIDIA Corporation SYSTEM_SERVICE_EXCEPTION On Sun 1/15/2017 9:12:24 AM your computer crashed crash dump file: C:\Windows\Minidump\011517-6546-01.dmp This was probably caused by the following module: fltmgr.sys (0xFFFFF8044E6D6364) Bugcheck code: 0x50 (0xFFFFB780F3102188, 0x0, 0xFFFFF8044E6D6364, 0x2) Error: PAGE_FAULT_IN_NONPAGED_AREA file path: C:\Windows\system32\drivers\fltmgr.sys product: Microsoft® Windows® Operating System company: Microsoft Corporation description: Microsoft Filesystem Filter Manager Bug check description: This indicates that invalid system memory has been referenced. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time. Conclusion 6 crash dumps have been found and analyzed. 6 are included in this report. 2 third party drivers have been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers: nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 376.33 , NVIDIA Corporation) rtkvhd64.sys (Realtek(r) High Definition Audio Function Driver, Realtek Semiconductor Corp.) If no updates for these drivers are available, try searching with Google on the names of these drivers in combination with the errors that have been reported for these drivers. Include the brand and model name of your computer as well in the query. This often yields interesting results from discussions on the web by users who have been experiencing similar problems. Read the topic general suggestions for troubleshooting system crashes for more information. Note that it's not always possible to state with certainty whether a reported driver is responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.