[Technical]Computer Freezes When Playing Warframe (Randomly)

[Syzodia]

So I just got a new computer: an HP Pavilion 15-ab257tx, which runs an i7-6500U @ 2.5GHz, 8GB RAM and an nvidia geforce 940M ( you can search that computer model online for more specs).

Essentially, the problem is that when I play warframe, at some point (random), everything will freeze, including the sound output (which'll stutter as is often typical of a BSOD, except no BSOD occurs); no "Display driver stopped responding" notification, no BSOD, no response to any input. The strange thing is that I only got this laptop yesterday, on which, iirc, warframe ran perfectly fine (and other games).

 

I have yet to fully diagnose what may be the primary cause, but my current hunch is the windows build I'm using. Factory defaults was running build 10240, but the problems seemed to have arisen after I installed the upgrade (which is now build 10586.36). I don't know if it's possible to rollback (or if I should).

 

I have tried verifying and optimising the cache, and i've tried all combinations of DX10/11, 64-bit mode, and multi-threaded rendering, none of which solved the problem. I've tried updating drivers, but only those recommended via hp support assistant; I'm reluctant to manually update others after attempting that on my audio controllers resulted in worse performance

 

A quick look at the EE.log seems to show the game runs normally, except the last line is truncated (not fully printed), as if the freeze was completely spontaneous.

 

In the event viewer, I sometimes (not always) see an error with warframe reported. The most recent looks like this:

Faulting application name: Warframe.x64.exe, version: 2015.12.17.17, time stamp: 0x567332cc

Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000

Exception code: 0xc0000005

Fault offset: 0x0000000200000303

Faulting process id: 0x234c

Faulting application start time: 0x01d140833a7928c8

Faulting module path: unknown

Report Id: 989f0ef4-fea4-401d-ac23-d63932edbbde

Faulting package full name: 

Faulting package-relative application ID:

 

Event ID: 1000, task category: (100)

And curiously, after booting, I see a series of DPTF errors (Intel Dynamic platform and thermal framework); dunno if this is relevant.

 

I still don't know what to do, but if anyone's gone through a similar ordeal and solved it, pls share the solution.

 

 

EDIT: Had this problem occur in another application. Looks like it's related to high load, but not sure what the trigger is.

Edited December 29, 2015 by Syzodia

[Rydian]

You seem to be pretty experienced so sorry if this seems basic, but I'd recommend running something like GPU-Z or another utility that can log temperatures and clock speeds over time to see if there's an increase in temps or a multiplier throttle or something that coincides with it.

[Syzodia]

You seem to be pretty experienced so sorry if this seems basic, but I'd recommend running something like GPU-Z or another utility that can log temperatures and clock speeds over time to see if there's an increase in temps or a multiplier throttle or something that coincides with it.

Ah, forgot to mention temps. GPU will at most hit below 60 celcius, the cores usually around 47; way cooler than my previous system

[Rydian]

Is it just Warframe that does this, as in other things continue to respond?

[LifeNine]

I did a quick search on what Intel Dynamic platform and thermal framework is, and it turns out this should be controlling the CPU such that you computer is dissipating heat at some specific rate. If your getting errors from it, then it could be that the program is not working properly or those errors are telling you that your computer is getting too hot or something.

 

From what I've read, it should shut down your computer if it detects that your laptop is getting too hot. Maybe that is what's happening. If your laptop doesn't feel hot, then maybe there is something wrong with your version of Intel Dynamic platform and thermal framework. You can try updating the driver and see if the problem continues.

 

Drivers for your laptop should be here: http://support.hp.com/au-en/drivers/selfservice/HP-Pavilion-15-Notebook-PC-series/8499306/model/8960443

the Intel Dynamic platform and thermal framework driver is under Driver-Chipset.

 

If you decide to try updating the driver, make sure to create a save point first in case anything goes wrong. Also back up important files if you're truly worried about loosing them.

[Syzodia]

Is it just Warframe that does this, as in other things continue to respond?

Yes. The closest I got to this were some hitches while playing Borderlands 2, but that was because I was recording video; otherwise it ran perfectly fine. for hours.

 

I did a quick search on what Intel Dynamic platform and thermal framework is, and it turns out this should be controlling the CPU such that you computer is dissipating heat at some specific rate. If your getting errors from it, then it could be that the program is not working properly or those errors are telling you that your computer is getting too hot or something.

 

From what I've read, it should shut down your computer if it detects that your laptop is getting too hot. Maybe that is what's happening. If your laptop doesn't feel hot, then maybe there is something wrong with your version of Intel Dynamic platform and thermal framework. You can try updating the driver and see if the problem continues.

 

Drivers for your laptop should be here: http://support.hp.com/au-en/drivers/selfservice/HP-Pavilion-15-Notebook-PC-series/8499306/model/8960443

the Intel Dynamic platform and thermal framework driver is under Driver-Chipset.

 

If you decide to try updating the driver, make sure to create a save point first in case anything goes wrong. Also back up important files if you're truly worried about loosing them.

BL2 runs hotter than warframe, so I doubt this is gonna be the solution. Not only that, but my current version already matches one of those listed drivers. Not sure if I should get .150 rev A or rev B, should I do so.

 

Gonna try sending a support ticket then.

 

Edit: before I do, the problem doesn't seem to be happening anymore ._. not sure why yet...

edit2: it's back, and i don't know why.

Edited December 28, 2015 by Syzodia

[Smokinwaffles43]

Yes. The closest I got to this were some hitches while playing Borderlands 2, but that was because I was recording video; otherwise it ran perfectly fine. for hours.

 

BL2 runs hotter than warframe, so I doubt this is gonna be the solution. Not only that, but my current version already matches one of those listed drivers. Not sure if I should get .150 rev A or rev B, should I do so.

 

Gonna try sending a support ticket then.

 

Edit: before I do, the problem doesn't seem to be happening anymore ._. not sure why yet...

If this has happened only one other time and that was when you were recording, than its probably an issue of your computer getting overloaded.

 

 

So I just got a new computer: an HP Pavilion 15-ab257tx, which runs an i7-6500U @ 2.5GHz, 8GB RAM and an nvidia geforce 940M ( you can search that computer model online for more specs).

Essentially, the problem is that when I play warframe, at some point (random), everything will freeze, including the sound output (which'll stutter as is often typical of a BSOD, except no BSOD occurs); no "Display driver stopped responding" notification, no BSOD, no response to any input. The strange thing is that I only got this laptop yesterday, on which, iirc, warframe ran perfectly fine (and other games).

 

I have yet to fully diagnose what may be the primary cause, but my current hunch is the windows build I'm using. Factory defaults was running build 10240, but the problems seemed to have arisen after I installed the upgrade (which is now build 10586.36). I don't know if it's possible to rollback (or if I should).

 

I have tried verifying and optimising the cache, and i've tried all combinations of DX10/11, 64-bit mode, and multi-threaded rendering, none of which solved the problem. I've tried updating drivers, but only those recommended via hp support assistant; I'm reluctant to manually update others after attempting that on my audio controllers resulted in worse performance

 

A quick look at the EE.log seems to show the game runs normally, except the last line is truncated (not fully printed), as if the freeze was completely spontaneous.

 

In the event viewer, I sometimes (not always) see an error with warframe reported. The most recent looks like this:

Faulting application name: Warframe.x64.exe, version: 2015.12.17.17, time stamp: 0x567332cc

Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000

Exception code: 0xc0000005

Fault offset: 0x0000000200000303

Faulting process id: 0x234c

Faulting application start time: 0x01d140833a7928c8

Faulting module path: unknown

Report Id: 989f0ef4-fea4-401d-ac23-d63932edbbde

Faulting package full name: 

Faulting package-relative application ID:

 

Event ID: 1000, task category: (100)

And curiously, after booting, I see a series of DPTF errors (Intel Dynamic platform and thermal framework); dunno if this is relevant.

 

I still don't know what to do, but if anyone's gone through a similar ordeal and solved it, pls share the solution.

 

Here you say you have an nvidia geforce. I may recommend turning down physx if you haven't already. All of those particles can really cause hiccups.

[Syzodia]

If this has happened only one other time and that was when you were recording, than its probably an issue of your computer getting overloaded.

 

Here you say you have an nvidia geforce. I may recommend turning down physx if you haven't already. All of those particles can really cause hiccups.

I don't think you understand; that other scenario was a different problem which exhibited similar symptoms (audio hiccups, stuttering, etc). I'm well aware that would be due to thermal throttling. This situation, however, the whole computer just freezes and locks up spontaneously, and doesn't run nearly as hot, but it has only occurred while playing warframe.

 

Also, PhysX is only usable in 64-bit mode. As mentioned in OP:

I have tried verifying and optimising the cache, and i've tried all combinations of DX10/11, 64-bit mode, and multi-threaded rendering, none of which solved the problem

[DaganEldr]

I don't think you understand; that other scenario was a different problem which exhibited similar symptoms (audio hiccups, stuttering, etc). I'm well aware that would be due to thermal throttling. This situation, however, the whole computer just freezes and locks up spontaneously, and doesn't run nearly as hot, but it has only occurred while playing warframe.

 

Also, PhysX is only usable in 64-bit mode. As mentioned in OP:

Hmm... You probably know a bit more than me, but have you tried messing around with your in-game graphics settings? In some places (and on some warframe skills) right now, while someone was testing (that I kindly keep anonymous), it was noticed that PhysX memory ran out and caused a similar freeze.

 

Honestly, this is one of those instances that sounds like support ticket time with the .ee log attached. That might hint more at the underlying problem. Wish I could help more, but that's the best I have with what I know. >.< Sorry.

[Syzodia]

So, maybe it's too early to call it, i dunno.

 

But I decided to rollback my windows 10 build to 10240, and here's what happened:

 

- While playing distance, I got a similar computer freeze, except audio ran normally. It recovered in a few seconds

- Later on, I got a more heavy freeze, similar to OP (glitched audio and whatnot), but it recovered a second later.

- Then played warframe, for one hour straight, and no freezes.

 

I think it's fixed. Although apparently having antivirus can interfere with the windows upgrade process; that may have been why my upgrade had this problem as this computer came with mcafee pre-installed. I have it uninstalled now, and running 10240, just fine (?)

 

Will mark this as solved after further testing.

[Rydian]

If I was you, I'd...

 

1 - Make a new partition.

2 - Back up stuff there.

3 - Grab the Windows 10 media creation tool and use it to make a USB or optical install disc.

https://www.microsoft.com/en-us/software-download/windows10

And do a clean install and then allow things to upgrade to the current buid.

 

Windows 10 should reactivate itself once online since you currently have a licensed copy for that machine and Microsoft keeps a record of that now to sidestep license key issues for reinstalls according to that (and other sources you could find if you're not sure).

 

If this is a lot of work you don't have to do it, but if I was in your situation it's what I would do.  Windows may have had a lot of changes in policies and all that jazz over time, but prebuilts are still pulling the same crap and a fresh install with unmodified media can work wonders.

[Syzodia]

If I was you, I'd...

 

1 - Make a new partition.

2 - Back up stuff there.

3 - Grab the Windows 10 media creation tool and use it to make a USB or optical install disc.

https://www.microsoft.com/en-us/software-download/windows10

And do a clean install and then allow things to upgrade to the current buid.

 

Windows 10 should reactivate itself once online since you currently have a licensed copy for that machine and Microsoft keeps a record of that now to sidestep license key issues for reinstalls according to that (and other sources you could find if you're not sure).

 

If this is a lot of work you don't have to do it, but if I was in your situation it's what I would do.  Windows may have had a lot of changes in policies and all that jazz over time, but prebuilts are still pulling the same crap and a fresh install with unmodified media can work wonders.

Wouldn't that render my warranty void? (I'm honestly not sure but I believe any form of partitioning does render it void)

 

Also....another update: same problem occurred on build 10240. That and I have other unrelated problems now.

ugh. At this rate I might have to claim warranty...so soon.

[Rydian]

Partitioning is a logical/software change, I'm not aware of any laptop warranty voided by it.