However, this little tick of time that it takes to prioritize and figure that all out is enough for the Reporting service to forget 32/64 bit error handling and causes the memory commit to fail. Since the service handles that it takes it and reads that most info it needs is null and pretends like it's an Information result. This results in a bad_module_info dump to the Error reporting service. The GPU compensates and Windows attempts to render committing to memory an action. Windows Error Reporting is having issues with Origin running 64 overlaying to the windows desktop with it's friends and invites etc.
#Bad module info pubg driver#
The Red errors are coming from gpu driver dumps. The information faults/errors are coming from Memory. The dump isn't able to compile all the commits. Since this fault lies with the application and rendering process(The Engine/GPU/Memory). Second: Windows Error reporting takes all errors and commits them to memory and compiles the dump of the errors. Usually in a non intrusive way: ie Check your error log for application information with bad_module_info. DX11 doesn't quite get this right sometimes and hence will fault/error.
#Bad module info pubg 64 Bit#
The reason it's happening is due to a few things:įirst x86 or 32 bit and 64 bit rendering is different. This is not to say it doesn't have short comings.
#Bad module info pubg update#
Particularly more accurate that it is a part of the Creators update and mean to help with using GPU intensive tasks in an optimized way. "Bad_Module_Info is a part of the Windows Error Reporting process. This is from a post in the official Apex Legends support discord by TheLumination. Report Id: 217417ac-eb03-4ddf-adf3-f1d395da446dįaulting package-relative application ID: Log:įaulting application name: bad_module_info, version: 0.0.0.0, time stamp: 0x00000000įaulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000įaulting application start time: 0x01d4c400c821d92bįaulting application path: bad_module_info This time it happeend about halfway through a Wraith portal as Bloodhound. This may launch your game in a windowed format, you can change this once you've launched. Towards the bottom of the form set "Disable Fullscreen Optimisations" to TRUE, (With a tick). Click on the "Compatibility" tab at the top. Right click on the aforementioned file and go to "Properties". Navigate to your C:\Program Files (x86)\Origin Games\Apex folder, (Or wherever you may have installed the game). I presume this is in relation to the graphical nature of the main menu of the game once loaded.Ī solution to the problem was to change the "r5apex" launcher in "C:\Program Files (x86)\Origin Games\Apex" to "Disable fullscreen optimisations" i found that this setting against either the origin launcher or the easyanticheat launcher did not yield any results. I was myself experiencing a crash on startup with no error message, interrogation of the error logs and assistance from Xane at EA support, highlighted the issue was in reference to a 2d Texture error and bad_module.
0 kommentar(er)
