Re: Battlefield 4 keeps crashing on PC

by EA_Bastian
Reply

Original Post

Battlefield 4 keeps crashing on PC [Jan 9]

[ Edited ]
★★★★★ Apprentice

I've been playing for about 3 hours and the game launches smooth, runs fantastic, but after 3 or 4 games it will crash. The audio will loop (sometimes) and the video will freeze. There doesn't seem to be any reason for it in game. Getting real sick of doing something important and watching it freeze up and die on me. What's going on?

 

Running Windows 7. Everything is up to date. I shouldn't be having any problems.

 

Edit: It appears I'm far from alone: http://battlelog.battlefield.com/bf4/forum/threadview/2955065217450058306/

Lots of posts like this over on the battlelog forums.

 

Edit 2: Wow, just got home. This is a 60 page thread now as of 9PM EST on 10/31

I just wanted to thank everyone for posting here. Hopefully this gets the message across that this is an urgent issue.

 

Users who want to help in this thread, please post your hardware specs. You can open your start menu on Windows and type in dxdiag and paste the relevant info. To reduce clutter on this thread, paste your info in a spoiler tag.  Click the 5th icon over on the toolbar when you make a post.

Spoiler
Like so.

I urge all of you who know people who are having this issue to have them get on this website to post here so we can make some noise.

If I have time later I will post another edit here. Things the community has tried to resolve this issue so we don't need to keep discussing the same fixes that don't work. No longer necessary thanks to EANils

 

Click the spoiler to see previous updates: 

Spoiler

 Edit 3: ...92 pages, still going through them right now. Getting close to 1000 replies in this topic. 11/1 @ 9:02PM EST

                                                                                                                                                                                                                                                                                   

UPDATE 1: The only official update on this problem so far can be read about here: http://battlelog.battlefield.com/bf4/news/view/b4-stability-updat/

 

UPDATE 2: Thanks to iamtaracei for posting on Page 78 with this linkSounds like we'll be waiting for a patch after November 7th?!

 

UPDATE 3: I saw a post somewhere on this thread mentioning the following. (I just saw it on Battlelog now [11/1 @ 11pm EST])

Check Battlelog. It shows this message underneath the Soldier/Multiplayer/etc tabs. Looks like you have to be on the main page to see it:

We will start rolling out new game servers to address stability issues. The deploy will start at 8:00 CET. While servers are updated you might be disconnected from your current game. 

 

UPDATE 4 (via DICE): Known Battlefield 4 Issues and Next Steps 

 

UPDATE 5: Another post on Battlelog as of 11/3 @ 12pm EST:

We have identified an issue where the game server will crash and disconnect players. We have a fix in progress. We are rolling out a PC fix for the join queue. 

 

Update 6 (via EANils): For now, do not use the M320 (LVG and FB), as some players have noted that they are causing crashes. 

 

Update 7 (via DICE):  We just rolled out a new server update (R7) for Battlefield 4 that should fix some of the most common server crashes across all platforms. Let us know if this patch improves server stability for you. For everyone interested in some of the tweaks we are working on for Battlefield 4, just head to this forum post for the latest details. Keep the feedback coming! We are listening.

 

Update 8 (via DICE): R8 Server Update in the Works 
We are working hard to deliver the next server update as quickly as possible to improve stability. 

Client Update in the Works 
We are also working on upcoming client patches for Battlefield 4 on all platforms. These will contain fixes for crashes and address a number of other issues that you have been feedbacking to us. Patch notes will be posted as we get closer to releasing these updates. 

 

Update 9 (via DICE): Server Update R8 rolling out 
We recently deployed the R8 Server Update. It should be propagating throughout servers in the upcoming hours. You can find the change notes below. 

R8 Update Notes: 
*Fixed a number of dog tags that were showing up as blank in-game. 
*Lowered the damage caused by Mobile AA Active Radar missiles to aircraft. The previous damage was incorrectly set too high. 
*Improved server crash reporting and performance tracking on all platforms. This should further help us identify and fix server crashes going forward. 

 

Update 10 (via DICE): Client patch (PC) 

The PC client patch for Battlefield 4 will go live in the near future and fixes a number of different issues you have helped us to identify, including a number of the most common crashes and freezes. We will get back to you with a full fix list and a specific date for this update soon. 

Maintenance downtime (All platforms) 
Nov 13, we have a planned maintenance starting at 9AM UTC/1AM PST. The maintenance will last for 2-3 hours and multiplayer for Battlefield 4 will be unavailable on all platforms in increments during this window. This maintenance is done in preparation for the upcoming client patches. 

Console Server Update (PS3/X360) 
During the Nov 13 maintenance window mentioned above, we will roll out the latest server update for X360 and PS3. This server update will include the following fixes: 
• Temporarily disabled the ”Indirect Fire” and ”Perimeter Defense” Field Upgrades on PS3 as they caused the game to crash when spawning. This is a temporary workaround while we work to solve the issue altogether. 
• Fixed a number of dog tags that were showing up as blank in-game. 
• Lowered the damage caused by Mobile AA Active Radar missiles to aircraft. The previous damage was incorrectly set too high. 
• Improved server crash reporting and performance tracking on all platforms. This should further help us identify and fix server crashes going forward. 

Upcoming console client patches (PS3/X360) 
We are testing and finalizing upcoming client patches for PS3 and X360. We will be able to give you an ETA on these at a later date. You can always find the latest info in this thread. 

Upcoming Live Scoreboard (PC) 
We will introduce Live Scoreboards in the PC server browser on Battlelog in the upcoming days. It will let you see the current status in the ongoing round on a server before you join, such as the number of remaining targets in a round of Obliteration. We will be able to give you specific date on this feature soon.  

 Edit (via EANils): List of a couple of fixes that were provided by fellow players. These are in no way solutions to every issue out there, but you may want to give these a try in the meantime:  http://answers.ea.com/t5/Battlefield-4/Battlefield-4-keeps-crashing-on-PC/m-p/1768465#M31273 

