Bsod system_service_exception

[drenonks]

This happens at random times. I can be playing games or just browsing the web. Unsure of what to do. If you need anymore info let me know. It is more frequent when playing games, can happen every few hours. When playing games like COD:AW or other games that i guess require a lot of memory and power i get the BSOD more frequently. I was getting other what appeared to be NVidia driver bluescreens but since updating my drivers to 344.60 those seemed to have stopped. Now I keep getting the below.

windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
CPU: GenuineIntel Intel(R) Core(TM) i7-4770K CPU @ 3.50GHz Intel586, level: 6
8 logical processors, active mask: 255
RAM: 17115525120 total
VM: 2147352576, free: 1933594624
GPU: Gtx 670
MOBO: z87 sabertooth

On Fri 7/11/2014 3:30:22 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\110714-7924-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x75BC0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8000377D0D0, 0xFFFFF880079BDC10, 0x0)
Error: [FONT=Segoe UI, Arial]SYSTEM_SERVICE_EXCEPTION[/FONT]
file path: C:\Windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
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.



[FONT=Segoe UI, Arial]On Fri 7/11/2014 3:30:22 AM GMT your computer crashed[/FONT]
[FONT=Segoe UI, Arial]crash dump file: C:\Windows\memory.dmp[/FONT]
[FONT=Segoe UI, Arial]This was probably caused by the following module: [FONT=Segoe UI, Arial]ntkrnlmp.exe[/FONT] (nt!KeBugCheckEx+0x0) [/FONT]
[FONT=Segoe UI, Arial]Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8000377D0D0, 0xFFFFF880079BDC10, 0x0)[/FONT]
[FONT=Segoe UI, Arial]Error: [FONT=Segoe UI, Arial]SYSTEM_SERVICE_EXCEPTION[/FONT][/FONT]
[FONT=Segoe UI, Arial]Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code. [/FONT]
[FONT=Segoe UI, Arial]This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. [/FONT]
[FONT=Segoe UI, Arial]The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time. [/FONT]

 

[Arc]

Hi drenonks.

Update USB3 driver from https://downloadcenter.intel.com/.

Uninstall the installed display driver using Display Driver Uninstaller.

Then download and install 340.52 WHQL.

Follow NVIDIA Drivers - Avoid Problems to have a perfect and clean driver installation.

Let us know the results.

 

[drenonks]

Hi drenonks.

Update USB3 driver from https://downloadcenter.intel.com/.

Uninstall the installed display driver using Display Driver Uninstaller.

Then download and install 340.52 WHQL.

Follow NVIDIA Drivers - Avoid Problems to have a perfect and clean driver installation.

Let us know the results.

okay i have done this now. Waiting to see if it bluescreens again.

 

[drenonks]

Blue screened again

[FONT=Segoe UI, Arial]On Tue 11/11/2014 2:05:40 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\111114-7924-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x75B90)
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
Error: [FONT=Segoe UI, Arial]KMODE_EXCEPTION_NOT_HANDLED[/FONT]
file path: C:\Windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: NT Kernel & System
Bug check description: This indicates that a kernel-mode program 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.


[/FONT]
[FONT=Segoe UI, Arial]On Tue 11/11/2014 2:05:40 PM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntkrnlmp.exe[/FONT] (nt!KeBugCheck+0x0)
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
Error: [FONT=Segoe UI, Arial]KMODE_EXCEPTION_NOT_HANDLED[/FONT]
Bug check description: This indicates that a kernel-mode program 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.



[/FONT]

 

[Arc]

Test your RAM modules for possible errors.

How to Test and Diagnose RAM Issues with Memtest86+
​

Run memtest86+ for at least 8 consecutive passes.

If it start showing errors/red lines, stop testing. A single error is enough to determine that something is going bad there.

Let us know the result.

 

[drenonks]

I passed 8 tests with 0 errors.

Attached is a photo.

 

[Arc]

Nice, now enable Driver Verifier to monitor the drivers.

Driver Verifier - Enable and Disable
​

Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.

   Information

Why Driver Verifier:
It puts a stress on the drivers, ans so it makes the unstable drivers crash. Hopefully the driver that crashes is recorded in the memory dump.

How Can we know that DV is enabled:
It will make the system bit of slow, laggy.

   Warning

Before enabling DV, make it sure that you have earlier System restore points made in your computer. You can check it easily by using CCleaner looking at Tools > System Restore.

If there is no points, make a System Restore Point manually before enabling DV.

   Tip

• If you fail to get on the Desktop because of DV, Boot into Advanced Boot Options > Safe mode. Disable DV there. Now boot normally again, and try following the instruction of enabling DV again.
• If you cannot boot in Safe mode too, do a System Restore to a point you made earlier.

Let us know the results, with the subsequent crash dumps, if any.