Windows 10: BSOD when laptop runs on battery

Hey guys, I hope someone can help with this. I upgraded my Alienware laptop to windows 10 several months ago but only recently did I try running it on battery power and found out that it repeatably/seemingly randomly crashes. So far this ONLY seems to happen when running on the battery. After installing Windows 10 I did a reset and cleared everything, letting Windows 10 format the HD and reinstall itself. Then I downloaded all my drivers from Alienware and installed them clean. Everything has been running fine up until now.

The error I am getting is:

"nvlddmkm.sys"
System Service Error

When I googled the error it said that it was a BSOD, so here I am. Any help with this would be greatly appreciated, thanks.

:)

 

BSOD when running on battery - driver_power_state_failure

Hi,

BugCheck 113, {19, 2, 10de, 1199}
*** WARNING: Unable to verify timestamp for nvlddmkm.sys

*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys

Probably caused by : dxgkrnl.sys ( dxgkrnl!DpiFdoHandleDevicePower+31fb8 )

From the stack the root cause seems to be:

nvlddmkm.sys dated 11/14/2017 Nvidia video drivers.

1. Check with MSI Support, their on-line documentation and drivers, and ask in their forums about any known issues. Update the BIOS, chipset drivers, and the major on-board and separate device drivers. Of course do the same at Nvidia and update
those drivers. If there are no newer Nvidia drivers it may be necessary to revert back to an older stable version (see driver update methods below).

BiosReleaseDate = 05/05/2015

SystemManufacturer = Micro-Star International Co., Ltd.

SystemProductName = GS60 2PE Ghost Pro

BaseBoardManufacturer = Micro-Star International Co., Ltd.

BaseBoardProduct = MS-16H2

BaseBoardVersion = REV:0.B

CPUID: "Intel(R) Core(TM) i7-4710HQ CPU @ 2.50GHz"

MaxSpeed: 2500

CurrentSpeed: 2494

MSI Support

MSI Global

MSI - Downloads (BIOS and Drivers)

MSI Global

MSI - Forums

MSI Global English Forum - Index

MSI - Service

MSI USA

MSI - Live Update On-Line

MSI Global

MSI - Contacts - Set to North America - USA

Nvidia - Drivers - Use OPTION 1 to manually enter your driver info to get most current drivers.

Download Drivers | NVIDIA

Nvidia Support - check with Support as it could be a known issue

Nvidia Support

Nvidia Forums - also check for forums as it could be a known issue and/or others likely to have it

http://forums.nvidia.com/

2. Run the memory tests (see methods below).

3. As needed use ALL the methods in the troubleshooters below.

4. After ALL the above if needed run Driver Verifier to see if it can indicate a

CAUSE (see Driver Verifier methods below).

--------------------------------------

Troubleshoot blue screen errors

http://windows.microsoft.com/en-us/windows-10/troubleshoot-blue-screen-errors

Have you updated your display/video or other major drivers lately - check in Control Panel - Windows Updates to see if a driver has been loaded there. Use the generic troubleshooter below and when you get to the driver section use the methods belwo and then
return to the troubleshooter as needed. In rare cases the antivirus/antispyware/security programs can cause this error.

BCCode: 113 0x00000113 <-- read this link

The dxgkrnl has encountered an unexpected fatal error.



==================================================

This utility makes it easy to see which versions are loaded :

Run DriverView - set VIEW to Hide Microsoft drivers - update those without

Dump in their names (and update BIOS and chipset drivers).

DriverView - Free - utility displays the list of all device drivers currently loaded

on your system. For each driver in the list, additional useful information is

displayed: load address of the driver, description, version, product name,

company that created the driver, and more.

DriverView: Loaded Windows Drivers List



For Drivers check System Maker as fallbacks and Device Maker's which are the

most current. Right Click the Start Button - Device Manager - Display Adapter -

write down the make and complete model of your video adapter - double click

- Driver's tab - write down the version info. Now click UPdate Driver (this may not

do anything as MS is far behind certifying drivers) - then Right Click - Uninstall -

REBOOT this will refresh the driver stack.

Repeat that for Network - Network Card (NIC), Wifi, Sound, Mouse and Keyboard

if 3rd party with their own software and drivers and any other major device drivers

you have.

Now go to System Maker's site (Dell, HP, Toshiba as examples) (as rollback) and

then Device Maker's site (Realtek, Intel, Nvidia, ATI as examples) and get their

latest versions. (Look for BIOS, Chipset, and software updates at System Maker's

site while there.)

Download - SAVE - go to where you put them - Right Click - RUN AD ADMIN -

REBOOT after each installation.

Always check in Device Manager - Drivers tab to be sure the version you are

installing actually shows up. This is because some drivers rollback before the

latest is installed (sound drivers particularly do this) so install a driver - reboot

- check to be sure it is installed and repeat as needed.

Repeat at Device Makers - BTW at Device Makers DO NOT RUN THEIR SCANNER -

check manually by model.

Manually look at manufacturer's sites for drivers - and Device Maker's sites.

How to Find and Download Drivers
====================================================

Memory tests do not catch all errors such as mismatched memory (possible even

for sticks that appear to be identical) and when faster memory is placed in the system

behind slower memory. So it is best to also swap sticks in and out to check for

those even if all memory tests fail to show a problem.

To test RAM check here - let it run 4+ hours or so. <-- best method

www.memtest.org

MemTestX86 - Test RAM With

MemTest86+ - Test RAM

For the Windows Memory Diagnostic Tool.

Type in Cortana's search box -> Windows Memory Diagnostics

........find at top of the list - click it. in Windows 8/8.1/10 the name is "Windows Memory

Diagnostic".



================================================

After doing ALL the updates you can, and if the issue continues, then run

DriverVerifier.

Driver Verifier can help find some BSOD issues :

Using Driver Verifier to identify issues with Windows drivers for advanced users

http://support.microsoft.com/kb/244617

How To Troubleshoot Driver Problems in Windows Vista or 7. (8/8.1 and 10

are essentially the same).

http://www.winvistaclub.com/t79.html

Using Driver Verifier

https://msdn.microsoft.com/en-us/li...448(v=vs.85).aspx?f=255&MSPPError=-2147217396

WINKEY + X - RUN - type in -> verifier /reset hit enter to disable

If Driver Verifier creates a minidump upload it and post the link here so we can

analyze it.

Hope this helps.

--------------------------------------------------------------------------------------------

Rob Brown -
Microsoft MVP <- profile - Windows and Devices for IT : Bicycle - Mark Twain said it right.

 

BSOD when running on battery - driver_power_state_failure

It took a while, but I finally found a new battery in my mail!

I installed it an... unfortunately the same BSOD occurred. (driver_power_state_failure)

Could this somehow be related to the wireless network card / the failing bluetooth? (Yeah, that still fails, even while running on 'high perfomance' and plugged in)

 

Nvlddmkm is the Nvidia display driver, fortunately there is a driver update available.
Please uninstall everything of Nvidia using Display Driver Uninstaller and install new drivers from HP. Be sure the clean install box is checked and only install the Graphics driver and the PhysX driver.
Attachment 71319

 

Well I followed the directions and uninstalled my driver in safe mode then reinstalled a freshly downloaded driver. I am trying it out now to see if it works. There is one problem however, my screen "dim" option is darkened out (when I click on the "battery" icon on my toolbar. Even in power options there is no slider to control screen brightness now.

Edit: I'll start a different thread about this since its not really BSOD related.