BSOD

[rg-more]

Okay so has anyone else had an issue with getting the BSOD while trying to play? I played for a couple hours yesterday with no issues (minus a frame rate drop at one point). Yet today I have gotten the same BSOD every time I have tried to play, it always happens a couple minutes into gameplay. "whea_uncorrectable_error"
My specs:
AMD II Phenom 1090T x6
Nvidia GTX770
Windows 10
I have been running the experimental BETA also, because of the SSE4.1 problem.

I have gone through a couple troubleshooting tips I found online to no avail. I was sort of hoping I have not been the only person with this problem. Any help would be appreciated

[AdvancedFollower]

Not related to the game.

"The WHEA_UNCORRECTABLE_ERROR bug check has a value of 0x00000124. This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA)."
https://msdn.microsoft.com/en-us/library/windows/hardware/ff557321(v=vs.85).aspx

Check your CPU and GPU cooling, stress test you RAM, video card, memory and CPU using tools such as Prime95, Aida64, Memtest, Furmark

[AcidBoiii]

Are you monitoring Temperature? Maybe overheating?

[Gromit]

Originally posted by rg-more:

Okay so has anyone else had an issue with getting the BSOD while trying to play? I played for a couple hours yesterday with no issues (minus a frame rate drop at one point). Yet today I have gotten the same BSOD every time I have tried to play, it always happens a couple minutes into gameplay. "whea_uncorrectable_error"
My specs:
AMD II Phenom 1090T x6
Nvidia GTX770
Windows 10
I have been running the experimental BETA also, because of the SSE4.1 problem.

I have gone through a couple troubleshooting tips I found online to no avail. I was sort of hoping I have not been the only person with this problem. Any help would be appreciated

yeah do you also get it while, exploring planets, and not in space or anything? I dont get bsods in even battlefield 4, so my hardware isnt faulty, im guessing, that the game isnt fully optimised for cards that dont support SSSE3 or SSE4.1, and that is causing them to crash when rendering, lots of stuff, such as planets.

[-[GFrost]Semi]

did u Overclock anything? ( i would guess CPU )

[Gromit]

Good to know im not the only person with this problem, im guessing because its only expermiental, there is still lots more optimisation ect to go in the way of amd chips

[El Dr. Gusman]

Originally posted by Snuggles:

Originally posted by rg-more:

Okay so has anyone else had an issue with getting the BSOD while trying to play? I played for a couple hours yesterday with no issues (minus a frame rate drop at one point). Yet today I have gotten the same BSOD every time I have tried to play, it always happens a couple minutes into gameplay. "whea_uncorrectable_error"
My specs:
AMD II Phenom 1090T x6
Nvidia GTX770
Windows 10
I have been running the experimental BETA also, because of the SSE4.1 problem.

I have gone through a couple troubleshooting tips I found online to no avail. I was sort of hoping I have not been the only person with this problem. Any help would be appreciated

yeah do you also get it while, exploring planets, and not in space or anything? I dont get bsods in even battlefield 4, so my hardware isnt faulty, im guessing, that the game isnt fully optimised for cards that dont support SSSE3 or SSE4.1, and that is causing them to crash when rendering, lots of stuff, such as planets.

Graphics cards don't have SSEX, it's the CPU's, so that has nothing to do with it.

It's a hardware fault, maybe none of the other games has stressed enough your rig, do as JimmiG said and do a stress test for at least 4 hours, also try to update all the drivers on your computer.

[Gromit]

Originally posted by El Dr. Gusman:

Originally posted by Snuggles:

yeah do you also get it while, exploring planets, and not in space or anything? I dont get bsods in even battlefield 4, so my hardware isnt faulty, im guessing, that the game isnt fully optimised for cards that dont support SSSE3 or SSE4.1, and that is causing them to crash when rendering, lots of stuff, such as planets.

Graphics cards don't have SSEX, it's the CPU's, so that has nothing to do with it.

