Jersey Bug,, After I pick my game jerseys to "PLAY IN"
EA. Where are the JERSEYS, Home option Jerseys, Road option Jerseys, Classic Jerseys etc.......We as customers pay for this game to have everything available to us at once.. Not some and pieces given to us throughout the MADDEN YEAR, We don't give EA, I don't give EA some and pieces of my money when I purchase this GAME!! FIX iT....
Need sack fumbles in Madden.
SACK FUMBLES Something we often see in the Live NFL games but rarely see in Madden. Also Mobile Quarterbacks ball carrying ratings should be higher around 80 & 82 fumbling less when running/ scrambling. But they should fumble way MORE when being SACKED. Trying to throw the Ball before contact should cause more fumbles forcing users to take more sacks instead of turnovers.Nickel / Dime 3-3-5 & 2-5-4 stopping the run.
Unfair strategic imbalance with formation personnel defenses that are structure to stop the pass are very effective at also stopping the run. The offensive line is very vulnerable & ineffective against formation like Nickel / Dime 3-3-5 & 2-5-4 Guards should pancake safeties playing linebacker and the guards should be blocking the linebackers standing in front of them. 4 to 5 yards should be the average on running plays with 2 tight ends or a tightend with fullback. if the defence is going to leave 8 men in pass coverage. Again strategic unfair advantage from a numbers perspective.There should be no reason 🤦🏾♀️
Its this many dropped interceptions on this game but defensive get instant block sheds with mediocre players on higher rated o linemen and constant pressure or sacks on 3 man rush while blocking 5 or 6 etc smh,game is disgusting 💯we need the people who made the old college football games back 💯cause yall have dont know what yall doing 💯WRC BSOD: eaanticheat.sys – 0x7F DOUBLE_FAULT – never launched on PC
EA SPORTS WRC has never successfully launched on this PC. The game was purchased through the Epic Games Store. Every attempt to launch WRC results in a Windows kernel BSOD involving EA Javelin AntiCheat / eaanticheat.sys. SYSTEM: Lenovo Legion 7 16IAX10 (83KY) Windows 11 Home 25H2, build 26200.9445 Intel Core Ultra 9 275HX NVIDIA GeForce RTX 5070 Laptop GPU 8 GB 32 GB RAM BIOS: Lenovo RXCN78WW CPU microcode: 0x121 CRASH: BugCheck: UNEXPECTED_KERNEL_MODE_TRAP (0x7F) Arg1: 0x8 – EXCEPTION_DOUBLE_FAULT Process: EAAntiCheat.GameService.exe Module: eaanticheat.sys EA AntiCheat image version: 1.0.33258.0 Failure bucket: 0x7f_8_eaanticheat!unknown_function I now have TWO independent usable Windows crash dumps from separate WRC launch attempts. Both reproduce the same fault at the exact same EA AntiCheat offset: eaanticheat+0x1766a24 The failing instruction is: mov qword ptr [rsp+68h],rax In both dumps, the trap frame contains a kernel stack pointer far outside the valid stack range of the EAAntiCheat.GameService.exe thread. Latest dump: Valid thread stack: Limit: ffff860f`eebb9000 Base: ffff860f`eebc0000 Current: ffff860f`eebbd790 Fault RSP: ffff860f`ffffffff CR2: ffff860f`ffffffe8 !pte on CR2 reports the address as NOT VALID. The earlier independent dump shows the same pattern: Fault offset: eaanticheat+0x1766a24 Fault RSP: ffffb801`ffffffff CR2: ffffb801`ffffffe8 !pte: not valid Therefore the failure is highly deterministic and reproducible in the EA AntiCheat execution path. I am NOT claiming that eaanticheat.sys must necessarily be the first component that corrupts the stack pointer, because the double-fault trap frame may already represent corrupted processor/stack state. However, two independent crashes reaching the exact same eaanticheat.sys offset with the same invalid-stack pattern strongly justify investigation by the EA Javelin AntiCheat engineering team. TARGETED DRIVER VERIFIER TEST: I also tested Windows Driver Verifier specifically against eaanticheat.sys using: - Special Pool - Force IRQL checking - Pool Tracking WRC immediately reproduced the same visible: UNEXPECTED_KERNEL_MODE_TRAP (0x7F) What failed: eaanticheat.sys Verifier did not produce an earlier/different verifier-specific bugcheck. Driver Verifier has since been fully disabled and verified as OFF. TROUBLESHOOTING ALREADY COMPLETED: - Full EA AntiCheat removal/reinstall - Full WRC deletion and clean reinstall through Epic Games Store - Game installed again to default location - EA AntiCheat files checked: Authenticode signatures are VALID and signed by Electronic Arts, Inc. - Windows 11 repair reinstall of the current 25H2 installation while preserving apps/files/settings - Windows Memory Integrity tested OFF + reboot; same BSOD; restored ON - Hypervisor tested OFF + reboot; same BSOD; restored to AUTO - NVIDIA / system drivers checked - BIOS and CPU microcode checked - Third-party filter/service isolation performed - Nahimic isolated - DAEMON Tools drivers isolated - Logitech joystick/G29-related drivers isolated; G29 physically disconnected - Lenovo SmartConnect / SmartEngine components isolated - SENetFilter completely removed and confirmed absent; WRC still produced the same BSOD - steamxbox driver isolated - RFDriveFs2 isolated - lenovoDriverBus isolated - No relevant third-party AV/VPN/EDR filter identified - Code Integrity logs checked; no blocked/unsigned driver failure corresponding to the crash - Storage/NTFS logs checked; no corresponding disk/storage failure - Windows crash-dump configuration repaired after earlier dump-writing failures The latest WRC crash successfully produced a completed kernel bitmap dump at 100%. Approximately 30 system restarts have occurred during this investigation, including planned troubleshooting reboots and BSOD-induced reboots. Conservatively, I estimate that more than 10 hours of active troubleshooting have been spent on this issue, excluding breaks and waiting time between tests. At this point I do not believe another generic reinstall, clean boot, Secure Boot toggle, Memory Integrity toggle, Windows repair, or similar first-line troubleshooting cycle is appropriate. These steps and significantly deeper kernel-level diagnostics have already been performed. REQUEST: Please escalate this report to the EA Javelin AntiCheat technical/engineering team. I would specifically like EA to investigate the reproducible eaanticheat.sys execution path at offset +0x1766a24 and whether there is a known compatibility issue involving this platform, particularly the Intel Core Ultra 9 275HX / Windows 11 25H2 environment. I can provide: - WinDbg output from both independent dumps - BSOD screenshots - minidump - system information - driver/service inventory - Code Integrity logs - additional diagnostic information requested by EA engineering The full latest kernel dump is approximately 2.9 GB, so it cannot be attached directly to this forum post, but I can provide relevant WinDbg analysis and smaller diagnostic files. Because the game has never successfully launched on this PC despite extensive troubleshooting, I would also appreciate guidance regarding the purchase through Epic Games Store and any available resolution/refund path if EA cannot provide a technical fix. Thank you.
