BSOD SYSTEM_SERVICE_EXCEPTION (3b)

[Alex-Nigma]

I have just got Windows 10 on my PC. It is legitimate as are all of the software I have installed (first day so there are really only the most basic programs). Recently I have been having BSODs with SYSTEM_SERVICE_EXCEPTION (3b) like every 30 mins.

Here are the dumps (the last in the list is the latest one chronologically)

https://www.dropbox.com/s/p1a88liqhg6ywa7/042116-5921-01.dmp
https://www.dropbox.com/s/vi4ig0xa2szihzy/042116-7171-01.dmp
https://www.dropbox.com/s/iagrt9329lqhw3u/042116-7312-01.dmp
https://www.dropbox.com/s/r1d8g7c83cisy1y/042116-7390-01.dmp
https://www.dropbox.com/s/o8lzoj5ixk36z74/042116-7390-02.dmp

Please advice, what can it be?

 

[Alex-Nigma]

And now I got IRQL_NOT_LESS_OR_EQUAL (a)

https://www.dropbox.com/s/k8gw08mpwedogkx/042116-7203-01.dmp

 

[Colif]

download and run this: http://www.resplendence.com/whocrashed
will look at those dumps and print them out in an easier to read format.
It should be a driver, it might even tell us which

Paste results in here.

also, what parts are in your new PC?

 

[Alex-Nigma]

download and run this: http://www.resplendence.com/whocrashed
will look at those dumps and print them out in an easier to read format.
It should be a driver, it might even tell us which

Paste results in here.

also, what parts are in your new PC?

Here is what it gives me:

Spoiler

System Information (local)
--------------------------------------------------------------------------------

Computer name: DESKTOP-HFM6BTP
Windows version: Windows 10 , 10.0, build: 10586
Windows dir: C:\Windows
Hardware: ASUSTeK COMPUTER INC., SABERTOOTH 990FX R2.0
CPU: AuthenticAMD AMD FX(tm)-8350 Eight-Core Processor AMD586, level: 21
8 logical processors, active mask: 255
RAM: 17073958912 bytes total




--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Thu 21.04.2016 18:30:59 GMT your computer crashed
crash dump file: C:\Windows\Minidump\042116-9953-01.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KxWaitForLockOwnerShip+0x14)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF8024D4803A4, 0xFFFFD001587FE678, 0xFFFFD001587FDE90)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
Bug check description: This indicates that a system thread generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Thu 21.04.2016 18:30:59 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x7E (0xFFFFFFFFC0000005, 0xFFFFF8024D4803A4, 0xFFFFD001587FE678, 0xFFFFD001587FDE90)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
Bug check description: This bug check indicates that a system thread generated an exception that the error handler did not catch.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Thu 21.04.2016 18:06:46 GMT your computer crashed
crash dump file: C:\Windows\Minidump\042116-7203-01.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0xA (0x4, 0x2, 0x1, 0xFFFFF80388F48649)
Error: IRQL_NOT_LESS_OR_EQUAL
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Thu 21.04.2016 16:47:32 GMT your computer crashed
crash dump file: C:\Windows\Minidump\042116-7390-02.dmp
This was probably caused by the following module: win32kbase.sys (win32kbase!hdevEnumerate+0x15A)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF803E5D4BB82, 0xFFFFD000223D9F10, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\win32kbase.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Base Win32k Kernel Driver
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



On Thu 21.04.2016 16:19:24 GMT your computer crashed
crash dump file: C:\Windows\Minidump\042116-7312-01.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0xA (0xC8, 0x2, 0x0, 0xFFFFF8003A6836CE)
Error: IRQL_NOT_LESS_OR_EQUAL
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Thu 21.04.2016 14:20:19 GMT your computer crashed
crash dump file: C:\Windows\Minidump\042116-7171-01.dmp
This was probably caused by the following module: dxgmms2.sys (dxgmms2!VidSchiSubmitCommandPacketToQueue+0x1D8)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF803AF935B82, 0xFFFFD00020346188, 0xFFFFD000203459A0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\dxgmms2.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics MMS
Bug check description: This indicates that a system thread generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



