Battlefield 4 BSOD after every multiplayer round

by Ryan-GBR
Reply

Original Post

Re: blue screen of death with BF4

★★★ Apprentice

english please. not making sense. 

Message 51 of 71 (3,337 Views)

Re: blue screen of death with BF4

★★★ Newbie

LOL thats smart, but have you ever had it crash during midgame? it happens a few times, but mostly during the next map transition causes the most BSOD. then it crashes HARD.

Message 52 of 71 (3,309 Views)

Re: Battlefield 4 BSOD after every multilayer round

★★★★ Novice

Use the link below and download and install the BETA 13.11Drivers!!

 

Then reboot!

 

http://support.amd.com/en-us/download/desktop?os=Windows%208%20-%2064

Message 53 of 71 (3,249 Views)

Re: Windows 8.1 Blue screen after game ends BAD_POOL_CALLER

★ Novice

Don't know if this helps, but I kept crashing in games after 8.1 update. Thing that seems to have fixed it is by going into the device manager, uninstalling and removing intel graphics driver, and then reinstalling the driver. I restarted as required.

 

My system is a laptop w HD4600 and a GTX770m, so i may have had some odd conflict. Good luck!

Message 54 of 71 (3,122 Views)

Bad Pool Caller Crash

★★★★ Novice

The only reason I am creating a new thread for this, is because the other one says this error was solved by an update to graphics card drivers. But, my computer is still getting BSOD'd after every game, even though I updated all my drivers. It only crashes when it loads the map for the next game, never any other time. The only work around I have been able to do that works, is quiting the game, and then re-joining it.

 

Here are my specs

 

Windows 8 64 bit

Intel Core i5-3570

CPU 3.40GHz

8Gigs of ram

AMD XFX R7700 graphics card

 

Any suggestions or advice?

Message 55 of 71 (3,084 Views)

Re: Battlefield 4

★★★ Newbie

upgrade your graphics card or get a better pc

Message 56 of 71 (2,802 Views)

Re: Bad Pool Caller Crash

★ Novice
I had the same issue. Win 8.1 64 with an amd 6970m card
Seem to have fixed it with 3 steps:
1 remove graphics drivers (google dismal driver uninstaller - there's some software someone has written called ddu which wipes amd/nvidia driver and software completely from your PC)
2 remove any other graphics devices/drivers (I was using air display to extend my screen and removed that)
3 install latest beta drivers

So far so good after about 4 hours of use (previously I'd always get a crash after playing that long)
Gl!
Message 57 of 71 (2,748 Views)

Re: BSOD between matches

★★ Apprentice

You would think that DICE would be all over this issue and fix it. This is completely rediculous that there is not a patch released yet to fix this issue. It seems to be related to the sychronizing of data to the cloud. I find it funny that people think new drivers will fix this issue when it is clearly a code error in the server software. Why, all of my other games run perfect, the test range/single player mode runs perfect and most importantly, the beta test they did ran just fine on my system during the testing period. I'm on the verge of demanding a full refund, this is just rediculous and no one from DICE is even coming into this thread and giving us any information.

Message 58 of 71 (2,640 Views)

Re: BSOD between matches

★ Apprentice

 

I own a Sapphire HD7970 OC 3GB and i'm getting random BSODs (13.11 v9.2):

 

Here's the WhoCrashed analysis:

 

"On Sun 24/11/2013 11:29:36 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\112413-22900-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x1A (0x783, 0xFFFFF88007FAF1F0, 0xFFFFF9803CB40000, 0xFFFFF8A011D4C880)
Error: MEMORY_MANAGEMENT
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Sun 24/11/2013 11:29:36 AM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x98DBF)
Bugcheck code: 0x1A (0x783, 0xFFFFF88007FAF1F0, 0xFFFFF9803CB40000, 0xFFFFF8A011D4C880)
Error: MEMORY_MANAGEMENT
file path: C:\Windows\system32\drivers\ntfs.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT File System Driver
Bug check description: This indicates that a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



On Thu 14/11/2013 11:47:12 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\111413-20716-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x7F (0x8, 0x80050033, 0x406F8, 0xFFFFF800042BE14E)
Error: UNEXPECTED_KERNEL_MODE_TRAP
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that the Intel CPU generated a trap and the kernel failed to catch this trap.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Mon 11/11/2013 6:50:36 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\111113-22573-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8000459F9D9, 0xFFFFF8800A5068F0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Sun 10/11/2013 11:26:07 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\111013-23478-01.dmp
This was probably caused by the following module: atikmpag.sys (atikmpag+0x8740)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF880052326BE, 0xFFFFF880075C5408, 0xFFFFF880075C4C60)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\atikmpag.sys
product: AMD driver
company: Advanced Micro Devices, Inc.
description: AMD multi-vendor Miniport Driver
Bug check description: This indicates that a system thread generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: atikmpag.sys (AMD multi-vendor Miniport Driver, Advanced Micro Devices, Inc.).
Google query: Advanced Micro Devices, Inc. SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M



Conclusion



5 crash dumps have been found and analyzed. A third party driver has been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers:

atikmpag.sys (AMD multi-vendor Miniport Driver, Advanced Micro Devices, Inc.)

If no updates for these drivers are available, try searching with Google on the names of these drivers in combination the errors that have been reported for these drivers and include the brand and model name of your computer as well in the query. This often yields interesting results from discussions from users who have been experiencing similar problems.


Read the topic general suggestions for troubleshooting system crashes for more information.

Note that it's not always possible to state with certainty whether a reported driver is actually responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further. "

Message 59 of 71 (2,620 Views)

Re: BSOD between matches

[ Edited ]
★ Novice

My game is crashing after every round. I can see the countdown for next map, and after the countdown reaches zero, the computer screens are black and the PC restarts.Sometimes all 3 screens flash red for a fraction of a seconds. 

Battlefield 4 is the only game on my comp that behaves this way. 

 

Why is this?


Im on the latest AMD official drivers for 7970, 13.9.

 

Windows 8.1

 

 

Message 60 of 71 (2,533 Views)