Re: Need for Speed 2016 Directx error and low fps and stutter issues.

@master2g

Okay good, let us know if the defrag helps. Just so you know, some defrag programs are better than others. Some will just mash all of your files together, getting rid of the space between them while the better ones will actually rearrange the files so that related files are physically (not just logically) placed beside each other. I cannot name specific products but a little Googling should help in this regard.

😕 Well im out of ideas. It is ether game or connection as every thing else has been tried. I used MyD on the hard drive, optimized it , and every thing. Installed the new 378.92 drivers and even went into my modems on line settings and made sure EA tunnel was in there and everything. I am in Canada and use Rogers high speed. Test give me 90Mbps . Connection doesn't make sense as the game is problematic in the same spots every time. I give up as there isn't anything left to try to my knowledge.

The game crashed again. Here are the Windows 7 event viewers logs. No particular order.

NFS crashes then Origin follows .

Log Name:      Application
Source:        Application Error
Date:          3/28/2017 4:51:34 PM
Event ID:      1000
Task Category: (100)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      Gary-PC
Description:
Faulting application name: Origin.exe, version: 10.4.6.33873, time stamp: 0x58d57545
Faulting module name: libGLESv2.dll, version: 0.0.0.0, time stamp: 0x58d3ec76
Exception code: 0xc0000005
Fault offset: 0x0011eaa9
Faulting process id: 0x12c0
Faulting application start time: 0x01d2a7fb6495c4b8
Faulting application path: E:\Program Files (x86)\Origin\Origin.exe
Faulting module path: E:\Program Files (x86)\Origin\libGLESv2.dll
Report Id: f1d8e520-13ef-11e7-b995-40167e230164
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Application Error" />
    <EventID Qualifiers="0">1000</EventID>
    <Level>2</Level>
    <Task>100</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2017-03-28T19:51:34.000000000Z" />
    <EventRecordID>130636</EventRecordID>
    <Channel>Application</Channel>
    <Computer>Gary-PC</Computer>
    <Security />
  </System>
  <EventData>
    <Data>Origin.exe</Data>
    <Data>10.4.6.33873</Data>
    <Data>58d57545</Data>
    <Data>libGLESv2.dll</Data>
    <Data>0.0.0.0</Data>
    <Data>58d3ec76</Data>
    <Data>c0000005</Data>
    <Data>0011eaa9</Data>
    <Data>12c0</Data>
    <Data>01d2a7fb6495c4b8</Data>
    <Data>E:\Program Files (x86)\Origin\Origin.exe</Data>
    <Data>E:\Program Files (x86)\Origin\libGLESv2.dll</Data>
    <Data>f1d8e520-13ef-11e7-b995-40167e230164</Data>
  </EventData>
</Event>

Here is the one for NFS 2016 -

Log Name:      Application
Source:        Application Error
Date:          3/28/2017 2:41:16 PM
Event ID:      1000
Task Category: (100)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      Gary-PC
Description:
Faulting application name: NFS16.exe, version: 1.0.0.0, time stamp: 0x57155d11
Faulting module name: NFS16.exe, version: 1.0.0.0, time stamp: 0x57155d11
Exception code: 0xc0000005
Fault offset: 0x000000000352836e
Faulting process id: 0x1224
Faulting application start time: 0x01d2a7de16139fc9
Faulting application path: E:\Program Files (x86)\Origin Games\Need for Speed\NFS16.exe
Faulting module path: E:\Program Files (x86)\Origin Games\Need for Speed\NFS16.exe
Report Id: be1ef274-13dd-11e7-ab6a-40167e230164
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Application Error" />
    <EventID Qualifiers="0">1000</EventID>
    <Level>2</Level>
    <Task>100</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2017-03-28T17:41:16.000000000Z" />
    <EventRecordID>130578</EventRecordID>
    <Channel>Application</Channel>
    <Computer>Gary-PC</Computer>
    <Security />
  </System>
  <EventData>
    <Data>NFS16.exe</Data>
    <Data>1.0.0.0</Data>
    <Data>57155d11</Data>
    <Data>NFS16.exe</Data>
    <Data>1.0.0.0</Data>
    <Data>57155d11</Data>
    <Data>c0000005</Data>
    <Data>000000000352836e</Data>
    <Data>1224</Data>
    <Data>01d2a7de16139fc9</Data>
    <Data>E:\Program Files (x86)\Origin Games\Need for Speed\NFS16.exe</Data>
    <Data>E:\Program Files (x86)\Origin Games\Need for Speed\NFS16.exe</Data>
    <Data>be1ef274-13dd-11e7-ab6a-40167e230164</Data>
  </EventData>
</Event>

Can give you a dxdiag upload as well if needed.

Like i said this is going to be a extremely hard fix . I am going to say big enough that we cant spend forever on it as you dont have that much time . Time to call in NASA.

Just to add bud,  i did a hard drive benchmark to get a reasonable idea where my games hard drive is at in performance. Here are the results . Thought maybe those areas i am having the low fps and stuttering are results of low HD speeds so i ran the test .

@master2g

Possible factors:

• Relatively low hard drive random access speed
• An issue with libGLESv2.dll - potentially fixed by an Origin clean reinstall: Link
• Origin not installed on C:\

Thanks for hanging in there with me bud. I owe you a few beer....er i mean sugar free soda because insinuating beer drinking on the forum would be just wrong, an i would never do that . :P Bad Gary bad !!

Those are good ideas so im going to run through them. Figure i will check them and related items as well like cables and such . Give me a few my friend to run through them and i will report back asap.

Reinstalled Origin , nothing fixed . I have Origin and Origin Games on my e drive that is my WD Black 1 tb drive. Actually every thing game wise is installed on that drive. Steam and all those games as well. The game runs some what better but now it wants to crash once or twice then works from there. I will play it and even if im sitting parked the game will just crash with in a 30m mark give or take. So I run it again and it crashes once more then oddly it works decent from there. So one problem partially fixed and another replaces it. It ether a windows 7 deep issue or the game/origin itself. I have gone thought everything on my system and this is the only game the gives me grief. It just doesn't like my gtx 1080 .Every other game , even NFS most wanted 2012 run all day long even on a higher over clock at that. Im dont friggen with NFS 2016 anymore . I cant prove it 100% but everything is pointing to a buggy game. Its been a majorly huge pain in the butt having to spend this much time on  game just to try and make it work. Anyways thanks a ton for the help my friend but i am moving on as i have run out of patience. ☹️

@master2g

You are welcome, sorry I could not do more for you.

No apology needed you helped plenty my friend. Look, I wouldn't want your job as you are the " middle man " fielding and having to deal with angry rants , insults and the rest of the **** comments that comes directed towards EA not you. Its like the gas station attended getting crapped on for high gas prices. You just work there it is not like you run the company and they listen to your decisions anyways  :P   You dont have to comment LOL on that statement as i know you need your job . Anyways i didn't abandon it right after i posted and tried a few things that wasn't really a go to solution. I redid my CPU over clock to a higher but even more safe over clock with finer detail. I worked on getting my 1080 and 4770k running in perfect "harmony"  by tweaking everything to the finest of numbers and it seems to have help all games across the board even NFS 2016. It still dips but not as bad and the stuttering has been reduced a good amount to. I am old enough to have learned by now to take 90 percent good and live with 10 percent bad . Asking for 100 % perfection in anything is just asking for a long painful road to acceptance of 90% in the end anyways  LOL. Anyways thanks again bud and have a good one and game hard always . :eahigh_file: