BSOD since istallation of SWTOR

[RDM]

Hi,

Since installing Star Wars The Old Republic I have been getting quite a few BSOD. Mainly with Memory_Management errors. The system has been running fine before that.

System will run happily until I start SWTOR which will then eventually crash, or the system will crash soon after I exit it.

Attached is all the information as requested, thanks in advance for any help!

 

[zigzag3143]

Hi,

Since installing Star Wars The Old Republic I have been getting quite a few BSOD. Mainly with Memory_Management errors. The system has been running fine before that.

System will run happily until I start SWTOR which will then eventually crash, or the system will crash soon after I exit it.

Attached is all the information as requested, thanks in advance for any help!

These crashes were caused by memory corruption (probably a driver). Please run these two tests to verify your memory and find which driver is causing the problem.

If you are overclocking anything reset to default before running these tests.
In other words STOP!!!


1-Memtest.

*Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Memtest86+ - Advanced Memory Diagnostic Tool

*Boot from the CD, and leave it running for at least 5 or 6 passes.

Just remember, any time Memtest reports errors, it can be either bad RAM or a bad motherboard slot.

Test the sticks individually, and if you find a good one, test it in all slots.

Any errors are indicative of a memory problem.

If a known good stick fails in a motherboard slot it is probably the slot.

http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html



2-Driver verifier

Using Driver Verifier is an iffy proposition. Most times it'll crash and it'll tell you what the driver is. But sometimes it'll crash and won't tell you the driver. Other times it'll crash before you can log in to Windows. If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.

I'd suggest that you first backup your data and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).

In Windows 7 you can make a Startup Repair disk by going to Start....All Programs...Maintenance...Create a System Repair Disc - with Windows Vista you'll have to use your installation disk or the "Repair your computer" option at the top of the Safe Mode menu .

Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.

Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).

If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.

http://www.sevenforums.com/tutorials/101379-driver-verifier-enable-disable.html


Further Reading
Using Driver Verifier to identify issues with Windows drivers for advanced users

 

[RDM]

Thanks for that zigzag3143.

With verifier running according to your instructions windows lasted a full 10 seconds after log in before crashing with a Driver_Verifier_Detected_Violation. Both times on ASACPI.sys.

Is this likely to be my culprit? If so, how do I go about making it better?

 

[zigzag3143]

Thanks for that zigzag3143.

With verifier running according to your instructions windows lasted a full 10 seconds after log in before crashing with a Driver_Verifier_Detected_Violation. Both times on ASACPI.sys.

Is this likely to be my culprit? If so, how do I go about making it better?

Asacpi.sys is a HUGE cause of BSOD's You should also turn verifier off.

Asacpi.sys

The pre 2009 version of this driver is a known bsod cause.

Please visit this link: Asus tek computer inc. -support- drivers and download p7p55d le

ASUSTeK Computer Inc. -Support- Drivers and Download P7P55D LE
ASUSTeK Computer Inc. - Motherboards- ASUS P5K-VM

Scroll down to the utilities category, then scroll down to the "atk0110 driver for windowsxp/vista/windows 7 32&64-bit" (it's about the 12th item down).

Download and install it.

Go to c:\windows\system32\drivers to check and make sure that the asacpi.sys file is date stamped from 2009 or 2010 (notbefore).

 

[Lemur]

It's an ACPI utility. Go to AsusTek and find the latest driver for this. I don't know if you have Rampage II Extreme or Rampage II Gene

 

[RDM]

Booted into Safe Mode and turned verifier off.

Asus Rampage II Extreme (they really need to come up with some slightly less geeky names...). Followed the advice and downloaded the 2009 version of the driver (the previous one seems to have been a 2005 one). Will give SWTOR and blast and see if this has solved my issues.

Thanks for all the help!

 

[zigzag3143]

Booted into Safe Mode and turned verifier off.

Asus Rampage II Extreme (they really need to come up with some slightly less geeky names...). Followed the advice and downloaded the 2009 version of the driver (the previous one seems to have been a 2005 one). Will give SWTOR and blast and see if this has solved my issues.

Thanks for all the help!

If you had the 2005 version I am sure the 2009 will fix it.

 

[RDM]

So far so good, system seems to be relatively stable with no crashes. Will give it a day or two before marking as solved just to make sure.

Thanks a lot for your help zigzag.

 

[zigzag3143]

So far so good, system seems to be relatively stable with no crashes. Will give it a day or two before marking as solved just to make sure.

Thanks a lot for your help zigzag.

My pleasure and good luck

 

[RDM]

Spoke too soon. System is certainly more stable but SWTOR will still cause it to crash if I try and use it more than once or for an extended period of time. However it gave me a different BSOD, this time BAD_POOL_HEADER. Will try the dirver verifier again and have attached the dmp file.

 

[RDM]

Well driver verifier running caused another asacpi crash seconds after log in. Tried running driver verifier without asacpi selected to see if someone else was also causing a problem. Running SWTOR with verifier enabled gave me a new crash, a new blue screen and a new error: SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION

Verifier enabled dmp file attached.

 

[Lemur]

Try running memtest86+. Let it make at least 7 passes ...

Memtest86+ - Advanced Memory Diagnostic Tool

 

[zigzag3143]

Well driver verifier running caused another asacpi crash seconds after log in. Tried running driver verifier without asacpi selected to see if someone else was also causing a problem. Running SWTOR with verifier enabled gave me a new crash, a new blue screen and a new error: SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION

Verifier enabled dmp file attached.

Veriified and related to win2k.sys. Please run system file check

Run a system file check to verify and repair your system files.

To do this type cmd in search, then right click to run as administrator, then
SFC /SCANNOW

It may need to be run up to three times before successful
Let us know the results from the report at the end.

Read here for more information http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html

 

[RDM]

SFC /SCANNOW came back with no errors. Will run memtest86+ again but it didnt come up with anything last time unfortunately.

 

[RDM]

Memtest came back with no errors. At a bit of a loss now.

 

[mocax]

i'm almost certain it's SWTOR making some illegal calls that cause a widespread memory corruption.
first my AMD/ATI HD6850 drivers got corrupted, and had to do a clean reinstall. then it managed to corrupt my regional locale, causing my ASUS and Intel utilities to display chinese text.

I've uninstalled SWTOR and reinstalled all my system drivers.

Will monitor another week without SWTOR to see if there're anymore BSoDs...

It doesn't help that SWTOR requires UAC elevation to run, a big no no nowadays.