Windows 10: Startup crash

The bootlog shows many attempts to load dxgkrnl.sys. Not sure why but it also show a driver being loaded from the archived section instead of Windows\System\drivers folder.. This interests me in that is this driver needed for your system and if so, why is it being loaded in such a manner.

I will check my Windows 10 install and see if CompositeBus.sys is being loaded on my system. If you have not already you might open an Administrative Command prompt and run the System File Check.

sfc /scannow

If it finishes with error that is fine. If it finds an error, you might then run the following command in that same admin window. It should put a text file on your desktop. Check near the end of the listing for something related to "unable to repair" references or attach the file.

findstr /c:"[SR]" %windir%\Logs\CBS\CBS.log >"%userprofile%\Desktop\sfcdetails.txt"

 

I have checked, and in the BIOS, PCI-E is the active, I don't know why does it even load the Intel driver. But if everything is lost, I'll remove it also, thanks.

Thanks, I don't really know what to check here, so I rather attached the file as you suggested *Smile

sfcdetails.txt

 

I checked my Windows 10 system and the same driver is being loaded from the same backup location, so it appears to be a windows 10 thing.

The SFC text only shows one bad file, opencl.dll, which seems to be occurring on most Windows 10 Nvidia systems. Someone in the Insider program stated the newest Nvidia driver, 361.43, stopped that error. I did not check for a mobile version of that driver.

So it looks like we might be back to why dxgkrnl.sys is having a problem loading. The Intel video is in the processor and I have not seen a problem with Windows 10 and that particular device. If you have the mobile dual graphics, which version do you have set as primary?

I will check the EventViewer listing next. Does Device Manager show both the Nvidia and Intel graphics adapters without any yellow marks?

 

Thanks for your time. I'm just upgrading to 361.43 to be sure, the problem persists woth the newest version too.
Both Intel HD Graphics and NVIDIA Geforce are in the device manager, without any mark.
(Also I don't really understand one of your questions, what is mobile dual graphics? )

 

Folks with laptops use the mobile M) Nvidia drivers. When you run those drivers, the Nvidia control panel gives you the option to set the Display adapter configurations. Since you are running a PC, it isn't relevant to your situation, just mentioned it because I wasn't sure what you were running when I created the response.

I am running an ASUS Z87 motherboard with two Nvidia GTX 680s and have not seen any problems. My device manager does not show the Intel adapter which is probably a Bios setting. If you are trying to run the Nvidia utility which allows using both Intel and Nvidia, I can't remember what it is called, but someone in another thread stated it did not work well in Windows 10.

The Event Log file you attached is unreadable, normally the .evtx files are usable for the normal user.

 

I have no idea why is it displayed then, in BIOS it's set to PCI-E.
Also I could only upload some file formats to the forum, so I renamed it, if you rename it back to .evtx, it should be readable *Smile

 

My Intel adapter may not be showing because it is a different motherboard.

On my ASUS Z77 system, there was an option for iGPU Multi-Monitor which allows for both Integrated and Discrete Video. This setting is in addition to the selections for the Primary Display. But again, a different Bios is involved so you probably have different options.

Do you know what this might be about?

 

Well, I have an ASRock motherboard, but I have no idea what's this Shop, and I don't even remember installing anything for the motherboard.

 

If you look at the path included in the Warning message, does it seem to be accurate?

You might open the Task Scheduler to see if you can find that task and try disabling it for a while.

taskschd.msc in a run box will open it.

Otherwise, you might check your manual or an ASRock user group to see if anyone else had experienced problems. I will do a search for the utility (ASRock APP Shop) and post back if I find anything.

 

I have just looked at the path, and the folder with some log files actually exists, but no exe files are in there. So I think it shouldn't be the core of the problem.


I might just reinstall Win10, I note what and when do I install, and if it starts to do it again, I'll know more accurately, what caused it, and that info may help someone else too.

Thanks for your time, if I know anything more, I'll share with you! *Smile

 

So, here am I again... *Smile
I reinstalled Win10 (on a different SSD). The first day, I have installed the nVidia drivers, and every Windows update, so Intel, Realtek, and everything was installed. Then, for some days it was perfect, so I think it shouldn't be caused by nVidia or something like that. Then it just started to do this again. I have checked the installation log, and only Office, some games, and their related tools (vcredist, DirectX, PunkBuster) was installed, no drivers at all. Also, no Windows updates were installed in the previous day.

The events: http://mezesmadzag.hu/boot.evtx
There were 2 crashes, once it just hanged in the login screen, and the other time the PC auto-restarted.

Is there anything else I can check?

 

I see some mention of Office problems as far as starting a VL, possibly related to activation after the install.

I also see problems related to ReadyBoot. I am trying to get more info concerning that and windows 10. You might search for it to see if you can turn it off. It does not appear to be the same thing as ReadyBoost.

I think if I was having your problems, I would do an install with minimal software. Let the system run to see what errors might pop up before installing other things. The event log does mention logging had ceased so it may not be showing some important events.

 

Thanks your help,

it was the idea behind reinstalling Windows. I started from scratch, and started to install drivers, then programs periodically. The raw OS did not crash sadly. I'm not sure if it's related to installed programs, cause Office, and some games shouldn't affect the boot in any way, and that's why I'm just totally out of ideas.

 

On new systems, there are different ways being devised to allow a system to restart or boot from power off a little quicker.

You might try turning off some of those. For instance, there may be some type of Fast Boot in your Bios settings. Windows has a fast startup option on the Power Options > System Settings page where it refers to what the power buttons do. You could try turning that off.

From my limited exposure to the event viewer error messages, it looks like some prefetch file is too large. Whether this is referring to Virtual memory or something else, I do not know. I have not yet found anything which describes ReadyBoot on a Windows 10 system, but I do show an entry for it in my Registry. It could be the Registry uses an old name for something currently using a different name.

 

Thanks for your time,

fast boot is turned off in BIOS, actually it has never been enabled. In addition, I have tried with Windows fast boot off/on too, causing the same symptoms, so sadly it's not the problem either.