cancel
Showing results for 
Search instead for 
Did you mean: 

Processors

Highlighted
Adept I
Adept I

Issues with access violations

Hey there folks I dunno if anyone has any ideas I'm really hoping this is software but at the same time I'm pretty much out of ideas as I've talked on other forums, and to AMD's support as well but I don't know what to do here. I'm so tired of doing tech support right now I have the biggest headache over it. So my old PC I was not ready to replace but it died and it HAD to be replaced, so I built a new one out of savings trying not to cut too many corners but leave room to upgrade. This new PC is pretty great... when it works right, and that's the problem, it's not. I'll see if I can remember everything I've done but I've had it about a month so I've been fighting with quite a bit, there's too many things to forget!

This new machine has the following stuff:

Asus x370-A Prime motherboard, newest bios

Ryzen 1800x

Corsair RAM DDR4 16 gb (2x 8gb sticks) 2666 Mhz (I'd have to look up the model, but it's on QVL)

EVGA Geforce GTX 1060 6gb

Crucial 250gb SSD M.2

WD 1TB HDD

Corsair CX650M PSU (650w)

So I'm grasping at straws for what's wrong. This PC in general is usually working fine, however it's the intensive programs like games that are the issue. I'm guessing 0xc0000005 general protection fault crashes (regular crashes, not BSOD level) frequently .While my older stuff is generally fine, the newer stuff is not. Star Trek 's never crashed it, Guild Wars 2.... I was saying it hadn't but it just did a little ago, Warframe, Batman Arkham Knight (which is already a terrible PC port) and Deus Ex Mankind Divided however do it frequently. In Batman's case the game won't stay running longer than 5 minutes in most cases, Deus Ex is random, sometimes it works for a while, sometimes it's a 5 min thing (I think it crashes on autosave, and actually that might be the case on Batman also, but not sure why.) Honestly as far as Batman goes, I'd like to play it but I know that's such a bad PC port there's plenty of people that have still never gotten it to work right.

I'm just stumped to what's doing this. I've ran benchmarks that don't fail. I've ran Memtest86 and the windows memory test which don't find anything wrong with the memory. I've done the usual sfc/dism/chkdsk to no avail. I've had probably 5-8 driver versions of Nvidia's drivers in here (honestly if it's a software thing I fully suspect them as the QA on their drivers has gotten more than a little terrible in recent years) as for the Nvidia drivers I did use DDU to blow those out in numerous cases, I'm quite familiar with that tool. As for other general drivers as far as I know, they should be up to date I installed stuff fresh from the company sites when I built this in just the last month. I'd done quite a bit with the video driver too, I often suspect Nvidia quite a bit these days. I had tried various builds, I'd tried installing the driver only without the extras especially PhysX, but no dice. Oh, and it's not overheating, either, not even close.

As for the RAM, it's in the recommended slots on the motherboard, I've also tried one stick, I've tried juggling them, it doesn't matter the crashes persist. I also didn't have DOCP turned on when I originally made this yet, so it ran at 2133mhz for over a week fine, and I've got DOCP now, running it at it's full expected 2666Mhz but it makes no difference, the errors still occur.

I'm also aware of the Ryzen batches that had the segmentation faulting issue that was mostly seen on Linux, I already contacted AMD's support though and they checked the serial number and said it shouldn't be in that batch, so I should have a good one, unless it's just broken. I'm also not sure if the board itself can be involved in that? Maybe? I hope it's not the board, cripes, this PSU power plug has such a death grip I'm afraid of how I'll replace it in the future.

I did contact AMD's email support, unfortunately they weren't very helpful. He wanted me to go try the CPU in another machine and would RMA it if it did it on another one. While the attic is full of old computers, everything's pretty outdated by the time I replace them, (or like the old one, they break down and even then it wasn't AM4) I don't have another AM4 machine to test anything in so if it is the CPU somehow I really hope that trying it in another machine that costs $200+ to make, which I don't need, isn't going to be a warranty contingency here. As much as I wish I could just do that to test it out and make this all less of a headache, I just don't have another AM4 PC or the money, or need, for one right now.

