FZG_Immel Posted May 28, 2024 Posted May 28, 2024 I initially though it was my RAM that was faulty, but after multiple tests, it doesnt appear to be the case. I can play all day long with the F-5, or even an F-14, but with the F-4, sooner or later I get a blue screen of death, and windows reboot. Im not saying its the F-4 fault only, because it doesnt happen to everyone, but there must me something with the F-4, in conjuction with my config that makes it happen. real bummer. if anyone has any idea... (ps, appanrelty, I am not the only one. At least one more person on reddit is reporting it) [sIGPIC]https://forums.eagle.ru/signaturepics/sigpic70550_3.gif[/sIGPIC] Asus Z390-H - SSD M.2 EVO 970 - Intel I9 @5.0ghz - 32gb DDR4 4000 - EVGA 3090 - Cougar FSSB + Virpil WRBRD + Hornet Stick - Thrustmaster TPR Pedal + WinWing MIP + Orion + TO and CO pannels - Track IR5
Rosly Posted May 31, 2024 Posted May 31, 2024 BSOD is not fault of DCS. BSOD is a mark your operating system catched problem with the HW. What DCS might have done is the specific code patterns can trigger problems with your HW stability, but you should fix the HW not blaming the game. The operating system and CPU features has ability to catch problems with the applications so if that would be an issue, the app would simply crash and close (there are threads about this in particular). But never whole operating system. For instance intensive use of floating point unit or SSE can make hot spots on CPU if your cooler is mounted improperly. Specific memory access patterns can trigger errors on overclocked DDRs. Shader code can push the tolerance of stability you played around with GPU clocks. Power supply is in most cases also a part of the problem as stability greatly relying on stable voltages. All of above can simply happen if you have thermal issues due dust and fans clogged.
HB_Painter Posted May 31, 2024 Posted May 31, 2024 Hey thanks for the report! Please submit a log so that we can take a look at it!
Recommended Posts