BSOD Playing BF3, 0x0000124

Both report a generic bus error that occurred between what I guess is crosstalk between CPU L0 instruction cache and some external cache like video card or RAM. Update BIOS and all motherboard component drivers, and uninstall all software/utilities that came with the motherboard. You may need to use Driver Sweeper (free) to assist in that, just to make sure they're gone for good and haven't left behind anything (which they often do).

Btw, I noticed a very odd-looking driver that was loaded, called ab6kffft.SYS. It does not show up in any driver list and google comes up nil. It looks like a randomly-generated driver name (or it's just a corrupt module list), which if that's the case, then the only things I see that often use random driver names are malware and Daemon Tools. Update Daemon Tools and its SPTD driver to their latest, but do know that DT has been known to be a bit buggy. As for possible infection, if you're concerned you may want to head over to the security subforum here at SF and deal with it there. Make sure to link to this thread for reference.

We should try to get a bit more info here. First, a question: does this ever happen with any other games with high graphics? Just to make absolutely sure we aren't dealing with a faulty driver, turn on BF3, then when it's up, minimize it and setup Driver Verifier. Remember to follow instructions as specified, click the "Finish", and restart PC. If you do not restart the PC afterwards, the changes will be lost. Hopefully your system will crash again after Driver Verifier is setup, in which case provide us the crashdumps. Try playing BF3 and get it to crash then as well if it doesn't otherwise crash earlier.

You will want to do some hardware tests. Run Memtest86+ overnight as well as a run of Prime95 on torture test with blend settings. Let that run for one night as well. If system crashes or the run fails, follow up with another overnight run of Prime95 on large FFT settings instead of blend.

Thanks for your reply,

I got Daemon Tools but im thinking to remove that.
at the moment i only play BF3 and Minecraft, it didn't happen with minecraft but that game isn't heavy at all.

I did the set up for Driver Verifier, and played some bf3 but the BSOD didn't come earlier, but it happened!
btw, windows says that i had a BSOD, but i still didn't see it anyway, only a freezed screen + sound, well... i uploaded the crash dump files hope u can find anything!

(101812-46722-01 is the last one)

Same problem, it didn't look like DV caught anything. Did you make sure to start up BF3, start up and setup Driver Verifier while BF3 was running, and then after finishing setting up DV, restarted the PC and then tried running BF3 again? The only reason why I ask you to run BF3 first before setting up Driver Verifier is because DV will only list modules (drivers) that are currently loaded, and BF3 includes some like for anticheating that may be buggy. By starting DV up when BF3 is on, it'll list those drivers which you would select, and then restart DV to save all DV changes and then start BF3 again to let DV test the drivers.

If you did setup DV properly and this was the crashdump that was related to your latest BF3 crash, then it sounds like we have a hardware issue. Still, deal with the BIOS, motherboard drivers, motherboard software, and Daemon Tools as previously instructed. If that does not remedy the situation, then run the hardware tests and try swapping the video card for another one or test with onboard video (if available) to see if those also will crash. If they remain stable on BF3 (regardless how sluggish it may get), then we're looking at a bad video card.

I will try DV again, update soon...

You said you have a new dump file but the latest one here is the one from your previous post. Did it crash when Driver Verifier was active?

The only viable graphics tests are either hardware swapping or to test other hardware components first, then if those all look good, run benchmarks like Heaven and Furmark (you'll want DirectX11 on Heaven as Furmark just tests OpenGL). If they are unstable, you got video card issues most likely. Unfortunately, there are no appropriate hardware diagnostic tests for video cards. There used to be MemtestCL, but it's very outdated and buggy on newer systems, so it's not reliable.

The last one is with a new dump file, but i also uploaded the lastest dump file ive got in this post.

Memtest completed without any errors.
i did a furmark test. Burn in 5 mins and benchmark 1 min @
1920x1080 (FS) - AA:0 samples
FPS: min:27, max:29, avg:26

and Heaven with a max fps of 67 and min 13 (i think because of loading)

it really should be an extended period of time for each benchmark. Best to just let it loop infinitely for a while, about a couple hours each or until you view signs of artifacting or instability.

Another of the same crashdumps with the same error. I'm afraid we are looking at hardware problems here. Let's continue that route. How long did you run Memtest, btw? Should be at least 7+ passes (all tests ran once = 1 pass).