dslreports logo
uniqs
6

The Flash
Premium Member
join:2002-10-17
Toronto, ON

The Flash to Napsterbater

Premium Member

to Napsterbater

Re: [Tech] AMD's Crimson - Bye bye CCC, New Drivers

Mantle has never work with me, kept crashing I have to use DX11.

Napsterbater
Meh
MVM
join:2002-12-28
Milledgeville, GA
(Software) OPNsense
Ubiquiti UniFi UAP-AC-PRO

Napsterbater

MVM

said by The Flash:

Mantle has never work with me, kept crashing I have to use DX11.

I have run repair, for giggles i'm now reinstalling, ill try it again, then maybe ill try DX11.

Krisnatharok
PC Builder, Gamer
Premium Member
join:2009-02-11
Earth Orbit

Krisnatharok to The Flash

Premium Member

to The Flash
said by The Flash:

Mantle has never work with me, kept crashing I have to use DX11.

My BF4 would hard freeze the system under DX11. Under Mantle I very rarely (like every couple months) might get a crash/close to desktop, but nothing that takes down the machine.

Napsterbater
Meh
MVM
join:2002-12-28
Milledgeville, GA
(Software) OPNsense
Ubiquiti UniFi UAP-AC-PRO

1 edit

Napsterbater to The Flash

MVM

to The Flash
Reinstalled BF4, Used Mantle, Crash, Ran "Dism /Online /Cleanup-Image /RestoreHealth" "SFC /scannow" and chkdsk /offlinescanandfix changed to DX11, still a crash.

I get 2 (well kinda 3) different errors in the Event Viewer.

The main one I had been gettings was:
Faulting application name: bf4.exe, version: 1.6.2.40658, time stamp: 0x561d4c02
Faulting module name: bf4.exe, version: 1.6.2.40658, time stamp: 0x561d4c02
Exception code: 0xc0000005
Fault offset: 0x0000000001123a3e
Faulting process id: 0x8d0
Faulting application start time: 0x01d126659f85697d
Faulting application path: C:\Games\Origin\Battlefield 4\bf4.exe
Faulting module path: C:\Games\Origin\Battlefield 4\bf4.exe
Report Id: 2b18d1f7-526b-4c4b-ad9a-8127513e75fa
Faulting package full name: 
Faulting package-relative application ID: 
 

Then ill get these two together for one crash somtimes:
Faulting application name: bf4.exe, version: 1.6.2.40658, time stamp: 0x561d4c02
Faulting module name: bf4.exe, version: 1.6.2.40658, time stamp: 0x561d4c02
Exception code: 0xc000001d
Fault offset: 0x0000000000799f5b
Faulting process id: 0x1ab4
Faulting application start time: 0x01d12731a15a3128
Faulting application path: C:\Games\Origin\Battlefield 4\bf4.exe
Faulting module path: C:\Games\Origin\Battlefield 4\bf4.exe
Report Id: b8cf4d90-52bd-4cfa-baf4-62591e1b17c9
Faulting package full name: 
Faulting package-relative application ID: 
 

Windows cannot access the file  for one of the following reasons: there is a problem with the network connection, the disk that the file is stored on, or the storage drivers installed on this computer; or the disk is missing. Windows closed the program Battlefield 4™ because of this error.
 
Program: Battlefield 4™
File: 
 
The error value is listed in the Additional Data section.
User Action
1. Open the file again. This situation might be a temporary problem that corrects itself when the program runs again.
2. If the file still cannot be accessed and
- It is on the network, your network administrator should verify that there is not a problem with the network and that the server can be contacted.
- It is on a removable disk, for example, a floppy disk or CD-ROM, verify that the disk is fully inserted into the computer.
3. Check and repair the file system by running CHKDSK. To run CHKDSK, click Start, click Run, type CMD, and then click OK. At the command prompt, type CHKDSK /F, and then press ENTER.
4. If the problem persists, restore the file from a backup copy.
5. Determine whether other files on the same disk can be opened. If not, the disk might be damaged. If it is a hard disk, contact your administrator or computer hardware vendor for further assistance.
 
Additional Data
Error value: 00000000
Disk type: 0
 

Edit: Add DDU driver uninstall/reinstall to that list, still no luck.

Krisnatharok
PC Builder, Gamer
Premium Member
join:2009-02-11
Earth Orbit

Krisnatharok

Premium Member

What app are you using to get and view those line-item errors? I tried using DDU and got a MACHINE_CHECK_EXCEPTION even in safe mode.

To be safe, I removed both 290X's and tried running DDU -- still the same BSOD. I am now convinced I have a CPU, mobo, or ram problem. Good, because I am fucking tired of this shitty Asus mobo and Ivy Bridge anyways. Fuck this build.
me1212
join:2008-11-20
Pleasant Hill, MO

me1212

Member

Asrock mobos have always done well for me, even on haswell E. May be work looking in to asrock.