Windows 8.1 BSOD system service exception. Kindly ask for help

After an auto-update (I think Windows) I get a BSOD after entering my password. Message: system service exception. I can start the computer in safe mode. Searched threads but could not find the fix.

I kindly would like to ask your advice or help in solving this.

Best regards,


Dump file (attached / info via Bluescreen View)

Dump File : 051515-5062-01.dmp
Crash Time : 14-May-15 23:40:58
Bug Check Code : 0x0000003b
Parameter 1 : 00000000`c0000005
Parameter 2 : 00000000`00000000
Parameter 3 : ffffd000`e86a5570
Parameter 4 : 00000000`00000000
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+150ca0
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+150ca0
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\051515-5062-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 9600
Dump File Size : 282,648
Dump File Time : 15-May-15 08:27:48

System info

OS Name Microsoft Windows 8.1
Version 6.3.9600 Build 9600
Other OS Description Not Available
OS Manufacturer Microsoft Corporation
System Name XPS12
System Manufacturer Dell Inc.
System Model XPS 12-9Q33
System Type x64-based PC
System SKU XPS 12-9Q33
Processor Intel(R) Core(TM) i7-4500U CPU @ 1.80GHz, 2394 Mhz, 2 Core(s), 4 Logical Processor(s)
BIOS Version/Date Dell Inc. A05, 25-Mar-14
SMBIOS Version 2.7
Embedded Controller Version 0.05
BaseBoard Manufacturer Dell Inc.
BaseBoard Model Not Available
BaseBoard Name Base Board
Platform Role Mobile
Secure Boot State On
PCR7 Configuration Binding Not Possible
Windows Directory C:\Windows
System Directory C:\Windows\system32
Boot Device \Device\HarddiskVolume1
Locale China
Hardware Abstraction Layer Version = "6.3.9600.17196"
Installed Physical Memory (RAM) 8.00 GB
Total Physical Memory 7.91 GB
Available Physical Memory 5.76 GB
Total Virtual Memory 15.9 GB
Available Virtual Memory 14.0 GB
Page File Space 8.00 GB
Hyper-V - VM Monitor Mode Extensions Yes
Hyper-V - Second Level Address Translation Extensions Yes
Hyper-V - Virtualization Enabled in Firmware Yes
Hyper-V - Data Execution Protection Yes

[Hardware Resources]


Resource Device
I/O Port 0x00000000-0x00000CF7 PCI Express Root Complex
I/O Port 0x00000000-0x00000CF7 Direct memory access controller

I/O Port 0x00000070-0x00000070 Motherboard resources
I/O Port 0x00000070-0x00000070 System CMOS/real time clock

I/O Port 0x000004D0-0x000004D1 Programmable interrupt controller
I/O Port 0x000004D0-0x000004D1 Motherboard resources

Memory Address 0xFF000000-0xFFFFFFFF Motherboard resources
Memory Address 0xFF000000-0xFFFFFFFF Intel(R) 82802 Firmware Hub Device

I/O Port 0x00001C00-0x00001CFE Motherboard resources
I/O Port 0x00001C00-0x00001CFE Intel(R) Serial IO GPIO Host Controller

I/O Port 0x00000080-0x00000080 Motherboard resources
I/O Port 0x00000080-0x00000080 Motherboard resources

I/O Port 0x0000FFFF-0x0000FFFF Motherboard resources
I/O Port 0x0000FFFF-0x0000FFFF Motherboard resources
I/O Port 0x0000FFFF-0x0000FFFF Motherboard resources



Windows Forum Admin
Staff member
Premium Supporter
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, 0, ffffd000e86a5570, 0}

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

Followup: MachineOwner
all three dump files blamed the same driver: ApHidFiltr.sys This relates to your Touchpad.
If it was updated via Windows update then at times this can cause an issue so usually I recommend users to not update drivers via Windows update.
Try uninstalling the Touchpad driver on the machine and then re-install the latest version from your machines support page here:
I would also apply any other updates which might be pending. You can always use Device manager to check on the version currently being used.

There is also a chance that this might not be linked to the driver but your RAM although time will tell especially after you've replaced the driver.

Thank you very much for the reply! My final solution was a clean install. The problem was that I could only start in in safe mode. In safe mode I ran into a number of small problems that I finally decided to do the clean install. I checked RAM btw and this was fine. Clean install work well.

Thank you once again!


Windows Forum Admin
Staff member
Premium Supporter
Thank you for updating and of course if the issue should re-occur then just post back.

This website is not affiliated, owned, or endorsed by Microsoft Corporation. It is a member of the Microsoft Partner Program.