This is just kinda killing me here. I really didn't have the money to be building this in the first place and had to use savings to do it because I can't sit here going stir crazy with nothing to do (and actually to make matters worse my TV broke while waiting on parts to make this new one, how about that timing, and we have no cable TV anyway lol ) My old PC, the PSU blew, I dropped a new one in (the one in this new PC now actually) and it came back, and worked fine for a few days, but then it started doing hangs and BSODing all the time, and it got increasingly worse. When that PSU blew though, it didn't just stop turning on, it stopped working when the PC was at a high load gaming and broke down, so I'm not sure it didn't damage anything. But, I was doing nothing but tech support at home for like 2 weeks trying to fix the stupid thing, eventually, it got to the point that it was hanging outside of Windows prior to boot and that was close to the final straw on that once I realized it couldn't possibly be software related or the disk. The old PC I'd been upgrading since 2009, so it wasn't really in a good place to be repaired, so I had to shell out on this new one, which I really didn't have money to be making, but I needed to make a reasonable foundation to upgrade in the future, ya know?

I was floating the idea that the PSU might not be working right seeing as the old PC didn't work right with this new one either. But I dunno, I'm just not really convinced unless someone else knows more about it than I do. As for wattage, 650 watt should be enough for this, I even ran my parts through various PSU calculators before deciding on the final build instead of eyeballing it. I did hear some shaky things about this PSU after buying it. At the time, I was just so distraught trying to get the PC repaired that Corsair's was what was available locally quickly, usually a reasonable brand, and had a general 4/5 star rating on it, but later on I found out there's a green and gray tagged version of this PSU and the earlier green printed ones were crappy build quality, mine's gray though, I hope it's ok but I don't know. Is it possible for voltage changes to cause an access violation of some kind? I really don't know. Either way if it's hardware, and it may very well, it this is already shaping into a massive headache especially if I gotta get that PSU off of this board haha... ugh... Seriously though, Corsair's board power supply plug has a death grip.

Anyway sorry for the verbose spiel, thanks for any ideas or help anyone can provide

0 Kudos
33 Replies
Highlighted
Esteemed Contributor III

Re: Issues with access violations

If you suspect the PSU may be an issue. I always suggest to download a free Diagnostic program called OCCT. It is probably the only one the actually stress test a PSU besides the CPU and GPU.

The PSU Test is basically running both the CPU and GPU test simultaneously to put the maximum stress on the PSU. If the PSU is underpowered or faulty, many times as soon as you start the test, the Computer shuts down. But if it runs, in full screen, you can check the PSU outputs to see if they are within tolerances.

* The OCCT PSU TEST might damage or ruin a weak or cheaply made PSU*  Just a warning.

Both CPU and GPU Test also shows the PSU Outputs while running those particular tests.

On another note: Sometimes updating the Motherboard BIOS and CHIPSET to the latest version helps in compatibility issues and other issues. PRIME X370-A Driver & Tools | Motherboards | ASUS USA  for Windows 10:

BIOS

Version 40112018/05/027.98 MBytes

PRIME X370-A BIOS 4011
Update AGESA 1.0.0.2a + SMU 43.18

Chipset

Version 5.12.0.382018/04/18372.43 MBytes

AMD Chipset driver
AMD AM4 Chipset Driver V5.12.0.38 for Windows Win10 64bit. (AMD package version is V17.40.3765, VGA driver version is V23.20.840.0)

Check the QVL list to see if your SSD are listed. Sometimes that can problems if not completely compatible with the Motherboard.

This is a list for the M.2 SSD that are compatible with your Motherboard. These are the crucial SSD listed: http://dlcdnet.asus.com/pub/ASUS/mb/SocketAM4/PRIME_X370-A/PRIME_X370-A_Devices_report.pdf?_ga=2.200... (04/24/2017)

M.2 SSD :

Crucial CT128M550SSD4

M500-120G

CT250MX200SSD4

0 Kudos
Highlighted
Adept I
Adept I

Re: Issues with access violations

hmm QVL for the SSD I hadn't thought of that, although not sure I'd be able to solve the problem if that's the case haha I'll have to take a look.

I did actually do OCCT already a bit and ran it for a while fine I may have to look deeper into that. As for the BIOS and chipset drivers those should be up to date.

As for the SSD I hadn't thought of that, that's an interesting point. You're right, it's not on the QVL list I hadn't even thought of trying a QVL list for that. Although, they didn't seem to test too many of the M.2s, especially from Crucial who I chose because of the brand quality. Mine is a CT250MX500SSD4, it seems they only tested the M500-120G, CT128M550SSD4, and CT250MX200SSD4. It would seem for a fairly new board, Asus didn't pick very good products to test, the first, I didn't really find a product for, the other two seem to be legacy products Crucial isn't selling anymore, the product codes are very similar though I wonder how different they are, hmm.

