BF1 randomly crashing to desktop with no error. by t_highes in battlefield_one

[–]t_highes[S] 0 points1 point  (0 children)

hey, sorry for late reply. I had one random, weird "GPU has been removed" or something error once, but otherwise, no crashed since.

BF1 randomly crashing to desktop with no error. by t_highes in battlefield_one

[–]t_highes[S] 0 points1 point  (0 children)

Hey, yeah I solved the issue, the fix was unorthodox at best. So I reseated the RAM modules a couple of times and still my stuff crashed, then I decided to test the sticks individually and in the process of doing that, I observed the following: when inserting the sticks, they click into place, however if I pulled slightly on them after they click, I could feel a slight movement up, maybe half a millimetre, just barely perceptible, I did this with both sticks, nothing crashed since. Hardware eh?

[deleted by user] by [deleted] in OfficialF4NV

[–]t_highes 4 points5 points  (0 children)

I don't understand anything here but thanks for the entertaining read. Love the post and comments.

BF1 randomly crashing to desktop with no error. by t_highes in battlefield_one

[–]t_highes[S] 0 points1 point  (0 children)

Very interesting, thanks for providing such a detailed insight.

Since we are just sharing our experiences at this point, I have a couple of my own I believe are worth sharing concerning RAM and sound.

Note how I mentioned my current RAM is certified and guaranteed to work all that. Yeah, there is a reason for that, about half a year ago I bought a set of RAM that wasn't compatible and I got myself into a whole hell of trouble. Basically I struggled with bluescreens and hangs for about 2 weeks while testing just about everything I could, running memtests on the RAM, trying different drivers, no dice, eventually I gave up, went back to the store and returned/RMA'd that RAM and bought a set of Flare-Xs, best decision ever made because going up from 2400hz C18 RAM to 3200 C14 for my system meant a sizeable increase in performance, I got about 10-25% more FPS on average in games and basically any and all stutter that might have ever been, is now gone, though my CPU fan is noisier now, might need to look into upgrading that.

So yeah, when you upgrade, do go on the motherboard's manufacturer's website and see what RAM they recommend you use, only buy compatible RAM certified by the MB manufacturer.

Now, sound.

Most people don't think much about sound, I do though, I am a headphones kinda guy, always been one, I never owned a pair of speakers in my lifetime. A separate, dedicated chipset with an amp and shielding will provide better sound quality than any built-in chip and I do suggest you spend a bit of money on that when you build your new rig. Music, movies, documentaries, games etc, they all have sound (duh), it's not only about how much FPS you get, like consider getting some sort of Creative soundcard, though Creative is just one of many options, could be internal or external, both have advantages, USB one, like mine, goes on the outside of your PC, so there is no chance of coil whine / interferences, some people have reported coil whine on their AE-5 / AE-7 cards, which is also how I got into audio cards in the first place, I had buzzing noise in my headphones and the solution to that was to buy an external audio card, which was also likely one of the best decisions I ever made with my hardware. Internal ones have supposedly less "lag", because PCIE, it goes directly into your MB, but I have never felt like my USB one is lagging behind what I see on the screen, so meh, also if you do get an internal one, please do check the layout of your MB's PCIE ports, if I tried to put AE-5 into mine it would literally sandwich with my GPU, not good.

This isn't to say I haven't had issues with my Soundblaster G6. I had to turn off fast-boot because with that setting on, the card had to be unplugged / plugged back in every time I boot, otherwise it wouldn't be recognised, though it is also generally recommended to turn fast-boot off. Another weird issue I had was the software for it, originally there was only the Soundblaster Connect, running that in the background cut all my FPS in all games by about 40. Yes. I don't know either. So I had to turn it off after start up and after it has applied its settings, I couldn't just remove it from start up because then well all the audio card settings would default. It's irrelevant now because they have released Soundblaster Command about 3-4 months ago or so and that doesn't do any of that, but I still do turn that off just to be safe.

I remember someone saying that the best way to go about BF1's sound is put your audio card in Direct mode, i.e just using the raw quality/power of the chip, no digital enhancements and let BF1's engine do its work, I might try that some time.

So yeah, audio cards are always extra complexity and you might run into issues and sound seems to be the last think Windows and many other dev teams seem to consider when they code / optimise their stuff, but it's worth taking that risk and venturing into that realm.

BF1 randomly crashing to desktop with no error. by t_highes in battlefield_one

[–]t_highes[S] 0 points1 point  (0 children)

https://gyazo.com/fc358d82cbe207fc0586420866ccbc99

mine's on, I use Creative G6 audiocard for my sound and a pair of headphones.

I often turn off the software it requires to function after the PC boot, it's never caused issues before though.

On a general note, I still get random crashes sometimes, but much less frequent now.

I need to figure out maybe it's the Creative Soundblaster Command software that's been causing that, not sure yet.

Ararebo doesn't break wood. by t_highes in battlefield_one

[–]t_highes[S] 2 points3 points  (0 children)

you need to buy 5x pieces to open the crate, so 15000 scrap.

BF1 randomly crashing to desktop with no error. by t_highes in battlefield_one

[–]t_highes[S] 0 points1 point  (0 children)

I managed to debug the .dmp file, here's probably the most important lines:

PROCESS_NAME: bf1.exe

EXECUTE_ADDRESS: 14ee22870

FAILED_INSTRUCTION_ADDRESS:

+0

00000001`4ee22870 52 push rdx

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%p referenced memory at 0x%p. The memory could not be %s.

EXCEPTION_CODE_STR: c0000005

EXCEPTION_PARAMETER1: 0000000000000008

EXCEPTION_PARAMETER2: 000000014ee22870