cancel
Showing results for 
Search instead for 
Did you mean: 

Drivers & Software

elstaci
MVP

Re: BOOTLOG_NOT LOADED dxgkrnl.sys

Before you blame the motherboard.

If the ingrade upgrade doesn't fix the problem. THEN do a CLEAN WINDOWS INSTALLATION. As soon as Windows finishes installing. See if the problem has gone away. IF IT HASN'T, then it is a very good indication it is HARDWARE RELATED.

At another website that specializes in BSOD, one of the MS Specialist that works at that site mentioned that if you do a clean Windows installation and the problem continue that means it is a hardware issue and not software. The reason is that Windows is totally clean and should not have any issues at all when first installed.

But first do an Ingrade Upgrade which is less hassle than doing a clean Windows installation plus it saves all your 3rd party software and configuration you have now but with a new Windows.

Afterwards if it still doesn't fix the problem and running Windows Disk Clean to remove Windows.old, Do a System Backup to another Hard Drive using Windows 7 Backup in Windows 10 Control Panel, THEN do a Clean Windows Installation. That way when you replace your motherboard, if it is defective, you can restore the System Backup and see if the problem is fix with all your 3rd party software installed.

Good luck.

It is a lot of work but it will save you time later on.

0 Likes
elstaci
MVP

Re: BOOTLOG_NOT LOADED dxgkrnl.sys

I reread your original question. I notice you have a 450 Watt PSU. Was thinking maybe that could be part of the problem. But I went to a website that shows what the minimum PSU you need for your computer with various GPU Cards and found out that your RX460 only requires a PSU of 380 Watts. So you enough power to run your GPU card and Ryzen CPU.

Also I not sure how a defective Motherboard will cause Windows corruption unless the hard Drive/ SSD is going bad by creating bad sectors thus corrupting whatever data was on those bad sectors.

Sometimes a failing RAM memory may cause data corruption also.

After you have finish install Windows either as an ingrade or clean installation. I would run MEMTEST86 and Seatools for Windows by Seagate (free) to check both the RAM Memory and Hard Drive/SSD or you can run CHKDSK /f/x/r in an elevated Command Prompt to check or repair your hard drive / SSD.

0 Likes
ishaan
Newcomer

Re: BOOTLOG_NOT LOADED dxgkrnl.sys

I ran memtest86 and my RAM passed all 4 tests. I downloaded seatools and ran the short tests which my drive passed. Now what I am thinking is that I should test the HDD little more by running long tests and then check the motherboard. I was already going to buy an ssd for my system. I'll see if that fix the problem. And should I install drivers for my hdd ? I think I manually installed them before from chipset drivers folder

0 Likes
elstaci
MVP

Re: BOOTLOG_NOT LOADED dxgkrnl.sys

This is Microsoft answer to when MSCONFIG reverts back to "Selective Startup" from "Normal Startup": https://support.microsoft.com/en-us/help/310567/the-msconfig-startup-selection-reverts-from-normal-t... 

See if that fixes your problem with MSCONFIG staying at Selective Startup.

0 Likes
elstaci
MVP

Re: BOOTLOG_NOT LOADED dxgkrnl.sys

Here is another good website that gives various tips on how to resolve the MSCONFIG issue. See if by applying any of the troubleshooting tips it fixes your MSCONFIG issue.https://troubleshooter.xyz/wiki/fix-msconfig-wont-save-changes-on-windows-10/ 

0 Likes
ishaan
Newcomer

Re: BOOTLOG_NOT LOADED dxgkrnl.sys

I tried doing what microsoft says but it did not work. If you read my previous replies carefully I have stated my problem with the debug option. The problem is that it is linked with normal startup option. When I try to disable it the startup mode switches to selective and when I enable debug and run it with normal mode it gives me BSOD on boot. And then I have to reinstall windows.

0 Likes
elstaci
MVP

Re: BOOTLOG_NOT LOADED dxgkrnl.sys

what BSOD error message does it show. ?

0 Likes
ishaan
Newcomer

Re: BOOTLOG_NOT LOADED dxgkrnl.sys

Forgot that message. It happened months ago. I think it was inaccessible boot device but I could be wrong.

0 Likes