bSOD playing E:TW only started recently, never used to

[ihatewindowsomg]

I'm not sure why but for some reason lately during battles I'm getting a blue screen of death trying to play Empire: Total War.

I've updated my graphics and audio drivers to no avail, still crashing.

The dump zip file thingy attached

Computer typeEdit Value
PC/Desktop
Computer Manufacturer/Model NumberEdit Value
Custom
OSEdit Value
Windows 7 Ultimate (x64) Service Pack 1 (build 7601)
CPUEdit Value
AMD FX 6300 6-core 3.5ghz
MotherboardEdit Value
Gigabyte Technology Co., Ltd. GA-970A-DS3
MemoryEdit Value
8174 Megabytes Usable Installed Memory
Graphics Card(s)Edit Value
AMD Radeon HD 6800 Series [Display adapter]
Sound CardEdit Value
Asus Xonar DG
Hard DrivesEdit Value
WDC WD1600JS-22MHB0 [Hard drive] (160.04 GB) -- drive 1, s/n WD-WCANM4480587, rev 02.01C03, SMART Status: Healthy
WDC WD6400AAKS-75A7B2 [Hard drive] (640.13 GB) -- drive 0, s/n WD-WCASYA304992, rev 01.03B01, SMART Status: Healthy

Any help would be greatly appreciated thank you!

 

[Boozad]

Your OS installation is counterfeit. You have an Acer OEM PID on a Gigabyte motherboard.

[FONT=&quot]Host Name: WEWEW[/FONT]
[FONT=&quot]OS Name: Microsoft Windows 7 Ultimate [/FONT]
[FONT=&quot]OS Version: 6.1.7601 Service Pack 1 Build 7601[/FONT]
[FONT=&quot]OS Manufacturer: Microsoft Corporation[/FONT]
[FONT=&quot]OS Configuration: Standalone Workstation[/FONT]
[FONT=&quot]OS Build Type: Multiprocessor Free[/FONT]
[FONT=&quot]Registered Owner: TommyT[/FONT]
[FONT=&quot]Registered Organization: [/FONT]
[FONT=&quot]Product ID: 00426-OEM-8992662-00006[/FONT]
[FONT=&quot]Original Install Date: 17/07/2013, 15:34:19[/FONT]
[FONT=&quot]System Boot Time: 10/06/2014, 16:20:30[/FONT]
[FONT=&quot]System Manufacturer: Gigabyte Technology Co., Ltd.[/FONT]
[FONT=&quot]System Model: GA-970A-DS3[/FONT]
[FONT=&quot]System Type: x64-based PC[/FONT]
[FONT=&quot]Processor(s): 1 Processor(s) Installed.[/FONT]
[FONT=&quot] [01]: AMD64 Family 21 Model 2 Stepping 0 AuthenticAMD ~3500 Mhz[/FONT]
[FONT=&quot]BIOS Version: Award Software International, Inc. F4,

[/FONT]
Counterfeit installations such as yours contained heavily modified code that causes the installation to behave it unexpected ways. Analysing BSOD's and determining their causes on these sorts of installations is very unreliable. For this reason, many analysts won't attempt it.

My recommendation is to install a genuine Windows 7. This will minimise the problems you are experiencing, and make subsequent diagnosis of BSOD's far more reliable. Once you are running a genuine Windows 7 installation, and are still experiencing BSOD's, we will be happy to help you solve them

 

[ihatewindowsomg]

It's not counterfeit it's the same windows installation I had when I bought the computer 4 years ago, though come to think of it when I switched from Intel Pentium to AMD and got a new motherboard my dad did do a reinstall using his disc something about different chipsets I don't know I'm not computer savvy but it wasn't formatted so i shouldn't imagine it would have changed much.

Anyway this only started happening in the last few weeks it's worked perfectly fine for 4 years :/

But fine don't help then guess i'll play a different game -_-

 

[Thedoctor44]

BugCheck [COLOR="Red"]F4[/COLOR], {[COLOR="Blue"]3[/COLOR], [COLOR="SeaGreen"]fffffa80093e24b0[/COLOR], fffffa80093e2790, fffff8000377d270}

