Windows 7: BSOD upon starting StarCraft 2, error not known

ToxicXGL · 26 Dec 2012

I recently have had a BSOD right after installing some new ram and a new graphics card. I encountered it right after starting up star craft 2 for the second time and i received this error. I have had this error before after i opened up LeBot and this was before any upgrading why am i getting these errors?

Arc · 27 Dec 2012

Post it following the Blue Screen of Death (BSOD) Posting Instructions .

ToxicXGL · 27 Dec 2012

Ok i have attached the file

Arc · 28 Dec 2012

So it is Symantec Heuristics Driver that crashed your computer.

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 6, {0, 0, 0, 0}

*** WARNING: Unable to verify timestamp for BHDrvx64.sys
*** ERROR: Module load completed but symbols could not be loaded for BHDrvx64.sys
Probably caused by : BHDrvx64.sys ( BHDrvx64+c51b4 )

Followup: MachineOwner
---------

Also Norton Internet Security is contributing in the crash.

Code:

fffff880`1197d490  fffff880`06cbd090Unable to load image \??\C:\Windows\system32\Drivers\SYMEVENT64x86.SYS, Win32 error 0n2
*** WARNING: Unable to verify timestamp for SYMEVENT64x86.SYS
*** ERROR: Module load completed but symbols could not be loaded for SYMEVENT64x86.SYS
 SYMEVENT64x86+0x22090

And Symantec Extended File Attributes

Code:

fffff880`1197d058  fffff880`01249a6fUnable to load image \SystemRoot\system32\drivers\N360x64\1401010.002\SYMEFA64.SYS, Win32 error 0n2
*** WARNING: Unable to verify timestamp for SYMEFA64.SYS
*** ERROR: Module load completed but symbols could not be loaded for SYMEFA64.SYS
 SYMEFA64+0x1a6f

Uninstall Norton and all Symentec products using Norton Removal tool. Use Microsoft Security Essentials as your antivirus with windows inbuilt firewall, and free MBAM as the on demand scanner.

Download and install those, and then run full system scans with both of them, one by one.

Daemon Tools, Alcohol 120% and Power Archiver Pro uses SCSI Pass Through Direct (SPTD), which is a well known BSOD causer. Uninstall Daemon Tools at first. Then download SPTD standalone installer from Disk-Tools.com, and execute the downloaded file as guided below :

Double click to open it.
Click this button only:
If it is grayed out, as in the picture, there is no more SPTD in your system, and you just close the window.

Free up the startup.

Click on the Start button
Type “msconfig (without quotes), click the resulting link. It will open the System Configuration window.
Select the “Startup” tab.
Deselect all items other than the antivirus.
Apply > OK
Accept the restart.

Let us know the results.

ToxicXGL · 30 Dec 2012

Ok so all that you asked for has been done MSE found 1 Trojan and got rid of it, and MBAM found some things ill put the notepad file below for you as well as i deleted those items, and i have uninstalled Daemon Tools and loaded up SPTD the uninstall was grayed out.

Arc · 30 Dec 2012

Well done

Now let us know how it is performing.

ToxicXGL · 30 Dec 2012

So far nothing has happen but the previous BSODs were random so is there anyway of making sure the problem is dealt with? Also does this mean that i cannot use Norton because i did pay for it so i am hoping that i can get my moneys worth out of it

Arc · 30 Dec 2012

Quote: Originally Posted by ToxicXGL

So far nothing has happen but the previous BSODs were random so is there anyway of making sure the problem is dealt with? Also does this mean that i cannot use Norton because i did pay for it so i am hoping that i can get my moneys worth out of it

About the money, sorry it is really out of my jurisdiction. What I experienced that Norton causes BSODs frequently, and MSE never. So, from the BSOD perspective, I'd always suggest you to use MSE. If you can compromise with those crashes, freely use Norton.

Wait and observe the situation, say a week, a fortnight or a month. Report then back, or report back when another crash takes place at an earlier time.

ToxicXGL · 30 Dec 2012

Ok thanks for the help i will see how this plays out

ToxicXGL · 30 Jan 2013

Another BSOD this time while playing zoids on the dolphin emulator.

Windows 7: BSOD upon starting StarCraft 2, error not known

BSOD upon starting StarCraft 2, error not known problems?