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

R

runuts

Member
Joined
Jul 26, 2017
Posts
19
Location
Cincinnati
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
 

Attachments

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.
 
Re: BSOD - Windows 10x64 Pro- NTOSKRNL.EXE

runuts said:
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.
Click to expand...

Did not resolve the problem. Left computer idle for 20-30 minutes and when I returned, it had a BSOD event.
 
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
 
Re: BSOD - Windows 10x64 Pro- NTOSKRNL.EXE

bwv848 said:
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
Click to expand...

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.
 
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?
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top