Windows 7: bsod playing bf3 error 1033

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.256.1
Locale ID: 1033



Additional information about the problem:
BCCode: 124
BCP1: 0000000000000000
BCP2: FFFFFA8004866038
BCP3: 00000000B2000040
BCP4: 0000000000000800
OS Version: 6_1_7601
Service Pack: 1_0
Product: 256_1


having this issue for awhile playing bf3 sytem is stable everything else seems fine new os pc about 3 yrs old new graphics card ram and psu later Im out of ideas pc runs flawless dont really want to upgrade to a new system yet so would be appreciate for any help, cheers.

Hi and welcome to Seven Forums,

If you are overclocking any hardware, please stop.


Please remove the following software:
It is not recommended to use automated driver update software. The software often finds drivers for devices that are similar but not the same as the devices in your system. This can lead to conflict issues and BSOD's. If you cannot find the driver for a specific device, create a thread here: Drivers - Windows 7 Forums so we can help you. In fact, it is not always necessary to update drivers and sometimes updating them can decrease system stability. It it ain't broke, don't fix it!


I have noticed that you do not have an anti-virus product installed on your PC. Please install Microsoft Security Essentials and scan your PC. Then install and scan your computer with Malwarebytes' Anti-Malware. DO NOT START THE FREE TRIAL. This will remove any viruses you may have caught.


Taking a look at your dumps, a lot of the show the the cause as being genuine Intel. This suggests to me that there is a hardware issue.

As a result I recommend you check your hardware for issues. Please run Memtest86+ to check your RAM. Let it run for 6-8 passes overnight as described in the tutorial. Pay particular attention to parts 2 and 3.

Also check your HDD for errors using Seatools. Download and create a bootable version of the Seatools for DOS program as described here

If you have any questions, feel free to ask,
Stephen

for some reason its working fine with a "sfc /scannow" from cmd it is a fresh os install and i have overclocked it to 3.2 GHz with memtest and a few benchmarks with no errors ever except bf3 i will check with Anti virus just haven't got around to it yet but i doubt it has anything to do with the bsod the hdd is about a month old and give it a check, but what bothers me is the CPU if its a genuine Intel dump issue it could be the fact its ES version which i didn't know about until recently or the main board could be on its way, thanks for the response its given me something to go on.

Just a note, not being nit-picky or rude, but could you please use some punctuation (full stops, capital letters etc.) in your posts? It would make my life easier.

Could you please run through the memtest and seatools tests and report back once they have completed. Once you do that, I can rule out the RAM and then focus on the CPU. It is possible that there are CPU issues but I can't say without running some tests.

It is also possible running the SFC /Scannow command could have stabilised the system, you might have just had some corrupt system files. If you get any more BSOD's, run back through the http://www.sevenforums.com/crashes-d...tructions.html and upload the file to another post so I can look at the dumps.

Stephen

How did you do your overclock? All your crashes are 0x124 Hardware stop errors. This indicates an unstable overclock. Your QPI/VTT or VCore Voltage is not where it needs to be for the overclock to run stable. They either need to be increased or decreased because one of them is providing too little or too much voltage for the CPU overclock. Make sure to change voltages in very small increments because drastic changes can damage hardware permanently.

It may also be that your overclock has caused hardware degradation and you are now experiencing the effect that an overclock will have on hardware. It reduces the lifetime.


If the QPI/VTT or VCore voltage changes do not resolve the hardware crashes, you need to turn off the overclock immediately to prevent further hardware damage.

Stop 0x124 - what it means and what to try