I may have to play with OCCT more I don't want to damage anything but I guess if it's working RIGHT it shouldn't damage anything hmm. I guess really I don't have a real reason to suspect that the PSU is bad. My old PC I had it in after it's old one blew, before I used it to build this one, had it's former PSU break down at peak usage during playing a game, so it comes as little surprise to me that it could have broken something on it's way out (and honestly, that old PSU was kicking after like 8 or 9 years which is just crazy to me especially since I took a risk on that originally getting a Rosewill I can't believe it lasted so long, although I've never had a PSU break anything when dying before but I know it happens.) After I put this new one in, the old PC started, ran ok for a couple days, but then started to just get worse and worse to the point that it would barely POST over a week or so. So I'm not sure if the old PSU broke something (likely) or if this one did over the course of the time fried stuff in that week or two it was in there, or if the original one's break down damaged it and this one made it worse (still unlikely I think) or what :\ I'd like to hope it's not frying this new PC, who knows, realistically it's hard for me to truly suspect it, since the old PC did just have a PSU die at peak usage when it died on me.

0 Kudos
Highlighted
Esteemed Contributor III

Re: Issues with access violations

Does your Motherboard has any Troubleshooting LED or ERROR CODES lit up when you are booting up?

Since it is getting worse and worse, it sounds like a hardware is failing. Eventually it probably will die and you might be able to see what component it was.

Stress testing, in this case, may cause an early death to your computer.

When you run OCCT, are the 12 VDC, 5.0 VDC and 3.3 VDC within tolerances?  Those are the three main outputs that the Motherboard and components use. If one of those are too low it will cause a lot of power issues. Look at the OCCT Graphs from your test carefully and check those voltages.

Normally, if you have a Overheating or Power issue and sometimes a failing component or incompatible issues your computer will shutdown as though you pressed the Power Off switch. No errors or BSOD.

EDIT: You may just want to contact ASUS SUPPORT and find out if your SSDs are compatible. In my opinion, it should be if they are newer than 4/2017, the date of the posting of the QVL List.  But you never know.

0 Kudos
Highlighted
Adept I
Adept I

Re: Issues with access violations

Oh the worse and worse one was on my old PC that was dying after the PSU failure, it's pretty much dead, which forced me to build this new one, which is the one with the access violations I'm having issues with now in this post. On the old PC, before it's old PSU failed, I had had no problems, when I put the new one in though, I was getting whacky BSODs and hard locks all the time which had gotten more frequent over a week or two, eventually the reset button wasn't even resetting, and it started producing the hard locks before windows even loaded which definitely lead to it not being a Windows/driver thing, and occasionally artifacts when it froze also, and I had tried another video card I had too so that wasn't it, I'm fairly sure the PSU broke something on that when it died. That PC was built in 2009 though, it was about ready to be replaced whether I had the money or not. I could talk about the insane amount of stuff I did trying to save the life of that one all day, but anyway, that lead me to building this new one.

