Forum Discussion

Re: The infamous "c0000005" again.

this error means that the application is addressed to the memory that should not be accessed

some of the possible causes:

- bad (overclocked) memory
- bad HDD
- old or not installed correctly:
Microsoft Visual C++
.NET framework
Microsoft XNA Framework

- corruption of system files or some drivers
- something else

the conclusions do themselves 👿

20 Replies

  • Anonymous's avatar
    Anonymous
    9 years ago

    The something else is a little bit broad. :D The memory is the best guess from your list. I'll try with 1.65v rams only. Maybe that helps. Thanks!

    edit:

    I got a "display driver stopped responding and has recovered" message just now. :D I don't understand. I used the same driver with the new mobo too, and with that it worked perfectly. At least I played and browsed about 10 hours with it without a single error message, crash, etc... I'll test that system further maybe it needs time to produce the same error messages. If so, then the problem is with the video card or the driver. Btw. is it sure that this is an issue with the ram on the mobo? I mean the video card has a ram too...

  • Anonymous's avatar
    Anonymous
    9 years ago

    I am using now performance mode by power settings. Now the game starts, but after a few hours it crashes with "the game did not start properly" and after that it let me wait infinite for exiting the game. Actually the bf4.exe is not even running, so I don't know what origin exits from. Better and better...

    edit

    After a while I got the c0000005 again. At least now after a few hours just by the old HDD. Okay, I'll check the RAM and I test the new mobo + cpu further. I am curious, maybe I got this error by the new system as well and the driver or the card is faulty.

  • MADrag0n's avatar
    MADrag0n
    9 years ago

    - c0000005 error related for RAM, but not for VRAM

    - "display driver stopped responding and has recovered"  error related to drivers if it happen in some software and related to fault video card if it happen in many application or even in OS, 2D mode.

    - u can attach to a message txt file of dxdiag for report some errors log to us

  • Anonymous's avatar
    Anonymous
    9 years ago

    Firefox just crashed and I wasn't able to restart it. It crashed by every restart again. This is something new again. :D

    I attached the dxdiag results after the firefox crash. It shows nothing as far as I can understand.

    So in theory the video card and the memory are okay, in practice we got errors related to them. Probably then the motherboard is not okay.

    I attached a hwinfo report as well. In theory the voltages are okay, but the rams are on 1.8v according to this. I remove now the 1.8v module and keep only the 1.65v modules now. Maybe that helps.

    I removed the high voltage memory module and its pair. Now I have only a pair of 1.65v modules with XMP. The BIOS shows 1.5v ram voltage and the hwinfo still shows 1.8v dimm voltage. I don't understand, both should be 1.65v. Wtf is going on? :D

  • MADrag0n's avatar
    MADrag0n
    9 years ago

    yes, for Win7 dxdiag not contains errors info..

    give to us report of msinfo32 /report C:\sysinfo.txt or perfmon /report or perfmon /rel

    Also u can try disable xmp and/or spd and setup memory settings manually

  • MADrag0n's avatar
    MADrag0n
    9 years ago

    This logs for Win7 is not useful for this case 👿 and language is not English... 🤭

    Let see on this: run command prompt as Admin, enter a command (then zip *.evtx files from our desktop and attach it to a message):
    for /D %T in (ACEEventLog Application Setup System)do wevtutil epl %T "%USERPROFILE%\Desktop\%T.evtx" /ow:true

  • Anonymous's avatar
    Anonymous
    9 years ago

    Yepp, Hungarian is the system lang, I was aftraid that you won't be able to read it. I attached the evtx files you requested. Thanks for your effort!

    I managed to set memory voltage to 1.64v, it did not help. I checked the newer RAM pairs separately, I still got the problem, so if this is a memory problem, then either the older ones are okay and the newer ones not or none of these old modules are okay. I'll check the system with the older modules too, but I think this is not a memory issue. I asked this on another forum, somebody told me, that this can be a hardware problem with the PCIE slot, so I probably won't be able to fix it. I cleaned the slot with acetone, it did not help. I'll get back my old video card for a day, so I will be able to check the system with that too. I hope it will work with that card and I will be able to sell it and forget these parts for eternity. I'll check the video card with the new parts further, maybe it has the hardware problem and not the old mobo. If so I can still send it back, I have 3 years warranty. Another possible suspect is the PSU, but the voltages appear to be okay. So I did not have much progress, still every part passes every test and benchmark, and still the game crashes after 2-3 hours.

  • MADrag0n's avatar
    MADrag0n
    9 years ago

    in this logs I have find some relation with cpu power errors and Origin crashes... Hmmm...

    So, I will recommend to u this:

    1) unplug all power connectors in system and plug it again (and make visual check)

    2) check new version of MB Bios and update it if it exist, load default settings, and don't make any overclock of cpu, gpu and ram

  • Anonymous's avatar
    Anonymous
    9 years ago

    The most recent BIOS is installed. I'll check the connectors. Do you think this can be a PSU failure?

  • MADrag0n's avatar
    MADrag0n
    9 years ago

    You can try find some info about this error (in yur log I find 10):

    Spoiler
    Log Name: System
    Source: Microsoft-Windows-Kernel-Processor-Power
    Date: 31.01.2017 14:09:46
    Event ID: 35
    Task Category: 🏈
    Level: Error
    Keywords:
    User: SYSTEM
    Computer: inf3rno-PC
    Description:
    Performance power management features on processor 1 in group 0 are disabled due to a firmware problem. Check with the computer manufacturer for updated firmware.
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
    <System>
    <Provider Name="Microsoft-Windows-Kernel-Processor-Power" Guid="{0F67E49F-FE51-4E9F-B490-6F2948CC6027}" />
    <EventID>35</EventID>
    <Version>0</Version>
    <Level>2</Level>
    <Task>2</Task>
    <Opcode>0</Opcode>
    <Keywords>0x8000000000000000</Keywords>
    <TimeCreated SystemTime="2017-01-31T12:09:46.657216100Z" />
    <EventRecordID>1218</EventRecordID>
    <Correlation />
    <Execution ProcessID="4" ThreadID="48" />
    <Channel>System</Channel>
    <Computer>inf3rno-PC</Computer>
    <Security UserID="S-1-5-18" />
    </System>
    <EventData>
    <Data Name="Group">0</Data>
    <Data Name="Number">1</Data>
    </EventData>
    </Event>
  • Anonymous's avatar
    Anonymous
    9 years ago

    In theory this should not be a problem, it is just a sign that speed step and cxe is turned off. So it is more like a warning than the cause of the problem. I reduced the multiplier to 6 from 8, but it is unplayeable. I'll try with low quality later.

    I got back my old video card, I'll test it tomorrow, but I am afraid it won't be enough for b4. Maybe at low quality or low resolution. Anyways I will be able to test whether the problem is with the new video card + driver, or with the mobo+cpu+ram+bios settings+psu, etc... I'll check the system with the other pair of ram too.

  • Anonymous's avatar
    Anonymous
    9 years ago

    Okay, this is not RAM related, nor GPU + driver related. I tried out with the other pair of RAMs. I tried out with my old video card. I tried out with 6x multiplier. It is not RAM, video card + driver related. I think it is not even CPU related, with 6x multipliter I had the same error, so it is not event tuning related I think. Afaik. when I first installed the new video card I did not change the BIOS settings, so it is probably not even BIOS settings related. The old PSU works properly with the new mobo, so I think this is mobo related. Probably the PCIE slot on the mobo or the related circuitry is broken. I have some issues with USB3 too. I have an USB3 hub and an extender cable. My pendrive works with the hub and with the extender, but not with the hub which is on the extender. I could not figure out why. They work properly together with the new mobo. So I think the mobo is broken. I'll dismantle the old system and test the new one further. If this is a PSU related problem I'll know.

  • @ET-inf3rno @MADrag0n Just to try to help make sure all this is fully up to date on your PC from the source Not the game. My other question is when you do install a new video card driver how much are you installing ? Are you doing custom install and picking only 1- Graphics Driver and 2- PhysX System or just allowing the video card driver to install all its shuff?....

    Latest version of DirectX see this page
    http://www.microsoft.com/en-ca/download/confirmation.aspx?id=35

    Reinstall Microsoft C++ For my game PC's I install both x64 and x86 as it does not hurt the PC as long as PC is X64
    http://www.microsoft.com/en-US/download/details.aspx?id=40784

    Update your Microsoft .NET framework.
    http://www.microsoft.com/en-ca/download/details.aspx?id=30653

    Adobe Flash Player update
    http://get.adobe.com/flashplayer/

    Go to Punk Buster site
    http://www.punkbuster.com/index.php?page=pbsetup.php

    1- Download PB then extract files to your desktop.
    2- Open Punk Buster folder.
    3- Click on the PB setup and it will open.
    4-Add your BF4 game to punk buster its at the top of Punk Buster.
    5-Then update punk buster again at the top of Punk Buster.

    Reboot PC test BF4

  • Anonymous's avatar
    Anonymous
    9 years ago

    Hi!

    I let the nvidia installer to install everything it wants including physx, .net framework, etc... I don't think this is driver or software related, since the same video card works properly in the new mobo. At least I tested it for 10 hours, and by the old mobo it takes at most 2-3 hours to get a crash, driver restart, etc... It is certainly not pb related, the pb cannot cause for example a firefox crash, or a video card driver restart. I installed everything the exact same way by the two systems. I'll buy thermal paste, and check the cpu, I'll probably put the cooler on the new cpu and forget this old stuff.

  • @ET-inf3rno I fully agree it is not punk buster lol but with a error like this it is best to have / be sure all this is updated on said PC to help pin point the issue.

  • Anonymous's avatar
    Anonymous
    9 years ago

    I found that the Xeon microcode was never added to the BIOS. I installed a modded BIOS. The old BIOS thought that the Tjmax is 100°C and started to throttle the CPU and sometimes kill the apps, when 50°C is reached, because it thought that 50°C is the T case. Now with the new BIOS the Tjmax is properly set to 85°C and the power management is fixed as well. The power errors went away and the system became more stable, but still I got this c00005 error after 2-6 hours while playing bf4. I'll test the memory this week again. I'll try out this punkbuster update idea too...

  • MADrag0n's avatar
    MADrag0n
    9 years ago

    Nice work. What bios version u have on GA-EP43T-USB3 ? I was read that in beta BIOS ver. F5D 2011/10/11 developers make some improve memory compatibility.

    In any way, this problem(s) have many variables 👿

    These MBs are too different. GA-EP43T-USB3 used chipset's system: CPU+🕹️MCH+ICH and Z97-P used chipset's system: CPU(includes GPU and IMC)+PCH

    We should not examine and compare the problems with them.

    Then it is some another sugessions:

    1) This Xeon designed to operate with "Intel® 5xxx Memory Controller" (it is on the server MB but not in this MB). Perhaps this may cause some incompatibility problems.
    So, u can try to test config with not Xeon CPU on this MB.

    2) Also u can make some tests after disabling any Intel virtualization technology in Bios.

    3) And how about tests on Win10? 👿

  • Anonymous's avatar
    Anonymous
    9 years ago

     - I had the f4, but now the modded f5d is installed. It is the beta you read of. I have some high density ddr3 rams, they did not work with the old BIOS, I am curious whether they work with this one.

     - Okay, I'll try disabling virtualization, I won't need virtualbox on this machine.

     - I don't have another CPU to test, I gave the old one to the local school.

     - I'll buy a win 10 for the new machine, but with OEM license bound to the first mobo it is installed on, so I won't be able to test it with win 10, unless I find a trial version. I somehow doubt that I can download a trial win 10 from MS, but who knows, I'll check it.

    - Ohh, I meant that I test it with the new mobo to see what happens with the same video card using the same driver on the long run.

  • Anonymous's avatar
    Anonymous
    9 years ago

    I tried without virtualization. Same results.

    According to hwinfo logs there is always thermal throttling and critical temperature when the apps crash. Sometimes origin crashes and bf4 exits automatically, sometimes bf4 crashes with c0+5. I thought that this thermal throttling is the sign of higher Tjmax, 100°C instead of 85°C. The T case is 67°C by this CPU and usually around 50°C it started to throttle. But one or two days before I set the CPU fan to 200RPM just to try out and the core temp reached 60°C without any issue. Now according to hwinfo it throttled around 45°C. So something is still not okay with the system, not to mention that throttling should not cause app crashes in theory. I'll try out with a different heatsink if I manage to get one. The current one might not lie properly on the CPU, it has a broken fastener which I managed to wire together. Maybe that's the problem, but I somehow doubt it.

    Ok. I found the cause of this throttling sign. The headers are at the end of the generated CSV file too. So the plot.ly plot viewer converts them to a true value and shows it as true on the graph. So in reality it wasn't any throttling according to the logs. Then this is not a temperature issue, this is most probably a RAM issue. I'll try it with the high density rams, maybe the new bios made the mobo compatible with them.

About Battlefield Franchise Discussion

Discuss the Battlefield games in this community forum.133,556 PostsLatest Activity: 2 hours ago