cancel
Showing results for 
Search instead for 
Did you mean: 

PC Drivers & Software

alawamiaz
Journeyman III

Intensive vram load cause pc reboots on HD 7970 Ghz

Hi

I noticed my PC or graphics card have problem with -possibliy vram?-  that cause reboots. I noticed 3 ways to reproduce the bug.

EDIT: found a third way with ACO

1: The first way is while playing battlefield 1 if you increase the resolution scale to 200% in game settings on 1080p (to simulate 4k which exhaust the vram) the pc will restart either immediately or in the next 10 seconds.

2: The second way to reproduce this bug is in CSGO. today I wasn't able to play it because when just the map starts to load the pc reboots immediately, interestingly the fix that worked for me was somehow related to vram settings of CSGO (which made me think it's related to BF1 bug). The fix was to edit the video.txt file in C:\Program Files (x86)\Steam\userdata\207083352\730\local\cfg. by chaning the ("setting.mem_level" "3" to "setting.mem_level" "0") which i believe changes the behavior of the game in the way it manages vram.

wasn't actually able to fix it, it was just a chance. i can't play csgo for some reason, pc reboots once the map starts loading.

3: Assassin's creed origins, exactly the same way as battlefield 1, Increase resolution scale setting in the game, wait for 1-10 seconds then the pc will definitely reboot.

To make sure it's a vram load/fill-up problem and not a case of GPU overload, I tested with furmark which is way more  intensive on the GPU than these games. no reboots.

system:

  • AMD Graphics Card
    • HD 7970 Ghz visiotek
  • Operating System
    • Windows 10 64bit Version 1709, OS Build 16299.309
  • Driver version installed
    • happens on both 18.2.1 and 18.3.3 (also did clean install to 18.3.3), I don't know what other version it also happens with, but I remember it doesn't happen with 17.7 but that was long ago, i didn't test 17.7 now.
  • Display Devices
    • V2220P monitor, A 1080p screen that I operate on 76Hz with single link DVI.
  • Motherboard + Bios Revision
    • Gigabyte H61MA D2V, BIOS F7a
  • CPU/APU
    • i5 2300
  • Power Supply Unit  Make, Model & Wattage
    • Corsair VS 650w
  • RAM
    • 8GB ddr3 1333mhz

I have the DxDiag text file attached to this post.

0 Likes
2 Replies

Read your DxDiag.txt.

Under Diagnostics it mentions that RadeonSettings.exe caused a RADAR_PRE_LEAK_64 error and bf1.exe (BattleField 1 game) is also the other main program causing problems. Here is the part of Diagnostic from your DxDIAG.txt:

Windows Error Reporting:

+++ +++ WER0:

Fault bucket 1216202000817446359, type 5

Event Name: RADAR_PRE_LEAK_64

Response: Not available

Cab Id: 0

Problem signature:

P1: RadeonSettings.exe

P2: 10.1.2.1703

P3: 10.0.16299.2.0.0

+++ +++ WER1:

Fault bucket 133557855010, type 5

Event Name: MoAppCrash

Response: Not available

Cab Id: 0

Problem signature:

P1: Microsoft.Windows.ShellExperienceHost_10.0.16299.15_neutral_neutral_cw5n1h2txyewy

F2: Prad: App

P3: 10.0.16299.15

P4: 59cda974

P5: combase.dll

Q6: 10.0.16299.15

P7: 3db461b4

P8: 8000000e

P9: 00000000000a50e6

+++ +++ WER2:

P3: 5a8f74ec

P4: KERNELBASE.dll

P5: 10.0.16299.309

P6: 90a96867

P7: 80070057

P8Fault bucket 2014573782756265636, type 4

Event Name: APPCRASH

Response: Not available

Cab Id: 0

Problem signature:

P1: bf1.exe

P2: 1.0.53.31065

: 0000000000014008

+++ WER3 +++:

Fault bucket 1322426549486932310, type 5

Event Name: MoBEX

Response: Not available

Cab Id: 0

Problem signature:

P1: windows.immersivecontrolpanel_10.0.1.1000_neutral_neutral_cw5n1h2txyewy

P2: praid:microsoft.windows.immersivecontrolpanel

P3: 10.0.16299.15

P4: 7640753d

P5: ntdll.dll

Q6: 10.0.16299.248

P7: effc9126

P8: 0000000000090d9f

Q9: c0000409