----- ETW minidump data unavailable-----
Probably caused by : [COLOR="SeaGreen"]wininit.exe[/COLOR]

wininit is the session 0 initialization which is marked as a critical system process, if terminated for any reason the system bugchecks which it has done.

Unfortunately, this isn't a Kernel Memory Dump so I can't check the virtual memory usage, therefore I cannot lean towards hardware or software.
We should try these tests first, then if no errors pop up switch to Kernel Memory Dumps.

Run a Disk Check to scan for errors

   Note

Afterwards go into an Elevated Command Prompt (Run as administrator) and type in sfc /scannow
If it finds errors reboot and run the scan two more times

Run SeaTools to see if your HDD or SSD is failing

Post back the results.

Follow these instructions on how to change to Kernel Memory Dumps.

http://www.sevenforums.com/tutorials/174459-dump-files-configure-windows-create-bsod.html

Once changed wait for another BSOD, then upload the new dump file to a file sharing website like OneDrive.
The new dump file will be located in C:/Windows/memory.dmp.

Don't zip it up as it corrupts the dump file by compressing it.

[COLOR="red"]Advanced SystemCare 7[/COLOR]	"c:\program files (x86)\iobit\advanced systemcare 7\asctray.exe" /auto	WEWEW\TommyT	HKU\S-1-5-21-1690549905-3012140248-608390324-1000\SOFTWARE\Microsoft\Windows\CurrentVersion\Run
[COLOR="Red"]DAEMON Tools Lite[/COLOR]	"c:\program files (x86)\daemon tools lite\dtlite.exe" -autorun	WEWEW\TommyT	HKU\S-1-5-21-1690549905-3012140248-608390324-1000\SOFTWARE\Microsoft\Windows\CurrentVersion\Run

These programs can cause BSODs, remove advanced system care then remove Daemon tools by following these instructions.

Daemon Tools/Alcohol is known cause of BSODs, you will have to find an alternative as there is no way around this.

Registry and SPTD problems | DAEMON Pro Help
How to remove sptd.sys from system

1. Uninstall Daemon Tools.
2. Download the SPTD standalone installer and follow these steps:
3. Double click the executable to open it
4. Click the button shown below

If the button it is grayed out, as shown in the image, there is no more SPTD installation on your system, and you can just close the window.


Yep, Boozad is correct, I missed that...
your installation is counterfeit, you must install genuine media.

 

[Brink]

It's not counterfeit it's the same windows installation I had when I bought the computer 4 years ago, though come to think of it when I switched from Intel Pentium to AMD and got a new motherboard my dad did do a reinstall using his disc something about different chipsets I don't know I'm not computer savvy but it wasn't formatted so i shouldn't imagine it would have changed much.

Anyway this only started happening in the last few weeks it's worked perfectly fine for 4 years :/

That's the problem then. OEM Windows are permanently tied to the motherboard, and can only be activated on the exact same computer. When you changed the motherboard, it's no longer the same computer and is why it will not activate.

You'll need to purchase a new retail copy of Windows to install and activate on your computer instead now.

But fine don't help then guess i'll play a different game -_-

A bad attitude like that will not get you any help.

 

[Arc]

You may try the http://www.sevenforums.com/tutorials/18715-activate-windows-7-phone.html way .... as the last resort. Explain the situation to them. They may try to generate an activation code for you.

 

[Thedoctor44]

You may try the http://www.sevenforums.com/tutorials/18715-activate-windows-7-phone.html way .... as the last resort. Explain the situation to them. They may try to generate an activation code for you.

Good idea Archie

 

[Arc]

It might not work; but better to have a try, IMHO.

I used this method a few times .... in critical situations. Never been unhappy with the result.

 

[ihatewindowsomg]

I'll try that ARc thanks.

And hmm interesting

I use both daemon tools AND Advanced Systemcare 7

I didn't know Systemcare could cause that stuff. Come to think of it I did only install that recently

Fixed: So I turned turbo boost off and then uninstalled Advanced SystemCare 7 and launched E:TW and went into quick battle

No BSOD! Thanks for your unofficial help i do appreciate it