It's a hardware fault, maybe none of the other games has stressed enough your rig, do as JimmiG said and do a stress test for at least 4 hours, also try to update all the drivers on your computer.

Seems dificult to believe, that this bsod happens in this game within 30 mins of playing, with all temps appsoultly fine, but not at battlefield 4 maxed out, for hours and hours.

[El Dr. Gusman]

Well, belive it, you don't know which instruction set uses one or the other, so you can't ensure those games use the defective hardware (if there is one).

NMS uses OpenGL 4.5, Battlefield 4 uses DirectX 11, so it's a big difference, also BF4 doesn't require SSE4 so it's another difference.

[Gromit]

Originally posted by El Dr. Gusman:

Well, belive it, you don't know which instruction set uses one or the other, so you can't ensure those games use the defective hardware (if there is one).

NMS uses OpenGL 4.5, Battlefield 4 uses DirectX 11, so it's a big difference, also BF4 doesn't require SSE4 so it's another difference.

wouldnt it crash straight away then? it only happems when im exploring planets, not at all when im in space, wouldnt this suggest the game is just not optimised for AMD cards yet?

[El Dr. Gusman]

Nope, it can be perfectly a thermal issue, when your GPU gets too hot some instructions may fail and thus it will crash only after some use. Also it can be because the concrete instruction causing the crash is only used by some concrete shaders, or you have some VRAM damaged and until it's not filled it doesn't crash, etc etc etc.

[Gromit]

Originally posted by El Dr. Gusman:

Nope, it can be perfectly a thermal issue, when your GPU gets too hot some instructions may fail and thus it will crash only after some use. Also it can be because the concrete instruction causing the crash is only used by some concrete shaders, or you have some VRAM damaged and until it's not filled it doesn't crash, etc etc etc.

I was running with evga presision X16 on in the background, it keeps my temps below 50 all of the time, also in gta 5 and rainbow six seige, (i have an evga 970 btw) and those games show how much the options you change will affect VRAM usage, and i maxed those out to 3.5 gig, and nothing happened.

[El Dr. Gusman]

Ok, if you don't want to test it just don't do it, but that doesn't means you don't have a problem in your rig.

As I said there is a nearly-infinite "etc etc etc", so the problem can be anything else, unless you do a full stress test you will not know if there is a problem.

Also, I don't know that evga program, but 1-if it doesn't messes with the frequencies then it's impossible to keep 50º. 2-If that program messes up with frequencies then it can be the root of problems, not all the programs accept a frequency change on the fly, so it can cause a crash.

Did you checked the temp of your CPU, not your GPU? that problem is usually more tied to CPU's than GPU's.

And finally, upgrade ALL your drivers, it can be perfectly a driver issue.

[Gromit]

Originally posted by El Dr. Gusman:

Ok, if you don't want to test it just don't do it, but that doesn't means you don't have a problem in your rig.

As I said there is a nearly-infinite "etc etc etc", so the problem can be anything else, unless you do a full stress test you will not know if there is a problem.

Also, I don't know that evga program, but 1-if it doesn't messes with the frequencies then it's impossible to keep 50º. 2-If that program messes up with frequencies then it can be the root of problems, not all the programs accept a frequency change on the fly, so it can cause a crash.

Did you checked the temp of your CPU, not your GPU? that problem is usually more tied to CPU's than GPU's.

And finally, upgrade ALL your drivers, it can be perfectly a driver issue.

CPU never got higher than 55, what kinda drivers are we talkin about here

[El Dr. Gusman]

Mainboard, CPU, GPU, anything, unless you check the dump log and read which hardware device caused the crash, it can be any part of your computer.

[jamescorvett]

sounds like a video driver issue with older GTX and win10. are ALL your drivers up to date?
i heard their newest just released was causing crashing / BSOD's.

Im running it on a phenom ii x4 3.2Ghz quad core and a R280... runs like it should for 11 hours. Im running the experimental beta. wouldnt even load w/o it. lol