1. #1

    Join Date
    Jul 2017
    Location
    Cincinnati
    Posts
    19

    [10ProInsPreV1712b17063 x64] 0x3B c0000005, SYSTEM_SERVICE_EXCEPTION, NTOSKRNL.EXE

    After running reasonable well for several months, BSOD and green screens have returned with a vengeance. System rarely stable for more than a few hours, and never overnight. Attempting to install updates or perform a repair install/update from an ISO guaranteed to cause a system crash. Complete system information included in attached file "System_Information_01-16-2018.zip". Summary below:

    OS - Windows 10 x64, Build 10.0.17063.
    x64.
    What was original installed OS on system? Windows 8.1 PRO x64
    Full retail version.
    Age of system (hardware) - Approximately 4 years with newer HDD (SSD),
    Age of OS installation - Approximately 2 years. Have entered computer in Insider Preview as updating the installation was the only path I found to overcome previous BSOD issues.

    CPU AMD A6 3650
    Video Card - Gigabyte 4 GB, AMD R9 290- currently running Windows Basic Display driver to eliminate any potential issues caused by AMD driver.
    MotherBoard - (if NOT a laptop) Gigabyte GA-A75M-UD2H
    Power Supply - brand & wattage (if laptop, skip this one) Thermaltake 700 W (less than 6 months old).

    System Manufacturer
    Exact model number (if laptop, check label on bottom) - Started as Medion - Original Motherboard, processor, memory, power supply and HDD have been replaced.

    Laptop or Desktop? Desktop
    Attached Files Attached Files


    • Ad Bot

      advertising
      Beep.

        
       

  2. #2

    Join Date
    Jul 2017
    Location
    Cincinnati
    Posts
    19

    Re: BSOD - Windows 10x64 Pro- NTOSKRNL.EXE

    Not certain if this is related. System was running fine. I had been using it steadily so it hadn't had a chance for the screen to shut off. I had to step away for a long enough period of time the screen had turned off. When I woke it up and logged in, I found the system had crashed, rebooted, crashed and then restarted. I've temporarily switched the screen to remain on at all times to see if this resolves the crashes.

  3. #3

    Join Date
    Jul 2017
    Location
    Cincinnati
    Posts
    19

    Re: BSOD - Windows 10x64 Pro- NTOSKRNL.EXE

    Quote Originally Posted by runuts View Post
    Not certain if this is related. System was running fine. I had been using it steadily so it hadn't had a chance for the screen to shut off. I had to step away for a long enough period of time the screen had turned off. When I woke it up and logged in, I found the system had crashed, rebooted, crashed and then restarted. I've temporarily switched the screen to remain on at all times to see if this resolves the crashes.
    Did not resolve the problem. Left computer idle for 20-30 minutes and when I returned, it had a BSOD event.

  4. #4

    Join Date
    Dec 2017
    Location
    92.96 million miles away from the sun
    Posts
    20

    Re: BSOD - Windows 10x64 Pro- NTOSKRNL.EXE

    I suspect a bug in Build 17063 is at fault, though sacrilegious and profane that may be. There are 30 dumps files in the uploaded report, essentially identical to the faulting instruction and the process accused to be responsible for the exception, viz., registry.exe. That process registry.exe has been around for a while in Insider builds, but Build 17063 is the first build to store registry hive data in it and is hence a little buggy. (The ultimate purpose of this new registry.exe process is just to reduce the registry's memory usage, giving better performance.)

    I've dumped the call stack for your interest of the latest minidump to highlight the registry activity prior to the crash.
    Read More:

    BTW, are you in the habit of running QQ International often? It's been noted that Tencent games (and perhaps in general any Tencent software) may cause GSODs. I've also noticed there are a few errors in Device Manager:
    Code:
    SCSI Controller    PCI\VEN_9004&DEV_5078&SUBSYS_78509004&REV_03\4&312BC670&0&30A4    The drivers for this device are not installed.
    Unknown USB Device (Device Descriptor Request Failed)    USB\VID_0000&PID_0002\5&10DB4AB&0&1    43
    It's also been noted that USB devices with unreliable connections can cause GSODs; care to remove any USB devices you have?

    Honestly, the best thing I can suggest here is rolling back to the previous build, or just being patient. Here are some of the known issues in Build 17063 - Announcing Windows 10 Insider Preview Build 17063 for PC - Windows Experience BlogWindows Experience Blog

  5. #5

    Join Date
    Jul 2017
    Location
    Cincinnati
    Posts
    19

    Re: BSOD - Windows 10x64 Pro- NTOSKRNL.EXE

    Quote Originally Posted by bwv848 View Post
    I suspect a bug in Build 17063 is at fault, though sacrilegious and profane that may be. There are 30 dumps files in the uploaded report, essentially identical to the faulting instruction and the process accused to be responsible for the exception, viz., registry.exe. That process registry.exe has been around for a while in Insider builds, but Build 17063 is the first build to store registry hive data in it and is hence a little buggy. (The ultimate purpose of this new registry.exe process is just to reduce the registry's memory usage, giving better performance.)

    I've dumped the call stack for your interest of the latest minidump to highlight the registry activity prior to the crash.
    Read More:

    BTW, are you in the habit of running QQ International often? It's been noted that Tencent games (and perhaps in general any Tencent software) may cause GSODs. I've also noticed there are a few errors in Device Manager:
    Code:
    SCSI Controller    PCI\VEN_9004&DEV_5078&SUBSYS_78509004&REV_03\4&312BC670&0&30A4    The drivers for this device are not installed.
    Unknown USB Device (Device Descriptor Request Failed)    USB\VID_0000&PID_0002\5&10DB4AB&0&1    43
    It's also been noted that USB devices with unreliable connections can cause GSODs; care to remove any USB devices you have?

    Honestly, the best thing I can suggest here is rolling back to the previous build, or just being patient. Here are some of the known issues in Build 17063 - Announcing Windows 10 Insider Preview Build 17063 for PC - Windows Experience BlogWindows Experience Blog
    Unfortunately, I do use QQ International almost daily to communicate with suppliers in China. Unfortunately, whatever the issue is with build 17063 it is preventing a rollback to the previous version or an update to 17074. The rollback feature fails, installing the update to 17074 or trying to update using the 17074 ISO generates a green screen. Windows won't allow an older version to be installed from an ISO unless it is a new installation where all previous files are wiped or the install is to a new partition.

    The SCSI controller is an old Adaptec for which there is no Windows driver. It does function with VueScan and an old desktop scanner. The USB is an external drive that is powered off. I can pull it, no problem. Will let you know if I find any solution that works.

  6. #6
    xilolee's Avatar
    Join Date
    Dec 2013
    Location
    World, Europe, Italy
    Posts
    2,296
    • specs System Specs
      • Manufacturer:
        XILOLEE.com
      • Model Number:
        XILO
      • Motherboard:
        ASROCK FM2A88M Pro3+ chipset A88X Bolton-D4
      • CPU:
        A10-7800, 4 CPU, 4 thr, 65/45W, FM2+, 28nm, Steamroller/Kaveri
      • Memory:
        10GB (Nanya and kingston ddr3-1333 9-9-9-24)
      • Graphics:
        Radeon R7 720MHz (8 GPU cores, integrated in CPU)
      • Sound Card:
        RealTek ALC662 (integrated in MB)
      • Hard Drives:
        Seagate ST500DM002-1BD142 500GB 7200RPM
      • Power Supply:
        SuperFlower 450W 80+ Platinum (SF-450P14PE)
      • Case:
        Sharkoon VG4-S
      • Cooling:
        Realtek RTL8111GR (NIC integrated in MB)
      • Display:
        Samsung SyncMaster SA100 LS22A100NS-EN
      • Operating System:
        Windows 10 Home/Standard x64

    Re: [10ProInsPreV1712b17063 x64] 0x3B c0000005, SYSTEM_SERVICE_EXCEPTION, NTOSKRNL.EX

    Current ram speed is 1333; MB and CPU specs say you can set your RAM speed to 1866.
    From the logs, it seems you seated your ram sticks in 3rd and 4th slots (starting from cpu).
    They should be in 2nd and 4th slots, or 1st and 3rd ones as second option.
    Did you remove the trustwave antivirus and are you running W10defender?

Similar Threads

  1. Windows 10 update fails with error code c0000005
    By Sefityke in forum Windows Update
    Replies: 12
    Last Post: 01-29-2016, 02:34 PM
  2. Windows 10 update fails with error code c0000005
    By Sefityke in forum Windows 10
    Replies: 1
    Last Post: 01-02-2016, 03:16 PM
  3. BSOD Random Crashes 0x3B & 0xA0 - Windows 7 x64
    By werty123412 in forum BSOD, Crashes, Kernel Debugging
    Replies: 2
    Last Post: 12-06-2014, 08:45 PM
  4. [SOLVED] Windows 8 SYSTEM_SERVICE_EXCEPTION BSODs
    By elephantnut in forum BSOD, Crashes, Kernel Debugging
    Replies: 11
    Last Post: 01-15-2013, 07:24 PM
  5. Windows 7 x64 Sp1 bsod 0x3b with U24DRV.sys
    By thermalfake in forum BSOD, Crashes, Kernel Debugging
    Replies: 1
    Last Post: 11-19-2012, 07:58 AM

Log in

Log in