Apparently random BSOD while playing

Game mode: [Single-player]
Type of issue: [Crash]
Server type: [PvE]
Region: [Local Instance]


Hello there,

for quite some time i am experiencing “random” Bluescreen while playing Conan Exiles and exclusively Conan Exiles. All other Games run just fine for hours on end.

There is no pattern as of which i can deduce, what the Problem is. It happens at different times (right after starting the game, after a few hours of playing) and on different actions (in fight, when just walking to a destination, standing around, opening inventory).

Win7 64 Bit SP1
RAM: 8GB
AMD FX 8350 8 Core Processor
AMD Radeon R9 200 Series

Drivers are up to date

Log:
Is located at Pastebin: xbyPjv4Z
I cannot add URLs, therefore just adding the Paste ID. (Append the ID to the Pastebin Base URL “pastebin (dot) com”)

Mini Dump

Microsoft ® Windows Debugger Version 6.3.9600.17336 AMD64
Copyright © Microsoft Corporation. All rights reserved.

Loading Dump File [C:\Users\hasifee\Desktop\062319-24866-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

************* Symbol Path validation summary **************
Response Time (ms) Location
Deferred SRVC:\SymCache {MICROSOFT SYMBOL URL}
Symbol search path is: SRVC:\SymCache {MICROSOFT SYMBOL URL}
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.24475.amd64fre.win7sp1_ldr.190516-0600
Machine Name:
Kernel base = 0xfffff80003019000 PsLoadedModuleList = 0xfffff80003252c90
Debug session time: Sun Jun 23 10:47:46.205 2019 (UTC + 2:00)
System Uptime: 0 days 1:43:01.375
Loading Kernel Symbols



Loading User Symbols
Loading unloaded module list


  •                                                                         *
    
  •                    Bugcheck Analysis                                    *
    
  •                                                                         *
    

Use !analyze -v to get detailed debugging information.

BugCheck 1E, {0, 0, 0, 0}

*** WARNING: Unable to verify timestamp for atikmdag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys




*** Either you specified an unqualified symbol, or your debugger ***
*** doesn’t have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing “.symopt- 100”. Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***


*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***


*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***


*** Type referenced: ExceptionRecord ***






*** Either you specified an unqualified symbol, or your debugger ***
*** doesn’t have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing “.symopt- 100”. Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***


*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***


*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***


*** Type referenced: ContextRecord ***






*** Either you specified an unqualified symbol, or your debugger ***
*** doesn’t have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing “.symopt- 100”. Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***


*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***


*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***


*** Type referenced: ExceptionRecord ***






*** Either you specified an unqualified symbol, or your debugger ***
*** doesn’t have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing “.symopt- 100”. Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***


*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***


*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***


*** Type referenced: ContextRecord ***



Probably caused by : dxgmms1.sys ( dxgmms1!VidSchiProcessDpcVSyncCookie+e9 )

Followup: MachineOwner

6: kd> !analyze -v


  •                                                                         *
    
  •                    Bugcheck Analysis                                    *
    
  •                                                                         *
    

KMODE_EXCEPTION_NOT_HANDLED (1e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Arguments:
Arg1: 0000000000000000, The exception code that was not handled
Arg2: 0000000000000000, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: 0000000000000000, Parameter 1 of the exception

Debugging Details:




*** Either you specified an unqualified symbol, or your debugger ***
*** doesn’t have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing “.symopt- 100”. Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***


*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***


*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***


*** Type referenced: ExceptionRecord ***






*** Either you specified an unqualified symbol, or your debugger ***
*** doesn’t have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing “.symopt- 100”. Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***


*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***


*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***


*** Type referenced: ContextRecord ***






*** Either you specified an unqualified symbol, or your debugger ***
*** doesn’t have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing “.symopt- 100”. Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***


*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***


*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***


*** Type referenced: ExceptionRecord ***






*** Either you specified an unqualified symbol, or your debugger ***
*** doesn’t have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing “.symopt- 100”. Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***


*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***


*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***


*** Type referenced: ContextRecord ***



CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT

BUGCHECK_STR: 0x1E

PROCESS_NAME: System

CURRENT_IRQL: 2

ANALYSIS_VERSION: 6.3.9600.17336 (debuggers(dbg).150226-1500) amd64fre

DPC_STACK_BASE: FFFFF8800316EFB0

EXCEPTION_RECORD: fffff88003166f98 – (.exr 0xfffff88003166f98)
ExceptionAddress: fffff88004d04f7d (dxgmms1!VidSchiProcessDpcVSyncCookie+0x00000000000000e9)
ExceptionCode: c0000094 (Integer divide-by-zero)
ExceptionFlags: 00000000
NumberParameters: 0

TRAP_FRAME: fffff88003167040 – (.trap 0xfffff88003167040)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000000
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88004d04f7d rsp=fffff880031671d0 rbp=fffffa8009aa39a0
r8=0000000000000000 r9=0000000000000000 r10=fffffa8009aa21f0
r11=fffff88003167288 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
dxgmms1!VidSchiProcessDpcVSyncCookie+0xe9:
fffff880`04d04f7d 48f7f1 div rax,rcx
Resetting default scope

LAST_CONTROL_TRANSFER: from fffff800030afcde to fffff800030aca70

STACK_TEXT:
fffff88003166088 fffff800030afcde : 0000000000000002 fffff880031677e8 fffff88003166800 fffff80003079b70 : nt!KeBugCheck
fffff88003166090 fffff800030b3ddd : fffff8000328f7fc fffff800031dafe4 fffff80003019000 fffff88003166f98 : nt!KiKernelCalloutExceptionHandler+0xe
fffff880031660c0 fffff80003078eb5 : fffff800031c2644 fffff88003166138 fffff88003166f98 fffff80003019000 : nt!RtlpExecuteHandlerForException+0xd
fffff880031660f0 fffff8000319399e : fffff88003166f98 fffff88003166800 fffff88000000000 fffffa8000000004 : nt!RtlDispatchException+0x415
fffff880031667d0 fffff800030baf42 : fffff88003166f98 fffffa80098b5410 fffff88003167040 0000000000000000 : nt!KiDispatchException+0x17e
fffff88003166e60 fffff800030b5ddc : 0000000000000000 fffff8801118f694 fffffa800d3012c0 000000000000000b : nt!KiExceptionDispatch+0xc2
fffff88003167040 fffff88004d04f7d : fffffa80098b5410 0000000000000000 fffffa8009aa2000 fffffa800d7a6af0 : nt!KiDivideErrorFault+0x2dc
fffff880031671d0 fffff88004d04d24 : fffff88000000000 fffff88000000021 fffff88000000000 0000000000000000 : dxgmms1!VidSchiProcessDpcVSyncCookie+0xe9
fffff88003167290 fffff88004d04c88 : 000000f410000000 fffffa80098b5410 fffffa800d3012c0 fffffa800d301580 : dxgmms1!VidSchDdiNotifyDpcWorker+0x80
fffff880031672e0 fffff88004c0a1cf : fffffa8008bb7480 0000000000000000 0000000000000001 fffffa800d301580 : dxgmms1!VidSchDdiNotifyDpc+0x94
fffff88003167330 fffff8801118eaa9 : fffffa800d3012c0 fffffa800d3012c0 fffffa800d3012c0 fffff88003167768 : dxgkrnl!DxgNotifyDpcCB+0x77
fffff88003167360 fffffa800d3012c0 : fffffa800d3012c0 fffffa800d3012c0 fffff88003167768 0000000000000000 : atikmdag+0xc2aa9
fffff88003167368 fffffa800d3012c0 : fffffa800d3012c0 fffff88003167768 0000000000000000 fffff880031673c0 : 0xfffffa800d3012c0 fffff88003167370 fffffa800d3012c0 : fffff88003167768 0000000000000000 fffff880031673c0 0000000000000000 : 0xfffffa800d3012c0
fffff88003167378 fffff88003167768 : 0000000000000000 fffff880031673c0 0000000000000000 0000000000000000 : 0xfffffa800d3012c0 fffff88003167380 0000000000000000 : fffff880031673c0 0000000000000000 0000000000000000 0000000000000001 : 0xfffff88003167768

STACK_COMMAND: kb

FOLLOWUP_IP:
dxgmms1!VidSchiProcessDpcVSyncCookie+e9
fffff880`04d04f7d 48f7f1 div rax,rcx

SYMBOL_STACK_INDEX: 7

SYMBOL_NAME: dxgmms1!VidSchiProcessDpcVSyncCookie+e9

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: dxgmms1

IMAGE_NAME: dxgmms1.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 5b94676d

IMAGE_VERSION: 6.1.7601.24260

FAILURE_BUCKET_ID: X64_0x1E_dxgmms1!VidSchiProcessDpcVSyncCookie+e9

BUCKET_ID: X64_0x1E_dxgmms1!VidSchiProcessDpcVSyncCookie+e9

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:x64_0x1e_dxgmms1!vidschiprocessdpcvsynccookie+e9

FAILURE_ID_HASH: {563df3f2-b5ac-cd6b-d157-580c3b7f02da}

Followup: MachineOwner

From what i gather from the Dump File, there appears to be a Divide-by-Zero Exception in Module dxgmms1.

Although i am not sure, if this is correct, since i am missing quite a few Symbol Declarations it seems.

I appreciate any help on this issue, since it really cuts down the excitement of playing it. :sweat_smile:


Please provide a step-by-step process of how the bug can be reproduced. The more details you provide us with the easier it will be for us to find and fix the bug:

  • None available, no clear pattern -
1 Like

Well written and detailed, Fairiestoy, which is unusual for a first time user, thank you.

Fortunately there are much more knowledgeable people here that can, hopefully, analyze this further and provide a cure.

Good luck !

Regards

jim

There is another one here:

1 Like

Do you see anything relevant in the UE4 saved logs after a BSoD?

steamapps\common\Conan Exiles\ConanSandbox\Saved\Logs

Jim1
Glad that the post appears complete. No Information no help, right? :wink:

Regarding your Question kefka:
I couldn’t find something odd in the Logs, but then again, i have nothing to compare them to. The last few Lines of the ConanSandboxLog do not look suspicous. (See below last lines). Not sure, if an AMD CPU/GPU would be the Issue. At least i hope not, would be a very bad thing for me ^^.

Currently i hope, that there is some odd call to a systems file that causes this and can be fixed easily. But, that’s just my hope.

  1. [2019.06.23-08.46.39:088][594]Items:Error: Data: [BP_Emote_Worship_Set] missing lore item in table: 0

  2. [2019.06.23-08.46.43:017][742]LogLevelActorContainer: Created LevelActorCluster (210) for /Game/Maps/ConanSandbox/Art/Caves/Art_Caves_x3_y2_B.Art_Caves_x3_y2_B:PersistentLevel with 126 objects, 0 referenced clusters and 16 mutable objects.

  3. [2019.06.23-08.47.10:274][719]LogEngine:Warning: GetWorldFromContextObject called with a NULL game instance object.

  4. [2019.06.23-08.47.10:274][719]GameEventTelemetryDebug:Display: -89952.4 163360.6 -11834.4 1 NPCDeath “HumanoidNPCCharacter_C_133”

  5. [2019.06.23-08.47.26:594][322]LogEngine:Warning: GetWorldFromContextObject called with a NULL game instance object.

  6. [2019.06.23-08.47.26:594][322]Items:Error: Data: [BP_Emote_Worship_Set] missing lore item in table: 0

  7. [2019.06.23-08.47.29:650][439]LogLevelActorContainer: Created LevelActorCluster (210) for /Game/Maps/ConanSandbox/Art/Caves/Art_Caves_x3_y2_B.Art_Caves_x3_y2_B:PersistentLevel with 126 objects, 0 referenced clusters and 16 mutable objects.

  8. [2019.06.23-08.47.38:745][769]LogLevelActorContainer: Created LevelActorCluster (192) for /Game/Maps/ConanSandbox/Gameplay/Camps_NPC/Camps-NPC_x3_y2-2.Camps-NPC_x3_y2-2:PersistentLevel with 20 objects, 0 referenced clusters and 11 mutable objects.

1 Like

On the next BSOD check if there’s a UE4CC-Windows-XXXXXXXXXXXXXXXXXXXX folder in the …/Saved/Logs directory.

It could contains :

  • CrashContext.runtime-xml
  • UE4Minidump
  • UE4Minidump.dmp.status

It might get us some clues. (I’m hoping it’s not an AMD related issue to :sweat_smile:)

Good luck.

1 Like

Will check, if i find it. The last few times, i couldn’t find such a folder or similar files in there.

Although it’s pretty brutal asking to fire the game up again and ‘waiting’ for another BSDO :grimacing:

Also going to look into possible Command Line Parameters for Game Start, haven’t looked for that just yet. Maybe we can squeeze some more info from the Game.

I know right, I’m so sorry :sweat:.
I’m actually at this point… I know that I’ll get a BSOD everytime I open Conan. Still yet I’m playing :grimacing:.

1 Like

Hey @fairiestoy

Welcome to our community and apologies for the frustration.
We imagine you might’ve checked our common technical issues thread as it contains some information about crashes on AMD hardware.
We’re going to send note to our QA so they can see if they can reproduce these crashes on their end.
Thanks for your feedback.

1 Like

@kefka
Same here. I still try to play.

I had another BSOD today. No different logs from last time. The files you mentioned did not show up. I also couldn’t figure out, if there is some kind of “extended” log. If you have some hint, would appreciate the info :slight_smile:

@Ignasis
Thank you for the notice. If your QA needs more Data on Hard/Software, let me know.

I have seen the Thread yes, but could not find my problem/solution in there. Most of the problems target freezes, weird behaviour with alt-tab or performance issues. If i still should try it, will make it so.

Before i started up today, i reinstalled my drivers with elevated privileges (you never know what works), still got a BSOD.

If i find some time this weekend, might try reinstall the game with elevated privs as well. Maybe something does not work due to restrictions (had something similiar with Virtualbox a while ago, kind of odd. BSOD due to some Hyper-V functions that could not be accessed as normal user)

1 Like

Your C++ Redistributable might be corrupted.
Go to
https://support.microsoft.com/en-us/help/2977003/the-latest-supported-visual-c-downloads

While you’re on that page:
Uninstall all previous versions using your Uninstall Program feature.

Then download and save the latest x86 and x64 C++ Versions.
Then run the install process for each one.
Reboot your PC.

That is what finally worked for me.

Hey Vahlok,

Could you share what OS, CPU and GPU you’re using?

Thanks

Here you go:

Computer Information:
Manufacturer: Gigabyte Technology Co., Ltd. (990FXA UD3 R5)
Model: To be filled by O.E.M.
Form Factor: Desktop
No Touch Input Detected

Processor Information:
CPU Vendor: AuthenticAMD
CPU Brand: AMD FX™-9590 Eight-Core Processor
CPU Family: 0x15
CPU Model: 0x2
CPU Stepping: 0x0
CPU Type: 0x0
Speed: 4721 Mhz
8 logical processors
4 physical processors
HyperThreading: Supported
FCMOV: Supported
SSE2: Supported
SSE3: Supported
SSSE3: Supported
SSE4a: Supported
SSE41: Supported
SSE42: Supported
AES: Supported
AVX: Supported
CMPXCHG16B: Supported
LAHF/SAHF: Supported
PrefetchW: Unsupported

Operating System Version:
Windows 7 (64 bit)
NTFS: Supported
Crypto Provider Codes: Supported 311 0x0 0x0 0x0

Video Card:
Driver: Radeon RX 580 Series
DirectX Driver Name: aticfx32.dll
Driver Version: 26.20.12001.7006
DirectX Driver Version: 26.20.12001.7006
Driver Date: 6 12 2019
OpenGL Version: 4.6
Desktop Color Depth: 32 bits per pixel
Monitor Refresh Rate: 60 Hz
DirectX Card: Radeon RX 580 Series
VendorID: 0x1002
DeviceID: 0x67df
Revision: 0xe7
Number of Monitors: 1
Number of Logical Video Cards: 1
No SLI or Crossfire Detected
Primary Display Resolution: 1920 x 1080
Desktop Resolution: 1920 x 1080
Primary Display Size: 26.65" x 15.00" (30.55" diag)
67.7cm x 38.1cm (77.6cm diag)
Primary Bus Type Not Detected
Primary VRAM Not Detected
Supported MSAA Modes: 2x 4x 8x

Sound card:
Audio device: Headphones (High Definition Audio)

Memory:
RAM: 32733 Mb

Miscellaneous:
UI Language: English
Media Type: DVD
Total Hard Disk Space Available: 953768 Mb
Largest Free Hard Disk Block: 704551 Mb
OS Install Date: Dec 31 1969
Game Controller: None detected
VR Headset: None detected

ALSO NOTE:
I ran a “Repair My Computer” with the Windows 7 OEM Installation disk and it found issues with the Bootup which it fixed.
I also ran a BIOS Update on the motherboard.

I upgraded the GPU from a 480 / 8GB to a 580 / 8GB
I also upgraded the CPU from an 8500 series CPU to the 9590 (with an accompanying CPU water cooler setup since those run hot … it’s now running a much cooler 35 degrees C).

As I had said previously, the lockup issue didn’t stop until I replaced the C++ redistributable with the latest versions from Microsoft. (After a new power supply, new GPU and CPU which might not have been necessary).

1 Like

When did Steam start with that?

As for me, mods terrify me. I won’t even mess with them until a decent wizard is built that can install and completely uninstall mods to restore the base game to its pristine condition.

I tried what you were suggesting. But still got a BSOD within 30m of gameplay.

But thanks for the sharing.

Quick Update: I am still yearning to play the Game without BSOD ^^

@Vahlok
Thank you for that hint. Tried it with the same result as @kefka

I am also using no mods. Just the Base Game plus some Content from a Bundle Purchase.

I know how crashes, and such can be frustrating.
But at verry first, don’t forget it’s summer now, and mostly hot in most countries, so make sure your system hasn’t any overheating issue.

Like for the previous post from @kefka , i see also here an older AMD configuration, with an GPU that also runned some good time.
Understand me right, i’m running myself an AMD machine, so i know how important a very good cooling system is for the older cpu’s and system.

So at very first, make sure there isn’t any overheating making your machine shuting down. This is a current issue at this periode of the year unfortunately.
Run some hardware tests, look at your temp while run your computer normally, then when launching the game, then after 5/10/15 min and so on.

Maybe check also the Radeon forum about blue-screen problems. I know some cartes had some issue over the time. You may also maybe found some clues there.

Consider also that your system may be able to run fine other games, all games are different, and so are the prerequisites, and needs. Also our configuration are different. Softwares can also interact badely by moment.

1 Like

Hey guys and girls,

I live on the Canadian East Coast. The weather high this week is 16C.
Yeah it’s summer, but we don’t need AC at all :cold_face:

That being said, I have monitored the temp and I never get close to the emergency shutdown temps from the manufacturer.
CPU 70C and GPU 85C

See ya.

Hey @fairiestoy,

I might be a little quick to call it resolved.

But I’ve been able to play for a while without BSOD by switching from fullscreen mode to windowed mode.

Since I was keeping an eye on my CPU and GPU sensors monitoring while playing, I had to switch mode. And well… no BSOD.

If you can check it out yourself, that will be nice.

Cheers.


Edit:
No BSOD since I’ve switch to Windowed mode.

1 Like

Oh that would be verry fine to me ! I don’t like the hot. :wink:
Actually you’re maybe not the majority here on the forum in this situation, but of course we have people from all around the world.
Happy to hear overheating seems not be your concern. :woman_shrugging:

What seems strange is that you blue screen seems still happen after you played a while (30 min approx).
So a solid hardware check can’t be wrong, just maybe bring some answer more.
Like said in different posts, i run myself an AMD build.
Try also run some mem-check, ram can also fail. All config are different, so hard to tell without solides tests mostly.