Recent Win 10 update breaking 1942?

pepsi_max2k · 2016-01-08 22:26:39

Ok so I don't know if this is Win 10, drivers, or just my bad luck, but...

I've been on Win 10 6 months no issues (or with win 7, or ever, really.... thanks for the patches tuia ).

Just went to play 1942 today, and it went straight to "BF1942.exe has stopped working...". Long story short, after testing numerous differing .exes (1.612, gamespy patch, original, etc) and under various compatibility settings (or lack of), I either get a straight crash, or can load menu, start joining game, then it gets to the map load part which normally goes slow (mine loads like 15% fast, slow bit up to 20%, then the rest immediately) but it just goes reallly reallly slow to the degree I esc from loading and it crashes.

All I've done in the last two weeks is* upgrade ATI drivers, and to Threshold 2. I may or may not have run BF successfully after some or all of this (meh; i don't play it as much as I used to...). Prior to this, no probs at all. Either way, today, nothing.

Known issue? Was there a win update today / this week / in thresh 2 known to mess everything up? Or in ATI drivers?

EDIT:

Faulting application name: BF1942.exe, version: 0.0.0.0, time stamp: 0x417564c4
Faulting module name: DINPUT8.dll, version: 10.0.10586.0, time stamp: 0x5632d687
Exception code: 0xc0000005
Fault offset: 0x000070b0
Faulting process id: 0x16c8
Faulting application start time: 0x01d14a536ac72857
Faulting application path: C:\Program Files (x86)\EA GAMES\Battlefield 1942\BF1942.exe
Faulting module path: C:\WINDOWS\SYSTEM32\DINPUT8.dll
Report Id: c0ac0370-060a-4ef6-b905-ffe54579d98a
Faulting package full name: 
Faulting package-relative application ID:

*And try to get a DualShock 4 working in a completely different program using various DirectInput / XInput affecting drivers....

inb4 noob

Last edited by pepsi_max2k (2016-01-08 22:35:23)

bud · 2016-01-08 23:17:40

DINPUT8.dll = Microsoft DirectX

pepsi_max2k · 2016-01-08 23:38:39

Yep I got that

So anyway, tip for 1942 players: don't install DS4Windows (Playstation DualShock drivers) or the official Microsoft Win 7 Xbox 360 control pad drivers.

One, the other, or a combination of the two, update DirectX (ie. DINPUT8.dll as bud says) which for whatever reason then stops 1942 from working as above.

Had to system restore back to a previous state to solve that one. Never thought I'd be thankful for system restore

