SYSTEM_SERVICE_EXCEPTION crashes

Page 2 of 2 FirstFirst 12

  1. Posts : 41,413
    windows 10 professional version 1607 build 14393.969 64 bit
       #11

    In the "My Computer" section:
    The motherboard for system one displayed: B150-HD3P-CF
    The logs though display: Z97X-UD3H-BK

    Please update the specs in the "My Computer" section: (For the motherboard please include the version)

    System Specs - Fill in at Ten Forums:
    System Specs - Fill in at Ten Forums | Windows 10 Tutorials
    In the left corner below in your post you find 'My System Specs'.
    After clicking it you can find a link a little below that says 'Update your System Spec', click on this link to get to the page where you can fill in your system specs.
    System Info - See Your System Specs - Windows 7 Help Forums


    Include PSU. cooler, case, peripherals and anything attached to the computer by wired or wireless (mouse, keyboard, headset, printer, xbox, port replicator, docking station, USB wireless network card, etc.)
    https://www.tenforums.com/profile.php?do=extra
      My Computer


  2. Posts : 8
    Windows 10 64bit
    Thread Starter
       #12

    Aside from the monitor Dell 2407fpw and the temporary Corsair Ripjaws 1600 DDR3 ram listed below the specs in my profile is as the machine sits right now. NOTHING else is attached to it.

    So I reset the CMOS, moved the SATA port on SSD and left the Blu ray connected. Worked well for a while until I got a new BSOD I haven't encountered yet in this entire ordeal... KMODE_EXCEPTION_NOT_HANDLED. This occurred while gaming. From what I have read that is pointing towards bad memory or thermal. The CPU isn't getting above 50C and the GPU isn't getting above 70C while gaming. I am currently using 8GB(4GBx2) that I ran memtest+ on and it passed without any errors. I RMAed the 16GB that was having errors last week.

    axe0 said:
    If it doesn't work, the only other test that you can run is a PSU test, i.e. measuring the voltages of the PSU. A quick way is to check the 3.3v, 5v and 12v values in the BIOS and see if they are within a range of 5% (e.g. 3.3v between 3.135 & 3.465). Software like HWinfo is not recommended, because they may be very off (as is the case on my pc).

    Since there are basically only a few parts left, that haven't been tested (yet) and all tested parts connect via the motherboard I, again a hunch, would think the motherboard needs to be replaced as there is no proper test for the motherboard.
    It is possible that the CPU or PSU is bad, but to me it seems more likely that the motherboard is causing all the trouble.
    CPU @ 1.236v
    DRAM @ 1.512v(XMP profile)
    +3.3v @ 3.304v
    +5v @ 5.040v
    +12 @ 12.096v

    I am starting to think the board is starting to have some major issues. Pricing on Z97 boards in good shape used is outrageous. Looking more and more like I need to bite the bullet and build a new system.

    I have attached the latest analysis file.

    Whocrashed report.....
    On Tue 5/29/2018 1:43:48 PM your computer crashed or a problem was reported
    crash dump file: C:\WINDOWS\Minidump\052918-2906-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x175570)
    Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF80318B92D9B, 0x0, 0xFFFFFFFFFFFFFFFF)
    Error: KMODE_EXCEPTION_NOT_HANDLED
    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 a kernel-mode program generated an exception which the error handler did not catch.
    This might be a case of memory corruption. This may be because of a hardware issue such as faulty RAM, overheating (thermal issue) or because of a buggy driver.
    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 5/29/2018 1:43:48 PM your computer crashed or a problem was reported
    crash dump file: C:\WINDOWS\MEMORY.DMP
    This was probably caused by the following module: ntkrnlmp.exe (nt!RtlRaiseStatus+0x6C9)
    Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF80318B92D9B, 0x0, 0xFFFFFFFFFFFFFFFF)
    Error: KMODE_EXCEPTION_NOT_HANDLED
    Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
    This might be a case of memory corruption. This may be because of a hardware issue such as faulty RAM, overheating (thermal issue) or because of a buggy driver.
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
      My Computer


  3. Posts : 1
    Windows, Debian, Ubuntu, ROS
       #13

    I got same BSOD.
    The problem was SSD
    Attachment 220993
      My Computer


  4. Posts : 26
    Windows 10
       #14

    Hi all.
    I've the same issues as JD53. Many of the SYSTEM_SERVICE_EXCEPTION are random, I'm suspectiong as some background task is responsible for that due to the fact that they are totally random.

    I've performed a MemTest, it was Ok. Updated the BIOS, etc...

    The reports from WhoCrashed are:

    On Tue 2019-02-19 01:01:40 your computer crashed or a problem was reported
    crash dump file: C:\Windows\Minidump\021919-5796-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x1B3440)
    Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8063426F62F, 0xFFFFCB0C7BC6ECF0, 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 2019-02-19 01:01:40 your computer crashed or a problem was reported
    crash dump file: C:\Windows\MEMORY.DMP
    This was probably caused by the following module: ntkrnlmp.exe (nt!setjmpex+0x7EA9)
    Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8063426F62F, 0xFFFFCB0C7BC6ECF0, 0x0)
    Error: SYSTEM_SERVICE_EXCEPTION
    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 Sat 2019-02-16 12:23:30 your computer crashed or a problem was reported
    crash dump file: E:\BlueScreenReports\021619-6343-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x1B3440)
    Bugcheck code: 0xA (0x90007B0, 0xFF, 0x15, 0xFFFFF80043DCA8CF)
    Error: IRQL_NOT_LESS_OR_EQUAL
    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 Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above. This is a software bug.
    This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out.
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

    On Fri 2019-02-08 01:33:55 your computer crashed or a problem was reported
    crash dump file: E:\BlueScreenReports\020819-5937-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x1B1B40)
    Bugcheck code: 0x1A (0x61941, 0x953F59C, 0xD, 0xFFFFFB09129CBB00)
    Error: MEMORY_MANAGEMENT
    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 a severe memory management error occurred.
    This might be a case of memory corruption. This may be because of a hardware issue such as faulty RAM, overheating (thermal issue) or because of a buggy driver. This problem might also be caused because of overheating (thermal issue).
    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 2019-02-07 13:46:40 your computer crashed or a problem was reported
    crash dump file: E:\BlueScreenReports\020719-5953-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x1B1B40)
    Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80313D4BD1D, 0xFFFFC98A9BC4BFC0, 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 2019-02-05 23:40:06 your computer crashed or a problem was reported
    crash dump file: E:\BlueScreenReports\020519-6109-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x1B1B40)
    Bugcheck code: 0xA (0x1E5E7F9, 0x2, 0x0, 0xFFFFF8021653CC16)
    Error: IRQL_NOT_LESS_OR_EQUAL
    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 Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above. This is a software bug.
    This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out.
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

    Thanks if someone could help.
      My Computer


  5. Posts : 14,901
    Windows 10 Pro
       #15
      My Computers


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 06:05.
Find Us




Windows 10 Forums