08-11-2018 08:22 PM
I've been having the BSOD "Driver Power State Failure" error after wakeup from sleep.
Already have the latest updates form Windows and Lenovo Vantage.
Recently upgraded Windows Home to Windows Pro via the upgrade key option in settings.
Maybe someone can look at my minidump files and see what drivers are causing the issue?
Any help is appreciated, the machine is not even a week old.
Solved! Go to Solution.
08-11-2018 08:47 PM
Can you zip up a couple of the minidumps and attach them to a reply, or if the are too large even compressed, post them on One Drive or Dropbox etc?
There is also this online crash dump analyzer that will allow you to view the the minidumps tht might interest you.
OSR's Instant Online Crash Analysis
08-11-2018 09:42 PM - edited 08-11-2018 09:44 PM
Thank you for the quick response, you can find the minidump files from the link below.
I didn't even know an online tool existed. I did try this method, however, I have no idea what to look for
Link: Google Drive
08-12-2018 09:10 PM
I appears to be caused by a Sierra Wireless Incorporated USB NDIS Miniport Driver (the actual driver file is having a problem is swg3kmbb00.sys) not wanting to sleep properly, thus you have a BSOD when you resume.
I do not see any drivers for the Sierra Wireless cards on Lenovo's website for the ThinkPad X1 Carbon 6th, so the first thing I would do is check with your wireless provider to see if they know of the problem and/or have an updated driver, but in the interim you could try the following.
If it is an external USB Card, unplug it and then test the sleep/resume function to see if that is indeed the problem
If it is an internal card,
Best of luck,
12-14-2018 12:06 AM
just bought X1 Extreme and on the 3rd day its gone in bsod with the same type.
Can you please help to indetify the driver that coused crash?
Here is the minidump
07-10-2019 04:00 AM
On a Lenovo P51, I have more times had the BSOD DRIVER POWER STATE FAILURE.
The latest dump attached.
How can these minidumps be viewed - or can you analyze it?
Is there another way to find out, which driver is failing? Windows logfiles?