Forum Discussion

Fornic8er's avatar
8 years ago

BF4 Lockup, requires reboot

Hi All,

          Running out of options and appreciate any guidance.

BF4 has been locking up for last 6 months approx.

Sometimes happens in first 5 mins, sometimes after 30 mins.

When it locks up, cannot Alt Tab to any other screen, can only CTRL ALT DEL & shutdown/reboot, can start Task Manager, but its in the background.

After reboot, can play for 30-60 mins before it happens again.

I really on play BF4, but loaded Crysis 2, it ran for 20mins and had similar problem, but was able to end task.

I've tried a long list of fixes - see below.

I restored Factory Image and reloaded/updated everything - no good.

I got Dell to replace my MB & GPU - problem still happened.

I got Microsoft support to do remote OS Install with latest version - no good, they couldn't help further

I then went to EA, their suggestions I had already tried, so they offered me a free game - not helpful.

Hardware:

Alienware M17 R3

Intel(R) Core(TM) i7-6700HQ CPU @ 2.60GHz (8 CPUs), ~2.6GHz

12GB RAM

Nvidia Geforce GTX 970M - 1.5GB (I think) - Driver 378.49

Tried fixes:

Reinstall Direct x
Reinstall C++
update .Net framework
Turn off Anti Aliasing - in game
bf4.exe, bf4_x86, origin - run as admin - (Had to undo this since Battlelog has been replaced recently, otherwise game wouldnt launch)
disable origin in game
Cloud storage turned off
bf4 - 64bit
disable A/V
Origin in Windows Compat. mode
Repair Game
Update all drivers - tried OEM & Nvidia drivers (OEM drivers were older and couldnt launch BF4)
sfc /scannow
Update BIOS
BIOS Diagnostics - Supplied to Dell, no problems found
Uninstall the HD Audio Driver
Factory Reset PC
Update Windows
Update Drivers
Re-install Origin/BF4
Replace GPU
Replace Motherboard - warranty
Windows 10 remote re-install - Microsoft support
Repair Game
Delete BF4 Docs folder
Change Video settings from Ultra to High/Medium
Turned off Origin Admin - got rid of Compatibility mode
Tried closing background apps

Attachment

 DxDiag Attached - Note - It shows Intergrated GPU, actual GPU used is Nvidia Geforce GTX 970M

Links: https://www.dropbox.com/sh/u5cvnm2gly6pv12/AAAFueVfHp8LdFopV_fttBrra?dl=0

Video capture of lockup

HW Monitor Logs of GPU

Performance Monitor File

Thanks in advance.

Forn