On Thu 21.04.2016 14:09:13 GMT your computer crashed
crash dump file: C:\Windows\Minidump\042116-7390-01.dmp
This was probably caused by the following module: win32kbase.sys (win32kbase!SURFACE::bDeleteSurface+0x625)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80167736B82, 0xFFFFD00023722CB0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\win32kbase.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Base Win32k Kernel Driver
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



On Thu 21.04.2016 13:40:13 GMT your computer crashed
crash dump file: C:\Windows\Minidump\042116-5921-01.dmp
This was probably caused by the following module: win32kfull.sys (win32kfull!vSynchronizeDriver+0x33)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF802F16DBB82, 0xFFFFD000217AAF90, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\win32kfull.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Full/Desktop Win32k Kernel Driver
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.

 

[Alex-Nigma]

And a new one:

Spoiler

On Thu 21.04.2016 19:21:41 GMT your computer crashed
crash dump file: C:\Windows\Minidump\042116-8953-01.dmp
This was probably caused by the following module: nvlddmkm.sys (0xFFFFF80074F4234C)
Bugcheck code: 0xBE (0xFFFFF80074F4234C, 0x80000000B9384121, 0xFFFFD000214D4580, 0xA)
Error: ATTEMPTED_WRITE_TO_READONLY_MEMORY
file path: C:\Windows\system32\drivers\nvlddmkm.sys
product: NVIDIA Windows Kernel Mode Driver, Version 364.72
company: NVIDIA Corporation
description: NVIDIA Windows Kernel Mode Driver, Version 364.72
Bug check description: This is issued if a driver attempts to write to a read-only memory segment.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 364.72 , NVIDIA Corporation).
Google query: NVIDIA Corporation ATTEMPTED_WRITE_TO_READONLY_MEMORY

 

[Colif]

Half of them point at your graphics drivers, DX and desktop

Rather annoying first day. I bet windows grabbed the drivers for you just before errors started.

I bet you have an Nvidia card too...

you might try this: http://www.tomshardware.com/faq/id-2767677/clean-graphics-driver-install-windows.html

 

[Alex-Nigma]

Half of them point at your graphics drivers, DX and desktop

Rather annoying first day. I bet windows grabbed the drivers for you just before errors started.

I bet you have an Nvidia card too...

you might try this: http://www.tomshardware.com/faq/id-2767677/clean-graphics-driver-install-windows.html

Actually I have manually installed the latest drivers, do you think I should roll back to the previous version?

 

[Colif]

Yes, it might be safer. I have never seen that last error before.. attempting to write to read only memory... thats a new one. And it makes it obvious who did it.

hope next Nvidia drivers are a bit better, They used to be the safe ones, AMD drivers were the bad drivers.. now, iI see more Nvidia cards than AMD with problems. And GTX 980 TI seem to get the worst of it. I am on same drivers and no problems.

 

[johnbl]

from the memory dump, the file and date stamp have been removed from many of your windows files. This can indicate malware/hacks/rootkits.
I would consider running a malwarebytes scan, root kit scan and runing
cmd.exe as an admin then run
dism.exe /online /cleanup-image /restorehealth

you are also running two very old drivers from 2012
(Logitech Camera driver, and Logitech USB Video Class Driver (webcam))

I would expect that it would be likely that either of these are corrupting your system memory and causing your bugchecks.
I would disable both devices in hardware and do a full reboot of your system then remove the drivers.

I was unable to read the BIOS info from the memory dump file, this often indicated a very out of date BIOS version is in use.
you should look for a update dated after 3/30/1213 to prevent problems with windows 10 and USB 3.0 drivers.

your system up time was 2 mins, the suberror code was 0xc0000005 this indicated either memory corruption. The memory corruption could be from the USB driver, or the USB subsystem support in the BIOS. It can also be from the actual RAM.

to test the RAM, update the BIOS or reset it to defaults and run memtest to confirm the RAM timings are ok.