For now, do not use the M320 (LVG and FB), as some players have noted that they are causing crashes.  

 

Spoiler

Update 11 (via DICE): PC client patch will be rolled out tomorrow at 10AM UTC/2AM PST. There will be a 1 hour PC downtime.


From Battlelog:

We are happy to report that the PC Battlefield 4 game update will go live tomorrow, November 14. The main focus of this update is threefold: 

1) Reduce the number of crashes 
We believe this update will solve a large portion of the most commonly occuring game crashes, and the improvement in overall stability should make a big difference for many players. 

2) Eliminate a network sync bug 
If you’ve been experiencing situations in multiplayer where it appears that you are taking damage from enemies through walls, you might have been the victim of a network sync bug. In this game update, we have identified and eliminated one such bug that caused this type of gameplay experience. We are continuing to work on more multiplayer optimizations concerning network performance. 

3) Improve Network Smoothing
 
We have made some improvements to the ”Network Smoothing” functionality that you can find in the OPTIONS>GAMEPLAY menu. The Network Smoothing slider governs a group of settings that aim to produce a tighter multiplayer experience based on your specific packet loss situation. 

If you’ve been experimenting with the Network Smoothing slider earlier, it might now yield better results. If you haven’t tried it before, please explore this setting and set it to the lowest value you can without experiencing graphical glitches in the game. By setting it lower, you can get a tighter multiplayer experience, depending on your specific network situation. 

More details upcoming 
Besides the above mentioned focus areas, this PC game update contains a number of other fixes and tweaks that we will detail once it’s live. 

This game update for PC goes live around 10AM UTC/2AM PST November 14. Your Origin Client should acknowledge and automatically download this update for you, as usual. Otherwise, you can right click your game in the client and select ”Check for Update”. There will be a Battlelog maintenance downtime for about an hour as this update goes live. During this time multiplayer on PC will be unavailable. 

We will release full patch notes for this game update later, but the three items mentioned above are by far the most important changes in this update. We understand that stability has been rocky for some players, and hope that this update will make the game run smoother and more stable for you.

UPDATE 12 (via DICE): PC game update is now live! 

Details on what the patch includes will be posted in a couple of hours. 

 

UPDATE 13 (via DICE): Server Update R10 rolling out 
We are seeing a lot of server crashes at the moment. These are being solved by rolling out a new server patch on PC (Server Update R10). It will take a few hours for this new server version to propagate, but it should be with most servers in a matter of a couple of hours. If you are getting error messages referring to the China Rising expansion pack when trying to join a multiplayer server, please try another server. This error will only appear if a server has not yet updated from server version R9 to R10. 

 

Update 14 (via DICE): PC Client Patch Notes 

NOVEMBER 14 PC GAME UPDATE PATCH NOTES 
In the November 14 PC game update, we fixed a number of issues that we have been seeing in the game. The main focus in this update is on crash fixes, and you can find a detailed list of the fixes below. We will continue our efforts to eliminate issues we find in the game, so stay tuned for more updates. Let us know how this update works for you. 


CRASHES & FREEZES 
-Fixed a crash that would occur randomly during gameplay. 
-Fixed a crash that would occur when an object is destroyed. 
-Every time that a player exited a vehicle, there was a small chance that the server would crash. This has been fixed. 
-Fixed an occasional crash during SP gameplay. 
-Fixed a crash that would occur during level loading. 
-Sometimes the game would attempt to load a model at the same time as it was being thrown out of memory. This has been fixed. 
-Sometimes the game would crash after removing old bullet holes/scratch marks in the world. This has been fixed. 
-Sometimes when a player or enemy was sitting in the jeep gunner entry and got killed, his body would rest on the vehicle in such a way that the physics simulation would require lots of CPU usage. This has been solved. 
-Fixed a crash occurring on Flood Zone when playing Conquest Large. 
-Fixed a common crash relating to surface shaders. 
-Fixed a crash on Test Range that could occur when using sniper rifles. 
-Fixed a common crash that occurred during map transition. 
-Fixed a crash that occurred when bringing up Battlescreen in-game on the Test Range. 
-Fixed a memory allocation bug that could lead to crashing. 
-Fixed a single player crash that could sometimes occur when being killed by AI enemies. 
-Fixed an issue where the game would get stuck in infinite loading if you got disconnected while trying to access online content. 
-Fixed an issue in single player in the South China Sea mission where the game would crash when idle for more than 60 minutes. 
-Fixed an issue where the game would get stuck in infinite loading if you used Win+L to lock your PC during loading. 

NETWORK PERFORMANCE 
Eliminated a network sync bug 
If you’ve been experiencing situations in multiplayer where it appears that you are taking damage from enemies through walls, you might have been the victim of a network sync bug. In this game update, we have identified and eliminated one such bug that caused this type of gameplay experience. We are continuing to work on more multiplayer optimizations concerning network performance. 

Improved Network Smoothing 
We have made some improvements to the ”Network Smoothing” functionality that you can find in the OPTIONS>GAMEPLAY menu. The Network Smoothing slider governs a group of settings that aim to produce a tighter multiplayer experience based on your specific packet loss situation. 

Removed network lag 
In certain specific situations, network lag would be introduced when interacting with objects in the game. This has been experienced by some players during melee combat, when climbing ladders, and when operating stationary weapons. The cause for these specific network lag situations has been solved. 

GAMEPLAY BALANCING 
-Removed the scout helicopter at the final base for the defenders in Rush mode on Siege of Shanghai 
-Adjusted a Conquest flag position on Zavod 311 that was obstructing vehicles. 
-At Hainan Resort in Rush mode, defenders were given too much armor at the first base. We have removed the defender IFV at the first base, added an attacker IFV at the first base, and increased the spawn delay on the defender IFV at the third base. 
-Fixed so that there is 1 revive per round Defuse, as opposed to 1 per set. 
-Removed all previously placed C4 and mines after a round of Defuse to eliminate the possibility to affect the next round. 