9 Replies

  • Fornic8er's avatar
    Fornic8er
    8 years ago

    Cheers Preston,

                                good advise, stop all the non windows processes, thanks.

    Unfortunately it didn't work, got about 2 mins of play before it locked.

    I'll give it another crack, thanks.

  • ragnarok013's avatar
    ragnarok013
    Hero+
    8 years ago

    @Fornic8er wrote:

    Cheers Preston,

                                good advise, stop all the non windows processes, thanks.

    Unfortunately it didn't work, got about 2 mins of play before it locked.

    I'll give it another crack, thanks.


    Since clean boot didn't help I recommend checking your windows installation for errors: 

    Run the System File Checker tool (SFC.exe)

    To do this, follow these steps:
    1. Open an elevated command prompt. To do this, do the following as your appropriate:
    2. At the command prompt, type the following command, and then press ENTER:
      sfc /scannow
      Command Prompt with administrator rights - sfc /scannow
       

      The sfc /scannow command will scan all protected system files, and replace corrupted files with a cached copy that is located in a compressed folder at %WinDir%\System32\dllcache.
      The %WinDir% placeholder represents the Windows operating system folder. For example, C:\Windows.

      Note Do not close this Command Prompt window until the verification is 100% complete. The scan results will be shown after this process is finished.
    3. After the process is finished, you may receive one of the following messages:
      • Windows Resource Protection did not find any integrity violations.

        This means that you do not have any missing or corrupted system files.
      • Windows Resource Protection could not perform the requested operation.

        To resolve this problem, perform the System File Checker scan in safe mode, and make sure that the PendingDeletes and PendingRenames folders exist under %WinDir%\WinSxS\Temp.
      • Windows Resource Protection found corrupt files and successfully repaired them. Details are included in the CBS.Log %WinDir%\Logs\CBS\CBS.log.

        To view the detail information about the system file scan and restoration, go to How to view details of the System File Checker process.
      • Windows Resource Protection found corrupt files but was unable to fix some of them. Details are included in the CBS.Log %WinDir%\Logs\CBS\CBS.log.

        To repair the corrupted files manually, view details of the System File Checker process to find the corrupted file, and then manually replace the corrupted file with a known good copy of the file.

    More Information

    How to view details of the System File Checker process

    To view the details that included in the CBS.Log file, you can copy the information to the Sfcdetails.txt file by using the Findstr command, and then view the details in the Sfcdetails.txt. To do this, follow these steps:
    1. Open an elevated command prompt as described in the previous step 1.
    2. At the command prompt, type the following command, and then press ENTER:
      findstr /c:"[SR]" %windir%\Logs\CBS\CBS.log >"%userprofile%\Desktop\sfcdetails.txt" 
      Note The Sfcdetails.txt file contains details from every time that the System File Checker tool has been run on the computer. The file includes information about files that were not repaired by the System File Checker tool. Verify the date and time entries to determine the problem files that were found the last time that you ran the System File Checker tool.
    3. Open the Sfcdetails.txt file from your desktop.
    4. The Sfcdetails.txt file uses the following format:
      Date/Time SFC detail
      The following sample log file contains an entry for a file that could not be repaired:
      2007-01-12 12:10:42, Info                  CSI    00000008 [SR] Cannot 
      repair member file [l:34{17}]"Accessibility.dll" of Accessibility, Version = 
      6.0.6000.16386, pA = PROCESSOR_ARCHITECTURE_MSIL (8), Culture neutral, 
      VersionScope neutral, PublicKeyToken = {l:8 b:b03f5f7f11d50a3a}, Type 
      neutral, TypeName neutral, PublicKey neutral in the store, file is missing
       


    How to manually replace a corrupted system file with a known good copy of the file

    After you determine which system file was corrupted and could not be repaired through the detail information in the Sfcdetails.txt file, find where the corrupted file located, and then manually replace the corrupted file with a known good copy of the file. To do this, follow these steps:

    Note You may be able to get a known good copy of the system file from another computer that is running the same version of Windows with your computer. You may perform a System File Checker process on that computer to make sure the system file that you intend to copy is a good copy.

    1. Take administrative ownership of the corrupted system file. To do this, at an elevated command prompt, copy and then paste (or type) the following command, and then press ENTER:
      takeown /f Path_And_File_Name
      Note The Path_And_File_Name placeholder represents the path and the file name of the corrupted file. For example, type takeown /f C:\windows\system32\jscript.dll
      Command Prompt with administrator rights - command succeeded
       
    2. Grant administrators full access to the corrupted system file. To do this, copy and paste (or type) the following command, and then press ENTER:
      icacls Path_And_File_Name /GRANT ADMINISTRATORS:F
      Note The Path_And_File_Name placeholder represents the path and the file name of the corrupted file. For example, type icacls C:\windows\system32\jscript.dll /grant administrators:F.
      Command Prompt with administrator rights
       
    3. Replace the corrupted system file with a known good copy of the file. To do this, copy and paste (or type) the following command, and then press ENTER:
      Copy Source_File Destination
      Note The Source_File placeholder represents the path and file name of the known good copy of the file on your computer, and the Destination placeholder represents the path and file name of the corrupted file. For example, type copy E:\temp\jscript.dll C:\windows\system32\jscript.dll.
     
    Properties

    Article ID: 929833 - Last Review: Apr 6, 2017 - Revision: 3

    Windows 10 Pro, released in July 2015, Windows 10 Enterprise, released in July 2015, Windows 8.1, Windows 8.1 Enterprise, Windows 8.1 Pro, Windows 8, Windows 8 Enterprise, Windows 8 Pro, Windows 7 Enterprise, Windows 7 Home Basic, Windows 7 Home Premium, Windows 7 Professional, Windows 7 Starter, Windows 7 Ultimate, Windows Vista Enterprise 64-bit Edition, Windows Vista Ultimate 64-bit Edition, Windows Vista Business, Windows Vista Business 64-bit Edition, Windows Vista Enterprise, Windows Vista Ultimate
  • Fornic8er's avatar
    Fornic8er
    8 years ago

    I've tried this one before, but did so again.

    Result:

    Windows Resource Protection did not find any integrity violations.

    Thanks anyway.

  • EA_Archi's avatar
    EA_Archi
    Icon for EA Staff (Retired) rankEA Staff (Retired)
    8 years ago

    Hello @Fornic8er 

    I am really sorry for all those troubles with Battlefield 4. Are you able to play other graphic heavy game on your PC, beside Crysis 2? This just looks like a general GPU-related issue, and not a game-related one. 

    Cheers,
    Archi

  • Hey Archie,

                      Really only play BF4, tried Crysis 2 to see if the problem was game related. I had this PC 6 months before the problem started without any issues.

    Pushed Dell into replacing my motherboard & GPU & LCD (Had line through it) under warranty - didn't fix the problem though.

    I reckon the problem started around the time Win 10 Anniversary was released, but not certain.

    Cheers.

  • EA_Archi's avatar
    EA_Archi
    Icon for EA Staff (Retired) rankEA Staff (Retired)
    8 years ago

    Hello @Fornic8er 

    And thank you for all the additional information on this issue. The Windows 10 update, you`ve mentioned does caused some issues on few occasions. Any chance you can rollback the update?

    Cheers,

    Archi 

  • ragnarok013's avatar
    ragnarok013
    Hero+
    8 years ago

    @Fornic8er wrote:

    Hey Archie,

                      Really only play BF4, tried Crysis 2 to see if the problem was game related. I had this PC 6 months before the problem started without any issues.

    Pushed Dell into replacing my motherboard & GPU & LCD (Had line through it) under warranty - didn't fix the problem though.

    I reckon the problem started around the time Win 10 Anniversary was released, but not certain.

    Cheers.


    Ah yes the BF4 WIn10 AU system issue here's a link with solutions to that issue @Fornic8er: https://forums.battlefield.com/en-us/discussion/13592/bf4-not-launching-windows-10-anniversery-update-causing-bf4-not-to-launch-disappear/p1?new=1

  • Fornic8er's avatar
    Fornic8er
    8 years ago

    Hi All,

                 Cant rollback Anniversary update to check if its the problem.

    Still have the problem, locks up in first 5 mins, I've shortened my reboot to a log off/log in, then I'm good for about 1hr of play.