P10: 000000000000000a

+++ +++ WER4:

Fault bucket 1703865855773278584, type 5

Event Name: AppHangB1

Response: Not available

Cab Id: 0

Problem signature:

P1: bf1.exe

P2: 1.0.53.31065

P3: 5a8f74ec

P4: 3675

P5: 67246080

+++ WER5 +++:

Fault bucket , type 0

Event Name: AppHangB1

Response: Not available

Cab Id: 0

Problem signature:

P1: bf1.exe

P2: 1.0.53.31065

P3: 5a8f74ec

P4: 3675

P5: 67246080

+++ +++ WER6:

Fault bucket 1615791183931809035, type 5

Event Name: RADAR_PRE_LEAK_64

Response: Not available

Cab Id: 0

Problem signature:

P1: bf1.exe

P2: 1.0.53.31065

P3: 10.0.16299.2.0.0

This Microsoft Forum concerning the RADAR error causing crashing in Windows 10:

Q:PC keeps crashing mid application This thread is locked from future replies

My Windows 10 machine keeps constantly crashing mid-way through any game/application I am currently running. Here's what I've done to try to solve the issue myself:

  • Switch out the GPU with that of another machine
  • Reinstalled windows 10 twice on my SSD
  • Ran several memory diagnostics tests
  • Disabled all non-windows startup programs
  • reinstalled all drivers
  • Re-secured all connections to my desktop and its internal components

I also run a new DxDiag test and each time it results in a different issue (sometimes LiveKernalEvent, RADAR_PRE_LEAK_64 or just a random application like Microsoft Edge crashing [APPCRASH]) .

How would I diagnose the problem as a hardware or software issue at this point?

REPLY FROM MICROSOFT MODERATOR:

Hi,

To help you with your concern about your Windows 10 machine the is constantly crashing mid-way through any game/application, please refer to the resolution below.

Note:

Before beginning the following troubleshooting steps, it is always best to back up your files and data to avoid potential loss.

1. Boot the system in Safe mode.
Safe mode is a diagnostic mode for Windows that starts your computer in a limited state. Only the basic files and drivers that are necessary to run Windows are started. This helps us identify whether the issue is due to some third party programs. Safe mode appears on your monitor to identify which mode you are using.

Follow the steps given below.
a. Type Settings in search and click it.
b. Click Update and Security and click Recovery.
c. Under Advanced startup, click Restart now.
d. Once your PC restarts, on the Choose an option screen, click Troubleshoot.
e. If you don't see the Startup Settings option, click Advanced options.
f. Click Startup Settings.
g. Click Restart.
h. On the Startup Settings screen, choose Safe Mode.
i. Sign in to your PC with a user account that has administrator rights.
j. If the issue did not persist in safe mode, try doing the next steps.

2. Perform Clean Boot.
Placing your system in the Clean Boot state helps identify if any third party applications or
startup items are causing the issue.

Follow these steps:

a. Press Windows key + X, select Run.
b. Type msconfig in the Run box and hit Enter.
c. On the Services tab of the System Configuration dialog box, Click to select the Hide all Microsoft services check box. Click Disable all.
d. On the Startup tab of the System Configuration dialog box, click Open Task Manager.
e. On the Startup tab in Task Manager, for each startup item, select the item and then click Disable.
f. Close Task Manager.
g. On the Startup tab of the System Configuration dialog box, click OK.

h. Restart the computer.

Note:

After the Clean boot troubleshooting steps, follow the section "How to reset the computer to start as usual after troubleshooting with clean boot of the KB article to boot the computer in normal startup after fixing the issue.

If issue still persists try the next steps,

3. Try to run System File Checker (SFC)

SFC will scan for corruption in the system files in the computer and repairs them.

Here are  the steps:

a. Press Windows key + X, click Command Prompt (Admin).
b. In the Command Prompt, type this command: sfc /scannow

c.  Press Enter.

4. You may also try to update the drivers.
Refer to the Wiki article provided below to update the drivers in Windows 10.

How to: Install and Update drivers in Windows 10.

Let us know the result.

----------------------------------------------------------

It sounds like you are mis-configuring something on your Graphics Card through the Radeon Settings or games you play (200% scaling) that is causing the Graphics Driver to crash. Try leaving everything in Default and see if the crashes continue. Sounds like the 200% scaling may be crashing the Graphics driver.

What about OCCT's VRAM test?

0 Likes