GRAPHICS 
-Fixed a minor graphical error on Operation Locker. 
-Fixed an issue where the in-game Battlelog would get distorted when a Commander launched an EMP attack. 
-Fixed a floating container on Golmud Railway near flag C in Domination. 
-Fixed an issue with the minimap in Rush mode. 
-Fixed an issue in Obliteration mode where the red light flash and beep sound was not played when the bomb carrier was moving. 
-Fixed an issue in Defuse where the bomb model sometimes did not display on the bomb carrier. 
-Fixed minor graphical alignment issues in the Spectator Mode camera layout. 
-Fixed an issue in Spectator Mode where the spectator's view incorrectly would get distorted during an EMP deployment from a Commander. 

MISCELLANEOUS 
-Fixed a bug that occasionally killed all sounds on the server if you fired the QBU-88 with an attached silencer. 
-Fixed the issue where pressing B would bring up the console. 
-Fixed an issue where the EMP effect lasted for too long on soldiers. 
-Fixed an issue with an area you couldn't traverse near one of the M-COM stations in Rush mode on Siege of Shanghai. 
-Fixed an issue relating to player skill levels. -Fixed an issue in Obliteration mode where the bomb would temporarily be placed in the sky after the bomb carrier was killed when swimming or in a water-based vehicle. 
-Fixed an occasional jitter in the kill camera. 
-Fixed so that Russian special characters are displayed properly in the chat window. 
-Fixed so that the System Performance Test option is working as expected. 
-Fixed a bug where a rank-up message would loop in-game 
-Moved a machine gun position on Lancang Dam that was placed on top of a building that can collapse. 
-Added sound when navigating the scoreboard in the End of Round screen. 
-Fixed a broken ladder in Siege of Shanghai. 
-Adjusted vehicle spawn locations on Dawnbreaker in Conquest mode to alleviate traffic jam. 
-Fixed a flickering-issue on Siege of Shanghai when using NVidia drivers 331.52. 
-Fixed a bug on Golmud Railway where a destroyed house at flag A would block gunfire. 
-Fixed a Ticket count issue in Rush mode. 
-Commanders can no longer erroneously try to get match-made into a game of Domination. 
-If the user restarts checkpoint during the End Scene , he will receive an old objective along with the credits. 
-Fixed a destruction issue on Flood Zone. 
-Fixed a Rhib boat issue in one of the single player missions. 
-Fixed an issue where players would respawn after getting killed and have no main weapon available. 
-Fixed so you won't see the emblem of a user that you have blocked. 
-Fixed an issue where you couldn't smash through the railings with a quad bike on the Dawnbreaker map. 
-Added clickable buttons to the in-game Battlelog. 
-Fixed a bug in single player where the player is killed if he climbs after Irish too fast up the ladder in one of the missions. 
-Various other minor issues. 

 

Update 15 (via Dice): PC GAME UPDATE 
We have a new game update in the works for BF4 on PC aimed at fixing a number of remaining issues in the game. We will have more details on the contens of this update and a rough timing estimate at a later date. You can always find the latest information on upcoming updates in this thread.

 

Update 16 (via DICE): PC Server Update R11 Rolling Out 
We are roling out a new server update on PC with some minor tweaks and a crash fix. Full change list below. We are also aiming to have a new PC game update live next week. Stay tuned for more on that. 

R11 PC SERVER UPDATE CHANGE LIST 

  • Fixed a common server crash 
  • Fixed an exploit where a player could get unlimited ammo on mortars by redeploying them 
  • Fixed an issue where your score displayed in the scoreboard was cut in half during double xp events 
  • Removed the possibility for server admins to kick players on official servers by using PunkBuster 
  • Game mode counter can now be set up to 400% for Ranked servers and 500% for Unranked servers. In addition, idle time out can now be set up to 86 400 (24 hours) for both server types 

Update 17 (via DICE) - R12 Server Update Notes 

  • Fixed several of the most commonly occuring server crashes (This should benefit all platforms) 
  • Fixed an issue where the cruise missile in Commander Mode was not launching when playing on Paracel Storm (in Obliteration mode) 
  • Fixed so that a player's skill is no longer negatively affected when playing as Commander 
  • Fixed an aircraft IR flares exploit where players could use the flares multiple times before reloading by exiting/re-entering the aircraft 
  • Fixed an issue with Ranked servers on Xbox One running with a 1% ticket count 
  • Defined a range of 25-400% for vehicle respawn delays on Ranked servers

 

Update 18 (via DICE) - Next PC Game Update Patch Notes (Date TBC) 

We are verifying the upcoming PC patch and making sure it is good to go. We are aiming to get this patch out the week of Dec 2. Right now, we don’t have a set date for it, but here’s what it will include. Stay tuned for more updates in the Battlefield 4 Control Room. 

 

PC Game Update Notes  

  • Removed the blur effect on soldiers that appeared when Commanders were using EMP attacks 
  • Fixed the audio bug where audio sometimes randomly dropped out while playing on certain multiplayer maps (typically Golmud Railway and Hainan Resort) 
  • Fixed the "one-hit kill bug" where occasionally damage from a single bullet was applied multiple times 
  • Fixed a common crash that would occur when exiting from the Single Player Campaign to Main Menu 
  • Tweaked the network and computer performance screen to show proper values. Players can now test their computer and network connection and get recommendations if they need to adjust something to improve their gameplay experience.

 

Update #20 (Dec 2) - PC Game Update

 PC: The upcoming PC game update will launch December 3, to coincide with the launch of the expansion pack Battlefield 4 China Rising for Premium members on all platforms.

 

The game update will start to roll out at 1AM PST/10AM UTC Dec 3, followed by the actual China Rising content around 2AM PST/11AM UTC. You can expect some downtime around these times as servers are being prepared to support this new content.

 

