Solved BSOD playing Battlefield 3

[Trasan]

Recently installed and started playing Battlefield 3 today and it all went fine for about half an hour or so, and then the BSOD came the first time.

Didn't think much of it then and just rebooted thinking it was a random event.

It wasn't..

Restarted Battlefield 3 and the problem occurred yet again..and a third time after that.

Should also note that the temperatures on both GPU and CPU never go above 70 degrees Celsius.

The weird part is that I can play any other game I have without any problem, with highest setting, Borderlands 2, Crysis 3 etc etc.

Thanks in advance!

 

[Dsprague]

Please post the following here, DO NOT start a new thread: http://www.sevenforums.com/windows-...ne-activation-issue-posting-instructions.html

 

[Trasan]

Diagnostic Report (1.9.0027.0):
-----------------------------------------
Windows Validation Data-->

Validation Code: 0
Cached Online Validation Code: N/A, hr = 0xc004f012
Windows Product Key: *****-*****-TMVMJ-BBMRX-3MBMV
Windows Product Key Hash: 55n8g6xdzhe4AOWhmTzdzQoLfa4=
Windows Product ID: 55041-292-0000007-85588
Windows Product ID Type: 5
Windows License Type: Retail
Windows OS version: 6.1.7601.2.00010100.1.0.001
ID: {83CBEA3C-B1BF-4657-B406-0C3B66966BF1}(1)
Is Admin: Yes
TestCab: 0x0
LegitcheckControl ActiveX: N/A, hr = 0x80070002
Signed By: N/A, hr = 0x80070002
Product Name: Windows 7 Ultimate
Architecture: 0x00000009
Build lab: 7601.win7sp1_gdr.130318-1533
TTS Error: 
Validation Diagnostic: 
Resolution Status: N/A

Vista WgaER Data-->
ThreatID(s): N/A, hr = 0x80070002
Version: N/A, hr = 0x80070002

Windows XP Notifications Data-->
Cached Result: N/A, hr = 0x80070002
File Exists: No
Version: N/A, hr = 0x80070002
WgaTray.exe Signed By: N/A, hr = 0x80070002
WgaLogon.dll Signed By: N/A, hr = 0x80070002

OGA Notifications Data-->
Cached Result: N/A, hr = 0x80070002
Version: N/A, hr = 0x80070002
OGAExec.exe Signed By: N/A, hr = 0x80070002
OGAAddin.dll Signed By: N/A, hr = 0x80070002

OGA Data-->
Office Status: 109 N/A
OGA Version: N/A, 0x80070002
Signed By: N/A, hr = 0x80070002
Office Diagnostics: 025D1FF3-364-80041010_025D1FF3-229-80041010_025D1FF3-230-1_025D1FF3-517-80040154_025D1FF3-237-80040154_025D1FF3-238-2_025D1FF3-244-80070002_025D1FF3-258-3

Browser Data-->
Proxy settings: N/A
User Agent: Mozilla/4.0 (compatible; MSIE 8.0; Win32)
Default Browser: C:\Program Files (x86)\Google\Chrome\Application\chrome.exe
Download signed ActiveX controls: Prompt
Download unsigned ActiveX controls: Disabled
Run ActiveX controls and plug-ins: Allowed
Initialize and script ActiveX controls not marked as safe: Disabled
Allow scripting of Internet Explorer Webbrowser control: Disabled
Active scripting: Allowed
Script ActiveX controls marked as safe for scripting: Allowed

File Scan Data-->
File Mismatch: C:\Windows\system32\systemcpl.dll[6.1.7600.16385], Hr = 0x800b0100
File Mismatch: C:\Windows\system32\user32.dll[6.1.7600.16385], Hr = 0x800b0100

Other data-->
Office Details: <GenuineResults><MachineData><UGUID>{83CBEA3C-B1BF-4657-B406-0C3B66966BF1}</UGUID><Version>1.9.0027.0</Version><OS>6.1.7601.2.00010100.1.0.001</OS><Architecture>x64</Architecture><PKey>*****-*****-*****-*****-3MBMV</PKey><PID>55041-292-0000007-85588</PID><PIDType>5</PIDType><SID>S-1-5-21-4122039028-49690979-2550169567</SID><SYSTEM><Manufacturer>System manufacturer</Manufacturer><Model>System Product Name</Model></SYSTEM><BIOS><Manufacturer>American Megatrends Inc.</Manufacturer><Version>0804   </Version><SMBIOSVersion major="2" minor="5"/><Date>20081030000000.000000+000</Date></BIOS><HWID>37473C07018400FE</HWID><UserLCID>0809</UserLCID><SystemLCID>0409</SystemLCID><TimeZone>W. Europe Standard Time(GMT+01:00)</TimeZone><iJoin>0</iJoin><SBID><stat>3</stat><msppid></msppid><name></name><model></model></SBID><OEM/><GANotification/></MachineData><Software><Office><Result>109</Result><Products/><Applications/></Office></Software></GenuineResults>  

