|
SoMad wrote: am guessing that your crash is related to Power Management given the first line in your dump
Yeah, it does look like that. Just curious if this is a Win10 thing or related to my H/W.
Of course this never happened in the past (only since recent updates) and never happened under Win8.1.
SoMad wrote: I don't think 997MB for the OS crash dump is surprising
I agree, as a developer it is not surprising. As a consumer, it's a bit surprising.
Also, with a dump with that much info I would think their might be an AI-type of process that Microsoft would provide that would give me a better idea of how to resolve.
Such, as:
Microsoft Debug AI: "PCI.sys has crashed due to conflict with Power settings driver. Please update power settings driver"
|
|
|
|
|
Take it to the hardware forum and I will answer you.
|
|
|
|
|
I've been a member here a long while and didn't even know there was such a forum.
I'll copy it over. thx.
|
|
|
|
|
My wife's older all-in-one started doing this a while back. In her case, it would bring up the sad-face bsod which mentioned a power-state-failure error. I seem to have fixed it by changing the power plan from the default to a different setting. Good luck!
"Go forth into the source" - Neal Morse
|
|
|
|
|
The problem I've been having is that I put the system to sleep, but I when I try to wake it up, it doesn't revive, so I have to hard boot it up.
|
|
|
|
|
Well,
raddevus wrote: I know better than to believe we would ever be able to run a cryptic thing like this down.
Here is the Intel Wireless Networking[^] forum.
Go over there with your ranting and tell them that your Intel® Dual Band Wireless-AC 3160[^] driver is crashing because NETwbw02.sys is holding a PNP lock causing a power IRP timeout... bugcheck 0x9f.
Your Intel wireless driver appears to be failing during this process:
Power IRPs for the System[^]
Btw looks like Intel released a new version on 06-Feb-2018 so you might want to make sure you've got the latest device driver.
Best Wishes,
-David Delaune
Edit:
I'm going to start charging you for these debugging sessions. You owe me 2 beers.
modified 18-Mar-18 4:41am.
|
|
|
|
|
Thanks very much.
|
|
|
|
|
Hi,
You are welcome. Now you see why the DMP file is automatically cleaned up by a daily script. It's gigantic.
Btw there are others complaining about similar blue screen bugs on the Intel wireless forum:
Built-in Dual Band Wireless-AC 3168 causing Bluescreens on my Ryzen desktop?[^] Note that I see one of them point out a DPC_WATCHDOG_VIOLATION which is in the same class of bugs as your problem.
This is why you should always go for the WHQL Microsoft signed device drivers. It means that the device driver has passed a huge series of tests[^] that confirm the driver is compatible with Windows.
At least one of the following statements is true of any device driver not WHQL signed:
1.) The device driver was not submitted to WHQL[^].
or
2.) The driver was submitted and failed the test.
Best Wishes,
-David Delaune
|
|
|
|
|
That is really great and valuable additional information on the drivers.
I may roll mine back (since it is currently the latest version) and see if it helps.
Thanks again
|
|
|
|
|
family safe
But, which is the programmer ? [^]
«... thank the gods that they have made you superior to those events which they have not placed within your own control, rendered you accountable for that only which is within you own control For what, then, have they made you responsible? For that which is alone in your own power—a right use of things as they appear.» Discourses of Epictetus Book I:12
|
|
|
|
|
Thanks Bill, I needed that one after an extremely long week. It brought back memories of the Elephant Nature Park; which I visited on October 19, 2016. There were no babies that day, just jumbos and heaps of fun!
|
|
|
|
|
Nice one !
|
|
|
|
|
|
I would have laughed at that except it is so close to my life it hurts.
Never underestimate the power of human stupidity
RAH
|
|
|
|
|
|
Thanks, Rajesh-ji, I'm really enjoying watching !
«... thank the gods that they have made you superior to those events which they have not placed within your own control, rendered you accountable for that only which is within you own control For what, then, have they made you responsible? For that which is alone in your own power—a right use of things as they appear.» Discourses of Epictetus Book I:12
|
|
|
|
|
With two sign-up buttons in the top-right; I wouldn't spend anything there
Bastard Programmer from Hell
If you can't read my code, try converting it here[^]
"If you just follow the bacon Eddy, wherever it leads you, then you won't have to think about politics." -- Some Bell.
|
|
|
|
|
I just learned today that attribute names, when added programmatically through the DOM, are always converted to lowercase. Explains why attributes look like stroke-width instead of strokeWidth .
Latest Article - Contextual Data Explorer
Learning to code with python is like learning to swim with those little arm floaties. It gives you undeserved confidence and will eventually drown you. - DangerBunny
Artificial intelligence is the only remedy for natural stupidity. - CDP1802
|
|
|
|
|
I'm so glad I work with services and databases.
|
|
|
|
|
Me-too have my hands full getting to grips with NHibernate at the moment ...
|
|
|
|
|
Suddenly Javascript doesn't seem so bad.
|
|
|
|
|
Node.js for the win!
|
|
|
|
|
Actually your browser will do it, not just JavaScript. XHTML 1.0: The Extensible HyperText Markup Language (Second Edition)[^]
this HTML
<html><body><div strokeWidth="10">test</div></body></html>
in chrome, firefox, and IE will render as strokewidth.
Everyone is born right handed. Only the strongest overcome it.
Fight for left-handed rights and hand equality.
|
|
|
|
|
Are you using data- attributes?
To get a data attribute through the dataset object, get the property by the part of the attribute name after data- (note that dashes are converted to camelCase).
So element.dataset.strokeWidth in JS corresponds to the data-stroke-width attribute.
"These people looked deep within my soul and assigned me a number based on the order in which I joined."
- Homer
|
|
|
|
|