The change list for this PC game update is the same as previously announced (see below.)

 

As ususal, we will continue to iterate on stability and tweak the game based on your feedback. Stay tuned.

 

PC Game Update Notes 

  •  Removed the blur effect on soldiers that appeared when Commanders were using EMP attacks 
  • Fixed the audio bug where audio sometimes randomly dropped out while playing on certain multiplayer maps (typically Golmud Railway and Hainan Resort) 
  • Fixed the "one-hit kill bug" where occasionally damage from a single bullet was applied multiple times 
  • Fixed a common crash that would occur when exiting from the Single Player Campaign to Main Menu 
  • Tweaked the network and computer performance screen to show proper values. Players can now test their computer and network connection and get recommendations if they need to adjust something to improve their gameplay experience.

Update #21 (Dec 9) - R15 Server Update Notes 

  • Various server side crash fixes, including the top seen crashes on R14 
  • Activated the reservedSlotsList.aggressiveJoin command that enables VIP players and server administrators directly joining full servers 
  • Client patch compatibility to make servers compatible with the Dec 09 client update

 

Update #22 (Dec 9) - PC Game Update Notes

Shot behind cover when changing stance 

Sometimes the character stance could get into a multiple frame desync and be part of the problem where you got shot even though your character was actually behind cover. This would mostly affect players doing transitions into crouch and prone as well as moving when crouched. The impact was smaller in a standing stance. This bug fix eliminates this particular desync issue. 

We have also increased the camera height when crouching and moving to more accurately reflect the actual height of your soldier in that stance (the first person camera was too low when crouching and moving, resulting in that you had a poor representation of how much of your soldier that was actually out of cover.)

 

  • Fixed one of the most frequently occurring client crashes 
  • Fixed broken collision on containers with open doors. The bug previously made grenades bounce back even though the doors were open. 
  • Fixed a bug in Defuse mode where defenders could win the round by killing all the attackers without disarming the bomb, if the bomb was disarmed in the previous round. 
  • Miscellaneous stability fixes further reducing the number of client crashes 
  • Fixed side gunner jitter when aiming in attack boats & transport helicopters 
  • Fixed some instances of frame rate drops when shooting at large Levolution objects after they have been destroyed (like the radar dish on Rogue Transmission) 
  • Fixed broken aiming for passengers on the China Rising dirt bike 
  • Fixed a bug where the sound when capturing a flag was not playing correctly 
  • Removed a bug that would double save during MP round transition and SP level transition. This fix will reduce the occurrence of corrupted save files.

 Update #23 (Dec 10) - Top Issues Tracker

Check out the link to the new Top Issues Tracker for Battlefield 4 that DICE just implemented. 

  

Update #24 (Dec 16) - R16 Server Update Notes 

  • Fix for some of the more common server crashes 
  • Overall performance enhancements 
  • UCAV ammo replenish time was set from 20 to 90 seconds 
  • Round time limit intervals were added for the different server types

Update #25 (Dec 16) - PC Game Update Notes 

We’ve rolled out a new PC game update and will continue to make improvements based on your feedback. The update includes fixes with the aim to increase the general stability of the game, and eliminates bugs that you may have experienced. It also includes an improvement to the so called “Netcode”. 

 

UPDATE: We have noticed that players who have SLI enabled on their graphics card may experience graphical flickering. Also, we're looking into the issue where the revive bar would get stuck on-screen in some instances. Both of these have our attention, and we're investigating them.

 

  • Fix for a crash that would cause the game to stall, resulting in a sound loop. This should eliminate most of the problems relating to this. 
  • Fix for the SUAV (introduced in the China Rising expansion pack) not exploding when hitting enemy soldiers. While these indeed should be deadly, they were never designed for “roadkilling” opponents. 
  • Fixed one of the issues related to the so called “Netcode” (see below for details) 
  • Fix for player tags not always showing when needed to, resulting in players shooting team members. 
  • Fix for graphical flickering appearing on terrain. 
  • Fixed the instance where players suddenly would transition into Spectator Mode while playing the Defuse game mode. 
  • Fix for a Defuse bug where none of the teams would win a round by letting the timer run out. -Fix for players getting stuck in the revive screen after being killed. 
  • Fix for players getting stuck in the kill camera after being revived. 
  • Fix for the game mode specific ribbons being counted twice in the multiplayer progression. 
  • Made the NVidia 331.82 driver version mandatory for all players. 
  • Disabled DirectX 11.1 on NVidia cards that have outdated drivers. 
  • Fixed driver version not being properly detected on NVidia Optimus systems. 
  • Fixed a minor crash that could occur when bringing up the scoreboard. 
  • Fix for the issue where the game would get stuck in loading screen when players tried to join a Second Assault map without actually owning Second Assault. 

“Netcode” improvement 
We’ve addressed the so called “Kill trading”. This refers to when two players fire at each other and, seemingly, both die at the same time. The time window where a bullet could cause damage from an already dead player is now calculated as intended, decreasing the timeframe when players with high latency could get a kill, even though they should be dead according to the server

 

Update #26 (Dec 20) - R17 Server Update Notes 

Servers are updating to a new server version (R17)  throughout the day. 

  • Fix for two server crashes 
  • Fix for a graphical bug that could occur when players accepted a revive within 1 second 
  • Server performance optimizations

Update #27 (Dec 20) - PC Game Update Notes 

  • Fix for terrain flickering when using SLI/CrossFire setup 
  • Fix for three of the top crash issues on the PC platform 
  • Fix for case when soldier can die with 1 HP instead of 0 
  • Fix for the issue where the revive UI could be permanently shown after accepting a revive

If the game update doesn't start automatically for you, you can trigger it by going into the Origin Client, right clicking Battlefield 4 and selecting "Check for updates". Patch notes below. 

 

