Forum Discussion

WaitDontSh00t's avatar
3 years ago

Crashing upon loading into a match

Hopefully someone can help me out..!

Here are my specs:

CPU: Intel Core i9-10900k @ 5.0Ghz

Mobo: ASUS Z590 ROG Hero XIII

Ram: Corsair Vengeance RGB Pro 32GB 4000Mhz

GPU: Asus TUF OC 4080

Cooling: Corsair H150i ELITE CAPELLIX 360mm RGB Water Cooling

PSU: Corsair HX1200

Storage: Western Digital WD Black 1TB 7200 RPM 64MB Cache SATA 6.0Gb/s
Western Digital WD Black 2TB 7200 RPM 64MB Cache SATA 6.0Gb/s
Samsung 850 Evo SSD 500GB Sequential Read 540 MB/s -- Sequential Write 520 MB/s
Samsung 850 Evo SSD 1TB Sequential Read 540 MB/s -- Sequential Write 520 MB/s
Samsung 960 Evo PCIe NVMe 1TB Sequential Read 3200 MB/s -- Sequential Write 1900 MB/s

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

Game boots up fine, can navigate all the menus. Whenever I try to load into a match though, I'll see the map loading screen for a few seconds and then it hard crashes. I then see a "negative" colored image of my desktop of sorts and my PC reboots. No crash message or box, nothing like that. Hoping someone can help me out. No crash dumps in my BF2042 folder either. Drivers / software / windows all up to date as well.

15 Replies

  • Rokebo73's avatar
    Rokebo73
    Seasoned Ace
    3 years ago

    @WaitDontSh00t   Hmm bluescreen error.
    This is hard to tell , unless ya do a detailed error/issue research.
    It can be hardware , fault cfg , broken, to hot ect ect ect.
    It can also be software that causing issues , broken / faulty windows !

    You could do a CHKDSK C: /F /R <-- it need to do a reboot . and will scan system before windows will boot (select Y).
    It will scan for drive errors and try to fix it, or even exclude bad clusters from drive
    This scan will take a lot of time, depends on the Drive size and Files/Folder at drive.

    Press Windows key + 'R' ,typ CMD, Press and hold down CTRL + SHIFT  ,then press ENTER.
    When User Account Control shows up, click Yes.
    Command prompt windows willl open,now enter the command:

    CHKDSK C: /F /R

    Update us !

  • I'll give that a shot too..

    Did a sfc scan, and everything was fine. This is a completely new install of windows on a new drive too. Temps are all low/normal. So strange...!

  • Rokebo73's avatar
    Rokebo73
    Seasoned Ace
    3 years ago

    Ya sure memory isnt faulty some how ?
    Wich memory banks did ya populate with memory sticks ?
    Is memory compatible with CPU ? (IN QVL ?)
    Ya sure there is now power issue ? Run HWINFO64 and check power / volt / watt / Mhz !

    Update us when ya did CHKDSK also.

    PS didnt cfg BIOS some how ?
    Else reset bios (load optimized defaults) , hard reset is by connecting 2 pins at motherboard , check manual for CLR CMOS pins !

  • Performed a chkdsk, it corrected any errors / problems. 

    All memory banks are used, no other issues with them. 

    Last crash was this:

    0xA(0x7FFFFFFF0000, 0x2, 0x0, 0xFFFFF8024F27078C)

    IRQL NOT LESS OR EQUAL

    This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above. This is a software bug.

    Also seeing ntoskrnl.exe in the crash file

  • DarthFDG's avatar
    DarthFDG
    Hero+
    3 years ago

    @WaitDontSh00t wrote:

    This is a software bug.


    All indications are that you have an issue with your hardware or associated drivers, which, to your point, is software.

    Some games simply leverage certain hardware in a way others do not. This is how PC-based games behave. I've had to resolve multiple hardware issues myself because "just this game is having a problem".

    Some of the posts I saw regarding your issues in Diagnostics section of DXDIAG support your having hardware issues. I suggest your google "Aac3572MbHal_x86.exe" and work thru some of the solutions, besides removing the Aura software.

About Battlefield 2042 Technical Issues & Bugs

Having issues with Battlefield 2042? Join here to report bugs, and find help with, crashes, connectivity and more.13,589 PostsLatest Activity: 2 hours ago