Updated my new Predator 572 laptop to win10 1803- all okay on ac power- crashes on battery

My older hp elitebooks updated okay to win10 1803 and are fine on ac or battery. My new Predator g3 572 is FINE all day as long as I'm on ac power. For the past two nights, I go to battery power only and within 3 minutes or so of boot up (not on internet at night), movies freeze, files freeze, and eventually, ms bsod shows critical process died, and then reboots. After observing this two or three times in a row, a "no bootable media" message came up... so I called it a night.

Today...again on ac power... 1803 and the computer are running great. My Acer/Intel drivers are all up to date (I checked yesterday), I verified my power plans are where I usually have them (still not sure if minimum processor state on battery should be set to 5%.. but that's where I have it at the moment)

When on battery, computer will freeze after 3-4 minutes no matter whether I have power saver/balanced/or high power selected.

Defender shows no viruses.... but if viruses were the culprit, seems I'd have trouble with the computer while on ac. Isn't a chrome problem (that I can imagine) because I'm on chrome all day long on ac and everything is fine. At night with the crashes, I'm not even connected to an internet signal.

My bios is at the current 3.11 or whatever. Not that that should make a diff.

Strange isn't it? The problem is only when on battery power. The little Acer battery-checker routine says the battery is fine... and of course the system is only 4 weeks old.

Any tips? If not, I may simply restore a Macrium image of the system I made about a week ago that will take me back to 17** or whatever we were on as of a week ago. Or maybe I'll call Acer Predator support

Accepted answers

All comments

IronFly

download this tool, whocrashed:

http://www.resplendence.com/download/whocrashedSetup.exe

before running it, browse to C:\windows\minidump

delete all files apart the first 2-3 files (newest)

then install whocrashed and run it

click on Analyze

report here the result.

DosWasBest

Thanks. I'll have to locate what you suggested. There is no minidump dir in my windows dir (and I have all folders visible). I looked up what I could in startup and recovery and all that is there at the moment is %SystemRoot%\Minidump. Which I don't know how to find. I just changed the box above that to do small dump 256k instead of Automatic. In case on the next crash, that is a helpful setting.

As I don't yet see how to access the dmp file(s), should I go ahead with downloading whocrashed and see what it comes up with?

IronFly

if minidump folder doesn't exist, whocrashed can't be helpful.
the other way is to check under windows Event viewer about any error or warning messages at the time/date of freeze/crashes.

windows logo + x key
Event viewer
Windows logs / have a look at System and Application

DosWasBest

Looking through the event viewer now. Errors, warnings, and critical msgs relate to the unplanned shutdowns. I'm going to clear all these logs, go to battery power-only over the next couple of hours and see what new events show.

On this minidump thing, I still can't figure out where exactly on the C drive that %SystemRoot%\MEMORY.DMP is supposed to be sitting. I'm showing all hidden files and there is no trace of a .dmp file anywhere on the root drive or how I'm supposed to read/interpret it once I ever do find it.

Perhaps the dmp file already erased itself. When I go back on battery power and get a freeze and bsod, I'll look again for the resulting dmp file somewhere.

Thanks for the tips so far.

DosWasBest

I'm also watching the general news about win10 1803 freezes. Maybe I'll get lucky and the May 8 MS hotfix will also just happen to cure whatever's going on with my freezes. Although mine seem strange being only on battery power.

IronFly

don't worry about minidumps at the moment, since they will be written only if your system reboot unexpectedly or gives a BSOD.

leong2699

This is also happening to me.
The only solution so far is to wait for 8th may hotfix, if not revert back to 1709.

Queen6

Predator 17 No crash on battery:
G9-793, 7700HQ, 32Gb RAM, GTX 1070, Bios 1.13, CPU undervolted with ThrottleStop (-133mV)

DosWasBest

I finally decided to stop trying to nail the problem down. I hit the revert to 1709 button last night and ever since, the laptop is just fine on ac and/or battery. I'll try 1803 again maybe in a month or so.

Seismic

This could be the current issue, I had to roll back to 1709 myself.
https://communities.intel.com/thread/125196

DosWasBest

Seismic said:

This could be the current issue, I had to roll back to 1709 myself.
https://communities.intel.com/thread/125196

That's interesting as on several of my reboots after freezes on 1803, messages came up during boot "no boot media" or something. Which at the time, was unnerving. Further rebooting got around that message. Some of the event viewer messages before 1803 freezes mentioned losing contact with something or other... and subsequent microsoft onscreen messages of "looks like your pc needs to restart; hold on while we write the error info......" would never go past 0%. Which would make sense if windows lost contact with the C drive via the freeze. Which would also maybe explain why I never had a dmp file written on the crashes.

My C drive is an intel ssdpekkw256G7, so I guess that puts me in the 600 series eh?

Oh well. I'm on 1709 for now and will just stay there.

The strange thing is that my 1803 freezes never occurred on ac power. Only when I was on battery. No idea why that may be, but gremlins are gremlins.

DosWasBest

After reverting to 1709 on my g3-572 win10 Home system a couple of times over the past week, of course Windows update wanted to reinstall 1803 at various times. Ugh, constant revert. Dunno why Acer uses Win10 Home instead of Pro. Although even Pro has limitations on delaying updates.

Anyway, after reading the above ssd drive pr situation earlier today.....a fairly nice thing (considering everything) happened a few minutes ago.

1803 came through once again on Windows update and tried reinstalling itself. No surprise. But this time, after it downloaded and then tried installing, a new message appeared saying "can not update, your computer hardware is incompatible with this update". Voila, 1803 goes away.

MS is right on top of blocking 1803 to these Intel 600 series ssd C drives (like in my G3-572).

That's good news for me as the constant reverting to 1709 was getting to be a hassle.

So on to the next thing, which is MS and Intel working out what the deal is with the incompatibilities on these drives.

Once they work that out, I guess 1803 will successfully come through.

Red-Sand

I've seen this issue alot recently and apparently the fix is to go to Acers driver download page and install the Intel VGA/Chipset/ACHI drivers.

If an error shows up from nvidia when your trying to install them, then uninstall nvidias driver and try to install again and you won't crash on battery.

DosWasBest

Red-Sand said:

I've seen this issue alot recently and apparently the fix is to go to Acers driver download page and install the Intel VGA/Chipset/ACHI drivers.

If an error shows up from nvidia when your trying to install them, then uninstall nvidias driver and try to install again and you won't crash on battery.

Thanks for the info. I have noticed posts with program hang problems etc where a re-download of drivers may have been helpful, but I'm pretty well convinced my problem is the incompatibility of my intel ssdpekkw256g7 600series C drive with 1803. At least MS is now blocking 1803 from downloading onto my g3-572 for what appears to be, that reason.

I'll just stick with 1709 until MS and Intel figure things out and send through a working 1803. Or at least, I'll HOPE 1803 works next time MS sends it down the pipeline