Update #28 (Jan 9) The Road Ahead 
Just a short note that we are finalizing the next game update for multiple platforms, aiming to release them later this month. Stay tuned for the full details in the Battlefield 4 Control Room.

 

Note: As always, you can find the latest info here: www.battlefield.com/bf4controlroom

Message 2 of 2,257 (173,559 Views)

freeze screen

★★★ Newbie

I have been trying to get into a server for a long time now and each time i try to join one i get to the point where battlelog is saying that i'm now playing on the server but in the screen it has frozen on the level loading screen, the sound is also frozen just repeating itself in a one second loop. i have only got into the game once and it froze straight away. is there a way arround this. also could you change your graphic settings out of game? thanks

Message 1 of 2,257 (140,678 Views)

Re: Battlefield 4 keeps crashing on PC

Community Manager (retired)

Could you please provide us some information about your system? It would help our community to find possible workarounds, if you could post your hardware specs as well as your Windows version and graphic driver built.

 

Cheers
Basti

Message 3 of 2,257 (172,651 Views)

Re: Battlefield 4 keeps crashing on PC

★★★ Novice

I'm having this same issue. It freezes after just a few minutes in every server I join. Hardlock with repeating audio that I have to go to the task manager to close.

 

I5 750

16GB DDR3 1600

GTX 680

Windows 8.1

Nvidia Driver Version 331.65

Message 4 of 2,257 (172,595 Views)

Re: Battlefield 4 keeps crashing on PC

[ Edited ]
★★★★★ Apprentice

Certainly. I'll post my dxdiag info.

 

 

Spoiler

------------------
System Information
------------------

Operating System: Windows 7 Home Premium 64-bit (6.1, Build 7601) Service Pack 1 (7601.win7sp1_gdr.130828-1532)
Language: English (Regional Setting: English)
BIOS: BIOS Date: 11/28/12 16:12:31 Ver: 04.06.05
Processor: Intel(R) Core(TM) i5-3570K CPU @ 3.40GHz (4 CPUs), ~3.4GHz
Memory: 8192MB RAM
Available OS Memory: 8076MB RAM
Page File: 2418MB used, 13730MB available
Windows Dir: C:\Windows
DirectX Version: DirectX 11
DX Setup Parameters: Not found
User DPI Setting: Using System DPI
System DPI Setting: 96 DPI (100 percent)
DWM DPI Scaling: Disabled
DxDiag Version: 6.01.7601.17514 32bit Unicode

 


---------------
Display Devices
---------------
Card name: NVIDIA GeForce GTX 670
Manufacturer: NVIDIA
Chip type: GeForce GTX 670
DAC type: Integrated RAMDAC
Device Key: Enum\PCI\VEN_10DE&DEV_1189&SUBSYS_26783842&REV_A1
Display Memory: 4038 MB
Dedicated Memory: 1990 MB
Shared Memory: 2048 MB
Current Mode: 1920 x 1080 (32 bit) (60Hz)
Monitor Name: BenQ GL2450 (Digital)
Monitor Model: BenQ GL2450
Monitor Id: BNQ78A5
Native Mode: 1920 x 1080(p) (60.000Hz)
Output Type: HDMI
Driver Name: nvd3dumx.dll,nvwgf2umx.dll,nvwgf2umx.dll,nvd3dum,nvwgf2um,nvwgf2um
Driver File Version: 9.18.0013.3165 (English)
Driver Version: 9.18.13.3165
DDI Version: 11
Driver Model: WDDM 1.1
Driver Attributes: Final Retail
Driver Date/Size: 10/23/2013 06:30:23, 18199872 bytes
WHQL Logo'd: Yes
WHQL Date Stamp:
Device Identifier: {D7B71E3E-52C9-11CF-AF57-75061CC2C435}
Vendor ID: 0x10DE
Device ID: 0x1189
SubSys ID: 0x26783842
Revision ID: 0x00A1
Driver Strong Name: oem40.inf:NVIDIA_SetA_Devices.NTamd64.6.1:Section089:9.18.13.3165Tongue outci\ven_10de&dev_1189
Rank Of Driver: 00E02001
Video Accel: ModeMPEG2_A ModeMPEG2_C ModeVC1_C ModeWMV9_C

 

Thanks. If you need any more info, I will provide it.

 

 

 

 

 

Message 5 of 2,257 (172,583 Views)

Re: Battlefield 4 keeps crashing on PC

★★★★★ Apprentice

Having the exact same issue.  Audio looping then freeze or the game will stop responding.

Message 6 of 2,257 (172,567 Views)

Re: Battlefield 4 keeps crashing on PC

[ Edited ]
★ Apprentice

Same problem here.

 

 

Spoiler

------------------
System Information
------------------
Operating System: Windows 8.1 Pro 64-bit (6.3, Build 9600) (9600.winblue_gdr.130913-2141)
Language: German (Regional Setting: German)
System Manufacturer: System manufacturer
System Model: System Product Name
BIOS: BIOS Date: 11/01/12 10:01:45 Ver: 36.02
Processor: Intel(R) Core(TM) i5-2500K CPU @ 3.30GHz (4 CPUs), ~3.3GHz
Memory: 16384MB RAM
Available OS Memory: 16352MB RAM
Page File: 3310MB used, 15472MB available
Windows Dir: C:\WINDOWS
DirectX Version: DirectX 11
DX Setup Parameters: Not found
User DPI Setting: Using System DPI
System DPI Setting: 96 DPI (100 percent)
DWM DPI Scaling: Disabled
DxDiag Version: 6.03.9600.16384 64bit Unicode

 

