Sign in with
Sign up | Sign in
Your question

SYSTEM SERVICE EXCEPTION Bsod

Tags:
  • Windows
  • Windows 8
  • Blue Screen
  • Computers
Last response: in Windows 8
Share
September 29, 2014 7:42:52 AM

Hey
I am having problems with the SYSTEM_SERVICE_EXCEPTION BSOD error. I am getting it a few times a day, it is mostly when i am not using my computer, like it is just on and doing nothing without runing windows. I can play for houers and its not getting any errors but when i just leave it for 10 minutes i am getting the BSOD. What Shuld i do?

092814-7843-01.dmp
28.09.2014 22:45:33
SYSTEM_SERVICE_EXCEPTION
0x0000003b
00000000`c0000005
fffff803`32614c40
ffffd000`22d65830
00000000`00000000
ntoskrnl.exe
ntoskrnl.exe+153fa0
NT Kernel & System
Microsoft® Windows® Operating System
Microsoft Corporation
6.3.9600.17085 (winblue_gdr.140330-1035)
x64
ntoskrnl.exe+153fa0
C:\Windows\Minidump\092814-7843-01.dmp
8
15
9600
296 
912
28.09.2014 22:46:03

More about : system service exception bsod

a b * Windows 8
September 29, 2014 8:25:45 AM

this error can be caused by a lot of thing.
I would start by running the system file checker
start cmd.exe as an admin
sfc.exe /scannow

this command will attempt to find and fix corrupted windows core files.

if that works, then I would run a malwarebytes scan.

if both of the scans come don't find a cause of the error
I would run memtest86 to test the machines hardware
and post the actual memory dump on a server with public access
ie post the file C:\Windows\Minidump\092814-7843-01.dmp on a server like mediafire, skydrive, or google docs and give them public access. Someone can look at the memory dump file with a debugger and see why windows shutdown.
m
0
l
September 30, 2014 8:21:55 AM

johnbl said:
this error can be caused by a lot of thing.
I would start by running the system file checker
start cmd.exe as an admin
sfc.exe /scannow

this command will attempt to find and fix corrupted windows core files.

if that works, then I would run a malwarebytes scan.

if both of the scans come don't find a cause of the error
I would run memtest86 to test the machines hardware
and post the actual memory dump on a server with public access
ie post the file C:\Windows\Minidump\092814-7843-01.dmp on a server like mediafire, skydrive, or google docs and give them public access. Someone can look at the memory dump file with a debugger and see why windows shutdown.


Well the system file checker dident work but here is a link to the dump file: https://www.dropbox.com/sh/ain8q3srj3ulyr7/AABNvZgzGfDm...
m
0
l
Related resources
a b * Windows 8
October 1, 2014 7:05:09 AM

-could not download the file without a account.
-why did the sfc.exe command fail? if it shows you have corrupted system files you need to repair them and do a malwarebytes scan.

Skalvik said:
johnbl said:
this error can be caused by a lot of thing.
I would start by running the system file checker
start cmd.exe as an admin
sfc.exe /scannow

this command will attempt to find and fix corrupted windows core files.

if that works, then I would run a malwarebytes scan.

if both of the scans come don't find a cause of the error
I would run memtest86 to test the machines hardware
and post the actual memory dump on a server with public access
ie post the file C:\Windows\Minidump\092814-7843-01.dmp on a server like mediafire, skydrive, or google docs and give them public access. Someone can look at the memory dump file with a debugger and see why windows shutdown.


Well the system file checker dident work but here is a link to the dump file: https://www.dropbox.com/sh/ain8q3srj3ulyr7/AABNvZgzGfDm...


m
0
l
October 1, 2014 1:40:48 PM

johnbl said:
-could not download the file without a account.
-why did the sfc.exe command fail? if it shows you have corrupted system files you need to repair them and do a malwarebytes scan.

Skalvik said:
johnbl said:
this error can be caused by a lot of thing.
I would start by running the system file checker
start cmd.exe as an admin
sfc.exe /scannow

this command will attempt to find and fix corrupted windows core files.

if that works, then I would run a malwarebytes scan.

if both of the scans come don't find a cause of the error
I would run memtest86 to test the machines hardware
and post the actual memory dump on a server with public access
ie post the file C:\Windows\Minidump\092814-7843-01.dmp on a server like mediafire, skydrive, or google docs and give them public access. Someone can look at the memory dump file with a debugger and see why windows shutdown.


Well the system file checker dident work but here is a link to the dump file: https://www.dropbox.com/sh/ain8q3srj3ulyr7/AABNvZgzGfDm...



Here, this link will work: http://www.mediafire.com/download/6taf8aqbex82j4v/09291...
I am trying to do a malware scan now ;) 
m
0
l
a b * Windows 8
October 2, 2014 12:32:02 PM

Update your bios, you are 5 updates behind, I would think they are having low level issues with your motherboard operations.

Manufacturer ASUSTeK COMPUTER INC.
Product MAXIMUS VII HERO
Version Rev 1.xx
BIOS Version 0508
BIOS Release Date 05/16/2014
http://www.asus.com/Motherboards/MAXIMUS_VII_HERO/HelpD...




----------------
I could not figure out the cause of the failure.
looks like you need to change your memory dump type from a mini dump to a kernel dump
and maybe set verifier.exe debugging tracking. I would update the BIOS first and see if that takes care of the problem.
m
0
l
!