BSOD System Service Exception Windows 10

Page 2 - Seeking answers? Join the Tom's Hardware community: where nearly two million members share solutions and discuss the latest tech.

Nuggets3

Prominent
Apr 25, 2017
24
0
510
Hi everyone,

I have an issue with my computer, in fact he crashes brutally and a blue screen appears with "System Service Exception" . The computer restart and recrash 10 minutes later
I've looked in internet but couldn't find any solutions .

Here's my Crash Dump from WhoCrashed :


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

Computer name: *******
Windows version: Windows 10 , 10.0, build: 15063
Windows dir: C:\WINDOWS
Hardware: MS-7752, MSI, Z77A-G45 (MS-7752)
CPU: GenuineIntel Intel(R) Core(TM) i5-3570K CPU @ 3.40GHz Intel586, level: 6
4 logical processors, active mask: 15
RAM: 8534364160 bytes total




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

Crash dump directory: C:\WINDOWS\Minidump

Crash dumps are enabled on your computer.

On Tue 25/04/2017 18:19:17 your computer crashed
crash dump file: C:\WINDOWS\Minidump\042517-33906-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x16BF70)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF800F77A7C1A, 0xFFFFAF8197A459D0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Tue 25/04/2017 18:10:24 your computer crashed
crash dump file: C:\WINDOWS\Minidump\042517-20609-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x16BF70)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80018DA8C1A, 0xFFFFE2004E6409D0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Tue 25/04/2017 17:59:40 your computer crashed
crash dump file: C:\WINDOWS\Minidump\042517-21515-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x16BF70)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF802EFB21C1A, 0xFFFFB6007D3969D0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Tue 25/04/2017 17:52:47 your computer crashed
crash dump file: C:\WINDOWS\Minidump\042517-23875-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x16BF70)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8004C7A4C1A, 0xFFFFD800272A99D0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Tue 25/04/2017 16:16:55 your computer crashed
crash dump file: C:\WINDOWS\Minidump\042517-20234-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x16BF70)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF801991A4C1A, 0xFFFFD000DB22C9D0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.





--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------

16 crash dumps have been found and analyzed. Only 5 are included in this report. No offending third party drivers have been found. Connsider using WhoCrashed Professional which offers more detailed analysis using symbol resolution. Also configuring your system to produce a full memory dump may help you.


Thx,
 
Solution
well we could have saved a lot of time if you told us you had 500 threats detected before the malware detector crashed ... but whatever.
assume that you have filled up all of 1.12 TB of storage in your system, then yes, invest in a new hard drive, portable or internal, doesn't matter.
destroy all evidence of the virus by backing up important files in the .pdf, .mp3 .doc(x) .jpg .gif but do not back up any .exe .com or anything that have .nfo in it. they may have undetectable viruses. well you know what is important for you better than anyone else. but use common sense. anything remotely executable you do not want to bring to your virus free environment.


Ok I'll buy a new USB tomorrow, this one is very old.
 
completely reinstall windows (clean install not upgrade option when booted from installer).
fresh complete install (cannot stress this enough). then do not install any third party antivirus (system defender from the os itself is enough).
if complete fresh install cannot be completed, it means that despite everything, your hard drive deserves to be trashed.
 
the point of scan memtest was to tell us if your memory ramm dimm sticks are the culprit. since it passed, it means the dimm sticks are good. it is not the culprit.
Right now I'm thinking a virus.
Before you clean reinstall windows, obviously you want to back up your photos, videos, and mp3s as well as any other important items such as documents, but downloads are suspect.
 
I too think that it may be a virus, In fact I wanted to check my pc with ZHPDiag and in about 50% of the scanning it crashes everytime (500 and more threats detected). So I'll have to buy a external HDD to keep all my datas ?
 
well we could have saved a lot of time if you told us you had 500 threats detected before the malware detector crashed ... but whatever.
assume that you have filled up all of 1.12 TB of storage in your system, then yes, invest in a new hard drive, portable or internal, doesn't matter.
destroy all evidence of the virus by backing up important files in the .pdf, .mp3 .doc(x) .jpg .gif but do not back up any .exe .com or anything that have .nfo in it. they may have undetectable viruses. well you know what is important for you better than anyone else. but use common sense. anything remotely executable you do not want to bring to your virus free environment.
 
Solution