BSOD System Service Exception Windows 10

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.
when ever you see the error code 0xC0000005
in a bugcheck. It means a bad memory address is being provided to a driver.
since all of your bugcheck show that code, you should update the BIOS and run memtest to confirm your BIOS memory timings are correct.

the update of the BIOS often will have updated BIOS timings and will remove any BIOS overclock you have set. You will want to also remove any windows overclocking drivers.

if the memtest86 works without errors, you would then boot into windows and start cmd.exe as an admin and run
sfc.exe /scannow
dism.exe /online /cleanup-image /restorehealth

then see if it finds any problems.

next step would be to update all of your motherboard drivers from your motherboard vendors website.

if you still get the problem, you would have to change the memory dump type to kernal rather than a minidump, wait for the next bugcheck and copy the memory dump to a server like microsoft onedrive, share it for public access and post a link.
then someone would have to look at the driver table for old drivers and try to figure out what driver was running at the that used the bad memory address.
 


I don't understant, what do I have to type in cmd ?

 
johnbl is saying you need to go to cmd, right click and go into administrative mode.
then type in

sfc.exe /scannow

let sfc.exe run it's course, then type in

dism.exe /online /cleanup-image /restorehealth

and let it run that course.

two commands
 
also google for memtest86 to find
http://www.memtest86.com/
so you can download and run the tester on its own boot image.
for updating the BIOS you have to go to your motherboard vendors website and get the update an a tool to install it.



 
technically it's called s.m.a.r.t. checker does a bunch of test on your hard drive or ssd and tell you if it's failing.
assuming you used crystaldiskinfo then try this with cmd.

wmic diskdrive get status

copy and paste.
does it says OK or Unknown or FAILING in the command prompt?
 


It says OK
OK
OK


 
http://www.memtest86.com/download.htm

download the free version either cd or usb (you propbably just use usb, easier unless you have a cd/dvd/blu ray burner on your system.

put the files after you extract them and put it on to a ubs key you have lying around.

boot from it by going into bios and (when starting computer, click delete key repeatedly until you get into uefi/bios, go into boot options and choose boot from usb.

let memtest run when you go to sleep.
at least one pass is recommended.

seriously you have never heard of memtest? you cannot diagnose computers without it.
edit:
https://www.youtube.com/watch?v=NaHL9usaM4Q
 


I have a poor 256 MB USB key is this enough ?