Windows 10: I am getting BSOD for VIDEO_DXGKRNL_FATAL_ERROR on unplugged startup

Twice now, I have gotten a VIDEO_DXGKRNL_FATAL_ERROR bsod at startup when starting up Windows without the AC plugged in. In one case I had unplugged the power shortly after startup, in the other the AC adapter was completely unplugged from the get-go.


I have attached V2 logs.

The last one was on the 13th. After it, I reinstalled my Nvidia drivers from scratch from GeForce Experience.

After today's, I reinstalled them using an update from Gigabyte Control Center. (Apparently, Gigabyte had a newer version 431.11, which was not showing up in GeForce Experience. GFE now claims it is the most up to date driver.)

:)

 

Can't get GPU-Z to start with Windows 8.1 startup

I'm not sure how to do that. Could you list the steps for a noob?

 

BSOD when running on battery - driver_power_state_failure

***Merged***

Hello,

Since a few months my laptop - MSI GS60 2PE running Windows 10 Home - started giving BSOD's with the DRIVER_POWER_STATE_FAILURE after a seemingly random time when running on the battery. As I'm using it every day for work,
I depend on the machine and managed by just plugging it in.

While that works, I know it should be possible to make it work on the battery...

I've recently "reset this pc" using the build in option in Windows 10, after which I installed all "latest" drivers from the MSI site. I also re-installed all programs required to do my job and play some games.

Yesterday, Windows wanted to install the Fall Creators Update: I did. Booting the laptop while unplugged now gave me another BSOD, though with a different message: VIDEO_DXGKRNL_FATAL_ERROR. This seems to point to the Intel HD 4600 or Nvidia
GTX 870M.

To sum up some other issues I was starting out with...

Syptoms

• When unplugged, a BSOD occurs after a seemingly random time. (driver_power_state_failure)
  • After updating to the fall creators version, it also throws video_dxgkrnl_fatal_error; feels like a coin flip which one it will show.
    
• Bluetooth was failing after a couple of minutes, regardless whether I used it or not and whether the laptop was plugged in or not.
  
• Shutting down Windows would sometimes just heat up the CPU, make the fan go haywire and do nothing but turning the screen off.

I've tried / did:

• All drivers are up to date. This was verified by using DriverView and manually going over all of the non-Microsoft drivers.
  • This step fixed symptom 2 described above. Next to the latest version there was some patch (or 3 major versions ago) that couldn't be removed by conventional means. The build in troubleshooter actually removed it and bluetooth is now working
    as it should.
  • The HD4600 drivers were removed from the device management and I installed the latest according to the Intel site.
  • DDU was used in safe mode to remove the Nvidia driver and the latest one was installed.
• BlueScreenViewer shows the minidumps and lots of drivers.
  
  • The one created when the driver_power_state_failure occurred is useless, as nothing is marked but the ntoskrnl.
  • The one created when the video_dxgkrnl_fatal_error occurred shows ntoskrnl, watchdog and dxgkrnl.
    
• A clean boot (disabling all non-Microsoft services and disabling all startup programs) still results in the BSOD.
  
• Booting the laptop while plugged in, letting it run for a couple of minutes so everything is started and then unplugging it also seems to work.
  • Yesterday, I unplugged it and could work with it for about 2.5 hours before it called out for power: I doubt the battery is the issue.
  • I was asked to run a battery check (powercfg -energy -output ...) but that doesn't seem to show any issues. (design capacity '55031' Last full
    charge '38556'. The laptop is over three years old.)
    
• Starting in safe mode with networking will not result in a BSOD. (At least not within the hour I left it on.)
  
• Unchecking 'turn on fast startup' - as suggested in so many posts - in the power settings only causes issues.
  • When unchecked, windows won't shut down properly.
  • When checked, it does shut down normally. This seems to be the
    fix for symptom 3.
    
• Running various Windows troubleshooters didn't do much. Only the 'Windows Update' said it had some fixes regarding the database and 'fixed' it.
  
• The bios is up to date. (Version E16H2IMS.112)

Any help would be welcome.

Cheers!

PS: yes this post looks a lot like my
previous post, but that was marked answered because a moderator thinks all checks suggested can be performed within three days, next to a daily routine.

 

Getting BSOD 0x124 error

Ignore what everone said here.

0x124 BSOD is usually related to VCCIO (VTT), run Prime95 version 26.6 with custom sizes of 512K to 640K with 50% of your memory for at least 8 hours.

If you get a 0x124 BSOD, increase VCCIO voltage by small steps, run Prime95 again until your stable.

If you pass Prime95 512K to 640K without a BSOD, then its Vcore too low. I'd suggest running IntelBurnTest with 80% of your memory to verify stability (8 to 12 hours).

Oh, and yeah, if this problem appeared all of the sudden, the reason is CPU degradation, you can prevent it by enabling C-States or adjust your overclock to use lower voltages.