---------------
Display Devices
---------------
Card name: NVIDIA GeForce GTX 680
Manufacturer: NVIDIA
Chip type: GeForce GTX 680
DAC type: Integrated RAMDAC
Device Type: Full Device
Device Key: Enum\PCI\VEN_10DE&DEV_1180&SUBSYS_126019DA&REV_A1
Display Memory: 12172 MB
Dedicated Memory: 3996 MB
Shared Memory: 8175 MB
Current Mode: 1920 x 1080 (32 bit) (60Hz)
Monitor Name: SyncMaster B2430L (Digital)
Monitor Model: SMB2430L
Monitor Id: SAM0645
Native Mode: 1920 x 1080(p) (60.000Hz)
Output Type: DVI
Driver Name: nvd3dumx.dll,nvwgf2umx.dll,nvwgf2umx.dll,nvd3dum,nvwgf2um,nvwgf2um
Driver File Version: 9.18.0013.3165 (English)
Driver Version: 9.18.13.3165
DDI Version: 11
Feature Levels: 11.0,10.1,10.0,9.3,9.2,9.1
Driver Model: WDDM 1.3
Graphics Preemption: DMA
Compute Preemption: DMA
Miracast: Not Supported
Hybrid Graphics GPU: Not Supported
Power P-states: Not Supported
Driver Attributes: Final Retail
Driver Date/Size: 10/23/2013 11:30:23, 18199872 bytes
WHQL Logo'd: Yes
WHQL Date Stamp:

 

 

 

Message 7 of 2,257 (172,561 Views)

Re: Battlefield 4 keeps crashing on PC

[ Edited ]
★ Guide

Same problem here. It happens in multi and test range. Tried a fresh install of vid card drivers, repaired game, and even setting game priority to high. All 4 CPU's are being utilized and the game runs smooth otherwise.

 

Spoiler
------------------
System Information
------------------
Time of this report: 10/29/2013, 13:39:51
       Machine name: CHRONOS
   Operating System: Windows 7 Home Premium 64-bit (6.1, Build 7601) Service Pack 1 (7601.win7sp1_gdr.120503-2030)
           Language: English (Regional Setting: English)
System Manufacturer: Gigabyte Technology Co., Ltd.
       System Model: GA-970A-D3
               BIOS: Award Modular BIOS v6.00PG
          Processor: AMD FX(tm)-4100 Quad-Core Processor             (4 CPUs), ~3.6GHz
             Memory: 8192MB RAM
Available OS Memory: 8190MB RAM
          Page File: 2611MB used, 13765MB available
        Windows Dir: C:\Windows
    DirectX Version: DirectX 11
DX Setup Parameters: Not found
   User DPI Setting: Using System DPI
 System DPI Setting: 96 DPI (100 percent)
    DWM DPI Scaling: Disabled
     DxDiag Version: 6.01.7601.17514 32bit Unicode

------------
DxDiag Notes
------------
      Display Tab 1: No problems found.
        Sound Tab 1: No problems found.
        Sound Tab 2: No problems found.
        Sound Tab 3: No problems found.
        Sound Tab 4: No problems found.
          Input Tab: No problems found.



---------------
Display Devices
---------------
          Card name: NVIDIA GeForce GTX 560
       Manufacturer: NVIDIA
          Chip type: GeForce GTX 560
           DAC type: Integrated RAMDAC
         Device Key: Enum\PCI\VEN_10DE&DEV_1201&SUBSYS_14633842&REV_A1
     Display Memory: 4050 MB
   Dedicated Memory: 978 MB
      Shared Memory: 3071 MB
       Current Mode: 1920 x 1080 (32 bit) (60Hz)
       Monitor Name: HP 2509 Series Wide LCD Monitor
      Monitor Model: HP 2509
         Monitor Id: HWP283A
        Native Mode: 1920 x 1080(p) (60.000Hz)
        Output Type: DVI
        Driver Name: nvd3dumx.dll,nvwgf2umx.dll,nvwgf2umx.dll,nvd3dum,nvwgf2um,nvwgf2um
