BSOD - SYSTEM_SERVICE_EXCEPTION (ks.sys)

wprecht · 16 Mar 2016

Fresh install of Win10 Pro and it's crashing quickly.

I am guessing it has to be a driver that came with the MB since I haven't had time to install anything else. But, I have no idea which one. I'd be grateful for someone to look at the bug checks and point me in the right direction.

Thanks.

Attachment 69822

axe0 · 17 Mar 2016

Your Creative camera drivers are way too old, either update the drivers or remove it.
Driver Reference Table - OA002Afx.sys

Code:

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

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff801409517c0, ffffd00020aa0d40, 0}

*** WARNING: Unable to verify timestamp for OA002Afx.sys
*** ERROR: Module load completed but symbols could not be loaded for OA002Afx.sys
Probably caused by : ks.sys ( ks!guard_dispatch_icall_nop+0 )

Followup:     MachineOwner

0: kd> lmvm OA002Afx
Browse full module list
start             end                 module name
fffff800`ca8e0000 fffff800`ca913f80   OA002Afx T (no symbols)           
    Loaded symbol image file: OA002Afx.sys
    Image path: \??\C:\Windows\system32\Drivers\OA002Afx.sys
    Image name: OA002Afx.sys
    Browse all global symbols  functions  data
    Timestamp:        Fri Jun 08 10:00:36 2007 (46690CA4)
    CheckSum:         0003D8A4
    ImageSize:        00033F80
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

wprecht · 17 Mar 2016

Well, that may have been a problem, but it's not *the* problem. In fact, it won't stay up long enough to gather a new dump zip. Since the last one I removed the Creative driver. Looks like Windows put in it's own driver for the monitor camera.

Is there anything else I can try?

axe0 · 17 Mar 2016

Updating drivers that should be provided by Gigabyte and updating Windows is what you could try :)

wprecht · 17 Mar 2016

Well, I slicked it and reinstalled Win10 Pro and used only fresh drivers from the website. It seems stable now. Thanks!

axe0 · 17 Mar 2016

Then you probably have updated Windows too :)
The drivers that needed updating should have mostly been updated.
The outdated drivers are/were

Realtek audio drivers
Intel graphics drivers
Intel chipset drivers
Network drivers from your killer network device

Apologies for not mentioning them earlier, I was at school and about to leave when I posted.