[steven001]

hi everyone.. i seen a lot of topics concerning SYSTEM SERVICE EXCEPTION (BSOD) but i can figure out how to fix this.. because there is no particular thing i do for the bsod to occur.. it happens basicaly anytime.. tried a couple of thing.. updated the driver because i though it might be vga related

The system is an HP655, windows8.

i have some dump files attached to this..

i will be gald if i get reply to this

Attached Files

•  082714-54678-01.zip   62.71KB   298 downloads

[Advertisements]

    steven001

 

You have Norton AV running, please uninstall it using the removal tool here restart the computer and then check that Windows Defender** has automatically been enabled, use the computer as you normally would to see if the computer crashes, post back with an update for us.

 

** Windows Defender in Windows 8 and 8.1 is an upgraded version that offers the same real time protection as Microsoft Security Essentials, you do not actually need to use a third party AV software unless you specifically want to, not using one does however avoid potential conflicts.

[phillpower2]

    steven001

 

You have Norton AV running, please uninstall it using the removal tool here restart the computer and then check that Windows Defender** has automatically been enabled, use the computer as you normally would to see if the computer crashes, post back with an update for us.

 

** Windows Defender in Windows 8 and 8.1 is an upgraded version that offers the same real time protection as Microsoft Security Essentials, you do not actually need to use a third party AV software unless you specifically want to, not using one does however avoid potential conflicts.

[Jared44]

Norton/Symantec is notorious for causing BSODs and other issues, and I would recommend taking Phill's advice.

However, without a Kernel memory dump I cannot be certain of the cause but it might not be Norton that is causing it (which is surprising).

 

In case it isn't then take a look at the following:

fffff880`1ad96868 fffff960`00152077 : 00000000`00000000 fffffa80`01ff4b00 fffffa80`055d6bc0 00000000`00000000 : 0x6025e000
fffff880`1ad96870 fffff960`00151c54 : fffff880`1ad969b0 00000000`00000001 00000000`00000000 00000000`00000000 : win32k!W32pThreadCallout+0xb7
fffff880`1ad968a0 fffff803`bca9a91a : fffff880`1ad96ac8 fffffa80`05db5db0 00000000`00000001 00000000`00000008 : win32k!W32CalloutDispatch+0x375
fffff880`1ad96900 fffff803`bca6f086 : fffffa80`0149b5b0 00000000`00000008 00000000`00000000 00000000`00000000 : nt!ExCallCallBack+0x3a
fffff880`1ad96930 fffff803`bca9ab00 : fffffa80`00000000 00000000`00000001 00000000`00000000 000000b8`78457350 : nt!PspExitThread+0x6b6
fffff880`1ad96a50 fffff803`bc6d2841 : 00000000`00000002 fffff803`bc6bd95e 00000000`00000000 fffff880`1ad96b28 : nt!PsExitSpecialApc+0x1d
fffff880`1ad96a80 fffff803`bc6dcb30 : 000000b8`0c79d100 fffff880`1ad96b00 fffff803`bca9a940 00000000`00000001 : nt!KiDeliverApc+0x2cf
fffff880`1ad96b00 fffff803`bc65c4fa : 00000000`000000a4 000000b8`0c79cd80 000000b8`00000010 000000b8`0d06fa20 : nt!KiInitiateUserApc+0x70
fffff880`1ad96c40 000007f8`7408466b : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceExit+0x9f
000000b8`0d06f9c8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x000007f8`7408466b

We can see a system service finishing after a user mode function (to see what the function is a full memory dump is required), we then see an APC being initiated and then the thread terminating from the APC (APCs are often used to terminate threads after they run specific code). A callback function is returned followed by another callout, afterwards we see another user mode process and then sometime after a bugcheck.

 

win32k.sys is the Windows Subsystem device driver which handles most, if not all graphics related operations which is why my main thought is your display driver.

0: kd> lmvm atikmdag
start             end                 module name
fffff880`06a04000 fffff880`07426000   atikmdag   (deferred)             
    Image path: \SystemRoot\system32\DRIVERS\atikmdag.sys
    Image name: atikmdag.sys
    Timestamp:        Thu Aug 02 04:34:54 2012 (5019F55E)
    CheckSum:         009D1C10
    ImageSize:        00A22000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Your display driver is over 2 years old and when running Windows 8 especially, I would recommend updating.

 

If the problem was Symantec/Norton and the problem is resolved then you can either update the driver anyway (I recommend doing so) or you can leave it as it isn't causing problems.