Driver File Version: 9.18.0013.2723 (English)
     Driver Version: 9.18.13.2723
        DDI Version: 11
       Driver Model: WDDM 1.1
  Driver Attributes: Final Retail
   Driver Date/Size: 9/12/2013 04:58:10, 15703688 bytes
        WHQL Logo'd: Yes
    WHQL Date Stamp:
  Device Identifier: {D7B71E3E-5141-11CF-5151-6E341CC2C435}
          Vendor ID: 0x10DE
          Device ID: 0x1201
          SubSys ID: 0x14633842
        Revision ID: 0x00A1
 Driver Strong Name: oem35.inf:NVIDIA_SetA_Devices.NTamd64.6.1:Section030:9.18.13.2723Tongue outci\ven_10de&dev_1201
     Rank Of Driver: 00E02001
        Video Accel: ModeMPEG2_A ModeMPEG2_C ModeVC1_C ModeWMV9_C
   Deinterlace Caps: {6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive
                     {F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY
                     {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY
                     {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalStretch
                     {6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(UYVY,UYVY) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive
                     {F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(UYVY,UYVY) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY
                     {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(UYVY,UYVY) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY
                     {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(UYVY,UYVY) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalStretch
                     {6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(YV12,0x32315659) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive
                     {F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(YV12,0x32315659) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY
                     {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(YV12,0x32315659) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY
                     {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(YV12,0x32315659) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalStretch
                     {6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive
                     {F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY
                     {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY
                     {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalStretch
                     {6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(IMC1,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(IMC1,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(IMC1,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(IMC1,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(IMC2,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(IMC2,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(IMC2,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(IMC2,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(IMC3,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(IMC3,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(IMC3,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(IMC3,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(IMC4,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(IMC4,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(IMC4,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(IMC4,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(S340,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(S340,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(S340,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(S340,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(S342,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(S342,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(S342,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(S342,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
       D3D9 Overlay: Supported
            DXVA-HD: Supported
       DDraw Status: Enabled
         D3D Status: Enabled
         AGP Status: Enabled

-------------
Sound Devices
-------------
            Description: Headset Earphone (11- Microsoft LifeChat LX-3000 )
 Default Sound Playback: Yes
 Default Voice Playback: Yes
            Hardware ID: USB\VID_045E&PID_070F&REV_0100&MI_00
        Manufacturer ID: 65535
             Product ID: 65535
                   Type: WDM
            Driver Name: USBAUDIO.sys
         Driver Version: 6.01.7601.17514 (English)
      Driver Attributes: Final Retail
            WHQL Logo'd: Yes
          Date and Size: 11/20/2010 23:23:47, 109696 bytes
            Other Files:
        Driver Provider: Microsoft
         HW Accel Level: Basic
              Cap Flags: 0xF1F
    Min/Max Sample Rate: 100, 200000
Static/Strm HW Mix Bufs: 1, 0
 Static/Strm HW 3D Bufs: 0, 0
              HW Memory: 0
       Voice Management: No
 EAX(tm) 2.0 Listen/Src: No, No
   I3DL2(tm) Listen/Src: No, No
Sensaura(tm) ZoomFX(tm): No

            Description: Speakers (Realtek High Definition Audio)
 Default Sound Playback: No
 Default Voice Playback: No
            Hardware ID: HDAUDIO\FUNC_01&VEN_10EC&DEV_0889&SUBSYS_1458A002&REV_1000
        Manufacturer ID: 1
             Product ID: 100
                   Type: WDM
            Driver Name: RTKVHD64.sys
         Driver Version: 6.00.0001.6449 (English)
      Driver Attributes: Final Retail
            WHQL Logo'd: Yes
          Date and Size: 8/30/2011 05:28:46, 3069032 bytes
            Other Files:
        Driver Provider: Realtek Semiconductor Corp.
         HW Accel Level: Basic
              Cap Flags: 0xF1F
    Min/Max Sample Rate: 100, 200000
Static/Strm HW Mix Bufs: 1, 0
 Static/Strm HW 3D Bufs: 0, 0
              HW Memory: 0
       Voice Management: No
 EAX(tm) 2.0 Listen/Src: No, No
   I3DL2(tm) Listen/Src: No, No
Sensaura(tm) ZoomFX(tm): No

            Description: Realtek Digital Output (Realtek High Definition Audio)
 Default Sound Playback: No
 Default Voice Playback: No
            Hardware ID: HDAUDIO\FUNC_01&VEN_10EC&DEV_0889&SUBSYS_1458A002&REV_1000
        Manufacturer ID: 1
             Product ID: 100
                   Type: WDM
            Driver Name: RTKVHD64.sys
         Driver Version: 6.00.0001.6449 (English)
      Driver Attributes: Final Retail
            WHQL Logo'd: Yes
          Date and Size: 8/30/2011 05:28:46, 3069032 bytes
            Other Files:
        Driver Provider: Realtek Semiconductor Corp.
         HW Accel Level: Basic
              Cap Flags: 0xF1F
    Min/Max Sample Rate: 100, 200000
Static/Strm HW Mix Bufs: 1, 0
 Static/Strm HW 3D Bufs: 0, 0
              HW Memory: 0
       Voice Management: No
 EAX(tm) 2.0 Listen/Src: No, No
   I3DL2(tm) Listen/Src: No, No
Sensaura(tm) ZoomFX(tm): No

            Description: Realtek Digital Output(Optical) (Realtek High Definition Audio)
 Default Sound Playback: No
 Default Voice Playback: No
            Hardware ID: HDAUDIO\FUNC_01&VEN_10EC&DEV_0889&SUBSYS_1458A002&REV_1000
        Manufacturer ID: 1
             Product ID: 100
                   Type: WDM
            Driver Name: RTKVHD64.sys
         Driver Version: 6.00.0001.6449 (English)
      Driver Attributes: Final Retail
            WHQL Logo'd: Yes
          Date and Size: 8/30/2011 05:28:46, 3069032 bytes
            Other Files:
        Driver Provider: Realtek Semiconductor Corp.
         HW Accel Level: Basic
              Cap Flags: 0xF1F
    Min/Max Sample Rate: 100, 200000
Static/Strm HW Mix Bufs: 1, 0
 Static/Strm HW 3D Bufs: 0, 0
              HW Memory: 0
       Voice Management: No
 EAX(tm) 2.0 Listen/Src: No, No
   I3DL2(tm) Listen/Src: No, No
Sensaura(tm) ZoomFX(tm): No

---------------------
Sound Capture Devices
---------------------
            Description: Headset Microphone (11- Microsoft LifeChat LX-3000 )
  Default Sound Capture: Yes
  Default Voice Capture: Yes
            Driver Name: USBAUDIO.sys
         Driver Version: 6.01.7601.17514 (English)
      Driver Attributes: Final Retail
          Date and Size: 11/20/2010 23:23:47, 109696 bytes
              Cap Flags: 0x1
           Format Flags: 0xFFFFF

-------------------
DirectInput Devices
-------------------
      Device Name: Mouse
         Attached: 1
    Controller ID: n/a
Vendor/Product ID: n/a
        FF Driver: n/a

      Device Name: Keyboard
         Attached: 1
    Controller ID: n/a
Vendor/Product ID: n/a
        FF Driver: n/a

      Device Name: Microsoft LifeChat LX-3000
         Attached: 1
    Controller ID: 0x0
Vendor/Product ID: 0x045E, 0x070F
        FF Driver: n/a

      Device Name: USB Gaming Mouse
         Attached: 1
    Controller ID: 0x0
Vendor/Product ID: 0x046D, 0xC041
        FF Driver: n/a

      Device Name: USB Gaming Mouse
         Attached: 1
    Controller ID: 0x0
Vendor/Product ID: 0x046D, 0xC041
        FF Driver: n/a

      Device Name: Dell Multimedia Pro Keyboard
         Attached: 1
    Controller ID: 0x0
Vendor/Product ID: 0x413C, 0x2011
        FF Driver: n/a

      Device Name: Dell Multimedia Pro Keyboard
         Attached: 1
    Controller ID: 0x0
Vendor/Product ID: 0x413C, 0x2011
        FF Driver: n/a

      Device Name: Dell Multimedia Pro Keyboard
         Attached: 1
    Controller ID: 0x0
Vendor/Product ID: 0x413C, 0x2011
        FF Driver: n/a

Poll w/ Interrupt: No

 

Message 8 of 2,257 (172,517 Views)

Re: Battlefield 4 keeps crashing on PC

★ Apprentice

#blazur

 

you have the problem or not?

Message 9 of 2,257 (172,500 Views)

Re: Battlefield 4 keeps crashing on PC

[ Edited ]
★★★★ Novice

Same here. A few of my crash logs and dxinfo.

 

Spoiler

------------------
System Information
------------------
Operating System: Windows 8.1 Enterprise 64-bit (6.3, Build 9600) (9600.winblue_gdr.130913-2141)
Processor: Intel(R) Core(TM) i5-3570K CPU @ 3.40GHz (4 CPUs), ~3.4GHz
Memory: 16384MB RAM
Available OS Memory: 16270MB RAM
Page File: 3331MB used, 15370MB available
Windows Dir: C:\Windows
DirectX Version: DirectX 11
DxDiag Version: 6.03.9600.16384 64bit Unicode


---------------
Display Devices
---------------
Card name: AMD Radeon HD 7900 Series
Manufacturer: Advanced Micro Devices, Inc.
Chip type: AMD Radeon Graphics Processor (0x6798)
DAC type: Internal DAC(400MHz)
Device Type: Full Device
Device Key: Enum\PCI\VEN_1002&DEV_6798&SUBSYS_32111682&REV_00
Display Memory: 10982 MB
Dedicated Memory: 3046 MB
Shared Memory: 7936 MB
Current Mode: 1920 x 1080 (32 bit) (60Hz)
Monitor Name: Dell P2310H(Display Port)
Monitor Model: DELL P2310H
Monitor Id: DELD029
Native Mode: 1920 x 1080(p) (60.000Hz)
Output Type: Displayport External
Driver Name: aticfx64.dll,aticfx64.dll,aticfx64.dll,aticfx32,aticfx32,aticfx32,atiumd64.dll,atidxx64.dll,atidxx64.dll,atiumdag,atidxx32,atidxx32,atiumdva,atiumd6a.cap,atitmm64.dll
Driver File Version: 8.17.0010.1247 (English)
Driver Version: 13.250.18.0
DDI Version: 11.1
Feature Levels: 11.1,11.0,10.1,10.0,9.3,9.2,9.1
Driver Model: WDDM 1.3

---------------
Diagnostics
---------------

Windows Error Reporting:
+++ WER0 +++:
Fault bucket -344557476, type 5
Event Name: AppHangB1
Response: Not available
Cab Id: 0

Problem signature:
P1: bf4.exe
P2: 1.0.0.0
P3: 52668dcb
P4: 44d2
P5: 67246080
P6:
P7:
P8:
P9:
P10:

+++ WER1 +++:
Fault bucket , type 0
Event Name: AppHangB1
Response: Not available
Cab Id: 0

Problem signature:
P1: bf4.exe
P2: 1.0.0.0
P3: 52668dcb
P4: 44d2
P5: 67246080
P6:
P7:
P8:
P9:
P10:

+++ WER2 +++:
Fault bucket 138811275, type 4
Event Name: APPCRASH
Response: Not available
Cab Id: -297344644

Problem signature:
P1: bf4.exe
P2: 1.0.0.0
P3: 52668dcb
P4: bf4.exe
P5: 1.0.0.0
P6: 52668dcb
P7: c0000005
P8: 0000000000856ec3
P9:
P10:

+++ WER3 +++:
Fault bucket -344557476, type 5
Event Name: AppHangB1
Response: Not available
Cab Id: 0

Problem signature:
P1: bf4.exe
P2: 1.0.0.0
P3: 52668dcb
P4: 44d2
P5: 67246080
P6:
P7:
P8:
P9:
P10:

+++ WER4 +++:
Fault bucket , type 0
Event Name: AppHangB1
Response: Not available
Cab Id: 0

Problem signature:
P1: bf4.exe
P2: 1.0.0.0
P3: 52668dcb
P4: 44d2
P5: 67246080
P6:
P7:
P8:
P9:
P10:

+++ WER5 +++:
Fault bucket -343206968, type 5
Event Name: BEX64
Response: Not available
Cab Id: -298555207

Problem signature:
P1: bf4.exe
P2: 1.0.0.0
P3: 52668dcb
P4: StackHash_ae92
P5: 0.0.0.0
P6: 00000000
P7: PCH_A6_FROM_ntdll+0x0000000000096B2A
P8: c0000005
P9: 0000000000000008
P10:

+++ WER6 +++:
Fault bucket 138319601, type 4
Event Name: APPCRASH
Response: Not available
Cab Id: 0

Problem signature:
P1: bf4.exe
P2: 1.0.0.0
P3: 52668dcb
P4: bf4.exe
P5: 1.0.0.0
P6: 52668dcb
P7: c0000005
P8: 000000000067722e
P9:
P10:

+++ WER7 +++:
Fault bucket -344557476, type 5
Event Name: AppHangB1
Response: Not available
Cab Id: 0

Problem signature:
P1: bf4.exe
P2: 1.0.0.0
P3: 52668dcb
P4: 44d2
P5: 67246080
P6:
P7:
P8:
P9:
P10:

+++ WER8 +++:
Fault bucket , type 0
Event Name: AppHangB1
Response: Not available
Cab Id: 0

Problem signature:
P1: bf4.exe
P2: 1.0.0.0
P3: 52668dcb
P4: 44d2
P5: 67246080
P6:
P7:
P8:
P9:
P10:

 

 

 

 

Message 10 of 2,257 (172,488 Views)