As our customers (we are selling Engineering software) are waiting since February 2016 for a solution, I kindly ask you how long will it take to release a fixed driver?
Currently they can´t print any PDF > there is always that Blue Screen.
2 of 2 people found this helpful
This issue seems to be a regression in Windows 10 and not in our driver. We can reproduce the same behavior on Nvidia cards.
We are continuing to investigate to see if we can find a workaround for you.
are there any news available?
This issue is a serious one for all our customers with AMD and WIN10.
For now we tell them to replace the AMD graphic card an buy a NVIDIA!!!
So please try to find a workaround asap!
Can you let us know which Nvidia card you have tested where this issue is working with Win10 ?
This will help us eliminate Win10 as the root cause. Our testing so far shows Nvidia cards failing with your test application.
using our software + Nvidia + WIN10 and (direct printing ) doesn´t force WIN10 to crash.
I´m using GTX 650 with driver version 368.81.
If I try it with the test source code, I can get WIN10 to crash. So there are some differences between AMD and NVIDIA regarding our software.
AMD + WIN10 > direct print from inside our software = CRASH
NVIDIA + WIN10 > direct print from inside our software = NO CRASH
1 of 1 people found this helpful
We looked into this issue and most likely it is a Windows 10 regression issue. First of all, Win7 and latest Windows RedStone are OK. Only Windows 10 (10240, 10586) has this issue. We uses NV's board and saw same problem with Windows 10 (10240, 10586). From the kernel debug output we got.
2: kd:x86> k
# ChildEBP RetAddr
00 00efe2cc 6eb2e6fe GDI32!NtGdiDdDDIOpenAdapterFromHdc+0xc
01 00efe774 6eb2f0c9 OPENGL32!EscapeCB+0x15e
02 00efeb68 6eb3d139 OPENGL32!wglCbGetAdapterLuid+0x239
03 00efeb80 6eb3defc OPENGL32!wglNumHardwareFormats+0x12
04 00efec30 6eb3d485 OPENGL32!wglDescribePixelFormat+0x10c
05 00efecc0 74c27b19 OPENGL32!wglChoosePixelFormat+0x55
06 00efece0 009f75ec GDI32!ChoosePixelFormat+0x39
WARNING: Stack unwind information not available. Following frames may be wrong.
07 00efed40 6bb83dcd Test3+0x75ec
2: kd:x86> .cxr 0xffffd001f4661390
eax=c000000d ebx=ffffd001 ecx=00000000 edx=00ef0000 esi=f4661ec0 edi=ffffd001
eip=0000000b esp=00000000 ebp=00000000 iopl=0 nv up di pl nz na po nc
cs=0000 ss=0018 ds=1db0 es=f901 fs=f030 gs=0000 efl=00000000
00000000`0000000b ?? ???
Looks like the process's stack is corrupted and the OGL driver is not loaded yet. So the suggested solution is to update your Windows 10 to the latest RedStone release (14393).
BTW, at the very beginning of this thread, the OS information is as follows. It is quite confusing as 6.2.9200 should be the version number of Windows 8. Why the caption tells it is Windows 10? How did you get the OS version information?
Caption: Microsoft Windows 10 Pro
OS Version: Microsoft Windows NT 6.2.9200.0
Please feel free to tell us if you observe different result from ours.
>BTW, at the very beginning of this thread, the OS information is as follows. It is quite confusing as 6.2.9200 should be the version number of Windows 8.
>Why the caption tells it is Windows 10? How did you get the OS version information?
I'm sorry, that's my fault. Caption is correct, version is incorrect. I have fixed it already.
2 of 2 people found this helpful
I didn't see the update. The correct OS version of Windows 10 should be something like 10.0.xxxxx. The "xxxxx" is 10240 or 10586.
Did you have chance to test RedStone (10.0.14393)?
brettsr is my colleague. The info about the version he posted in February is wrong. The test was done on WIN10. (10.0.10586)
As you recommended in your post from 08.08.16 11:27 we have installed now WIN10 redstone update (10.0.14393) and with brettsr tool WIN10 did not crash anymore.
As I have only NVIDIA card installed, we now wait for the test results (will be done in our developement department on WIN10 Redstone + AMD).
It was a very helpful hint from you, to install the fresh released WIN10 update.