The new one just uses the PSU I had bought as a replacement for the old one, since the old PC wouldn't be needing it and I'm not made of money haha, and from multiple power calculators I played with, 650 should easily make the clearance I need. I've seen no actual symptoms on the new one that would lead me to believe the PSU is actually bad though. I haven't had anything like monitor black outs, or TDRs on the video card or anything similar with the new one. Normally this PC runs perfectly fine and very well, until I run into a random game crashing with a protection fault, anyway. It's just regular general protection faults too, not the BSOD nature, just regular crashes but they're 0xC0000005 every time (and usually show itself as the faulting module, but occasionally, one of the kernel DLLs or a visual C++ DLL but I've already got all the C++ ones up to date too not sure what could cause that from that angle), but multiple games are doing it, and it's ONLY games doing it, especially newer ones that push the PC harder, the older ones seem to do it less or not at all, or kind of middle ground on something like Warframe where it's from 2013 but they've upgraded the graphics and content continually over time. Although, Witcher 3 hasn't done it, which is one of the few other more recent games with high tier graphics I have, maybe these particular games are just REALLY badly programmed, I know Batman is for sure though?

I had recently seen another case where somebody had this happening and RMA'd their CPU and the new one didn't do it, but I'm not sure I'll have luck with that unless I can prove it's the CPU for sure, and I sure don't want to wait on an RMA or have to redo it if I'm being honest. I had contacted AMD's support already but they expect me to test it in another PC which if I'm being honest is not really realistic, I don't keep multiple current generation PCs around and even then I couldn't guarantee it'd be socket AM4 either, having to purchase parts for a whole extra PC to test a product that costs less than it for a warranty isn't really reasonable. I wonder if I should try stressing it with OCCT more than I had before?

I suppose there's the possibility it's still a driver. That would be the easiest solution if I could figure out what it was causing it though. I usually suspect Nvidia but after trying 5-10 driver versions already that's not really helped. I wish I had more crash more dumps too. I can't do a ton with it but I had broken down Batman Arkham Knight and Deus Ex Mankind Divided's crashes more in a debugger. Deus Ex's and Batman's dumps are as follows, from the place where Deus Ex crashed I would have expected Nvidia's involvement, as for Batman that points to a function in the Wwise audio pipeline middleware a lot of games use.

I suppose there's the possibility it's a completely unrelated driver but I'm not really sure where to go to start tracking that down, I already got the newest version of everything when I built this PC around a month ago it should be all fairly up to date if not entirely up to date, they don't really change the non-video related drivers too often. But yeah if you have any other suggestions throw it at me

0 Kudos
Highlighted
Adept I
Adept I

Re: Issues with access violations

Oh whoops can't edit these and silly me I forgot to paste in the debugger break down on the two game crashes whoops here they are, I'll bold the part that stood out to me but I'm not THAT good of a programmer so I can't really do much especially with these not being my code to break into further haha:

Deus Ex:

User Mini Dump File: Only registers, stack and portions of memory are available

************* Path validation summary **************

Response                         Time (ms)     Location

Deferred                                       srv*

Symbol search path is: srv*

Executable search path is:

Windows 10 Version 17134 MP (16 procs) Free x64

Product: WinNt, suite: SingleUserTS Personal

17134.1.amd64fre.rs4_release.180410-1804

Machine Name:

Debug session time: Mon Jul 30 03:34:15.000 2018 (UTC - 4:00)

System Uptime: not available

Process Uptime: 0 days 0:10:55.000

................................................................

.............................................................

Loading unloaded module list

............

This dump file has an exception of interest stored in it.

The stored exception information can be accessed via .ecxr.

(3318.13ec): Access violation - code c0000005 (first/second chance not available)

*** WARNING: Unable to verify checksum for DXMD.exe

*** ERROR: Symbol file could not be found.  Defaulted to export symbols for DXMD.exe -

DXMD!NvOptimusEnablement+0xeb2b1c:

00000001`4317474c 488b4d08        mov     rcx,qword ptr [rbp+8] ss:00000002`22944ef8=????????????????

0:000> .excr

rax=0000000000000003 rbx=0000000000000000 rcx=0000000040000093

rdx=00000001e2944e70 rsi=00000001e2944e60 rdi=0000000148300010

rip=000000014317474c rsp=000000000014bfc0 rbp=0000000222944ef0

r8=0000000000000010  r9=0000000000000000 r10=0000000148300000

r11=0000000018dd4840 r12=0000000000000001 r13=0000000000000000

r14=0000000040000090 r15=00000001e2944e60

iopl=0         nv up ei ng nz na pe cy

cs=0033  ss=002b  ds=002b  es=002b  fs=0053  gs=002b             efl=00010281

DXMD!NvOptimusEnablement+0xeb2b1c:

00000001`4317474c 488b4d08        mov     rcx,qword ptr [rbp+8] ss:00000002`22944ef8=????????????????

Batman:

User Mini Dump File: Only registers, stack and portions of memory are available

************* Path validation summary **************

Response                         Time (ms)     Location

Deferred                                       srv*

Symbol search path is: srv*

Executable search path is:

Windows 10 Version 17134 MP (16 procs) Free x64

Product: WinNt, suite: SingleUserTS Personal

17134.1.amd64fre.rs4_release.180410-1804

Machine Name:

Debug session time: Thu Aug  2 01:35:09.000 2018 (UTC - 4:00)

System Uptime: not available

Process Uptime: 0 days 0:01:43.000

................................................................

................................................................

Loading unloaded module list

.............

This dump file has an exception of interest stored in it.

The stored exception information can be accessed via .ecxr.

(3bac.389c): Access violation - code c0000005 (first/second chance not available)

ntdll!NtWaitForMultipleObjects+0x14:

00007ffc`0003aa04 c3              ret

0:034> .excr

rax=0000000000000000 rbx=0000000000000001 rcx=000000018541db60

rdx=0000000000000000 rsi=0000000000000000 rdi=0000000015966610

rip=0000000144f6cc86 rsp=000000001404f8e0 rbp=000000001404fa60

r8=0000000015966610  r9=0000000000000000 r10=00000000ffffffff

r11=0000000000000000 r12=0000000008699fe0 r13=00000000ffffffff

r14=0000000008699fe0 r15=0000000198bd81e0

iopl=0         nv up ei pl zr na po nc

cs=0033  ss=002b  ds=002b  es=002b  fs=0053  gs=002b             efl=00010246

BatmanAK!AK::Monitor::GetTimeStamp+0x6856:

00000001`44f6cc86 488b02          mov     rax,qword ptr [rdx] ds:00000000`00000000=????????????????

I had to Google around to check into that one, but it does seem to be part of AudioKinetic's Wwise audio pipe lining stuff. I'm not really sure what to make of this, I had expected these to be similar if it were the video driver which I usually suspect as an issue with things like this but Wwise shouldn't be touching that, I had even disabled all the audio devices and ran the game and had it crash so not sure on that front.

I'd like to see more data on Warframe's too as it's the third game crashing most commonly, but it has it's own crash handler which to my knowledge leaves no dumps for a debugger behind, only the game logs which I don't think I really saw a link to being the same thing each time it crashed though. It only saves one game log crash or not, each run though, so if it's crashing I have to save a copy before the next run of it and I don't have a crashing one to paste at the moment on that one, personally I didn't see anything that was a red flag in it, but I may be missing it staring me in the face too. It just seems a bit too convenient to me that 3 higher tier graphics games all do the same general protection fault crash to not be related ya know?

0 Kudos
Highlighted
Esteemed Contributor III

Re: Issues with access violations

have you tried running DXDiag and see if it comes up with any errors?  If you make a copy of DXDIAG at the very bottom of the report it will mention any problems with installed programs or files. It can be useful at times.

Try running SFC /scannow in an a elevated COMMAND PROMPT just to be sure your Windows is not corrupted or missing files.

Also what are the temperatures for the GPU and CPU like while gaming?

This seems to be a difficult error to fix.

Try running a Clean Windows environment. This will run Windows Desktop without any 3rd party software running in the background. Just Microsoft related programs. It is similar to running Safe Mode in a Windows Desktop. Here is how to do it: https://support.microsoft.com/en-us/help/929135/how-to-perform-a-clean-boot-in-windows .

This is a concise version. Follow the instructions on the above link to do it correctly.

To perform a clean boot in Windows 8 or Windows 10:

  1. Press the "Windows + R" key to open a Run box.
  2. Type msconfig and click OK.
  3. On the General tab, click Selective startup.
  4. Clear the Load startup items check box.
  5. Click the Services tab.
  6. Select the Hide all Microsoft services check box (at the bottom).
  7. Click Disable all.

I am not sure if games will be able to run under these conditions though.

0 Kudos
Highlighted
Adept I
Adept I

Re: Issues with access violations

Yeah DXDiag's got nothing wrong, I've already ran the full load of chkdsk/sfc/dism. The temps are fine, the CPU is usually 40-50C tops, GPU 55-70 tops, it usually doesn't hit the top unless I'm intentionally doing something like OCCT or something.

Haven't tried a clean thing yet, although I'm getting concerned after finding a big fat red flag popping up in my event viewer tonight, I think it's time for a VERY long memtest86:

Information    8/4/2018 11:04:50 PM    Memory-Diagnostic-Task-Handler    1001    None

Windows removed bad memory regions from this PC.

Yeaaaaaah I don't like that one bit

0 Kudos
Highlighted
Esteemed Contributor III

Re: Issues with access violations

When you ran MEMTEST86 the first time, did you get any error at all or did it show ZERO errors after you ran the test?

If it showed at least one or more errors, you have a bad memory module.

0 Kudos
Highlighted
Adept I
Adept I

Re: Issues with access violations

Nope! If I saw ANY error in there I would have been RMAing it so fast heads would spin, but I've since ran memtest some more like probably 9-15 hours more and still not managed to get it to trigger

0 Kudos