Double tip: if you need to do exactly this, you need to restore to the restore point *before* the "Installed DirectX" restore point (if you select that exact point, it still won't work). So pray to god you have additional restore points before this. I had 1 left. Lucky, lucky me... .

Last edited by pepsi_max2k (2016-01-08 23:42:17)

pepsi_max2k · 2016-01-09 00:00:52

annndd... now it's happened again. erm. any ideas? some directx foolery going on. i might have to give up entirely.

bud · 2016-01-09 00:02:37

heh close one

sometimes you can fix such stuff in a bit unortodox way, like bf42 first look for some files in the "root" folder of the game, if it cant find it there it looks in the windows system folder etc. some games comes with there own versions of .dll files.

atleast this was the case before, might not work on never windows versions.

edit: try reinstall directx (or if it says check files or something like that)

Last edited by bud (2016-01-09 00:03:54)

pepsi_max2k · 2016-01-09 14:02:58

Ok so... where's the best techy 1942 forum? This is getting weird.

If I roll back to before the "Install DirectX" system restore point (which was initiated on exactly the same day / time as I was messing aroudn with DS4Windows and general pad / Dinput / Xinput drivers) it's fine, UNTIL I connect to internet, then within a few minutes it's borked again.

I've tried uninstalling any drivers / 360 pad program / ds4windows / whatever I can, but clearly something appears to be updating online and mucking up something control related. could be a windows update for something completely unrelated, but seems a little bit too much of a coincidence not to be ds4windows related.

system32/dinput8.dll file is showing no file access since October, so maybe some dependency file.

Anyone know enough about 1942's dinput useage to have any idea what's happened and how to fix it? Also, system32 folder not allowing me file write access even as admin

and bud - DirectX is inbuilt in windows 10. Only way to "install" or "reinstall" it is to do so for the whole OS. which is probably my next trick, after trying it with 1942 to see if it's just a control config file issue.

Last edited by pepsi_max2k (2016-01-09 14:05:09)

(BB)DinkW · 2016-01-09 15:35:23

I do not think this is a Win 10 issue. I have just updated my Win10 and everything is working fine, I suggest you look somewhere else.

HoOK · 2016-01-09 16:25:12

that's why win10 sucks

pepsi_max2k · 2016-01-09 19:01:39

>> I do not think this is a Win 10 issue.

Yup, it's a DirectInput / DirectX issue, see previous posts. I can't change the original title so...

nämeless · 2016-01-09 19:52:32

pepsi_max2k wrote:

If I roll back to before the "Install DirectX" system restore point (which was initiated on exactly the same day / time as I was messing aroudn with DS4Windows and general pad / Dinput / Xinput drivers) it's fine, UNTIL I connect to internet, then within a few minutes it's borked again.

In case it works fine with no Internet connection, it does mean something is trying to download and install updates in your system. You can try to hide some DirectX-related updates for your Windows. Just roll back using your stable restore point and go to the list of updates to install. You can hide the updates you don't want to install manually, just use your right mouse button. Also, you can check the utility by the manufacturer of your graphic card. It may start with your Windows and work as Windows service. Try to check your tray or control panel to find one. One more thing to check is your Windows Task Scheduler. There you can find tasks to update Adobe Flash Player or K-Lite Codec Pack, for example. Who knows, maybe there is something related to your problem.

bud · 2016-01-09 21:12:34

Is there any compability mode thingy in win 10? If there is i would try that first.

ATF_SurrenderMonkey · 2016-01-10 17:57:32

i've had nothing but problems playing this game since win10. Now, my system freezes at end of each map and I need to restart my laptop. And yes, i have setup the hidden adminstrator settings, direct, compatibility mode, all hardware has latest drivers...and oh..this laptop is about two weeks old...or young i guess...

windows 10 imo officially sucks for this old game.. think i will install windows 7 and reload game..

pepsi_max2k · 2016-01-10 18:26:30

nämeless wrote:

In case it works fine with no Internet connection, it does mean something is trying to download and install updates in your system. You can try to hide some DirectX-related updates for your Windows. Just roll back using your stable restore point and go to the list of updates to install. You can hide the updates you don't want to install manually, just use your right mouse button. Also, you can check the utility by the manufacturer of your graphic card. It may start with your Windows and work as Windows service. Try to check your tray or control panel to find one. One more thing to check is your Windows Task Scheduler. There you can find tasks to update Adobe Flash Player or K-Lite Codec Pack, for example. Who knows, maybe there is something related to your problem.

Thanks nämeless, but I can't find anything obvious.

Win 10 doesn't have the best windows update system - you can't use it online as previously, and the inbuilt system barely shows any details. That said, it's showing no updates at all during the time things went wrong, and nothing since.

Graphics afaik isn't updaing anything. Nothing obvious in task scheduler (DirectX, HID, input, DS4Windows, driver, whatever related). Same with services.

I'm gonna try find out from the DS4Windows dev if they have anything that could be doing anything online, or anything that would survive an uninstall and system restore. Otherwise, full restore it is

pepsi_max2k · 2016-01-10 20:40:42

Did some more digging and my timestamp for file .exes shows I installed Xbox360_64Eng at exactly the same time (down to the minute) as the "Installed DirectX" restore point shows up. And of course the exe includes a directx version from 2009, xinput related things, and various other stuff.

Looks like this may well be the culprit then: https://www.microsoft.com/hardware/en-u … or-windows

Serves me right for installing Win 7 drivers on Win 10 I guess . Still can't figure out how to delete the thing though.

Last edited by pepsi_max2k (2016-01-10 20:54:53)

Trench · 2016-01-10 22:22:28

pepsi_max2k wrote:

Still can't figure out how to delete the thing though.

I don't have any direct experience with this driver set, nor have an XBox 360 controller to try it with.

http://support.xbox.com/en-US/xbox-360/ … r-computer is suggesting that on Windows 10 the drivers should come from Windows Update automatically, without any separate driver set installation.

You may have already covered the normal bases for removing the Windows 7 driver set installation, such as "Uninstall" on the controller entry in Device Manager, followed by using the Add/Remove Programs control panel to remove any entry(ies) that the Windows 7 driver installation created. Since we're talking DirectX files, that might also include some kind of "DirectX runtime"-named entry in addition to the XBOX-related entry(ies).

But having performed the "Uninstall" in Device Manger such that the XBox no longer appears there, upon reboot it should detect the connected controller again and go fetch driver support through Windows Update (since you had also uninstalled the locally-installed Windows 7 driver set).

If it seems to be pulling the Windows 7 driver set even after removal and reboot, an additional approach can be to right-click the XBox controller in Device Manager and select "Update Driver" and force Windows to look for an updated driver in Windows Update that way.

All of which you may have already done; just describing it in case.

-Trench

pepsi_max2k · 2016-01-11 01:23:00

Thanks trench, and yeah - it's all pretty much been covered. No DirectX stuff to uninstall.

From what I can tell, the 360 drivers installed a modified directx 9.0c alongside the 12 built in to win 10. And this survives a restore point without any obvious services or software that can be removed (or at least enough of it survives to mess up the current install within 10 odd mins of a restore, give or take a net connection) other than the stuff I've already done - namely uninstalling the Xbox 360 Accessories software. I've uninstalled anything I can through dev manager but actually never had a 360 controller anyway (it was a long shot to get something else working...).

In addition, I can't "update" 9.0c to a correct version as the 9.0c installer refuses due to currently being "up to date". Extracting, and trying to regedit some directx version numbers didn't get it going. And I can't uninstall it because officially I only have DirectX 12 installed, which can't be uninstalled (or is a very bad idea)

FWIW, 1942 does start up in compatibility mode, it just hangs on map load (presumably whilst it's loading control drivers).

Full restore next week then. Failing that, hopefully the win 7 image still works... (with 1942 preinstalled ) Honestly I'm stumped - none of it really makes sense - how the hell does a driver / dx version that no longer exists after a restore, somehow reappear with a net connection despite having been both uninstalled and techincally never having been installed (given the restore point). almost makes me want to packet sniff everything. but i have a life

Last edited by pepsi_max2k (2016-01-11 01:31:09)

bud · 2016-01-11 01:54:01

Dunno if you can check the service list in win 10?

edit: bf42 does read the dll if it is in the root folder, i placed a phony one there for testing

try stick these files directly in your game folder (they seems to work together) it should override those that causing problem

Last edited by bud (2016-01-11 02:35:09)

-=TL=-FearofthedarkHU · 2016-01-11 10:44:40

Solution: Get dual boot up and running instead of that upgrade (need to acquire a win 10 installer for that tho). Then test bf1942 on win 10 without any problems if you encounter problems..

It is possible to remove one operating system from the dual boot config later on..

Windows 10 and windows 7 (also older versions) work well alongside. It is very simple.

You only have to be careful with activation. If you install Windows 7 activate it and then windows 10 (activate it), then you will need to reactivate win7 again.

About directx - BF1942 doesnt use Directx 10,11,12 etc, it uses an older version of directx and that is 9.0c. Thats why a directx update us important.

If you want to update all components and versions of directx, well personally i use this:

https://www.microsoft.com/en-us/downloa … px?id=8109 even though it says direcx 2010 redist, it still has the newest components. Try this if you havent already.

(download, create a folder on desktop, use the self installer to extract everything there and run setup.exe)

also directxwebsetup is also fine..

you cant uninstall directx because it is part of windows. (well probably you can but not recommended to mess around with it)

no idea about xbox or anything related to that lol.

Last edited by -=TL=-FearofthedarkHU (2016-01-11 11:03:51)

bud · 2016-01-11 21:16:54

pepsi_max2k wrote:

FWIW, 1942 does start up in compatibility mode, it just hangs on map load (presumably whilst it's loading control drivers).

No thats something else, is this singleplayer or when joining a server?

pepsi_max2k · 2016-01-16 21:02:53

Thanks bud and fearhun, unfortunately nothing's working so far.

And bud - it's the best explanation I have. Unless two major things stopped working at exactly the same time, during which only a handful of major changes happened to the system, both of which are fixed by the same restore to before the same software/driver install, then... obvious error is obvious.

Gonna reset soon as I have time. If it still doesn't work... well, every other win 10 user should start seeing the same issue Until then... stay the *#@! away from Xbox 360 pad drivers

bud · 2016-01-17 11:55:18

Good luck man, hope you get it to work.

I have a cameyo version you can try if you like http://ks3353793.kimsufi.com/bf42mods/

pepsi_max2k · 2016-01-18 00:06:32

Stuff I'm finding out:

1. Unless windows has *vastly* improved over the last few years, Win 10 Reset doesn't entirely remove everything. Unless they're very specific with their choice of default drivers (both proper ATI ones, and Gigabyte branded realtek audio drivers - specific to my mobo - *really*?? ).

2. The DINPUT8.dll error is pretty generic. I'm getting it for tons of reasons (ctd during map changes, etc).

3. It crashes *a lot* on Win 10.

4. The pause during map load at 25% (where it just loads a tiny bit reaaalll slow and keeps doing it forever) *could* be caused by a firewall block. Eg. fresh install, try to load map, stops, then I notice firewall exception prompt, exempt bf1942.exe, then map loads fine.

5. Vanialla is pretty much fine.

6. Mods (FH / FHSW all i have atm) still have exactly same error - on map load (if started via vanialla), or using their desktop shortcuts to run (immidiate DINPUT8.dll error).

7. losing the will to live

Last edited by pepsi_max2k (2016-01-18 00:15:59)

pepsi_max2k · 2016-01-18 00:58:17

EDIT: ok... possibly solved by simply turning off compatibility mode (forgot I had it on when i shouldn't...). but I've been here before and ther error's returned. anyway, on the off chance it works, I'm just gonna drop a win 10 install routine for anyone else needing it....

prelogue:
- NEVER EVER install Xbox 360 pad drivers!
- 1942 won't execute at all until the last few steps (nocd patch - needed due to SECDRV.sys error - see http://battlegroup42.de/News-BattleGrou … em-72.html ). And yes, the FH stuff is probably a requirement (it, eventually, includes some specific win patches that, well, ymmv if you don't use them).

1. CD install as normal; you'll need to run setup from disc (it doesn't autorun afaik). Origin ymmv.
2. Install 1.6.19 patch (google a link - standard official download).
3. Install 1.6 to 1.61b patch (google a link - standard official download).
4. Forgotten_Hope_0.7_origin_win7 - from http://forgottenhope.warumdarum.de/downloads.php , needed for the following:
5. FH_Fan_Mappack_6 - from http://www.moddb.com/mods/forgotten-hop … /downloads , also needed for the following
6. FHSW_v0.552_Setup_Part_1 from http://www.moddb.com/mods/forgotten-hop … /downloads , also needed for the following
7. FHSW_v0.552_Setup_Part_2 from http://www.moddb.com/mods/forgotten-hop … /downloads . and say YES to any win 7 patches / fixes / modded exes / whatever. In short, steps 4 to 7 are purely to install these patches. sure, you might getaway without them, but don't blame me if it doesn't work
8. battlefield_1942_gamespy_patch_v1.61 from http://team-simple.org/download/ , needed to get gamespy working again. and I believe this includes widescreen and nocd patch.

Note you'll need to install "Direct Play" or something like that on first run (win 10 will auto prompt you). And you'll need to set the BF1942.exe in root to run as admin, but *not* compatibility mode. And first internet run you'll need to whitelist in firewall (another auto prompt).

And I think that's all. If it still doesn't run, also try one of to following from team simple (last link above):
Battlefield 1942 v1.61 Retail executable patched
Battlefield 1942 v1.612 Retail executable patched
Battlefield 1942 v1.61 Origin executable patched
Battlefield 1942 v1.612 Origin executable patched

Last edited by pepsi_max2k (2016-01-18 00:58:46)

Chibi · 2016-01-19 14:23:32

My Windows 10 experience running Battlefield 1942 has been chequered.

On my desktop computer everything runs flawlessly without needing to tamper with compatibility und so weiter.

On my laptop, however, I need to create desktop shortcuts with "+restart 1 +joinServer host:port" at the end of the path. If I try to join games from the in-game browser I will get a perpetual black screen during map loads or map changes.

HoOK · 2016-01-19 14:25:45

i can run game without using windows compatibility even tho i got better ping around "74ms" on simple server...

ATF_SurrenderMonkey · 2016-01-23 23:13:19

Chibi wrote:

My Windows 10 experience running Battlefield 1942 has been chequered.
On my desktop computer everything runs flawlessly without needing to tamper with compatibility und so weiter.
On my laptop, however, I need to create desktop shortcuts with "+restart 1 +joinServer host:port" at the end of the path. If I try to join games from the in-game browser I will get a perpetual black screen during map loads or map changes.

I will try the add server host in the link.
My bf consistently gets black screen and I have to restart laptop at end of map change...get black screen when map changes.
task manager wont kill bf that's why I have to restart laptop.

and this is from cd fresh install jan 21. still does it.

pepsi_max2k · 2016-01-31 23:17:45

So turns out this may all have been an AMD Radeon driver issue after all.

Updated to latest Crimson edition (the only *other* thing installed alongside the 360 drivers) and.... almost the same thing. DINPUT8.dll errors. Plus side is this time it's only doing it when map changes (or when changing between mods). I can load up one map fine. Which is good enough. Though I'm already trying to download the older non-Crimson edition Radeon drivers (before 15.11) - see if that helps.

EDIT: Nope, 15.7 just CTDs all the time, as OP. Going back to 16.1 to see if it at least boots... :\

Win 10 Tip 2: Don't update Radeon drivers. Like, ever.

EDIT 2: 16.1s got back to at least running, crashing during map/mod change. Good enough I guess. Maybe they'll fix it in a later release...

Tip 3: Nvidia.

Last edited by pepsi_max2k (2016-01-31 23:42:24)

bud · 2016-02-01 15:19:08

Thanks for the update, not easy to find such "stupid" errors.

pepsi_max2k · 2016-02-01 18:02:17

Thanks. It causes one other specific issue that's a bit weird - usually after exiting a map the menu (at least on the server browser screen) doesn't show the secondary level of buttons. Ie. all the Update Server, Join Server buttons are invisible, plus the bottom punkbuster icons. Some weird graphical stuff there. They work, but they're just not visible. Makes me think it could be a rendering setting in drivers that just needs tweaking, but it's not like it's far off default settings as is. I better talk to some AMD guys and see what they think. Either way, if it is the drivers, surely it's not long before everyone with Radeons starts being affected?

Last edited by pepsi_max2k (2016-02-01 18:02:41)

(BB)DinkW · 2016-02-01 18:22:23

I can see all the people at Nvidia rubbing their hands together

SiMPLE | Forum

Announcement

#1 2016-01-08 22:26:39

Recent Win 10 update breaking 1942?

#2 2016-01-08 23:17:40

Re: Recent Win 10 update breaking 1942?

#3 2016-01-08 23:38:39

Re: Recent Win 10 update breaking 1942?

#4 2016-01-09 00:00:52

Re: Recent Win 10 update breaking 1942?

#5 2016-01-09 00:02:37

Re: Recent Win 10 update breaking 1942?

#6 2016-01-09 14:02:58

Re: Recent Win 10 update breaking 1942?

#7 2016-01-09 15:35:23

Re: Recent Win 10 update breaking 1942?

#8 2016-01-09 16:25:12

Re: Recent Win 10 update breaking 1942?

#9 2016-01-09 19:01:39

Re: Recent Win 10 update breaking 1942?

#10 2016-01-09 19:52:32

Re: Recent Win 10 update breaking 1942?

#11 2016-01-09 21:12:34

Re: Recent Win 10 update breaking 1942?

#12 2016-01-10 17:57:32

Re: Recent Win 10 update breaking 1942?

#13 2016-01-10 18:26:30

Re: Recent Win 10 update breaking 1942?

#14 2016-01-10 20:40:42

Re: Recent Win 10 update breaking 1942?

#15 2016-01-10 22:22:28

Re: Recent Win 10 update breaking 1942?

#16 2016-01-11 01:23:00

Re: Recent Win 10 update breaking 1942?

#17 2016-01-11 01:54:01

Re: Recent Win 10 update breaking 1942?

#18 2016-01-11 10:44:40

Re: Recent Win 10 update breaking 1942?

#19 2016-01-11 21:16:54

Re: Recent Win 10 update breaking 1942?

#20 2016-01-16 21:02:53

Re: Recent Win 10 update breaking 1942?

#21 2016-01-17 11:55:18

Re: Recent Win 10 update breaking 1942?

#22 2016-01-18 00:06:32

Re: Recent Win 10 update breaking 1942?

#23 2016-01-18 00:58:17

Re: Recent Win 10 update breaking 1942?

#24 2016-01-19 14:23:32

Re: Recent Win 10 update breaking 1942?

#25 2016-01-19 14:25:45

Re: Recent Win 10 update breaking 1942?

#26 2016-01-23 23:13:19

Re: Recent Win 10 update breaking 1942?

#27 2016-01-31 23:17:45

Re: Recent Win 10 update breaking 1942?

#28 2016-02-01 15:19:08

Re: Recent Win 10 update breaking 1942?

#29 2016-02-01 18:02:17

Re: Recent Win 10 update breaking 1942?

#30 2016-02-01 18:22:23

Re: Recent Win 10 update breaking 1942?

Board footer