Random BSOD while playing Newest games

Hello abyssninja. Have a look. It is norton that is crashing your computer.

Code:

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

Use !analyze -v to get detailed debugging information.

BugCheck 50, {fffffa000d480c10, 0, fffff8800136976b, 7}

*** WARNING: Unable to verify timestamp for SYMEFA64.SYS
*** ERROR: Module load completed but symbols could not be loaded for SYMEFA64.SYS

Could not read faulting driver name
Probably caused by : SYMEFA64.SYS ( SYMEFA64+11076b )

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

Description here: Driver Reference Table - SYMEFA64.SYS.

Also another component of norton 360 ...

Code:

fffff880`0a9e3958  fffff880`01157da5Unable to load image \SystemRoot\system32\drivers\N360x64\1402010.016\SYMDS64.SYS, Win32 error 0n2
*** WARNING: Unable to verify timestamp for SYMDS64.SYS
*** ERROR: Module load completed but symbols could not be loaded for SYMDS64.SYS
 SYMDS64+0x2da5

Description here: Driver Reference Table - SYMDS64.SYS

Razer Lycosa ... a very well known cause of the BSODs ....

Code:

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

Use !analyze -v to get detailed debugging information.

BugCheck 1E, {0, 0, 0, 0}

*** WARNING: Unable to verify timestamp for Lycosa.sys
*** ERROR: Module load completed but symbols could not be loaded for Lycosa.sys

Probably caused by : Lycosa.sys ( Lycosa+1c23 )

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

And the driver is very old.

Code:

fffff880`02400000 fffff880`02407100   Lycosa   T (no symbols)           
    Loaded symbol image file: Lycosa.sys
    Image path: \SystemRoot\system32\drivers\Lycosa.sys
    Image name: Lycosa.sys
    Timestamp:        Wed Sep 08 08:31:26 2010 (4C86FC86)
    CheckSum:         0001462D
    ImageSize:        00007100
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Update it from Razer Support

Finally come to the graphics related crash. It is evident that your display driver is not the latest one.

Code:

fffff880`04a00000 fffff880`04a8d000   atikmpag T (no symbols)           
    Loaded symbol image file: atikmpag.sys
    Image path: \SystemRoot\system32\DRIVERS\atikmpag.sys
    Image name: atikmpag.sys
    Timestamp:        Thu Dec 20 01:02:55 2012 (50D21667)
    CheckSum:         00095A98
    ImageSize:        0008D000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Update your ATI/AMD display driver.
You can get it from the link in our forum, Latest AMD Catalyst Video Driver for Windows 7, or you may go to AMD Graphics Driver and Software and opt for Automatically Detect and Install the appropriate driver for your card.


During installation, you may opt for advanced installation, and install the display driver only, not the Catalyst Control Center.

Have another look ....

Code:

STACK_COMMAND:  kb

FOLLOWUP_IP: 
dxgmms1!VIDMM_MEMORY_SEGMENT::EvictResource+430
fffff880`04732bf0 44846920        test    byte ptr [rcx+20h],r13b

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  dxgmms1!VIDMM_MEMORY_SEGMENT::EvictResource+430

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: dxgmms1

IMAGE_NAME:  dxgmms1.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4ce799c1

FAILURE_BUCKET_ID:  X64_0x50_dxgmms1!VIDMM_MEMORY_SEGMENT::EvictResource+430

BUCKET_ID:  X64_0x50_dxgmms1!VIDMM_MEMORY_SEGMENT::EvictResource+430

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

Dont pay attention to the dxgmms1 thing, it is an OS component. It actually represents the graphics element, your display driver. It says something about the Video Memory thing. And, here it comes ....

Code:

Name        :   AMD Radeon HD 6800 Series
Adapter RAM :   1.00 GB (1,073,741,824 bytes)

Is it enough for the newest resource hungry games? I doubt. Also, How old the GPU is?

After installing the latest display driver, stress test the Graphics Card using Furmark.
Video Card - Stress Test with Furmark

Also perform a Video Memory Stress Test.

Let us know the results.

abyssninja said:

AS far as the Norton goes, should i just get rid of it and try out a different anti-virus?

Good point

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. MSE, cause it is most lightweight o the system and never causes a BSOD.

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

As all the others are apparently OK, wish you best of luck with the antivirus swap :) Let us know how the computer works after that.

That's obvious. Norton's crasher, at least for you

Inform us how the computer is running when you think your issue is fixed or not.

Do you use Linksys AE3000? If so, update the driver.

Scan the system for possible virus infection.

• Anti-rootkit utility TDSSKiller
• Windows Defender Offline

And then enable Driver Verifier to monitor the drivers.
Driver Verifier - Enable and Disable
Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.

   Information

Why Driver Verifier:
It puts a stress on the drivers, ans so it makes the unstable drivers crash. Hopefully the driver that crashes is recorded in the memory dump.

How Can we know that DV is enabled:
It will make the system bit of slow, laggy.

   Warning

Before enabling DV, make it sure that you have earlier System restore points made in your computer. You can check it easily by using CCleaner looking at Tools > System Restore.

If there is no points, make a System Restore Point manually before enabling DV.

   Tip

• If you fail to get on the Desktop because of DV, Boot into Advanced Boot Options > Safe mode. Disable DV there. Now boot normally again, and try following the instruction of enabling DV again.
• If you cannot boot in Safe mode too, do a System Restore to a point you made earlier.

Let us know the results, with the subsequent crash dumps, if any.

It failed to record the crash dump.

Disable driver verifier. (If needed, boot into safe mode and disable it there)
Remove all the startup entries other than the antivirus.
Enable verifier again, make it sure that you are not checking any driver provided by "microsoft" and "unknown"

Hopefully this time we will get a crash dump.