|
|
Why hasn't it been deleted yet?
|
|
|
|
|
I would only worry if it was from a Nigerian Prince... 
<sig notetoself="think of a better signature">
<first>Jim</first> <last>Meadors</last>
</sig>
|
|
|
|
|
AIUI, a chess engine uses some sort of minmax algorithm, but a minmax algorithm would search for a path that guarantees the least worst option - and since a chess engine assigns integral points for pieces, it seems that the score should be some integral value. What's going on here? (I presume that there must be a few folks here that are in both the set of chess players and the set of folks who do artificial intelligence.)
|
|
|
|
|
Most of the time it is just a little guy in the box that does the moves 
|
|
|
|
|
Usually a Mobility score is also part of the equation, with a non-integral weight. If you're interpolating between game phases (using different scoring for the opening, midgame and endgame and interpolating to avoid sharp discontinuities at phase transitions) of course many scores will not be integral.
|
|
|
|
|
I don't understand the question. Nor the appeal of the game for that matter.
|
|
|
|
|
(I'm going to use the Stockfish engine as example. I don't know how other engines do this, but it could be the same.)
Short answer: Stockfish does output an integral score but your chess interface divides it by 100.
Long answer:
Internally, Stockfish does have an integral value as score. This value is rather big (looking at just the piece values[^], the value of a pawn in the midgame is 171 and the value of the queen is 2526) and it's also not just the piece values, there is also a bunch of bonuses and penalties[^] to adjust this value.
When Stockfish tells you how it evaluates a position, it won't give you its internal value, but it will give you the score in "centipawns"[^]. (1 pawn = 100 centipawns) So if Stockfish's raw output says "200", it means that you have an advantage of 2 pawns.
But even that number is still provided by Stockfish as an integer. Your chess interface, however, may decide to show you the evaluation in pawns rather than centipawns, thus dividing Stockfish's centipawn evaluation by 100.
The quick brown ProgramFOX jumps right over the Lazy<Dog>.
|
|
|
|
|
<EDIT>
Moved to Hardware forum ==> Win 10 Crash again (captured DMP file) - hw - Hardware & Devices Discussion Boards[^]
</EDIT>
I originally posted how my Win10 i7, 8GB laptop had crashed and restarted itself here at:
Seriously Win10 What's With the Restart? - The Lounge[^]
@randor had mentioned that I could take a look at the dump file to get more info.
However, at the time the DMP file got delete so I was unable to go further.
My machine rebooted and this time I still have the 997MB DMP file (which is crazy) and I opened it up with WinDbg.
Here's what I see...
I know it's a lot of info but just thought it might be interesting.
You can see that it looks like it is the PCI.sys driver that failed.
Reason I'm Mentioning This
I mention this out of interest and to see if anyone else has had a situation with their Win10 PC rebooting itself like this while not in use.
Just a discussion, not looking for an answer. I know better than to believe we would ever be able to run a cryptic thing like this down. This is the Way of Windows, a magical land where the magic often fails. 
DRIVER_POWER_STATE_FAILURE (9f)
A driver has failed to complete a power IRP within a specific time.
Arguments:
Arg1: 0000000000000004, The power transition timed out waiting to synchronize with the Pnp subsystem.
Arg2: 000000000000012c, Timeout in seconds.
Arg3: ffffe680b6184040, The thread currently holding on to the Pnp lock.
Arg4: ffff87012fc7d910, nt!TRIAGE_9F_PNP on Win7 and higher
Debugging Details:
------------------
Implicit thread is now ffffe680`b6184040
KEY_VALUES_STRING: 1
TIMELINE_ANALYSIS: 1
DUMP_CLASS: 1
DUMP_QUALIFIER: 401
BUILD_VERSION_STRING: 16299.15.amd64fre.rs3_release.170928-1534
SYSTEM_MANUFACTURER: TOSHIBA
SYSTEM_PRODUCT_NAME: Satellite S55t-B
SYSTEM_SKU: INVALID
SYSTEM_VERSION: PSPRDU-008004
BIOS_VENDOR: INSYDE Corp.
BIOS_VERSION: 1.40
BIOS_DATE: 05/13/2014
BASEBOARD_MANUFACTURER: Type2 - Board Vendor Name1
BASEBOARD_PRODUCT: Type2 - Board Product Name1
BASEBOARD_VERSION: Type2 - Board Version
DUMP_TYPE: 1
BUGCHECK_P1: 4
BUGCHECK_P2: 12c
BUGCHECK_P3: ffffe680b6184040
BUGCHECK_P4: ffff87012fc7d910
DRVPOWERSTATE_SUBCODE: 4
IMAGE_NAME: pci.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 43aeedb9
MODULE_NAME: pci
FAULTING_MODULE: fffff80b9ac70000 pci
CPU_COUNT: 8
CPU_MHZ: 9be
CPU_VENDOR: GenuineIntel
CPU_FAMILY: 6
CPU_MODEL: 3c
CPU_STEPPING: 3
CPU_MICROCODE: 6,3c,3,0 (F,M,S,R) SIG: 1E'00000000 (cache) 1E'00000000 (init)
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXPNP: 1 (!blackboxpnp)
DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
BUGCHECK_STR: 0x9F
PROCESS_NAME: System
CURRENT_IRQL: 2
ANALYSIS_SESSION_HOST: MOBISILVER8
ANALYSIS_SESSION_TIME: 03-17-2018 12:04:23.0467
ANALYSIS_VERSION: 10.0.17074.1002 amd64fre
STACK_TEXT:
ffff8701`2fc7d8d8 fffff800`3608fbc4 : 00000000`0000009f 00000000`00000004 00000000`0000012c ffffe680`b6184040 : nt!KeBugCheckEx
ffff8701`2fc7d8e0 fffff800`362c6916 : ffff8701`2fc7db10 ffffd680`92cce180 ffffd680`92cce180 000000e6`7551f100 : nt!PnpBugcheckPowerTimeout+0x60
ffff8701`2fc7d940 fffff800`35f58923 : ffffd680`92cce180 00000000`00000000 ffff8701`2fc7db18 00000000`00000000 : nt!PopBuildDeviceNotifyListWatchdog+0x16
ffff8701`2fc7d970 fffff800`35f599bd : 00000000`00000018 00000000`00000000 00000000`00252ac4 ffffd680`92cce180 : nt!KiProcessExpiredTimerList+0x153
ffff8701`2fc7da60 fffff800`3600cdfa : 00000000`00000001 ffffd680`92cce180 00000000`00000000 ffffd680`92cdc200 : nt!KiRetireDpcList+0x43d
ffff8701`2fc7dc60 00000000`00000000 : ffff8701`2fc7e000 ffff8701`2fc78000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x5a
FOLLOWUP_NAME: MachineOwner
IMAGE_VERSION: 10.0.16299.251
STACK_COMMAND: .thread ; .cxr ; kb
FAILURE_BUCKET_ID: 0x9F_4_Netwbw02_IMAGE_pci.sys
BUCKET_ID: 0x9F_4_Netwbw02_IMAGE_pci.sys
PRIMARY_PROBLEM_CLASS: 0x9F_4_Netwbw02_IMAGE_pci.sys
TARGET_TIME: 2018-03-15T05:11:51.000Z
OSBUILD: 16299
OSSERVICEPACK: 0
SERVICEPACK_NUMBER: 0
OS_REVISION: 0
SUITE_MASK: 784
PRODUCT_TYPE: 1
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
OSEDITION: Windows 10 WinNt TerminalServer SingleUserTS Personal
OS_LOCALE:
USER_LCID: 0
OSBUILD_TIMESTAMP: 2018-03-01 00:36:55
BUILDDATESTAMP_STR: 170928-1534
BUILDLAB_STR: rs3_release
BUILDOSVER_STR: 10.0.16299.15.amd64fre.rs3_release.170928-1534
ANALYSIS_SESSION_ELAPSED_TIME: 620
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:0x9f_4_netwbw02_image_pci.sys
FAILURE_ID_HASH: {6709efd6-2555-4107-d407-a72ec07f114d}
Followup: MachineOwner
modified 17-Mar-18 13:38pm.
|
|
|
|
|
Did you try rebooting?
I have never had problems with Windows 10 crashing, but I am not running it on a laptop, so I don't have any power policies enabled - I am guessing that your crash is related to Power Management given the first line in your dump.
BTW, I have worked with application crash dumps that were larger than 1GB, so I don't think 997MB for the OS crash dump is surprising.
"When you don't know what you're doing it's best to do it quickly" - Jase #DuckDynasty
|
|
|
|
|
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. ![Beer | [beer]](https://codeproject.global.ssl.fastly.net/script/Forums/Images/beer.gif)
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
|
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
