BSOD System Service Exception


  1. Posts : 8
    Windows 10 Pro 64bit
       #1

    BSOD Loop: Service Exception, WHEA Uncorrectable, KMODE, Cache Manager


    Hello All,

    I must say, I am at my wits end and am really hoping that the wonderful folks here at TenForums are able to help.

    My computer frequently, yet seemingly random, BSODs. The error it throws on the Blue Screen is "System Service Exception" with no numbers, or anything other than that.

    I have attempted a number of things to resolve, but as of yet, no success. Ive run MemTest86+ a few times at boot, all good there. I disabled or uninstalled a some drivers, applications, services etc that I thought may be causing the problem, but no success there either.

    Anyway, I really like this computer when its working and would really hate to have to get a new one and I am hoping that the collective genius here at TenForum can pinpoint the problem so I wont have to replace everything. Thanks in advance for any assistance.

    I have attached my recent log as per the forum instructions, and additionally added my system info for reference.

    Thank you!

    Attachment 110501Attachment 110502

    While waiting for a response, I went ahead and reinstalled the OS (clean) and then updated my drivers. And, shortly after my pc starting BSODing again This time it threw the WHEA Uncorrectable error, immediately followed by a KMODE Exception Not handled. After that, I booted to recovery cmd prompt and ran SFC Scannow. About 5 minutes into that it BSOD'ed with CACHE_Manager error. Ugh...

    Here are most recent logs:
    Attachment 110535

    Round 3: Attachment 110800
    Last edited by Jbobnew; 20 Nov 2016 at 12:11. Reason: Adding most recent log dump
      My Computer


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

    bump for update to original
      My Computer


  3. Posts : 8
    Windows 10 Pro 64bit
    Thread Starter
       #3

    Been running verifier for some time and was going strong, but eventually two BSOD's back to back. This time it indicated a NTFS.SYS error followed by a IRQL Not Less Or Equal BSOD.

    Ran BlueScreenView from nirsoft and came up with this info from the earlier System Service Exception BSOD that I posted in my edit to the original post (not sure why there is no dump from the NTFS.sys BSOD): Bug Check Code 0x0000003b; Caused by driver ntoskrnl.exe.

    Any chance this is a lead??

    Looking forward to help!
      My Computer


  4. Posts : 8
    Windows 10 Pro 64bit
    Thread Starter
       #4

    Hi Gents,

    Ive had verifier.exe running for some time now and now getting different errors indicated on the BSOD. Most recently back-to-back NVLDDMKM.sys "Driver portion must be non paged" BSODs.

    Anyone have any suggestions on what might be causing all of this?? Please.

    Most recent log dump added to original post and here:
    Attachment 110801
      My Computer


  5. Posts : 14,046
    Windows 11 Pro X64 22H2 22621.1848
       #5

    When you reply to your own thread, it looks to us like someone is already working with you so we move on to the next BSOD that has no responses.

    Looked at the latest dump and see this:
    Code:
    BugCheck D3, {fffff80001c9b01d, 2, 0, fffff803313150f6}
    *** WARNING: Unable to verify timestamp for nvlddmkm.sys
    *** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
    Probably caused by : memory_corruption
    You currently have the 375.86 version, the web site had:
    Code:
    Version: 375.95
    Date: 2016.11.18
    Also, because of the possible memory corruption, it would be good to run memtest86+ as follows:
    ===================================================
    Follow this tutorial: MemTest86+ - Test RAM - Windows 10 Forums

    MemTest86+ is a diagnostic tool designed to test Random Access Memory (RAM) for faults. MemTest86+ will verify that:

    • RAM will accept and keep random patterns of data sent to it
    • There are no errors when different parts of memory try to interact
    • There are no conflicts between memory addresses


    Memtest86+ runs from bootable media to isolate the RAM from the system, no other components are taken into account during the test.

    warning   Warning
    MemTest86+ needs to run for at least 8 passes to be anywhere near conclusive, anything less will not give a complete analysis of the RAM.


    If you are asked to run MemTest86+ by a Ten Forums member make sure you run the full 8 passes for conclusive results. If you run less than 8 passes you will be asked to run it again.

    Note   Note
    MemTest86+ has been known to discover errors in RAM in later passes than the eighth pass. This is for information only; if you feel there is a definite problem with the RAM and 8 passes have shown no errors feel free to continue for longer.


    Running 8 passes of MemTest86+ is a long and drawn out exercise and the more RAM you have the longer it will take. It's recommended to run MemTest86+ just before you go to bed and leave it overnight.
      My Computers


  6. Posts : 8
    Windows 10 Pro 64bit
    Thread Starter
       #6

    Hi ZTruker,

    Thank you very much for the response. Peculiar about the Nvidia driver being out of date because its one that I thought I had updated upon clean install of the OS. I will certainly double check that.

    Regarding the MemTest86+, I had run that a number of times, all 8 passes or more, and originally wasn't receiving any errors. But, on a whim, I decided to fire it up again last night and this morning it had completely locked up after having thrown at least 24 errors. When reading the errors , the column on the furthest right rather than saying "chan", instead says "CPU" with "0" listed under that heading for all of the errors.

    Does this mean that my CPU could be going/already is bad?

    Thanks again for the responses.
      My Computer


  7. Posts : 14,046
    Windows 11 Pro X64 22H2 22621.1848
       #7

    I don't know what that means nor can I find any useful info on it.
    For additional testing, remove all but 1 DIMM and out it in slot 2 then run memtest86+ and see if it fails. If no, swap in another DIMM and tes. Repeat until the defective one is found.

    If no help, I see you have 24GB of ram. Looking at the manual that is not a supported configuration (2 slots of 4 filled).
    I suggest running with 16GB (8GB in two slots) in slots 2 and 4 per the manual, see if that helps.

    Attachment 110922
      My Computers


  8. Posts : 8
    Windows 10 Pro 64bit
    Thread Starter
       #8

    Hi ZTruker,

    So I can happily report that my system has not BSOD since the last post. I ended up removing a stick of RAM as suggested, but also went ahead and completely broke down and reseated everything, including the CPU. I think we can call this resolved. Thanks again for all the help.
      My Computer


  9. Posts : 14,046
    Windows 11 Pro X64 22H2 22621.1848
       #9

    Great, hope that's the end of it.
      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 18:00.
Find Us




Windows 10 Forums