Spsys.log Content: 0x80070002

Licensing Data-->
Input Error: Can not find script file "C:\Windows\system32\slmgr.vbs".

Windows Activation Technologies-->
HrOffline: 0x00000000
HrOnline: N/A
HealthStatus: 0x0000000000000000
Event Time Stamp: N/A
ActiveX: Registered, Version: 7.1.7600.16395
Admin Service: Not Registered - 0x80070005
HealthStatus Bitmask Output:


HWID Data-->
HWID Hash Current: OgAAAAIABAABAAEAAQAEAAAAAQABAAEA1gTkZtpodxaMJmhlRryENOIA+vlqyEJ94EUKEaOgRCTqgg==

OEM Activation 1.0 Data-->
N/A

OEM Activation 2.0 Data-->
BIOS valid for OA 2.0: yes, but no SLIC table
Windows marker version: N/A
OEMID and OEMTableID Consistent: N/A
BIOS Information: 
  ACPI Table Name	OEMID Value	OEMTableID Value
  APIC			103008		APIC2212
  FACP			103008		FACP2212
  HPET			103008		OEMHPET 
  MCFG			103008		OEMMCFG 
  OEMB			103008		OEMB2212
  OSFR			103008		OEMOSFR 
  SSDT			DpgPmm		CpuPm

 

[Dsprague]

I looked through your files and a few things come to mind about the type of BSOD you are having which is a 0x124. Firstly if you are doing ANY over clocking stop the type of error you are getting is indicative of a failed OC. Next please see if there is an update for your BIOS as this type of error can be caused by a BIOS bug.

If both of those things are done begin doing some hardware stress testing:
Prime95:
Free Software - GIMPS

Prime95 Setup:
- extract the contents of the zip file to a location of your choice
- double click on the executable file
- select "Just stress testing"
- select the "Blend" test. If you've already run MemTest overnight you may want to run the "large FFTs" test instead.
- "Number of torture test threads to run" should equal the number of CPU's times 2 (if you're using hyperthreading).
The easiest way to figure this out is to go to Task Manager...Performance tab - and see the number of boxes under CPU Usage History
Then run the test for 6 to 24 hours - or until you get errors (whichever comes first).
The Test selection box and the stress.txt file describes what components that the program stresses.

Furmark:
FurMark: VGA Stress Test, Graphics Card and GPU Stability Test, Burn-in Test, OpenGL Benchmark and GPU Temperature | oZone3D.Net

FurMark Setup:
- If you have more than one GPU, select Multi-GPU during setup
- In the Run mode box, select "Stability Test" and "Log GPU Temperature" (BurnIn test in newer versions).
Click "Go" to start the test
- Run the test until the GPU temperature maxes out - or until you start having problems (whichever comes first).
- Click "Quit" to exit

other thoughts:

I not you have Daemon tools installed, it is known to cause BSODs please uninstall it then download and run this tool:

DuplexSecure - Downloads

when the tool runs if the uninstall button is grayed out then your done and can close the window. DO NOT click the install button it will install a driver known to cause BSODs

you may also want to preform a clean boot to troubleshoot any application conflicts:

http://www.sevenforums.com/tutorial...ation-conflicts-performing-clean-startup.html

 

[Trasan]

Alright. Cant try it out today because I have to go to work in a while.

However when I OC'd I ran Prime95 for a couple of hours withour errors or overheating.

But as I said, will try it all out later tonight/tomorrow and come back with the results by then.

Thanks so far.

 

[Dsprague]

I look forward to your results

 

[Layback Bear]

I do believe this code means their is a activation problem.
0xc004f012

 

[NoelDP]

The installation is counterfeit - enabled by the hacker's tool RemoveWAT.

You need to reformat and reinstall using genuine media - or at least get rid of the hack using either the original RemoveWAT in Restore mode, or using the WATFix tool
WATFix

 

[gregrocker]

Do you own a copy of Win7 you can use to do a Clean Install Windows 7 now?

Be sure to delete all partitions during booted Custom Install, using the Drive Options shown in Steps 7 and 8.

 

[Trasan]

Okay I solved it after much testing.
I reset my OC to default, didn't help.
Thought it might be my Memory-sticks not working properly, It wasn't.
Ran Furmark, and Prime95, no issues there.
Clean boot didn't help either.
Then I disabled the integrated soundcard, and it seems like the problem is gone.
So if anyone else get the same problem, go to BIOS and disable it and it might just solve your problem aswell.